Setup Tasks allow for export and import of the entire setup task as a CSV File package (zip file).
Object Type Identification
- When populating files from source control management (SCM), FlexDeploy will classify all zip files containing "SetupTasks/FastFormulas" (case-insensitive) in their path as Fast Formula, otherwise zip files containing "SetupTasks" (case-insensitive in their path) will instead get classified as Setup Task.
File Extensions
- .zip
Object Type Code
SETUP_TASK
Attributes
| Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
| Source | SOURCE | Object Source Location Type | SCM | SCM, CLOUD |
| Offering Code | OFFERING_CODE | Typically the highest-level or starting point of application configuration | ** | |
| Functional Area | FUNCTIONAL_AREA | Finer tuned business name or rule used to defined the business activity or process | ** | |
| Task Code | TASK_CODE | Unique id for Setup Task | FILE_NAME* |
Related Project Properties
| Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
Considerations
- See csvExport for details on how find Task Code for a Setup Task.
- *When creating a Setup Task (not from SCM), the Task Code is inferred from the file name by default. Otherwise, the Task Code is pulled from the CSV file package stored in SCM.
- @since 5.6.0.5
- Offering Code and Functional Area are no longer supported attributes.
- The following convention is generally used for the File Name (with Path) → "/SetupTasks/<Task Code>.zip"
- @before 5.6.0.5
- The following convention is generally used for the File Name (with Path) → "/SetupTasks/<Offering Code>/<Functional Area>/<Task Code>.zip"
- **Offering Code and Functional Area attributes are inferred from the 2nd and 3rd parts of the path starting from the end, respectively