---
title: "Preview-Publish-Transport Apps"
slug: "preview-publish-transport-section"
updated: 2022-06-10T04:56:22Z
published: 2022-06-10T04:56:22Z
canonical: "help.pillir.io/preview-publish-transport-section"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.pillir.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Preview-Publish-Transport Apps

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

An App development process follows a series of steps:

1. Creating the [Business Process](https://help.pillir.io/docs/how-to-create-a-new-business-process) and [Business Functions](https://help.pillir.io/docs/business-functions-and-roles#how-to-create-a-new-business-function)
2. Modeling the flow in the [App Process Modeler](https://help.pillir.io/docs/app-process-modeler-canvas)
3. Creating the UI Screens in the [App Designer](https://help.pillir.io/docs/app-designer-overview)
4. Adding Behavior for each component and screens in the [App Behavior Section](https://help.pillir.io/docs/java-script-js-builder)
5. Calling the BOS for each screen from the [Integration Builder](https://help.pillir.io/docs/integration-builder).

The **Preview/Publish/Transport** section is accessed once all the stages of App Development are complete. The icons are seen on the top right of the App Process Modeler canvas. ![ppt.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/ppt%281%29.png)

## 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 **preview mode** is chosen.

![preview](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/preview.png)

NOTE

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

On clicking **Next**, an intermediate screen appears.

![preview-intermediate screen](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/preview-intermediate%20screen.png)

The preview of the app screen is displayed. The following preview options are available:

1. Zoom - 50% - 150%
2. iPhone or Android Vertical preview mode
3. iPhone or Android Horizontal preview mode
4. iPad or Windows or Tablet Vertical preview mode
5. iPad or Windows or Tablet Horizontal preview mode
6. Web preview mode

![Previewofapp](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/Previewofapp.png)

### Preview in a Workflow App

In a workflow app, after the '**Generating Preview**' popup window, the '**Preview your business function workflow**' popup window appears. This window displays a list of all the workitems created in the app. The workitems can be in any state or assigned to any user role. The user can do one of the following actions:

- Click **New Request** to create a new workitem in preview mode
- Click **Select** to view/edit an existing workitem in preview mode.

If a new workitem is created it is added to the list of workitems in 'draft' state; If an existing workitem is edited, the state of the workitem changes accordingly.

The user can view the error message of workitems with the error icon and rectify it accordingly. Errored workitems cannot be previewed.

![workflow-preview](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/workflow-preview.png)

NoteThe workitems created in published Apps alone are visible under the **Workflow Console** tab.

## 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](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/to%20publish.png)

NoteIn a Workflow app, the apps created for each user role is listed in the above screen.

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.

![publish.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/publish.png)

After all the fields are entered, the user clicks **Publish**. The progress is displayed in the next two popup screens.

| During Publishing | Publishing Complete |
| --- | --- |
| ![publishing progress.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/publishing%20progress%281%29.png) | ![published successfully.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/published%20successfully%281%29.png) |

Once the App is successfully published, the final popup is displayed with instructions to download and access the App. ![published message.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/published%20message%281%29.png)

NoteThe '**Publish**' process follows the same steps for both workflow and non-workflow Apps. In workflow apps, each role(lane) will be published as a standalone app.

## 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.

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627637851135.png)

Clicking the **Transport** button moves the App with the user-selected version to the Quality environment. The following items of an App are transported in the backend:

- DB structures
- BOS objects
- Integrated systems

In the next popup, the respective Roles, Apps, Plugins, Systems, Tables, Screens, Services, Icons, Images, Assets are checked.

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627637951319.png)

Once it is transferred, the following popup appears.

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627638748652.png)

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

NOTEThe user can refer the **[Mobile App](https://help.pillir.io/docs/mobile-application-edgeready-applications)** 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.

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627640595476.png)

Users can select the Projects and redirect to the [App Process Modeler](https://help.pillir.io/docs/business-functions-and-roles) 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. ![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627643492106.png)

NOTEFor 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. ![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627643828253.png)

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 Progress | Transport Complete |
| --- | --- |
| ![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627643980563.png) | ![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627644005066.png) |

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**.

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627644109533.png)

## Production Landscape

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

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627644314830.png)

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

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627644391850.png)

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.

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627644976842.png)

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

![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627645228705.png)

NOTEThe 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 Progress | Rejection Complete |
| --- | --- |
| ![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627645803407.png) | ![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1627645812373.png) |

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