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. |
...
Manage HCM Extract Definitions - this requires use of ExtDefinitionId, which is not visible on FSM UI. Other values do not work with Export CSV API. See https://docs.oracle.com/en/cloud/saas/human-resources/21d/oedmh/payflows-20167.html#payflows-20167 to write an adhoc BIP report to query the underlying FSM tables and retrieve name & associated ExtDefinitionId. Other option would be to manually export from FSM UI to capture ExtDefinitionId from
ASM_SETUP_CSV_METADATA.xmlwhich is part of Export zip file.Payroll Flow Patterns - this requires use of FlowId, which is not visible on FSM UI. Other values do not work with Export CSV API. See https://docs.oracle.com/en/cloud/saas/human-resources/21d/oedmh/perextdefinitionsb-13198.html#perextdefinitionsb-13198 to write an adhoc BIP report to query the underlying FSM tables and retrieve name & associated FlowId. Other option would be to manually export from FSM UI to capture FlowId from
ASM_SETUP_CSV_METADATA.xmlwhich is part of Export zip file.
Filter Criteria
...
Filter criteria are a list of rules used to filter the setup data after CSV export. This means if export criteria are configured, then filter criteria are applied to the result of that. The filter criteria are useful when the user only wants to deploy, a subset of the setup data to the target Oracle SaaS environment(s) and export criteria alone is not sufficient. It is recommended to start with export criteria first and after use filter criteria to fill any gaps if additional filtering is required by your use case. While export criteria only works for specific tasks and attributes combinations; filter criteria are configurable for any task and attribute. A couple reasons export criteria is preferred:
...