The Stack Overflow podcast is back! Listen to an interview with our new CEO.
4

You named your Flow input variable wrong to get the Flow User ID. The proper format for that input variable should be LoginFlow_UserId as noted in this support article. It's not working because you aren't actually passing that users ID to the Flow, so it will never return the values you want from the User record. The following input attributes are ...


4

You cannot run a process builder/trigger/workflow without logging in. The best you do is with invalid password then lockout the user. Set the lockout effective period to forever, then show a locked user a page asking them to email the admin/security team. By this way, the security team will always know whats going on with users. Another Approach will be ...


4

You may be in luck. There's something call the ExperienceID or expid that potentially could be used to do what you want to achieve. Its primary purpose is to be able to customize the "branding experience" for customers depending on where they are sent to your community from. You can learn more about it by reading this link to the Salesforce External ...


2

Yes, that is one of the examples giving in the official documentation. Seems there is even a link to an unmanaged package to install different login flow samples into your org.


2

It seems like what you're looking for is SSO with salesforce as both the SP and IP. I've never tried it within the same org however. Here is some info that you can try to use: Salesforce to Salesforce SSO SSO in communities In theory, you set up SSO, Then you enable your community to use SSO pointing to Salesforce as the IP, then you create a login flow ...


2

While I agree that seems like an issue (aka a bug), you should be able to parse the user agent in the login flow or the platform to determine if they are coming from outlook and bypass the login flow in that case. See this article for the variables that you have access to in your login flow. Will take some experimentation / analytics to determine the best ...


1

Check this article(Connecting one Org to another via Rest API) : https://cloudvista.wordpress.com/2015/07/23/connecting-one-salesforce-org-to-another-via-rest-api/ Note: this uses connected App but has all step by step details


1

The Metadata Coverage Report is the centralized location for which metadata elements are supported by functionality like Salesforce DX and the Metadata API. The LoginFlow component is not supported by source tracking, which drives sfdx force:source:pull. It's also not supported by the Metadata API or any version of packaging. Unfortunately, you won't be ...


1

You have to remove it from Setup > Login Flows, not only deactivate it from Flows because it's still looking for the flow to be executed.


1

This could be a known issue check this link. At present the only workaround is to use chrome and firefox. You can build something custom to overcome this instead of using login flow


1

If you are only looking to send it based upon the first time they ever log in could you have a workflow/trigger/process that fires off of LastLoginDate. When they have never logged in that value is blank.


1

Have you tried setting debug log for the user who is facing error in login. I am sure, there would be class invoked in login flow (if using the login flow provided on SF blog) and you can capture fault events there in logs.


1

You can use the @invocableMethod annotation to make a static Apex method available to use in a Login Flow. You cannot run a trigger on logins as of S17.


1

You can use simple merge values in a flow, so it's entirely possible to do things like what you're talking about. For retrieving labels, you apparently can't merge those in directly, so you'd have to use the InvocableMethod interface to set a flow variable before using the label. For records, you can query the record via Fast Lookup, then merge that within ...


Only top voted, non community-wiki answers of a minimum length are eligible