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.

Object Type Identification

• When populating files from source control management (SCM), FlexDeploy will classify all zip files containing "SetupTasks" (case-insensitive in their path) will get classified as Setup Task. This assumes the other object types do not take precedence.

File Extensions

• .zip

Object Type Code

SETUP_TASK

Attributes

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 Details

Please follow help provided in UI to enter attribute values for export criteria. See known issues below.

• 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

In order to download file from an environment, at the minimum you must configure file for Task Code as shown below. User can start typing name or code of a task and FlexDeploy will display a list of suggestions to choose from. Task Code can be entered manually as well if necessary. Note that File Name (with Path) will automatically be populated based the task and if there are any export criteria defined. If the task does not support scope (export criteria), then the table will be empty. In addition, FlexDeploy will tell you the list exported CSV files which will eventually be in the exported CSV file package.

Click OK and eventually click Save to save configurations. Now you can add this file to Package and perform, export and import.

Source from SCM

The following convention is generally used for the File Name (with Path) in Source Code Repository. "/SetupTasks/<Task Code>.zip" for entire setup task or "/SetupTasks/<Task Name>/<Attribute Value>.zip" for a scoped setup task. If you follow these conventions, then you do not have to configure Files manually. You are ready to perform export and import using FlexDeploy package once files are discovered in FlexDeploy.

Task Code is derived from zip file sourced from SCM.

How to find Task Code for a Setup Task?

To initiate the export or import process, Oracle endpoints requires providing a code for the task. Following these instructions to find the Task Code. We are assuming you have access to FSM resource.

1. Click Navigator > My Enterprise > Setup and Maintenance.

2. In the Setup and Maintenance work area, click Manage Setup Content from the Tasks panel tab.

3. To search for the code of a task

   1. On the Manage Setup Content page, click Manage Task Lists and Tasks.

   2. In the Search field, select Tasks and click Search.

   3. In the search results, click the name of the task.

   4. On the Task page, look for value that appears against Code.

   5. Copy the code and use it where necessary.