Restrict the Variety of Concurrent Classes in Salesforce

Final Up to date on October 10, 2022 by Rakesh Gupta

Massive Concept or Enduring Query:

• Learn how to restrict the variety of concurrent periods for a person? 

Goals:

After studying this weblog, you’ll have the ability to:

• Perceive concurrent periods and establish them utilizing Stream
• Restrict the Variety of Concurrent Classes with Login Flows
• Use LoginFlow_ForceLogout variable
• Work with Get Information, Delete Information, Project, and Display Components
• And way more

Rachel Gillett is working as a Junior Developer at Gurukul on Cloud (GoC). She has acquired the next requirement from the administration:

1. Implement the variety of concurrent periods per person to at least one.
2. Present a capability to kill their earlier session and begin a brand new session when login-In.

👉 Demo

Automation Champion Strategy (I-do):

Person Concurrent periods confer with the variety of interactive, UI-based periods a person person can have open and lively per person account. Customers could create a number of person periods as they log in to an account from completely different browser varieties and units. 

To boost the safety of the general Salesforce org, an administrator can implement a Login Stream or use the Transaction Safety Coverage (Requires Salesforce Defend or Salesforce Occasion Monitoring add-on subscriptions) to restrict the variety of concurrent periods for a person.

There are a number of doable options for the above enterprise situation. We’ll use Display Stream and Login Stream to resolve the requirement.

Earlier than we proceed additional, allow us to perceive the traits of an AuthSession object – It represents a person person session in your group.

Earlier than discussing the answer, let me present you a diagram of a Course of Stream at a excessive stage. Please spend a couple of minutes going via the next Stream diagram and understanding it.

Let’s start constructing this automation course of.

Guided Follow (We-do):

There are 7 steps to resolve Rachel’s enterprise requirement utilizing Display Stream and Login Stream. We should:

1. Outline movement properties for display screen movement
2. Add a Get Information factor to seek out the logged-in person’s periods
3. Add an Project factor to get the rely of logged-in person’s periods
4. Add a Determination factor to verify whether or not the rely is bigger than 1 or not
5. Add a Display factor to show the message and the choice to kill different periods 
6. Add a Determination factor to verify if the person needs to kill different periods
   1. If the choice is chosen:
      1. Add a Get Information factor to seek out the logged-in person’s present session
      2. Add a Delete Information factor to kill different periods 
   2. If the choice NOT is chosen:
      1. Add an Project factor to drive logout person 
7. Configure Login Stream for Salesforce Platform licensed customers  

👉 Think about using customized metadata varieties to make the variety of present periods configurable. 

Step 1: Outline Stream Properties

1. Click on Setup.
2. Within the Fast Discover field, sort Flows.
3. Choose Flows, then click on on the New Stream.
4. Choose the Display Stream choice and click on on Create and configure the movement. 
5. It’ll open the movement designer for you.

Step 2: Including a Get Document Component to Discover the Logged-In Person’s Classes 

The subsequent step is utilizing the AuthSession object to seek out the logged-in person’s periods. 

1. On Stream Designer, click on on the +icon and choose the Get Information factor.
2. Enter a reputation within the Label subject; the API Identify will auto-populate.
3. Choose the Auth Session object from the dropdown checklist.
4. Choose All Situations Are Met (AND). 
5. Set Filter Situations
   1. Row 1:
      1. Area: UserId
      2. Operator: Equals
      3. Worth: {!$Person.Id}
   2. Click on Add Situation
   3. Row 2:
      1. Area: ParentId
      2. Operator: Is Null
      3. Worth: {!$GlobalConstant.True}
   4. Click on Add Situation
   5. Row 3:
      1. Area: SessionType
      2. Operator: Does Not Equal
      3. Worth: TempUIFrontdoor
   6. Click on Add Situation
   7. Row 4:
      1. Area: SessionType
      2. Operator: Does Not Equal
      3. Worth: InternalServiceCall
6. How Many Information to Retailer:
   1. Choose All document
7. Learn how to Retailer Document Knowledge:
   1. Select the choice to Mechanically retailer all fields. 
8. Click on Accomplished.

Step 3: Including an Project Component to Discover the Depend of Logged-In Person’s Session 

The subsequent step is to get the logged-in person’s session rely. For this, we’ll use an Project factor. 

1. Create a Quantity Variable varN_SessionCount to retailer the rely.
2. On Stream Designer, click on on the +icon and choose the Project factor.
3. Enter a reputation within the Label subject; the API Identify will auto-populate.
4. Set Variable Values
   1. Row 1:
      1. Area: {!varN_SessionCount}
      2. Operator: Equals
      3. Worth: {!Get_Sessions}
5. Click on Accomplished.

Step 4: Add Determination Component to Verify Whether the Session Depend is Larger than 1 or Not

Now we’ll use the Determination factor to verify the quantity variable from step 3 to seek out if the rely is bigger than 1 or not.

1. On Stream Designer, click on on the +icon and choose the Determination factor.
2. Enter a reputation within the Label subject; the API Identify will auto-populate.
3. Underneath End result Particulars, enter the Label the API Identify will auto-populate.
4. Situation Necessities to Execute End result: All Situations Are Met (AND)
   1. Row 1:
      1. Useful resource: {!varN_SessionCount}
      2. Operator: Larger Than
      3. Worth: 1
