Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 - Asset Console Configuration and Administration Guide


12.5.5 Examples of activity definitions

This subsection illustrates the procedure for defining activities with Activity Designer using the example of software installation request jobs.

There are two possible situations for software installation request activities:

The following subsections describe each definition example.

Organization of this subsection

(1) Example of activity definition (when only one software asset is registered)

This activity registers the requested software asset and license keys. It assumes that the Item window has been defined in such a manner that the following items are specified and attached:

Request user name, Group of request user, Phone of request user, Software name (mandatory), Number of licenses (required), License keys (required) (file attachment), Notes, Reason for rejection

The following shows the contents of the file attachment for the license keys. License key, Product ID, and Serial No. are specified in the file.

Key101,aaa-aaa-aaa,123456789
Key102,bbb-bbb-bbb,123456789
Key103,ccc-ccc-ccc,123456789
Key104,ddd-ddd-ddd,123456789
Key105,eee-eee-eee,123456789
Settings in Use tasks

The tasks to be selected and their order are as follows:

Add new software
*Loop start
Add license key
*Loop end
Settings in Task conditions for Add new software

The following shows an example of setting assigned items for Add new software.

Figure 12‒28: Example of setting assigned items for Add new software (when only one software asset is registered)

[Figure]

Because only one software asset is registered, for Asset No., set the management name of the object that specifies Asset No. . For other required items, set a fixed value.

Settings in Task conditions for *Loop start

To register the license keys specified in the CSV file, set Number of lines of uploaded file for Loop target and the management name of the object that specifies License key for Assigned items.

Settings in Task conditions for Add license key

The following shows an example of setting assigned items for Add license key.

Figure 12‒29: Example of setting assigned items for Add license key (when only one software asset is registered)

[Figure]

For Target asset no. of software and Target group name, set the management names of the objects that specify their values. For Target group name, you can specify only the object for which Group reference was selected as the object attribute Data type.

For Product ID, License key, and Serial No., set the applicable column numbers in the CSV file.

(2) Example of activity definition (when multiple software assets are registered)

This activity registers requested multiple software assets and multiple license keys for each software asset. It assumes that the Item window has been defined in such a manner that the following items are specified and attached:

Request user name, Group of request user, Phone of request user, Software (required) (file attachment), License keys (required) (file attachment), Notes, Reason for rejection

The following shows the contents of the file attachment for the software. Asset No., Software name, Number of licenses, and License name are specified in the file.

Asset000001,Software001,2,License001
Asset000002,Software002,2,License002
Asset000003,Software003,2,License003

The following shows the contents of the file attachment for the license keys. Asset No., License key, Product ID, and Serial No. are specified in the file.

Asset000001,Key101,aaa-aaa-aaa,123456789
Asset000001,Key102,bbb-bbb-bbb,123456789
Asset000002,Key103,ccc-ccc-ccc,123456789
Asset000002,Key104,ddd-ddd-ddd,123456789
Asset000003,Key105,eee-eee-eee,123456789
Asset000003,Key106,fff-fff-fff,123456789

When multiple software assets are registered, you must specify Asset No. to identify each software asset.

Settings in Use tasks

The tasks to be selected and their order are as follows:

*Loop start
Add new software
*Loop end
*Loop start
Add license key
*Loop end

The loop processing itself can be structured hierarchically. However, this example does not use a hierarchical structure because if the license keys to be registered vary from one software asset to another, a hierarchical structure cannot provide the intended processing.

This example requires assignment of information between the CSV files for the Add new software and Add license key tasks. It is therefore necessary to specify the assigned key in both CSV files. In this example, Asset No. is the assigned key.

Settings in Task conditions (*Loop start)

To register the information specified in the CSV file, set Number of lines of uploaded file for Loop target. For Assigned items, set the management name of the object that specifies Software or License key.

Settings in Task conditions (Add new software)

The following shows an example of setting assigned items for Add new software.

Figure 12‒30: Example of setting assigned items for Add new software (when multiple software assets are registered)

[Figure]

For Asset No., Software name, Number of licenses, and License name, set the applicable column numbers in the CSV file. For Group name and Notes, set the management names of the objects that specify their values. For other required items, set fixed values.

Settings in Task conditions (Add license key)

The following shows an example of setting assigned items for Add license key.

Figure 12‒31: Example of setting assigned items for Add license key (when multiple software assets are registered)

[Figure]

For Target asset no. of software and Target group name, set the management names of the objects that specify Asset No. and Group name, respectively. For Product ID, License key, and Serial No., set the applicable column numbers in the CSV file.