Prompt users for a more guided experience using screen flows. When creating a Salesforce Flow, Users now have the ability to add the following Squivr Components to be referenced in a screen:
Setting the Design Attributes when using Screen Flow
Org Chart Wrapper
Populate the data for Org Chart by completing the following design attributes:
Parent Field: This is used to reference a parent record based on a field on the current record. This field is necessary if you do not populate the Record Id (see below) with an Account Id from the provided record.
Enabled Objects: This field allows you to determine which objects are displayed on the Org Chart. Valid inputs are Parents and Children, Parents, Children, with the default being Parents and Children.
Org Chart Configuration: This field needs the External Id (squivr__External_Id__c) of the Org Chart Configuration you want to use, if you do not plan to override the default Configuration you do not need to worry about this field.
Record Id: This is the record Id referenced for the Org Chart. If passing the Id of the current record, the Parent Field is not needed unless referencing another parent record related to the current record. If the Record Id is any other object that is not the primary object of the Org Chart Configuration, the Parent Field will need to be populated with the field API Name that references the object you want to view.
Timeline
Populate the data for Timeline by completing the following design attributes:
Record Id: This is the record Id referenced for the Timeline. This can be any Id that references an object configured for Playbook.
GanttChart
Populate the data for GanttChart by completing the following design attributes:
Record Id: This is the record Id referenced for the GanttChart. This can be any Id that references an object configured for Playbook.
Note: when creating a variable for Record Id you must set it to be Available for Input
Screen Flow Setup Examples
Org Chart Examples
Account Screen Flow
Simply search for the Org Chart Wrapper component and drag the component onto the screen. In this example, since we are planning to launch this flow from an action on the Account page and reference an Account based configuration, we did not need to set a value for Parent Field
The variable set for Record Id is of Date Type Text and is Available for input
Opportunity Screen Flow
In this example, we plan to launch the Screen Flow from an Opportunity page action so the Parent Field (AccountId) is populated.
Playbook Example
In this example, the Flow contains two Screen elements - one for the Timeline component and one for the GanttChart component. This will be launched from an Opportunity providing insight into how we are tracking against key milestones. The variable used for Record Id is configured exactly like the Org Chart examples above.
The Screen element for Timeline and GanttChart will reference the same Record Id variable.
Calling Screen Flows from an Action or Link
After completing the steps above you will be able to add your Squivr Screen Flow to either an Action or Link for the appropriate object.
Action
When creating an Action, you can simply reference the created flow:
Link
When creating a Link, you will need to know the API Name of your Screen Flow. You will need to update the FLOWAPINAME to the API Name of your Screen Flow and {!Record.Id} to use the API Name of the current object in the Flow Link URL below.
Flow Link URL: /flow/FLOWAPINAME?recordId={!
Example: /flow/Org_Chart?recordId={!Account.Id}
After saving either the Action or Link, you will be able to add them to the appropriate section of your existing page layout.