telecomlobi.blogg.se - Screenflow upgrade freezing

SCREENFLOW UPGRADE FREEZING UPDATE

Navigate to the user record and confirm that the Unfreeze button is shown on the user record.On the Freeze a User app page, select a user and leave the freeze date/time to the default (i.e.Test your automation before production deployment. īest practice tip: Provide a description so you and other/future admins know what this flow is for. Set Field Values for the User Login Records:ĭ.

SCREENFLOW UPGRADE FREEZING UPDATE

Condition Requirements to Update Records: All Conditions Are Met (AND).Configure a Update Records flow element called Freeze User to update the User Login record where the UserId Equals the recordId, update the IsFrozen to true. When to Run the Flow for Updated Records: Only when a record is updated to meet the condition requirementsī.Control Navigation: Deselect Previous and Pause.”īest practice tip: Provide a description so you and other/future admins know what this flow element is used for. Otherwise, it is set to false.įormula: If ( Freeze_Date_Time_c will be frozen on. If the freeze time is greater than or equal to now, set the checkbox to true. Second, create a F ormula (checkbox) custom field called User can be frozen. Grant Read/Edit FLS to the field.īest practice tip: Provide a description so you and other/future admins know what this field is used for. In the User object, create two new custom fields.įirst, create a Date/Time custom field called Freeze Date/Time. Note: The user implementing this should be a system administrator or have Manage Users permission to be able to update the user.ġ. Then, when the time equals the Freeze Date/Time, Salesforce will update the IsFrozen attribute to true for the User Login record. This flow fires when a user record is updated after the record is saved when the freeze date/time has a value and the User can be frozen field is true.

The automation solution (record-triggered flow) looks like this: (3) Lastly, we show a confirmation message that notes the “ will be frozen on. (1) The screen flow prompts the user for the user via lookup search and the freeze date/time (set to now by default) (2) Then, we update the freeze date/time field for the selected user’s user record. The automation solution (screen flow) looks like this: With a record-triggered flow using a scheduled path, Salesforce freezes the user per the user’s freeze date/time. With a screen flow, she prompts the user to select the user and the freeze date/time and updates the user record with the freeze date/time. Being the #AwesomeAdmin that she is and a true Flownatic, Addison, of course, turns to flow for the automation solution. She learned that the IsFrozen user attribute is stored in the User Login object. Solution: A ddison Dogster knows the Freeze button is shown on a user record but had investigate what determines whether a user can be frozen or is frozen. Her staff can freeze users right away or can schedule a future freeze date. She wants the ability for her staff to be able to select a user and their freeze date/time in minimal clicks. Mary has staff who manage users in Salesforce, but are not true system administrators.

Create a record-triggered flow with a scheduled path.īusiness Use Case: Addison Dogster is the system administrator at Universal Containers.

Create a screen flow using the standard lookup component.

Here are a few lessons learned from implementing this use case: Yes! This is all doable with two custom fields, a screen flow, a record-triggered flow and adding the screen flow to a lightning app page. Rather than having to remember to freeze them later, wouldn’t it be great if you can schedule the user’s freeze date/time? Or, what if you can lookup the user and select to freeze them now in less clicks? Or you may be aware of a user’s upcoming departure date. As someone who performs user administrative tasks, you may need to freeze a user right away.