Content Comparison

The FlexDeploy OAC solution allows enables developers to either source the WebCatalog objects either from a development OAC instance or directly from a source control system. To When sourcing WebCatalog objects from source control WebCatalog objects there are two main practices that , two key practices must be followed. For fully automated process see Automate check-in of development OAC catalog items to SCM.

First, the web catalog objects stored in directory structure of the WebCatalog objects in the source control system must maintain the same directory structure as the mirror that of the OAC WebCatalog.   The While the root path directory in your the source control repository can be anythingvary, but the internal directory structure under it must exactly precisely match that of the WebCatalog. For example, notice consider the following WebCatalog path for the report below:

The path above must match the path in the source control system as we see below.

For the above example, FlexDeploy project source configuration will be configured with "OAC/shared/Financials"as the sparse folder checkout folders when using Git. This would ensure that all objects under that folder will be discovered as WebCatalog objects and the file path starts with /shared/Financials which matches the WebCatalog path in OAC.

Secondly, the files stored in source control should be named with the following extensions corresponding to the object type.  The extensions are important to both ensure the deployment operation is handled correctly, and to make it easier to identify and search for these objects in FlexDeploy.