Preview-Publish-Transport Section
  • 30 Jul 2021
  • 3 Minutes to read
  • Contributors
  • Dark

Preview-Publish-Transport Section

  • Dark

What is the Preview-Publish-Transport Phase in the EdgeReady Cloud?

Ideally, any app development process follows a series of steps:

  1. Creating the Business Process and Business Functions
  2. Modeling the flow in the App Process Modeler
  3. Creating the UI Screens in the App Designer
  4. Adding Behavior for each component and screens in the App Behavior Section
  5. Calling the BOS for each screen from the Integration Builder.

The Preview/Publish/Transport section is accessed once all the stages of App Development are complete. The icons can be found on the top right of the App Process Modeler canvas.

Why do we need the Preview/Publish/Transport Section?

In the EdgeReady Platform:

  • Preview demonstrates a ‘Live’ app based on the ‘Deployment Settings’ (e.g. display in Browser or Device).
  • Publish helps to publish the App
  • Transport helps to transfer the App to the subsequent Environment (e.g. Development to Quality or Quality to Production).

How to do an App Preview?

If Preview is clicked, the following screen popup appears: The deployment platform and device preview is chosen.


In the current version, the Preview/Publish/Transport option is available for Hybrid Apps only.

On selecting the Preview, an intermediate screen appears.
generating preview.png

The preview of the app screen is displayed. The preview option is available for different devices.
generated preview.PNG

How to Publish the App?

Once the App screens and settings are previewed and verified, it is ready to be published. The user clicks the Publish button to publish the App. The following popup appears.
to publish.png

The user selects Next. The next popup requests for details of the App. The version number for the publish has to be specified along with the comments. This enables the same App to be published multiple times.

Once all the fields are entered, the user clicks Publish. The progress is displayed in the next popups.

During PublishingPublishing Complete
publishing progress.pngpublished successfully.png

Once the App is successfully published, the final popup is displayed with instructions to download and access the App.
published message.png

How to Transport the App?

Once the App is previewed and published, it undergoes two stages where the App is Transported from the Development environment.

  1. The App is transported to Quality for testing.
  2. The App is transported from Quality to Production for deployment and rollout.

To transport the app, the user clicks the Transport icon. The following popup appears.

Clicking the Transport button moves the App with the respective version to the Quality environment. In the next popup, the respective Roles, Apps, and Screens are checked. 

Once it is transferred, the following popup appears. 

After successful transport, users can log in to the Quality Environment with their credentials and check the new App with their respective version. 

The user can refer the Mobile App generation document for a detailed procedure to download the App.

Quality Landscape

In the quality environment, the new projects that have been transferred appear on the dashboard with a "New Commit" highlight. 

Users can select the Projects and redirect to the App Process Modeler section where they can be Approved/Rejected by the Admin. 

The following screen depicts how the transported Project appears on the App Modeler canvas. The Admin can Accept or Reject a Project after verification. In the below example, different versions of the same project are approved and listed.

For different versions of the same Project, the Quality/Production Environments support only a single Active version. For instance, if one version is made active, the remaining versions are made inactive by default. 

Accepting the Transport follows the steps:

The version with comments are entered.

In the next popup, the app elements are checked and verified. Once checked, the user clicks Accept. Accepting the Project enables the transfer Process. 

Transport ProgressTransport Complete

Once the Project is successfully transferred, it is listed along with the previously accepted Projects on the left. Users must note that the current version of the project became the Active version

Production Landscape

The active Project can be Approved or Rejected. Only Approved Projects can be transported to the Production Environment. 

Once the user clicks the Approve button, the following popup appears.

By specifying the version number and comments, the user can Transport the Active App to Production. This step follows another approval process where the App elements are verified once again. 

Once Approved, the Project is transferred to Prod and displayed in the list of Approved Projects on the left. 

The Admin cannot alter or preview the contents of the Project that have been Transferred to the Quality or Production environments. They can only revert changes (to previous versions) and verify the existing contents.

On verification, if the Project does not meet the required standards, the user can click Reject. This process is displayed in the popups below. 

Rejection ProgressRejection Complete

If a particular version is Rejected, the previous version becomes the active version by default. 

Was this article helpful?