Page Comparison

Deploy the Apex application to Deploys an Oracle APEX application (produced by a build workflow using the buildAPEX plugin operation) to a target database. This operation requires one or more exported SQL files, these files can be either specified by using the APEX SQL Files (FDAPEX_SQL_FILES) on Project Properties or the plugin will deploy the ".sql" files in the artifacts folder. Files in artifacts folder during Deploy execution are result of Build workflow execution associated with Project Version selected for deployment. @Since 5.0.0.1.2 version of FlexDeploy APEX plugin, you can also deploy individual page files, which will require you to maintain page level SQL files in your SCM folder. In order to achieve partial deployment model, create project of Generic type with files sourced from your choice of SCM.If there are supporting database objects for Apex application being deployed, you must deploy them as separate project using   This operation manages deployment of builds produced by both the Full Deployment and Partial Deployment models. 

Any supporting database objects for the application are outside the scope of this operating, but can be managed in a separate project and workflows using the JDBC Plugin.

This plugin supports deploying the same APEX application to the same database. This requires setting the Offset. This situation is not normaltypical, so most likely you will not have to worry about offsetoften the offset can be ignored.

• If the application has never been deployed and you do not currently have an offset, the plugin can generate the offset. Just select Use APEX Offset (FDAPEX_USE_OFFSET), make sure you note the offset value used and set the property APEX Offset Value (FDAPEX_OFFSET) for the next deployment.  

• If you know the offset, select Use APEX Offset (FDAPEX_USE_OFFSET) and set the property APEX Offset Value (FDAPEX_OFFSET).

...