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 environmentAccount will be required on either the plugin input or environment instance. If a value is set on both then, the plugin input will take precedence. See Special Considerations below for instructions on how to create Oracle SaaS FSM account. |
Project Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
...
| 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 PasswordAccount will be required on either the plugin input or environment instance. If a value is set on both then, the plugin input will take precedence. See Special Considerations below for instructions on how to create Oracle SaaS FSM account. |
| 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 900 seconds (5 15 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. |
...
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
...
Oracle SaaS FSM Account
...
Oracle SaaS FSM project type has one object type Setup Tasks with 4 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)
- Functional Area - Finer tuned business name or rule used to defined the business activity or process (Not Required)
- Task Code - Unique id for Setup Task (Required)
In general, the following convention is followed for the File Name (with Path) that way the other attributes can be set for you base on the path without having to enter it again.
Format: "../SetupTasks/<Offering Code>/<Functional Area>/<Task Code>"
| Info | ||
|---|---|---|
| ||
If you are populating from SCM, then by default FlexDeploy will find all zip files that contain "SetupTasks" (case-insensitive) and classify them as Setup Tasks in your project files catalog. TaskCode is determined based on the content of the zip file automatically. If you are creating the file then, you have to manually enter the TaskCode from the FlexDeploy UI. In both cases, by default the Offering Code Functional Area will be set to 2nd and 3rd parts in path starting from the end of the file path. |
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.
...
*
Before using this plugin operation, navigate to Topology → Integrations → Cloud, then create an account with provider OracleFSM for each one of your SaaS environments. This account will store the URL and credentials to make HTTPS requests to your SaaS environment. The account will be reusable by all Oracle SaaS FSM Plugin operations. All fields shown are required.
See Object Type - Setup Task, Object Type - Fast Formula, Object Type - Value Set, etc.. for details on how to configure Files for export.
How to find Task Code for a Setup Task?
...