Overview

Workflows give users the ability to automate tasks before and after the patch cycle. The workflow contains the sequence of pre- and post-patching tasks that run as part of a Remediation Plan.

When creating a workflow, it is important to consider three key elements:

• Scripts – Added to Tasks. JetPatch provides many built-in scripts for your use.
• Tasks – Added to Workflows. Built-in tasks are available out of the box.
• Workflows – Contain the sequence of pre- and post-patching Tasks.

An easy way to think about it: Scripts are added to Tasks, and Tasks are added to Workflows.

Scripts and Tasks

Scripts

Navigate to System → Scripts to view the Scripts library. There are two different types of scripts:

• Built-in Scripts – Marked with a blue ‘B’. Available for your use, but cannot be edited. JetPatch provides built-in scripts for rebooting all operating systems (Windows, Linux, AIX, Solaris) and many other common tasks.
• Personal Scripts – Scripts that the user creates. To create a script, select Create Script and fill in the relevant fields.
• Mor Info - Here

Tasks

Navigate to the Tasks tab (above Scripts) to view the Tasks library. Like Scripts, there are many built-in Tasks ready to use.

• To create a personal task, select Create Task and fill in the relevant fields, including selecting the script to use.
• Built-in tasks cover common operations such as reboots for all operating systems. You can search by name (e.g., “reboot”) to quickly find the right task.
• More Info - Here

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 System → Workflows from the left-hand menu.
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.

Creating a Workflow

1. Navigate to System → Workflows.
2. Click +Add (or Create Workflow at the top right).
3. Fill in the relevant details: Workflow Name, Description, and Operating System.
4. Add the desired tasks to the Pre-Patching and/or Post-Patching sections. For example, to perform a Windows reboot after patching: select Post-Patching, choose Simple Windows Reboot as the task, and click Add.
5. Click Save. Your workflow is now ready to use.

Duplicating Workflows

As of version 4.2.8, you can now duplicate existing Workflows directly from the Library. This is useful for creating variations of complex workflows (e.g., adding an extra pre-task for a specific set of servers) without manually re-entering all steps. To clone a workflow, click the Duplicate icon in the Actions column.

Using the Workflow Table

Once set up, the Workflow table shows:

• The workflow description.
• The operating system is meant for.
• Whether it is currently active in the Remediation Plans.

To set a workflow as the default for a specific operating system, hover over the checkmark on the right side of the workflow row and click it. Default workflows are shown in parentheses under the Operating System column.

Workflow Control

After each workflow task activity (Pre/Post-Patching tasks), JetPatch will check the exit code and 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.
• If the exit code indicates failure:
  • Pre-Patching failure – JetPatch will not continue with the other Pre-Patching activities and will not execute the patch operation. Post-patching activities can be executed based on system configuration.

• Post-Patching failure – JetPatch will not continue with the other Post-Patching activities. based on system configuration.

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 about 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 (also to prioritize them...)

To summarize the full workflow setup process:

• Decide what built-in script you would like to use.
• Make sure there is a task that uses that script.
• Create a workflow that uses the task for any pre- or post-patching activities.
• If applicable, set that workflow as your default workflow for the relevant operating system.
•