Exports CSV File Package(s) from an Oracle SaaS FSM server to the file system. This operation can be used from an 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.
...
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| Oracle SaaS FSM Account | FDFSM_CLOUD_ACCOUNT_CODE | No* | Oracle SaaS FSM Account will be required on either the plugin input or environment instance. 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. |
...
| 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 non-Value Set Setup TasksTask. |
| 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 non-Value Set Setup TasksTask. |
| 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. *Required to apply scope to Setup Task. In the case on non-Value Set Setup Tasks. In the case of Value Set Setup Tasks Setup Task object type (I.E. Value Set, Lookups, or Flexfields), only Attribute Value and TaskCode are required. BusinessObjectCode BusinessObjectCode and AttributeName can be left empty. See JSON object 5 example in FSMSetupTasks-Development.json |
...