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. |
...
Export Criteria are details about the Setup Task used to filter the setup data during CSV export. The 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 have been known to 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.
Support for those Setups which are missing Export Criteria likely need to go through Oracle support before going through Flexagon support.
...
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:
On the File Catalog or Package Files page click CREATE
Select “Setup Task” as the Type
Search for
...
your Setup Task by task name or task code
...
. FlexDeploy will
...
give you suggestions as you are typing.
If the task supports filtering the setup data, then Export Criteria will be shown.
(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 values with ## (i.e. VALUE1##VALUE2). To filter by more than one attribute name for a business object, click the Add button at the button of the business object. Naturally, if you can click the remove button to remove a filter.
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 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
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.
...