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.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Object Type Identification
...
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. |
...
Please follow help provided in UI to enter attribute values for export criteria. See known issues below.
Manage HCM Extract Definitions
...
To export an HCM Extract, use the PER_MANAGE_EXTRACT_DEFINITION Task Code.
...
If you want to filter by ExtDefinitionId, 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. Otherwise, filter on a different Attribute Name.
Payroll Flow Patterns
...
Export using BaseFlowName, plugin will automatically convert to use appropriate FlowId when you use BaseFlowName in export criteria.
| Info |
|---|
The Payroll Flow Patterns task will work only for custom tasks, seeded ones will not get exported. The Flow Status should be active as well. |
Filter Criteria
@since 7.0.0.2
...
All configured rules are joined together with AND operations. For example, if 2 rules are configured for a given business object, then both rules must resolve to true to keep a row in the csv file. Logical or is not supported between rules. You can filter by multiple values in a given rules rule by separating the values with the delimiter ## (i.e. ClickShipCollect1##ClickShipCollect2).
...