Setup Tasks allow for export and import of setup task as a CSV File package (zip file). If supported, scope can be applied to export a subset of the CSV File package data via Export Criteria. Export Criteria can be easily configured via the FlexDeploy during manual file creation. In the case, scope cannot be applied, please see other supported Oracle Saas FSM object types as an alternative solution.
...
Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
Source |
| Object Source Location Type |
|
|
Task Code |
| Unique id for Setup Task |
| |
Export Criteria |
| Export Criteria used to apply scope to a setup task. | ||
Filter Criteria |
| After export, filter criteria is used to apply additional filtering to the setup task. |
...
Export by ExtDefinitionId works but that id is not visible in FSM UI, you can upload this BIP Report
| View file | ||
|---|---|---|
|
ASM_SETUP_CSV_METADATA.xml which is part of Export zip file. Otherwise, filter on a different Attribute Name.| Note |
|---|
Note that there is a known issue with HCM Extract Definitions. Oracle does not update them if they exist, and there isn’t an API available to rename or delete them. The import is reported as successful, but the extract is not updated. Please log an Oracle SR if you would like to see this changed. |
Payroll Flow Patterns
Export using BaseFlowName, plugin will automatically convert to use appropriate FlowId when you use BaseFlowName in export criteria.
...