This operation exports file(s) from the build Oracle SaaS environment or your SCM repository, waits for all exports processes to complete, and then downloads results as single as zip file artifact. The csvExport operation can only be used with a FlexDeploy partial deployment project of type Oracle SaaS FSM.
...
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| Oracle SaaS FSM Account | FDFSM_CLOUD_ACCOUNT_CODE | No* | The Oracle SaaS FSM account with all the required properties like instance URL, Username, and Password. The account will be likely be different for each FSM environment. |
...
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Oracle SaaS FSM Account | FDFSM_INP_CLOUD_ACCOUNT_CODE | No | The Oracle SaaS FSM account with all the required properties like instance URL, Username, and Password. |
| API Timeout | FDFSM_INP_TIMEOUT | No | Maximum amount of time (seconds) to wait for export process to complete after it is started. Defaults to 300 seconds (5 minutes). |
| Save Export Result File | FDFSM_INP_SAVE_EXPORT_RESULT_FILE | No | Saves a comparison result file to the reports directory as a JSON file. The JSON file provides a summary of the comparison process and represents the table shown in the Comparison Details section of the user interface. |
| Save Export Report File | FDFSM_INP_SAVE_EXPORT_REPORT_FILE | No | Saves a comparison report file to the reports directory as a Excel file. The excel file provides comparison reports for each of the business objects that were processed. For each business object, a report each for Only in Configuration 1, In Both With Mismatch, and Only In Configuration 2, as applicable is provided. |
| Save Export Summary Report File | FDFSM_INP_SAVE_EXPORT_SUMMARY_REPORT_FILE | No | Saves a comparison report file to the reports directory as a Excel file. The excel file provides a summary of the process results, which displays a list of all the processed business objects, and whether their processing completed successfully, or with errors. |
...
*Oracle SaaS FSM Account will be required on either the input or environment instance. If a value is set on both then, the input will take precedence.
Object Types (2)
Setup Task
Setup Task Object Type Attributes:
- File Name (with Path) - absolute file path matching structure in Oracle SaaS FSM environment (Required)
- Offering Code - Typically the highest-level or starting point of application configuration (Not Required) @before 5.6.0.5
- Functional Area - Finer tuned business name or rule used to defined the business activity or process (Not Required) @before 5.6.0.5
- Task Code - Unique id for Setup Task (Required)
Before 5.6.0.5 the following convention is followed for the File Name (with Path) → "/SetupTasks/<Offering Code>/<Functional Area>/<Task Code>.zip"
On and after 5.6.0.5 were removed from the attributes so the following convention is followed for the File Name (with Path) → "/SetupTasks/<Task Code>.zip"
Fast Formula
@since 5.6.0.5 .
Fast Formula Object Type Attributes:
- File Name (with Path) - absolute file path matching structure in Oracle SaaS FSM environment (Required)
- Task Code - Unique id for Setup Task (Required)
- Fast Formula - The base formula name you want to filter your Fast Formula Setup Task by. This value is typically the formula name in all uppercase. (Required)
For Fast Formulas the following convention is followed for the File Name (with Path) → "/SetupTasks/FastFormulas/<Task Code>/<Formula Name>.zip"
Project Files
When populating files from source control management (SCM), by default FlexDeploy will classify all zip files containing "SetupTasks/FastFormulas" (case-insensitive) in their path as Fast Formula. All zip files containing "SetupTasks" (case-insensitive in their path) will instead get classified as Setup Task. In addition, with SCM the TaskCode is determined based on the content of the zip file automatically; assuming the zip file is a valid CSV file package.
If you are creating a Fast Formula file then, the TaskCode is inferred from the 2nd last part of the path by default.
If you are creating a Setup Task file then, the TaskCode is inferred from the file name by default.
In both cases, you can always manually override the values as needed or write a custom default script for the attribute (Task Code, Formula Name, etc..) in question.
If you are on 5.6.0.4 or earlier, then Offering Code and Functional Area attributes are inferred from the 2nd and 3rd parts of the path starting from the end, respectively. Otherwise, Offering Code and Functional Area will no longer be displayed.
Create a new file
From the project files screen, click the create button, add your file name following the previous format, click evaluate, review attributes set automatically from File Name (adjust path and re-evaluate as necessary), and finally click ok when you're done.
...