Exports CSV File Package(s) from an Oracle SaaS FSM server to the file system. This operation can be used from an a utility workflow, which can also be augmented to sync the files to a source control management system (such as Git or Subversion). This allows the Oracle SaaS FSM project which is used for build and deployment to source from a source code repository rather than directly from a development SaaS instance.
| Tip |
|---|
Endpoint TipThis operation uses HTTPS to communicate remotely to the Oracle SaaS FSM server, and therefore, can be executed on any endpoint (including LOCALHOST). |
Target Properties
Property Name | Property Code | Required | Description | ||
|---|---|---|---|---|---|
Oracle SaaS FSM Account |
| No* | Oracle SaaS FSM Account will be required on either the plugin input or Target. If a value is set on both then, the plugin input will take precedence. See Special Considerations below for instructions on how to create Oracle SaaS FSM account. |
Project Properties
...
Property Name
...
Property Code
...
Required
...
Description
Inputs
Input Name | Input Code | Required | Description | ||
|---|---|---|---|---|---|
Oracle SaaS FSM Account |
| No* | Oracle SaaS FSM Account will be required on either the plugin input or Target. If a value is set on both then, the plugin input will take precedence. See Special Considerations below for instructions on how to create Oracle SaaS FSM account. | ||
API Timeout |
| No | Maximum amount of time (seconds) to wait for export process to complete after it is started. Defaults to 900 seconds (15 minutes). | ||
Download Folder |
| No | Absolute or relative target folder path. Relative path will be assumed in FD_TEMP_DIR. | ||
Stop on Error |
| No | Stop exporting CSV File Package, if any error occurs. If false or not specified, exporting of other CSV File Packages will continue. | ||
JSON File Path |
| Yes | Absolute or relative path to a file containing a json array of tasks. Relative path will be assumed in FD_TEMP_DIR. You can either
See special considerations for more information about format and contents of JSON File Path. |
Outputs
Description
Artifacts
This operation does not produce any artifacts.
...
The JSON objects within the "tasks" array can contain these 5 keys.
Key | Required | Description |
|---|---|---|
TaskCode | Yes | Code of the Setup Task. |
BusinessObjectCode | No* | Code of the business object whose attribute is used as the scope. Leave value empty to export entire Setup Task. *Required to apply scope to Setup Task object type. |
AttributeName | No* | Name of the attribute of the business object used as the scope. Leave value empty to export entire Setup Task. *Required to apply scope to Setup Task object type. |
AttributeValue | No* | Value of the named attribute that defines the filter criteria. Provide multiple values using ## I.E. VALUE1##VALUE2. Leave value empty to export entire Setup Task. If you provide more than one value using ## separator, individual file for each value is downloaded. *Required to apply scope to Setup Task object type. Otherwise, all supported non-Setup Task object type (I.E. Value Set, Lookups, or Flexfields), only Attribute Value and TaskCode are required. BusinessObjectCode and AttributeName can be left empty. See JSON object 5 example in FSMSetupTasks-Development.json |
FileName | No* | Name of zip file. If no provided attribute value is used as zip file name. Spaces in name are replaced with _. If multiple values are provided for AttributeValue using ## separator, you can provide same number of elements for FileName as well for individual file. |
...