Workflows

The workflow contains the sequence of pre and post-patching tasks. Before creating a workflow, you should add tasks and scripts to your library.

Workflow Library

The Workflow Library contains Workflows you have created in addition to four automatically created workflows, one for Windows, Linux, AIX, and Solaris.

1. To view the Library select Workflows from the lefthand menu under System > Workflows
2. The Search bar at the top left corner will enable you to search through the Workflows by name only.
3. You can Edit (), Delete () or Set as default for any of the listed Workflows by clicking on the respective action button.

Note:  When creating a remediation plan the default workflow will be selected automatically for  patch deployment unless you choose otherwise

Note 2: The default workflows for Windows and Linux have built-in post patching tasks for checking if a reboot is needed, and then rebooting if necessary.

Creating a Workflow

1. Select Workflows from the main menu
2. Click on +Add
3. Fill in the relevant details: Workflow Name, Operating System, and Pre+Post tasks.
4. Click Save

Note 1: A reboot task must be the last task in a workflow.  If you need to run tasks after reboot, use run task or use a compliance health test.

Note 2: A task categorized as Internal Script cannot be added to a workflow.

Workflow Control

After each workflow task activity (Pre/Post-Patching tasks), JetPatch will check the exit code and will decide the next steps:

• If the exit code is in the successful list of exit codes (default is 0) - JetPatch will continue to execute the workflow.
• Otherwise -
  
  • If the failure is in the Pre-Patching activity - JetPatch will not continue with the other Pre-Patching activities and won’t execute the patch operation. Post-patching activities can be executed - based on system configuration.

• • If the failure is in the Post-Patching activity - JetPatch will not continue with the other Post-Patching activities. See this article for more information.

Notes

• JetPatch considers it to be a failure in the patching operation only if there were no successful patching operations. Post-patching activities can be executed - based on system configuration.
• Running server reboot as a post-task on Linux servers requires the Linux at command to be installed. (Learn more on how to install the Linux at command utility)

Choosing a Workflow

• When creating a remediation plan, the user can choose a different Workflow for different groups and operating systems