Setting the Go To Instance for a workflow
Use the Workflow Designer (Advanced) application to set Go To Instance for a workflow.
About this task
The Go To Instance flag is used when a workflow is launched from the Workflow Launcher application. It can be used to force a transition to the object created by the Workflow Launcher application.
Launch on Demand must be enabled before you can set Go To Instance for a workflow.
When Go To Instance is enabled, you can specify the application to switch to when the workflow is launched on demand. The application is specified in the "Go To Instance Application" field.
If the application is not specified when Go To Instance is enabled, a dialog displays with the list of applications that are supported by the object. The user can select an application from the list or click Cancel.
When an application is selected from the list, the application value is entered in the "Go To Instance Application" field, and Go To Instance flag is set.
If there is only one application available, the "Go To Instance Application" field will be filled in automatically. If there are no applications available for the object type, then Go To Instance cannot be enabled.
If Go To Instance is not enabled when the workflow is launched from the Workflow Launcher, the object will be created and routed into the workflow, but the submitter of the workflow will not be transferred to the created object, and will not have the opportunity to set any information in the object. This behavior can be useful for workflows that are intended to perform a very specific task. For example, the workflow might be designed to turn off the power in a lab on the 3rd floor of building 201. In this case, the submitter does not have to provide any information. The workflow proceeds through the process of turning off the power (including approvals if needed). If the workflow is designed in a more general fashion, where the submitter is expected to specify the floor and the building when launching the workflow, then Go To Instance should be enabled, and the workflow should include an interaction node that navigates the submitter to the appropriate tab on the application (a Change for example) to enter values for floor and building.