Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • PIPEFORCE Enterprise 7.0 or higher

  • You have a valid PIPEFORCE Developer account

Introduction

In PIPEFORCE an app groups together resources like scripts, templates, configurations and others which solve a certain business task together. Any pipeline, form or workflow for example is part of exactly one app.

...

In this tutorial you will learn how to create and publish an app using the online workbench in a few simple steps.

1 - Create a new app with the online workbench

The easiest way to create a new app is by using the online workbench. To do so, follow these steps:

  1. Login to your portal https://YOUR_NAMESPACE.pipeforce.net.

  2. Navigate to LOW CODE → Workbench.

  3. Select the node app in the tree and click the plus icon at the top.

  4. The new property view opens:

    1. As a property key use the value global/app/MY_APP/config/app. Replace MY_APP with the name of the app you would like to create, for example myapp24. Do use only lower case letters and don’t use special characters or spaces!

    2. As mime type select application/json.

  5. Click SAVE:

    Image RemovedImage Added
  6. The new property configuration was created and pre-filled with some data.

  7. Here you can make later changes to configure your app.

  8. For now don’t do any changes and leave it as it is.

  9. Navigate to All Apps in order to show the apps overview page.

  10. Here also your app should be listed.

  11. Congrats, you’ve created your first custom app!

...

If you click your app, currently nothing happens since we did not add any logic to this app for now. This will change in the next tutorials.

2 - Release your app

For security and productivity reasons any app created this way is by design only visible to developers, but not to other users: It is automatically staged in development mode in the beginning.

...

Info

Staging
Staging is the process of hiding an application from the production context until it was fully tested and approved for production. After this approval it will be switched to a production context so that it will be visible and usable by the target users. PIPEFORCE has two different concepts of staging:

  • Staging by permission (soft staging)
    An app can be switched to production by changing its permission. The advantage here is that it is very quick and easy to do so. The downside is that other apps in the same namespace are already in production mode and side effects could potentially harm them. Therefore, you have to be careful in development since apps in development and in production stage reside side by side in the same namespace.

  • Staging by namespace
    There are two namespaces: development and production. In the development namespace apps are developed. Also services like databases or other microservices can be in this namespace. Once development and testing is finished, the app will copied to the production namespace. The advantage here is that the two namespaces separate each app with its environment from each other. Chances are very low that development on an app will affect apps in production. The downside is that it is much more effort to put such an app from development to production stage. Staging by namespace requires at least two Enterprise instances or a Corporate license.

Next tutorial: Tutorial: Create a new form