Deprecated: Optional parameter $list declared before required parameter $is_script is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 21
Deprecated: Optional parameter $register declared before required parameter $footer_or_media is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 45
Deprecated: Optional parameter $register declared before required parameter $footer_or_media is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 104
Deprecated: Optional parameter $expire declared before required parameter $path is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_functions.php on line 54
Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/themes/entaro/inc/classes/megamenu.php on line 155
Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/themes/entaro/inc/classes/mobilemenu.php on line 147
Deprecated: Optional parameter $args declared before required parameter $wp_customize is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/extensions/customizer/extension_customizer.php on line 583
Deprecated: Optional parameter $args declared before required parameter $wp_customize is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/extensions/customizer/extension_customizer.php on line 606
Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/feed-rss2.php on line 8 Invocable process Archives - Salesforce Next Gen
http://salesforcenextgen.com/tag/invocable-process/
Trailhead and BeyondMon, 28 Dec 2020 19:32:22 +0000en-US
hourly
1 https://wordpress.org/?v=6.5.3https://salesforcenextgen.com/wp-content/uploads/2020/10/cropped-76dc0dd6-326a-4956-a412-bfdf20c7fb23_200x200-32x32.pngInvocable process Archives - Salesforce Next Gen
http://salesforcenextgen.com/tag/invocable-process/
3232Invocable process
https://salesforcenextgen.com/invocable-process/
https://salesforcenextgen.com/invocable-process/#respondMon, 05 Oct 2020 23:14:51 +0000http://www.salesforcenextgen.com/?p=1417Invocable processes are the processes which are built to modularise the code and reuse it whenever required, for example when your organisation closes won an opportunity, then a follow up task created for the owner to touch base with the account contact. Similarly when an Opportunity is closed Lost, then a follow up task is … Continue reading Invocable process
]]>Invocable processes are the processes which are built to modularise the code and reuse it whenever required, for example when your organisation closes won an opportunity, then a follow up task created for the owner to touch base with the account contact. Similarly when an Opportunity is closed Lost, then a follow up task is created to touch base with the Account contact.
Therefore it makes sense that you build a process build which creates a follow up task and is then called from different nodes of another process and gets executed.
To Create a invocable process you need to follow the below process.
Click on the Gear Icon on the right hand top corner.
Type Process Builder in the Quick find box.
Click on the process builder.
Click on the new button and fill out the below fields.
Process name: Opportunity Follow up Task
API Name: Opportunity_Follow_up_Task
The process starts when: It’s invoked by another process
Click on the object and since we want the task to be associated to an opportunity, we select opportunity as the object and click on save.
Click on the Criteria node and Select: No criteria—just execute the actions!
Save the Criteria and click on the ‘+ Add Action’ button and define the Action as below
Action Name: Follow up task
Record Type: Task
Set Field Values:
Field: Assigned To ID , Type: Field Reference, Value: [Opportunity].OwnerId
Field: Priority, Type: Picklist, Value: High
Field: Status, Type: Picklist, Value: High
Save the action and Activate the Process to use in other processes.
To Call this process from another process, we will use the existing process ‘Opportunity Won’
Click on the process Opportunity won and click on the clone button to create a new version of this process.
Click on the ‘+ Add Action’ next to the node Opportunity won and define the Action as below.
Action Name: Follow up task
Process: Opportunity Follow up Task
Set Process Variables
Process Variable*: SObject
Type: Field Reference
Value: [Opportunity]
Save the action and repeat for the Node Opportunity Closed Lost