exportWebCatalog (OAC)
- Karl Henselin
- Chandresh Patel
- Muthu Sankaralingam
Extracts WebCatalog objects from an OAC server to the file system. This operation is only supported for Package-based projects.
This operation is especially useful to automate the syncing of catalog items to a source control management system.
Endpoint Tip
This operation uses HTTP operations to communicate remotely to the OAC server, and therefore, can be executed on any endpoint (including LOCALHOST).
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OAC Account |
| Yes | The OAC account includes essential properties such as the URL, Username, Password, and OAuth details for the OAC instance. Cloud account credentials are required for downloading or uploading catalog items. You can manage the OAC account via the Integrations > Cloud page. In FlexDeploy versions 9.0.0.2 or earlier, three separate properties (FDOAC_SERVER_HOST, FDOAC_USER, FDOAC_PASSWORD) were used instead of the OAC account. If you are upgrading from FlexDeploy 9.0.0.2 or earlier, the OAC cloud account will be automatically created from the target properties (URL, Username, Password). A separate cloud account will be created for each target. See Configuring OAC Cloud Account for additional details. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OAC WebCat Object Path |
| Yes | The WebCatalog path to be recursively exported. Separate folders with a forward slash (/) (e.g. /shared/Custom/Financials). Default value is "/shared/Custom". |
OAC Analytics WSDL Path |
| No | The path to the analytics WSDL. We don’t recommend changing this option unless the OAC instance you are using has a different path to the analytics WSDL. Use at your own risk. Default value - /analytics-ws/saw.dll/wsdl/v12 |
Discover Sub-Files |
| No | Select the objects to make their sub-files to be discoverable in the file catalog. |
Project File Includes |
| No | Controls files included from Project Files. Enter expressions separated by ##. Leave empty to select all files. Begin or end the expression with * for simple wildcards. Otherwise, regex is used. (e.g. /Custom/*##*.xdo##*Risk Management*##(.*)Workflow Notifications(.*) @since 9.0.0.1 |
Project File Excludes |
| No | Controls files excluded in Project Files. Enter expressions separated by ##. Leave empty to select all files. Begin or end the expression with * for simple wildcards. Otherwise, regex is used. (e.g. /Custom/*##*.xdo##*Risk Management*##(.*)Workflow Notifications(.*) @since 9.0.0.1 |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Export Folder |
| No | Absolute or relative target folder path. Relative path will be assumed in FD_TEMP_DIR. |
Copy Object Permissions |
| Yes | Copy object with current permissions. If false, parent folder permissions in the deploy environment will be used. |
Keep Timestamps |
| No | Export object with timestamp details. |
Artifacts
This operation does not produce any artifacts.
Endpoint Selection
This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the target. Selecting a specific resource will result in the selection of endpoints associated with the target which have that resource defined.
Endpoint Execution
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where the previous step may have been executed. Changing this value to "All" will result in execution on all selected endpoints.
Related content
- style