Abstract trigger revisions allow Workflow Automation to upgrade workflow revisions using the trigger to the latest trigger revision. Workflow Automation provides the following abstract trigger revisions in the Start of Workflow activity:
N.* represents the latest trigger revision with a specific major revision number (N) and highest minor revision number. For example, when you create Workflow Revision A and assign the abstract revision 1.* of Trigger A, the current trigger revision is 1.1. When Workflow Automation upgrades the workflow revision, Workflow Automation upgrades Trigger A to revision 1.5, which is the most recent 1.* revision, rather than to the latest revision of Trigger A, which is 2.2.
*.* represents the latest trigger revision with the highest major and minor revision numbers. For example, when you create Workflow Revision B and assign the abstract revision *.* of Trigger A, the current trigger revision is 1.1. When Workflow Automation upgrades the workflow revision, Workflow Automation upgrades to the latest revision of Trigger A, which is 2.2.
Workflow Automation upgrades to the latest trigger revisions in the following scenarios:
When you put a workflow revision with abstract trigger revisions into production for the first time, Workflow Automation assigns the latest trigger revision according to the rule for the specified abstract revision. For more information about putting a workflow into production, see Putting a Workflow Revision into Production.
When you create a new trigger revision, Workflow Automation verifies whether any workflow revisions reference one of the trigger’s abstract revisions, and displays the Deploy Trigger Updates window. Workflow Automation ignores workflow revisions that are currently Under Construction.
When you manually deploy trigger updates for a specific trigger, Workflow Automation verifies whether any workflow revisions reference one of the trigger’s abstract revisions, and displays the Deploy Trigger Updates window. Workflow Automation ignores workflow revisions that are currently Under Construction.
In each scenario, Workflow Automation restricts the list of workflow revisions to the ones you have the permissions to view, clone, and put into production.
When you deploy trigger updates, Workflow Automation clones the specified workflow revision, and then puts the clone into production, which upgrades all triggers to use their latest trigger revisions. For more information about cloning a workflow revision, see Cloning a Workflow Revision.
If you upgrade a workflow revision that is currently out of production, the clone remains out of production.