Publish and manage applications

1. Publish an application

After you build and debug a project, you can publish it as an application that robots can then request and run. To publish the application, click the publish button on the editor toolbar and fill in the required information.

Application version number

• The version number consists of three segments. A developer manually enters the first two segments in the editor when publishing the application. The server-side automatically increments the final segment by 1 after a successful publication.

• When a robot client runs an application, it automatically pulls the latest version of the application file from the server.

Application publishing address

• Cloud: This is the default publishing method, which publishes the application to the server. At runtime, the robot automatically pulls the corresponding version of the application file from the server.

• Local: This method publishes the application to the local file system of the client. If you use a local application, you must import the application file to the server before a robot can run it. Only on-premises servers support importing application files. The public cloud does not support local applications.

2. Test and release an application to production

During development, an application often requires testing before it can replace the existing production version. You can use the application name to distinguish between test and production versions. For example, if the application name is `send_msg`:

1. Test phase: You can add a suffix to the application name when you publish the project. For example, you can name it `send_msg_test` and run your tests.

2. Release to production: You can publish the project as an application named `send_msg` to replace the production version.

3. Manage applications

You can manage published enterprise applications and components on the Enterprise Applications page. The available operations include listing, delisting, and approving applications.

• Listing and delisting. An application is listed by default after it is published. If you delist an application, all its versions become unavailable. You can relist a delisted application.

  Important

  When you delist an application, any tasks that are currently running the application are not affected and will continue to run until completion. However, new tasks that attempt to run the application will fail.

• Assignment. An administrator assigns the application to users, so they do not need to request access.

• Approval. After a user requests an application, an administrator with management permissions for Enterprise Applications can approve or reject the request.