Versioning and Promotion System (VPS)

A new system has been added to provide versioning of definitions for audit and historical purposes, as well as the ability to roll-back changes.

Promotion is included in the new system to provide the ability to promote definitions from one environment to another in different instances of Opswise. An option to bundle definitions together for promotion is also included in this new system as well as a utility script to export versions in bulk.

Central Script Library

Scripts can now be stored in Opswise for central management and access.

Copy Trigger

In addition to being able to copy a Task and Workflow, you can now copy an existing Trigger in order to create new Triggers more easily.

SAP Task Type

Opswise can now run workload on an SAP system. New built-in variables jobname and jobid provide workflow automation capabilities between SAP tasks. For example, you can leverage the SAP jobname and jobid variables of an SAP Task instance as input to another Task instance or use them in a Task Email Notification.

Updating Multiple Records on a List

Warning: Exercise great caution when using this powerful feature.

Two menu options available from any list of records allow you to make updates to multiple records. You can make these "global" changes to the list for any field that is common to every record in the list or every selected record. For example, if your list includes multiple Cron triggers, you can make "global" changes to all fields on a Cron trigger. If your list includes all task types, you can make "global" changes to any field that is common to all task types. The more uniform your list is, the greater the number of fields you can change.

Task Instance Validators

All Task Types will now be validated upon definition.

SQL Warning Messages

SQL warning messages are now captured and available with the DB Task output from the Activity Window

Resource Wait

The "Resource Wait" status has been separated into two distinct statuses: "Resource Wait" and "Resource Requested." Any Task instance that requires resources will transition through the "Resource Requested" status. However, only those Task instances that need to wait for their resources (they are not available immediately) will transition into the "Resource Wait" status. Furthermore, a new column, "Waited for Resources," was added for Task History. On completion, any Task instance that transitioned through the "Resource Wait" status will show up in the History with "Waited for Resources" as "true." By filtering on this column, a user can determine where there was contention on Virtual Resources.

Multi-selection Support

You can now select multiple tasks in the Activity Window in order to perform the same command against them at one time. The lowest common command set will be available for selection.

Monitor Task Enhancements

Task Monitor enhancements include the ability to specify a Workflow Condition and a Time Scope, as well as add the capability to specify Restrict Times on the Task Monitor Trigger.

Estimated End Time Calculation

For improved forecasting, the Estimated End Time of Workload is based on Historic Averages.

Export

New scripts to export history have been added to the utilities.

• opswise_bulk_export.js
  Used when migrating data to updated software. Exports all current record definitions, without versions. See Upgrading Opswise Controller.
• opswise_bulk_export_activity.js
  Used when migrating data to updated software. Exports all activity (finished or unfinished). See Upgrading Opswise Controller.
• opswise_bulk_export_history.js
  Used when migrating data to updated software. Exports task instance history, which includes all task instances in an end state (cancelled, failed, skipped, finished, success). See Upgrading Opswise Controller.
• opswise_bulk_export_with_versions.js
  Used when migrating data to updated software. Exports all current records along with older (non-current) versions of record definitions. See Upgrading Opswise Controller.

The export of history was previously part of "opswise_bulk_export.js." However, it is now contained within its own script "opswise_bulk_export_history.js." If customers wish to export and/or migrate their history data, they will need to execute "opswise_bulk_export_history.js" in addition to the "opswise_bulk_export.js."

...

Opswise Message Service (OMS)

For Opswise Automation Center 5.2.0, Opswise Message Service (OMS) replaces the Message Hub and Transporter components of the 5.1.0 Outboard as the network communications provider between Opswise Controller and Opswise Universal Agent.

OMS uses similar, message-based communications protocol as the Message Hub and Transporter. It provides fault tolerant, reliable, secure messaging.

OMS is packaged as a component of Opswise Universal Agent, and it is installed and configured just like any other Opswise Universal Agent component.

Security

New Permissions

Added a Virtual resources permission.

Added a Variable permission.

Business Services

Added Member of Business Services to Virtual Resources.

Added Member of Business Services to User-Defined Variables.

New Properties

Added a Virtual Resources Security Enabled property.

Added a Variable Security Enabled property.

Workflow Improvements

Two new commands have been added - Force Finish (Halt) and Force Finish/Cancel (Halt) - that let you:

• Force finish task being monitored by a File Monitor task or FTP File Monitor task without completing the monitoring process.
• Force finish a task without releasing successor tasks in a workflow.

Force finishing a command that does not notify the task monitors would help in cases were you need to force finish the task but you don't want the task monitors to complete; for example, if the task was launched in error.

Force finishing a task without releasing successor tasks in a workflow would help in cases where a task instance - due to a number of possibilities - is stuck in Queued status, and you want to force finish and re-run the task without impacting workflow dependencies.

Trigger on Existence

Added a Trigger on Existence option to Create File Monitor type.

User Mode Install

For UNIX, you can now select the directories where everything gets installed.

Simulated Trigger

The Forecast Information screen indicates if the forecast information is for a simulated trigger.