#Salesforce Admin토론 중인 항목 324개

Hi, the User object documentation doesn't provide any information that could help in explaining your answer but the login history object answers it. There are fields in that object which mentions who/which user/automation logged in. 

In my knowledge no process can update this field except the api login. Otherwise login is not required by any automation in salesforce. If you have a integration user configured then the field will not get updated on a normal user.

https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_loginhistory.htm

@Sahil Gupta

 Try this approach. Before changing the email address of Brochan Pane, use the System.setPassword() method to set an interim password -> then update the email address and you would receive the email -> On clicking the link, it will ask you to login as Brochan -> use the password that you have set -> it will ask you to reset the password, please do that -> finally on next screen, email would get verified. 

Please try and let me know if this works. 

Thanks. 

Abhishek

@Terry Howard

A few things to verify:

• Make sure the Salesforce user is still Active and has the required Account Engagement permission set/access.
• Check whether the corresponding Account Engagement user is active and properly linked to the correct Salesforce user.
• Verify the user has the required Account Engagement role/permissions and that there isn’t a duplicate or mismatched user mapping.
• If the Account Engagement user is actually appearing in the Recycle Bin, check the Account Engagement user management/setup and restore/recreate the user if necessary.
• Also check whether the user was recently deactivated, deleted, or had their Salesforce license/profile/permissions changed, as this can affect the Account Engagement user.
• If everything looks correct, I would check the Account Engagement Setup - Salesforce Integration status and run through the user-sync/integration troubleshooting.

Hey Mohit, 

Classic Approval Process's standard Reject button can't launch a screen flow, it only has a plain Comments text box, no way to force a required field or picklist before rejecting. 

The real fix is to move this to a Flow Approval Process instead of Classic Approval Process, that's what Salesforce built specifically for this use case. With Flow Approval Processes, you build the approve/reject screen yourself: 

- Create a Screen Flow with a radio button (Approve/Reject) 

- Use a Decision element, when Reject is selected, show a Rejection_Reason picklist as a required field on that same screen 

- Use the "Resolve Approval Request" flow action (or Update Records if you're setting the field directly) to set Application_Status__c = Rejected and Rejection_Reason__c from what the user entered 

- This entire screen replaces the standard Approve/Reject buttons, so your rejection reason requirement is enforced right there in the flow, no separate popup needed 

If you're on Classic Approval Process and don't want to migrate, there's no native way to inject a screen flow into the Reject button, that part's a real platform limitation. Migrating to Flow Approval Process is the supported path here, not a workaround. 

Reference: