Tutorial: Creating a package migration workflow

You can create a workflow that provides notifications on the status of migrated packages. This workflow offers several key benefits:

• Real-time Updates and Activity Tracking: You can stay informed of the latest migration activities and closely monitor the progress of each migration.
• Quickly troubleshoot failed migrations: By setting up an alert for unsuccessful migrations, you can promptly identify and resolve potential issues.
• Integration with external ticketing systems: Integrate your workflow with an external ticketing system to streamline the process of resolving migration issues

Complete the following steps to create a package workflow in Oomnitza that triggers a notification upon a migration event.

Step 1: Create a workflow

1. Click Configuration > Workflows and click Add (+).
2. Select Migration Package from the list.

Step 2: Configure the Begin Block

Specify the criteria to trigger the workflow in the Begin block.

1. Edit the Begin block
2. Add rules to trigger the workflow.
   1. Change the Actions to Migration Pushed.
   2. Add Rule criteria to make the workflow run more efficiently and target the packages that you want to track. For example, you might want to trigger the workflow only when the packet migration fails.
3. Click Save.

Fig: Begin block criteria that targets packages that have failed to migrate successfully 

Step 3: Add the Notify Block

1. Click Blocks, and drag and drop the Notify block onto the canvas.
2. Click Edit.
3. Specify the notification details in the Information tab.
4. Enter the message recipients in the Recipients tab. 
5. Create your message in the Message tab.
6. Click Save.

Using the Notify block

Fig: Message created using package metadata

Table: Message metadata

Name	Description
Archived	Indicates that the package is archived. Returns a blank value if the package is not archived. Returns Y if the package is archived.
Category	The package category.
Change Date	The date when the package was last modified.
Changed By	The user who last made changes to the package.
Created By	The user who created the package.
Creation Date	The date when the package was created.
Description	A brief summary of the package details.
Documentation Link	A link to an article about the package.
Initiated By	The user who triggered or who caused the package workflow to be triggered.
Last Run End Time	The date and time when the most recent package migration operation was completed.
Last Run Logs	The logs relating to the latest package migration event.
Last Run Start Time	The date and time when the most recent package migration operation began.
Last Run Status	The status of the migration such as Success or Failure.
Migration Items	The package contents.
Name	The name of the package.
Package Version	The user-defined version of the package.
Predecessor	An internal value that contains the ID of the source package.
Record ID	A unique identifier for the package.
Status	The current status of the package.
Subcategory	The package subcategory.
Version	The system package version. This might be different from the package version if, for example, the record was updated to add new information about the same package version.

Step 4: Add additional blocks

Tip

To keep users in the loop during a migration event, you can add an API block to your workflow. This enables you to notify users through an external ticketing system. For instance, you might consider using one of the following ticketing presets to create a ticket or an issue:

• EasyVista: Create new ticket
• Freshservice: Create ticket
• Jira: Create an issue
• ServiceNow: Create incident
• Zendesk: Create ticket

Step 5: Launch the workflow

1. Click Save and connect the blocks
2. Validate the workflow and Activate, so that the workflow is now live in your system.

Result
The workflow will send a notification every time a user performs a migration.

Performing the migration