The workflow console provides several tools for administering workflow instances to ensure that they are executing as expected.
註解：
The JMX console provides additional workflow maintenance operations.
A range of consoles are available for administering your workflows. Use the global navigation to open the Tools pane, then select Workflow:
- Models: Manage workflow definitions
- Instances: View and manage running workflow instances
- Launchers: Manage how workflows are to be launched
- Archive: View history of workflows that completed successfully
- Failures: View history of workflows that completed with errors
-
註解：
The abort status is considered as a successful termination as it occurs as a result of user action; for example:
- use of the Terminate action
- when a page, that is subject to a workflow, is (force) deleted, then the workflow will be terminated
When a workflow fails, AEM provides the Failures console to allow you to investigate and take appropriate action once the original cause has been handled:
- Failure Details
Opens a window to show the Failure Message, Step and Failure Stack. - Open History
Shows details of the workflow history. - Retry Step
Executes the Script Step component instance again. Use the Retry Step command after you have fixed the cause of the original errror. For example, retry the step after you fix a bug in the script that the Process Step executes. - Terminate
Terminate the workflow if the error has caused an irreconsilable situation for the workflow. For example, the workflow can rely on environmental conditions such as information in the respository that are no longer valid for the workflow intance. - Terminate and Retry
Similar to Terminate except that a new workflow instance is started using the original payload, title, and description.
Minimizing the number of workflow instances increases the performance of the workflow engine, so you can regularly purge completed or running workflow instances from the repository.
Configure Adobe Granite Workflow Purge Configuration to purge workflow instances according their age and status. You can also purge workflow instances of all models or of a specific model.
You can also create multiple configurations of the service to purge workflow instances that satisfy different criteria. For example, create a configuration that purges the instances of a particular workflow model when they are running for much longer than the expected time. Create another configuration that purges all completed workflows after a certain number of days to minimize the size of the repository.
To configure the service, you can use the Web Console or add an OSGi configuration to the repository. The following table desribes the properties that you need for either method.
註解：
For adding the configuration to the repository, the service PID is:
com.adobe.granite.workflow.purge.Scheduler
Because the service is a factory service, the name of the sling:OsgiConfig node requires an identifier suffix, for example:
com.adobe.granite.workflow.purge.Scheduler-myidentifier
| Property Name (Web Console) | OSGi Property Name | Description |
|---|---|---|
| Job Name | scheduledpurge.name | A descriptive name for the scheduled purge. |
| Workflow Status | scheduledpurge.workflowStatus | The status of the workflow instances to purge. The following values are valid:
|
| Models To Purge | scheduledpurge.modelIds | The ID of the workflow models to purge. The ID is the path to the model node, for example: To specify multiple models, click the + button in the Web Console. |
| Workflow Age | scheduledpurge.daysold | The age of the workflow instances to purge, in days. |
You can set the maximum size of the inbox by configuring the Adobe Granite Workflow Service, using the Web Console or add an OSGi configuration to the repository. The following table describes the property that you configure for either method.
註解：
For adding the configuration to the repository, the service PID is:
com.adobe.granite.workflow.core.WorkflowSessionFactory.
