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. |
...
Equals
Equals (case insensitive)
Not Equal
Includes
Includes (case insensitive)
Doesn’t Include
Empty
Empty includes column values containing empty string or white space characters only.
Not Empty
Not Empty includes column values not containing empty string or white space characters only.
Regex
Applies a regex expression to the column value
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.
| Note |
|---|
With export and filter criteria it is highly suggested to avoid overlapping of file definitions between two or more Setup Task files. When two files deploy overlapping data, it will become difficult to track which package/project deployed changes and to prevent issues of deploying unwanted changes to the target SaaS environment. To guarantee no data overlap, review the CSV File Package from the csvExport and compare with other executions using the same Setup Task to confirm there are no duplicate rows. |
Source from Development Environment
...