Task/Template Instantiation Workflow Block

The Task/Template Instantiation workflow block creates a task or template instance.

Task/Template Instantiation Workflow Block Properties

Exit Ports

Exit Port	Description
OK	Continue to the next block.
Failed	General exit port for a failed integration action. A logical next step is to trigger a notification.

Properties

Property	Description
Title	A unique name for the workflow block.
Select Task/Template Source Object	The source task or template object. Select from the drop-down list.
Select Task/Template Source Record	The source task or template record object. Select from the drop-down list.
Select Task/Template Source Relationship	The source task or template relationship object. Select from the drop-down list.
Select Target Object	The target object. Select from the drop-down list.

Actions

Button	Action
Save	Commits your settings.
Cancel	Exits without saving.

Example

The Following is a working example for Frequent Traveler Setup.You have two objects:

•FulfillmentItemPackage

•FulfillmentItem

A package is a template; when used, it creates a FulfillmentItem. Fulfillment items are built from FulfillmentItem packages.

In the packages, the Task Catalog tab lists tasks created by the task/template block for that FulfillmentItem. Therefore, "Tasks are built from Task Catalogs."

To clarify the process:

"Frequent Traveler Setup" allows selection of Fulfillment Items from a list of packages.

The workflow (WF) iterates over this list, adding FulfillmentItem objects to the service request.

When a FulfillmentItem is added, its WF triggers the Task/template block.

This block iterates over the task catalog items in the FulfillmentItemPackage to create tasks and attach them to the FulfillmentItem (not directly to the service request).

This explanation helps manage the complexity of multiple items and the importance of the insert multi-child block for entering values into Fulfillment Items.

You have a list of fulfillment items. This list is validated against fulfillment. The Multi block iterates over this list when inserting items.

On the Insert Multi-Child:

1.Define the relationship for adding new entries.

2.Specify the field or parameter to iterate over, such as the list control called 'Items'.

Expressions pull data from each selected 'item' to create FulfillmentItems, using 'boRecId' as the RecID for the current entry the multi-child block is processing.

$(GetBOValue(RecId, "boRecId", "FulfillmentItemPackage#", "Name"))

 

This is why you select the 'Select Child Object Type' relationship above; it is tied to FulfillmentItem.

The first "insert multi-child" workflow simply adds the fulfillment items. A standard workflow in FulfillmentItem then adds the tasks from the catalog.

In the FulfillmentItem object, a workflow triggers whenever a new fulfillment item is created. This workflow uses Task/Template Instantiation. When the first workflow creates the fulfillment item, this triggers the creation of tasks on the fulfillment item based on the template.

On the initial insert multi-child block, define the relationships for the template. The TemplateLink_Relationship between FulfillmentItemPackage and TaskCatalog creates tasks based on the catalog items linked to the package.

In the fulfillment item:

•TemplateLink_Category: FulfillmentItemPackage - The base business object being evaluated.

•TemplateLink: $(GetBOValue(RecId, "boRecId", "FulfillmentItemPackage#", "RecId")) - Pulls the RecId of the fulfillment package currently processed in the insert multi-child iteration.

•TemplateLink_Relationship: FulfillmentItemPackageAssocTaskCatalog - The relationship from FulfillmentItemPackage to TaskCatalog. The block iterates over items in this relationship specific to the package RecId and inserts tasks using the 'Target', causing multiple tasks to be added.

•Target: The location where the task will be created.

Example:

Here is a Fulfillment Item Package with two task catalog items. Each time this package is used, two tasks are created.

Following is the submission snapshot.

Following is the outcome snapshot.

The two expected tasks are created.