Defining a Task Chain

1. Create an AsyncSchedule record to act as a template

   For security purposes, you're not able to start any arbitrary task, instead you must define an AsyncSchedule to act as a template.

    
   1. Create an AsyncTaskChain record in the Customer database
      
      The AsyncTaskChain identifies the AsyncSchedule record and gives the task a name that you can reference in the starting task.
      
      The TaskChain plug-in on form 1378 (Edit Schedule Task) allows you to perform this action in ClientTrack. You must have Integration access to view/edit this setting.
       
   2. If you want to be able to start the task from another customer environment, create an AsyncTaskChainAccess record
      
      For example, if you want to run a task in training, then run a task in production, you must grant access to the training environment.
      
      On the form, you do this by specifying the CustomerID in the “Share With” field.
       
2. Set the async-TaskChain parameter in the first task
   
   The value of the parameter is JSON-formatted data in the following format:

{
	"customerId": "Target environment",	// optional - used for cross-environment requests
	"name": "Name of the AsyncTaskChain record",
	"params": [	// A list of parameters to set in the target task
		{
			"name": "Name of the parameter to set",
			"value": "The value to set it to",
			"encrypt": true	//optional - set to true to encrypt the value
		}
	]
}

The value can be a dynamic value. Dynamic values will load the value from the source task's Output, the source task's own parameters, or global parameters such as @UserID@ or @DATE@. It also supports the special value @FileToken@ that can be used in cross- environment task chains to allow the target environment to access the file produced by the source environment.

The TaskChain plug-in on form 1378 (Edit Schedule Task) allows you to configure this action via the "Run another task" parameter in ClientTrack. You must have Integration access to view/edit this setting.

Standard Outputs

• FileName [for tasks that generated a file and stored it on the file server]- the name of the file produced
• FTP-URL [for tasks that generated a file and uploaded it to an FTP server]- the URL of the file on the FTP server
• ImageID [for tasks that generated a file and stored it in the FileUpload table]- the ID of the file