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.

...

Offering code and Functional Area attributes were available prior to 5.6.0.5, They are not needed and hence removed.

Special Considerations

Export Criteria

Export Criteria criteria are details about the Setup Task used to filter the setup data during CSV export. The Export Criteria export criteria are useful when the user only wants to export, and ultimately deploy, a subset of the setup data to target Oracle SaaS environment(s). Due to Oracle API limitations, only a subset of the exportable Setup Tasks support criteria functionality. It is known that some export and import processes can timeout which is likely due setup data being too large (>10MB) and/or taking too much execution time (>5 minutes). In those cases, use the Export Criteria to divide the setup data into more manageable deployment chunks.

...

• 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.xml which 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.xml which is part of Export zip file.

Source from Development Environment

...

Filter Criteria

@since 7.0.0.2

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. A couple reasons export criteria is preferred:

1. There are known issues with Oracle’s Export API where API requests would timeout. Speculation says this is due to size limitation (default is 10MB). Export criteria will keep exported artifacts smaller and help prevent timeouts.

2. Execution time will be much faster with Export Criteria versus exporting the entire Setup Task. Execution time on the Oracle’s side mostly depends on the number of business objects associated to the task and size of data for each.

While export criteria only works for specific tasks and attributes combinations; filter criteria are configurable for any task and attribute.

Filter Criteria Operators

Filter criteria support a set of operators to help users achieve filtered CSV file packages. See the below for a full list below:

1. Equals

2. Equals (case insensitive)

3. Not Equal

4. Includes

5. Includes (case insensitive)

6. Doesn’t Include

7. Empty

   • Empty includes column values containing empty string or white space characters only.

8. Not Empty

   • Not Empty includes column values not containing empty string or white space characters only.

9. Regex

   • Applies a regex expression to the column value

10. Latest Version

    • Assuming the column contains a version number like MAJOR.MINOR.PATCH (1.0.1) or similar. This operator will find the latest or most recent version in the entire column.

    • If the attribute name (column) selected with this operator does not follow a version like format, then this operator will not behave as expected.

Source from Development Environment

In order to download a CSV file package from an environment, at the minimum you must configure a file for a setup with the following steps:

1. On the File Catalog or Package Files page click CREATE

2. Select “Setup Task” as the Type

3. Search for your Setup Task by task name or task code. FlexDeploy will give you suggestions as you are typing.

4. (optional) If the task supports filtering the setup dataExport Criteria, then Export Criteria will be shownsection will be shown. Configure as needed.

   • (optional) For each business object, select an attribute name and set a value. Think of the business object as a CSV file and the attribute name as a column in the CSV file. Multiple values can be filtered for by delimiting with ## (i.e. VALUE1##VALUE2). To filter by more than one attribute name in the same CSV file, click the Add button at the bottom of the business object. Naturally, if you can click the remove button to remove a filterone attribute name in the same CSV file, click the Add button at the bottom of the business object. Naturally, if you can click the remove button to remove a filter.

5. (optional) Configure Filter Criteria as needed.

   1. Click ADD to create a rule.

   2. Select a business object (CSV file) or type in your own if the business object you’re looking for is not in the drop down list.

   3. Select an attribute name (column) or type in your own if the attribute name you’re looking for is not in the drop down list.

   4. Select an operator from the available list.

   5. Type in the value you wish to filter by. By design, if the selected operator does not require a value i.e empty, not empty, regex, etc…, then the value column will not display.

6. Click Save to save your configurations. FlexDeploy will tell you the list exported CSV files which will eventually be in the exported CSV file package. Now you can add this file to a Package and perform export and import.

Note that File Name (with Path) will automatically be populated based the task and if there are any export criteria defined.

...

Source from SCM

...