5. Click on Accomplished.

Step 5: Add a Display Component to Show the Message and Choice to Kill Different Classes 

1. Underneath Block Node, click on on the +icon and choose the Display factor on Stream Designer.
2. Enter the next data:
   1. Enter Label the API Identify will auto-populate.
3. Take a look at the video for step-by-step directions and a few suggestions.

Step 6: Add Determination Component to Verify If the Person Desires to Kill the Different Classes or Not

Now we’ll use the Determination factor to verify if the person has chosen Signal out all different internet periods checkbox in step 5 or not.

1. On Stream Designer, click on on the +icon and choose the Determination factor.
2. Enter a reputation within the Label subject; the API Identify will auto-populate.
3. Underneath End result Particulars, enter the Label the API Identify will auto-populate.
4. Situation Necessities to Execute End result: All Situations Are Met (AND)
   1. Row 1:
      1. Useful resource: {!Sign_out_all_other_web_sessions}
      2. Operator: Equals
      3. Worth: {!$GlobalConstant.True}
5. Click on Accomplished.

Step 6.1.1: Including a Get Document Component to Discover the Logged-In Person’s Present Session 

The subsequent step is utilizing the AuthSession object to seek out the logged-in person’s present session. 

1. Underneath Sure Node, click on on the +icon and choose the Get Information factor on Stream Designer.
2. Enter a reputation within the Label subject; the API Identify will auto-populate.
3. Choose the Auth Session object from the dropdown checklist.
4. Choose All Situations Are Met (AND). 
5. Set Filter Situations
   1. Row 1:
      1. Area: UserId
      2. Operator: Equals
      3. Worth: {!$Person.Id}
   2. Click on Add Situation
   3. Row 2:
      1. Area: ParentId
      2. Operator: Is Null
      3. Worth: {!$GlobalConstant.True}
   4. Click on Add Situation
   5. Row 3:
      1. Area: SessionType
      2. Operator: Equals
      3. Worth: UI
6. Kind Auth Session Information
   1. Kind Order: Descending
   2. Kind By: CreatedDate
7. How Many Information to Retailer:
   1. Choose Solely the primary document
8. Learn how to Retailer Document Knowledge:
   1. Select the choice to Mechanically retailer all fields. 
9. Click on Accomplished.

Step 6.1.2: Add a Delete Information Component to Kill Different Classes 

1. On Stream Designer, click on the +icon and choose the Delete Information factor.
2. Enter a reputation within the Label subject; the API Identify will auto-populate.
3. For Learn how to Discover Information to Delete, choose Specify situations.
4. Choose the Auth Session object from the dropdown checklist.
5. Set Filter Situations
   1. Row 1:
      1. Area: UserId
      2. Operator: Equals
      3. Worth: {!$Person.Id}
   2. Click on Add Situation
   3. Row 2:
      1. Area: ParentId
      2. Operator: Does Not Equal
      3. Worth: {!Get_Most_Recent_Session.Id}
   4. Click on Add Situation
   5. Row 3:
      1. Area: Id
      2. Operator: Does Not Equal
      3. Worth: {!Get_Most_Recent_Session.Id}
6. Click on Accomplished.

Step 6.2.1: Including an Project Component to Pressure Logout Person

The subsequent step is to kill the person’s present session forcefully. For this, we’ll use an Project factor. 

1. Create a Boolean Variable LoginFlow_ForceLogout. When this variable is about to trueThe person is instantly logged out.
2. Underneath No Node, click on on the +icon and choose the Project factor on Stream Designer.
3. Enter a reputation within the Label subject; the API Identify will auto-populate.
4. Set Variable Values
   1. Row 1:
      1. Area: {!LoginFlow_ForceLogout}
      2. Operator: Equals
      3. Worth: {!$GlobalConstant.True}
5. Click on Accomplished.
6. Add a Display factor with no contents.

In the long run, Rachel’s Stream will appear like the next screenshot:

As soon as every little thing seems good, carry out the steps beneath:

1. Click on Save.
2. Enter Stream Label; the API Identify will auto-populate.
3. Click on Present Superior.
4. API Model for Working the Stream: 56
5. Interview Label: Concurrent Classes Exceeded {!$Stream.CurrentDateTime}
6. Click on Save.

Nearly there! As soon as every little thing seems good, click on the Activate button.

Step 8: Configure Login Stream for Salesforce Platform Licensed Customers  

1. Click on Setup.
2. Within the Fast Discover field, sort Login Flows.
3. Choose Login Flows, then click on on the New.
4. Choose the Kind from the drop-down Stream.
5. Enter Concurrent Classes a Identify.
6. The subsequent step is to pick out Stream, Person license, and Profile. Observe the steps as proven within the following screenshot:
7. Click on Accomplished.

Proof of Idea

Take a look at the video for a demo: 

Formative Evaluation:

I need to hear from you!

What’s one factor you realized from this submit? How do you envision making use of this new data in the true world? Be happy to share within the feedback beneath.