Oracle SaaS FSM Object Type - Flexfields
- Karl Henselin
- Emily Simon
Flexfields are one grouping of Setup Tasks. Make use of the Flexfields object type to export and import individual Flexfields by Flexfield Code.
Object Type Identification
When populating files from source control management (SCM), FlexDeploy will classify all zip files containing "SetupTasks/Flexfields" (case-insensitive) in their path as a Flexfield.Â
File Extensions
.zip
Object Type Code
FLEXFIELDS
Attributes
Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
Task Code |
| Unique id for Setup Task | Â | Â |
Flexfield Code |
| A set of placeholder fields associated with business objects and placed on the application pages to contain additional data. This can be found in FSM UI on any flexfields setup task (IE. Manage Key Lookups). |
| |
Rollback Source Type |
| Where to retrieve file when initiating a rollback deployment. | Project Version  | Project Version, SCM Revision, Backup Repository, and Rollback File SCM Revision and Rollback File options are only available when the project has SCM details configured, and Backup Repository should only be used if the FlexDeploy server and project are configured to take backups. |
Rollback File |
| The associated file to deploy which will roll back this file. Only applicable when Rollback Source Type is Rollback File | Â | Any project file sourced from SCM |
Considerations
Flexfield Deployment
The flexfield on the source SaaS environment must be in Deployment Status of Deployed before the csvExport operation is executed. If the flexfield is not Deployed, then the exported CSV File Package will not contain data for that flexfield and ultimately, import will not deploy those changes.Â
Source from Development Environment
In order to download file from an environment, you must configure file for Flexfields as shown below. Note that File Name (with Path) should be entered first in format - /SetupTasks/Flexfields/<TASK_CODE>/<FLEXFIELD_CODE>.zip. File name is used as Flexfield Code, and parent folder is used as Task Code. Task Code can be selected from drop down list if necessary. Also, Flexfield Code can be entered manually as well if necessary. Make sure to update File Name (with Path), respectively, if either of previous attributes are edited manually. Steps - Enter File Name in proper format, Click Evaluate, then click OK and eventually click Save to save configurations. Now you can add this file to Package and perform, export and import.
Source from SCM
The following convention is generally used for the File Name (with Path) in Source Code Repository. "/SetupTasks/Flexfields/<TASK_CODE>/<FLEXFIELD_CODE>.zip". If you follow these conventions, then you do not have to configure Files manually. You are ready to perform export and import using FlexDeploy package once files are discovered in FlexDeploy.
Task Code is derived from zip file sourced from SCM.
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, click Manage Setup Content from 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
- style