Page Comparison

B-04367

Add Cluster Broadcast for UDM File Transfer Tasks Utility Agent

File Transfer Tasks using the UDM Transfer Protocol now support the Agent Cluster Broadcast functionality for the Tasks Utility Agent.
 
For Example, a Linux/Unix Agent Cluster contains the following three Agents:
 

 
In order to configure a UDM file Transfer Task to transfer files from agent UCDDKR001 - UCDDKR001 to each of the Agents in this Agent Cluster, you would configure the UDM file Transfer Task as follows:
 

<ul>
<li> Utility Cluster Broadcast<br>
This will Launch an Instance of the UDM File Transfer Task on each of the three Agents in the Agent Cluster Definition.
<li>Source UDM Agent<br>
This specifies the single Agent where the file is being transferred from.
<li>Source File Name<br>
This specifies the file to be transferred to each of the three agents in the Agent Cluster Definition.
<li>Destination UDM Agent Option = UDM Agent Variable<br>
This allows the specification of a variable in place of a hard coded destination agent name.
<li>Destination UDM Agent<br>
The built in variable ${ops_agent_name} will resolve to the agent assigned to each task spawned by the Cluster Broadcast function, one task for each of the three agents in the Agent Cluster Definition.
<li>Destination File Name<br>
Specifies the location to transfer the file(s) to on each of the destination agents.
</ul>

When you Launch a UDM File Transfer Task, the Controller will create a unique instance of the Task for each of the three agents in the Agent Cluster Definition. Consequently, the /tmp/ops_user.xml file on UCD-DKR001 will be transferred to /tmp/ops_user.xml on each of the three agents in the Agent Cluster Definition.
 

B-10316

Ignore Inactive or Suspended Agents for Cluster Broadcast

When you create or update an Agent Cluster definition, you now have the option to prevent agents from being used by the Cluster Broadcast function if an agent, or its membership in the Cluster, is either Suspended or Inactive. Two new check-boxes in the Agent Cluster Details have been provided to facilitate this new functionality. By default, these options are unchecked; to use the new functionality, you must check the required option(s).
 

B-05576

Add capability for Cluster Broadcast Variable in tasks where Cluster Broadcast is used.

All tasks that can use the Cluster Broadcast functionality now support selection of the Agent Cluster for Cluster Broadcast via a variable.

B-10376

Report Chart Group by for Date/Time fields to specify Range of Grouping

Previously report charts that grouped data by any of the available date/time fields based the grouping on the way the date/time field is stored in the database (typically at the millisecond level).
 
This enhancement allows for the creation of more meaningful reports that can group chart data with the following levels of granularity:

<ul>
<li> Group by Year  : yyyy ? YYYY
<li> Group by Month : yyyy-mm ? YYYY-MM
<li> Group by Day : yyyy-mm-dd ? YYYY-MM-DD
<li> Group by Hour : yyyy-mm-dd hh ? YYYY-MM-DD HH24
<li> Group by Minute : yyyy-mm-dd hh:mm ? YYYY-MM-DD HH24:MI
</ul>

For example, the following report shows the number of Task Definitions updated each day stacked by the Task Type:
 

 

B-10828

New Example Reports

The following build in reports have been added:

• UAC - Task Based License Report (Completed Task Counts : Grouped by Month / Stacked by Type)
• UAC - Task Based License Report (Completed Task Counts : Grouped by Month)
• UAC - Hourly Completed Task Throughput Last 24 Hours
• UAC - Hourly Completed Task Throughput Last 24 Hours (Stacked by Type)

B-06219

Choice Field Dependency - Show If Field/Show If Field Value

For Universal Tasks when creating a new Universal Template, you now can specify to Show or Hide certain user-defined fields depending on the value of a choice field.
 
Firstly, create the Choice Field and Choice Values you want to use to decide if other fields are displayed.
 
When Creating a Field that you want to be shown only if specific choices are selected from the Universal Task Details drop-down, you now can select a choice field in the Validation section of the Universal Task Field definition and specify which values would display this new field in the Universal Task Details. You additionally can control whether blank space is reserved in the Universal Task Details when this field is hidden.
 

B-06293

Boolean Field Dependency - Show If Field/Show If Field Value

For Universal Tasks, when creating a new Universal Template, you now can specify to Show or Hide certain user-defined fields depending on the value of a Boolean field.
 
Firstly, create the Boolean Field you want to use to decide if other fields are displayed.
 
When Creating a Field that you want to be shown only if a specific selection is specified from the Universal Task Details drop-down, you now can select a Boolean field in the Validation section of the Universal Task Field definition and specify which value would display this new field in the Universal Task Details. You can additionally control whether blank space is reserved on the Universal Task Details when this field is hidden.
 

B-09484 and B-09507

Read Only & Hide options for Universal Template Fields

Customers now have the ability to deliver Universal Tasks that have certain defaulted fields marked as Read Only or completely Hidden from the end user. For example, if a specific Universal Task can run only on a Specific Server with a Specific Credential, the Universal Template Administrator now can Hide these fields in the Universal Task or mark these fields as Read Only.
 
The default fields will be grouped at a high level for visibility purposes; each group can be restricted only as a whole:

<ul>
<li> <b>Agent Fields</b> (Agent, Agent Variable, Agent Cluster, Agent cluster Variable, Cluster Broadcast)
<li> <b>Credential Fields</b> (Credentials, Credentials Variable, Run with Highest Privileges, Runtime Directory, Interact with Desktop, Create Console)
<li> <b>Environment Variables Fields</b> (Environment Variables)
<li> <b>Exit Code Processing Fields</b> (Exit Code Processing, Exit Codes, Output Type, Scan Output for, Output File)
<li> <b>Automatic Output Retrieval Fields</b> (Automatic Output Retrieval, Wait For Output, Failure Only, Start Line, Number of Lines, Scan Text, Automatic Output File) 
</ul>

The following options are available for each of the above Field Groupings:

<ul>
<li> No Restriction: This is the Default value whereby no restriction is in place. This is the same behavior as prior to these new restrictions.
<li> Read Only: Makes all the fields in the group appear as Read Only on the Task Universal form with respect to this Universal Template.
<li> Hidden: Makes all the fields in the group Hidden on the Task Universal form with respect to this Universal Template.
</ul>

B-10609

Universal Template - Copy

Universal Template Administrators can now copy an existing Universal Template from the Universal Templates list. The new copy option has been implemented as a right-click option in line with the copy capability for other definition types.

B-05590

Allow the running of commands that make sense for task instances even if their workflow container is complete.

Universal Controller now supports the following commands for task instances (excluding sub-workflows) in a completed Workflow task instance.

<ul>
<li> Re-run
<li> Force Finish
<li> Force Finish/Cancel
<li> Cancel
</ul>

By completed, we mean that the Workflow task instance is in an Inactive end state (SKIPPED, FINISHED, or SUCCESS).
 
Re-running a task instance in a completed Workflow will not re-run successor task instances, since the dependencies have already been satisfied. If a task instance is re-run in a completed Workflow and the task instance fails, conditional processing will not force finish the task instance; it will remain in Failed status.