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 a single zip file artifact. The csvExport operation can only be used with a FlexDeploy partial package-based deployment project of type Oracle SaaS FSM.
Artifact is a single zip file containing zipped CSV File Packages.
...
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle SaaS FSM Account |
| No* |
Oracle SaaS FSM |
The account will be likely be different for each FSM environment.
Project Properties
Account will be required on either the plugin input or Target. 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. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Oracle SaaS FSM Account |
| No* |
Oracle SaaS FSM |
Account will be required on either the plugin input or Target. 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 |
| No | Maximum amount of time (seconds) to wait for export process to complete after it is started. Defaults to |
900 seconds ( |
15 minutes). | |||
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 |
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 |
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 |
Outputs
...
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
...
This operation will select all available endpoints associated to the environment/instanceTarget.
Endpoint Execution
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 2 object types, Setup Tasks and Fast Formulas.
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 Object Type Attributes: @since 5.6.0.5
- 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.
For Fast Formulas the following convention is followed for the File Name (with Path) → "/SetupTasks/FastFormulas/<Task Code>/<Formula Name>.zip"
| Info | ||
|---|---|---|
| ||
If you are populating from SCM, then by default FlexDeploy will find all zip files and classify a file as Fast Formula if its path contains "SetupTasks/FastFormulas" (case-insensitive), otherwise if its path contains only "SetupTasks" (case-insensitive) it will be classified as Setup Task. In addition, with SCM the TaskCode is determined based on the content of the zip file automatically. 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 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. |
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, Oracle SaaS FSM Object Type - Fast Formula, Oracle SaaS FSM Object Type - Value Set, etc.. for details on how to configure Files for export.
How to find Task Code for a Setup Task?
To initiate the export or import process, Oracle endpoints requires providing a code for the task. Following these instructions to find the Task Code. We are assuming you have access to FSM resource.
Click Navigator > My Enterprise > Setup and Maintenance.
In the Setup and Maintenance work area,
clickclick Manage Setup Content
fromfrom the Tasks panel tab.
To search for the code of a task
On the Manage Setup Content page, click Manage Task Lists and Tasks.
In the Search field, select Tasks and click Search.
In the search results, click the name of the task.
On the Task page, look for value that appears against Code.
Copy the code and use it where necessary