I think that everyone understands that labeling and color coding your links is a wonderful best practice; it really makes everything much easier to follow. The problem is that I am pretty lazy and hate actually changing these properties. So, to fix this problem I have updated the Orchestrator Administration project to include functionality for setting what we internally have defined as best practices for link modifications on exports. The two sub projects of this project have been updated to reflect this change (that is the integration pack for exporting runbooks https://scorch.codeplex.com/releases/view/92063 and the parse orchestrator export GUI tool https://scorch.codeplex.com/releases/view/104915).
What are the Best Practices
We defined the best practices as follows
- If a link comes from an object that is flattened, modify the name of the link to reflect
- If a link has a delay modify the name to show the delay and if a color is not set change it to blue
- If a link is a ‘success’ of previous object change it to green and add success to the name
- If the link is a ‘always continue’ (success, warning, failure) of previous object update link name to always and change color to green width 2
- If the link is a ‘failure’ or ‘failure or warning’ of previous object update link name to failure and set color to red
- If there are other criteria (multiple criteria or based on property of previous object) set link to orange and add custom criteria to the end
What does it look like?
Here is an example of a runbook pre-export and link modification
And post modification
How to set it up on the export runbook object
Set the optional property
How to use it on the Parse Orchestrator Export Tool