Guides need not be self-contained. Most guides embed externally created sets of actions, as follows:
Service Calls
. To make a call to specific actions from within the current guide.
Embedded Guides
. To place an embedded guide within the current guide.
Process Calls
. To place a process or subprocess within the current guide.
Service calls are often specific to the object selected in the Properties dialog, so you may not see it. In addition, there are objects that are unique to one object and only appear when that object is selected. For example, if the guide is being applied to a Salesforce lead, you will see a Create Lead service call action.
You define Service Call steps for tasks that can be automatically executed. You can define them within Process Designer or access those available in services and systems integrated with Process Designer, such as Salesforce.
You can see both built-in actions and those added for applications and services categorized within the Action list. For example, the Create category shown here references several actions, including Create Account:
The actions listed are specific to your organization. However, you can usually find the built-in actions in the Advanced, Lists, and Integration categories. Some of the built-in actions are available only if you are licensed to use the Salesforce connector.
Drill down to see available actions using the right arrows.
The Action list also contains a list of Processes if you have published a process in Process Designer, similar to how service connectors are accessible in a process. The list shows the name of each process available to the Service Call step. If the process also exposes events, the event names appear in the list.