Programming Guide › Customizing Business Flows › Standard CA GovernanceMinder Building Blocks › Transformation Building Blocks

Transformation Building Blocks

The following three new workflow building blocks can be added to a workflow process by using the Workpoint Designer:

• ExecutePDIFile—accepts a transformation file stored locally on the file system. Provide the full path for the file name parameter. This option is a fast way to deploy a PDI transformation.
• ExecutePDIPackage—runs a transformation that has been loaded onto the server. The name of the package in the PDI_BUNDLE_NAME parameter should be the same name you use when uploading the transformation to the server. This option is more suitable for cluster deployments, as the package does not need to be local.
• ExecuteCMD—calls a command line executable that runs locally on the server.

Providing parameters for the two PDI building blocks (ExecutePDIFile and ExecutePDIPackage) is done with the PARAMS field. It accepts a list of parameters that are separated by commas, and start with "-param:". For example:

"-param:configurationName=model","-param:target=newModel"

In the previous example, the PDI transformation gets two parameters, "configurationName" with the value "model" and "target" with the value "newModel".

The parameters for the ExecuteCMD building block are as follows:

• CMD_SCRIPT_FILE—the name of the command. For example, "run.bat". The CMD_SCRIPT_FILE must exist in the file system. CMD commands (like "copy") cannot be used.
• CMD_WORKING_FOLDER—the name of the folder used as the starting point for the command.
• PARAMS—the list of parameters separated by commas. For example:

  PARAMS = ASGFASDGSDFG@$#!@","-value2"," ASGFASDGSDFG@$#!@"