Execute a Jython script. This operation differs from executeCode by executing the code snippet for every file in the package. This operation has the same support for inputs and outputs available to it as the executeCode operation. In addition it has the following variables available with information about a particular file.
File Level Variables With Example
Variable Name | Description | Value if File Name (with path) is /XXHR/publisher/APXSOBLX_1.rtf |
|---|---|---|
| File path of the package deploy file. (File Name (with path)) on the package deployment screen. | /XXHR/publisher/APXSOBLX_1.rtf |
| File name of the package deploy file. | APXSOBLX_1 |
| File path, excluding the file name and extension. | /XXHR/publisher |
| File extension on the package deploy file. | rtf |
| Fully qualified location of the file on the endpoint. | Fully qualified path to file being processed. This can be different locations for build and deploy workflow execution as there might be some checkout folder specified for build. See examples below for build and deploy workflow where FILE_PATH is in bold text.
|
| The Hash of the file as generated recorded by FlexDeploy. | |
| The SCM Revision of the package deploy file. |
All file attributes defined on Project Files tab are included as well.
Project Properties
Property Name | Property Code | Required |
|---|---|---|
Stop On Deployment Error |
| No |
Inputs
Input Name | Input Code | Required |
|---|---|---|
Code Snippet |
| Yes |
Classpath |
| No |
Artifacts
This operation delegates the consume/produce artifacts decision to the workflow developer.
...