Let’s imagine a scenario: you have been tasked to make a Login Flow for your organization, yet for unknown reason, it simply isn’t working for you. You’ve been twofold checking the variable’s data/yield esteem, the field level security of the clients, and pretty much everything else you can consider—yet, nothing is working.
What’s more, you’re about to toss the towel in for the day when you realize that Salesforce isn’t giving you a chance to utilize your desired naming tradition, on the grounds that you should utilize theirs. In this post we are going to experience the variables that Salesforce gives us and what they are utilized for.
To begin, you need a basic understanding of what’s going on.
- Confirmed User Access
- Get extravagant with some Geo-fencing administration
- Quiz the User a ‘mystery question’
- Restrict IP Usage on a User Basis
- Ready Messaging
- Push far reaching alarms out
- Data Cleaning
- Make beyond any doubt your clients approve their contact data at regular intervals
- Preparing
- Put together a progression of preparing screens for new clients
- Put your discharge notes of new components inside to ensure clients know
Since we have gone over a few thoughts around what we can do, let us dive into the traits.
Login Type
The Login Type is the place you can tell what TYPE of User is entering your Flow/Org. This permits you to see whether it is a client kind of Application or something like Chatter Community. This ordinarily will be Application.
IP Address
This is the Current IP location of the client. This is the IP Address of the User that is signing in. Presently, this is really effective… consider it. You can now confine particular IP Addresses down to the Profile, User, or whatever other field identified with the User Object in the event that you needed to!
Client Agent
This is the client specialist’s string gave by the client’s program. For my situation when I signed into a Screen demonstrating to me this variable, I got truly a long string back. Beyond any doubt enough, however, Google Chrome was within it. On the off chance that you needed to avoid clients from signing into your Org with Internet Explorer, you could do it utilizing this (on the off chance that you can ace the information that the client specialists are giving).
Stage
What is the client signing in from? Macintosh OSX? Something else? This is the place you’ll figure out.
Application
What are they signing in from? Discover here! Possibly you need to send them to an alternate completion area (home screen) in view of what gadget they are utilizing.
Group
This will show the present Community, if this login stream applies to a Community.
Session Level
This shows the security level of the present session. This is either Standard or High Assurance.
Client Id
This shows the client’s 18-character ID. Here is the place you can do a Lookup on the Login User and question the framework to locate any related fields that you need to use in your Flow.
Login Flow Variables can be utilized for some effective stuff. Ensure you name them precisely as they are recorded here (and in Salesforce’s documentation), else it won’t work! Salesforce has given us a considerable amount of energy to figure out who is entering the Org and what we need to do with them.
Study up and consider how this may have the capacity to assist your business. With this you gain knowledge on a variety of things such as cloud computing, integration and technology solutions for business.