+ Start a Discussion
Robert Robinson 48Robert Robinson 48 

Identifying type of Automation used

I am inheriting an org with quite a bit of automation left by a consultant. I am trying to determine efficiently what type of automation (Flow, Process Builder, etc) is being used. Is there any way to trap a process when it is run and see the root automation behind it? Thanks.
Best Answer chosen by Robert Robinson 48
Khan AnasKhan Anas (Salesforce Developers) 
Hi Robert,

Greetings to you!

You can troubleshoot Processes with Apex Debug Logs. 

When using debug logs to troubleshoot a process, consider the following.
  • Processes created in the Process Builder appear as flows and workflow rules in debug logs. The generated names have some resemblance to the process names, but they don’t map one-to-one.
  • Record change processes appear as flows of type Workflow. Invocable processes appear as flows of type InvocableProcess. Event processes appear as flows of type CustomEvent.
  • Immediate actions that are executed in a block are strung together in the flow. If one action fails in the middle, then the following actions aren’t executed.
  • Scheduled actions are executed after a FLOW_WAIT element. The actions are executed similarly to immediate actions after the process resumes.
  • WF_CRITERIA_BEGIN and WF_CRITERIA_END refer to the workflow rule criteria that are always set to true and not the criteria defined in your process.

https://help.salesforce.com/articleView?id=process_troubleshoot_debuglogs.htm&type=5 (https://help.salesforce.com/articleView?id=process_troubleshoot_debuglogs.htm&type=5)

You can also try below tool to find out where this field is referenced (apex code, workflow rules, validation rules etc), getting updated (workflow field updates etc) and is available (page layouts, profiles etc).

https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000EcsCZUAZ

I hope it helps you.

Kindly let me know if it helps you and close your query by marking it as solved so that it can help others in the future. It will help to keep this community clean.

Thanks and Regards,
Khan Anas

All Answers

Khan AnasKhan Anas (Salesforce Developers) 
Hi Robert,

Greetings to you!

You can troubleshoot Processes with Apex Debug Logs. 

When using debug logs to troubleshoot a process, consider the following.
  • Processes created in the Process Builder appear as flows and workflow rules in debug logs. The generated names have some resemblance to the process names, but they don’t map one-to-one.
  • Record change processes appear as flows of type Workflow. Invocable processes appear as flows of type InvocableProcess. Event processes appear as flows of type CustomEvent.
  • Immediate actions that are executed in a block are strung together in the flow. If one action fails in the middle, then the following actions aren’t executed.
  • Scheduled actions are executed after a FLOW_WAIT element. The actions are executed similarly to immediate actions after the process resumes.
  • WF_CRITERIA_BEGIN and WF_CRITERIA_END refer to the workflow rule criteria that are always set to true and not the criteria defined in your process.

https://help.salesforce.com/articleView?id=process_troubleshoot_debuglogs.htm&type=5 (https://help.salesforce.com/articleView?id=process_troubleshoot_debuglogs.htm&type=5)

You can also try below tool to find out where this field is referenced (apex code, workflow rules, validation rules etc), getting updated (workflow field updates etc) and is available (page layouts, profiles etc).

https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000EcsCZUAZ

I hope it helps you.

Kindly let me know if it helps you and close your query by marking it as solved so that it can help others in the future. It will help to keep this community clean.

Thanks and Regards,
Khan Anas
This was selected as the best answer
Robert Robinson 48Robert Robinson 48
My, my...I really like this Field Pro!