Undeploy a Visual Application

You can undeploy a visual application that’s deployed to your environment’s Visual Builder instance when it’s no longer required. Undeploying an application is a permanent action that completely removes application metadata and data stored in its database. This action can’t be undone. Before you undeploy, consider the impact of removing your application, especially if the version is live, because once a version has been removed from the system, it can’t be recovered.

• If your visual application was deployed to a Visual Builder instance in the same identity domain as your VB Studio instance, you can manually undeploy the application from your environment’s list of deployments:

  1. In the VB Studio left navigator, click Environments .

  2. If necessary, select the environment where the visual application was deployed to, then click Deployments.

  3. For the visual application you want to undeploy, click Actions and select Undeploy.

  4. In the confirmation dialog box, click Undeploy. If your application was deployed without the version in the URL (indicating a live application), you’ll need to select Yes, I’m sure to confirm your selection, then click Undeploy.

• If your visual application is deployed to a Visual Builder instance in a different identity domain (say, a production instance) or the instance was added to an environment through credentials, you’ll need to add and configure steps in a build job to undeploy the application:

  1. In the VB Studio left navigator, click Builds .

  2. Click + Create Job. Give the job a new name and a description, select the build executor template, then click Create.

  3. On the Job Configuration page, click Steps.

  4. Click Add Step, select Visual Application, then select Undeploy.
     

     Description of the illustration vbs-build-jobs1.png

  5. In Instance, select the Visual Builder instance where the application is deployed.

  6. In the Authorization section, Use OAuth is selected by default. You can also select Use Basic, but OAuth is the recommended authorization method. You should use Basic authentication only if you run into issues with setting up an OAuth connection.

     • With Use OAuth selected, the Authorization is required message indicates that this build step needs to be authorized, which you can do either by clicking Authorize or by running the build manually and entering the credentials when prompted. After authorization, the Authorization has been provided message shows.

     • With Use Basic selected, enter your Visual Builder instance credentials in Username and Password.

  7. In Application URL Root and Application Version, enter the visual application’s root URL and its version. You can find this information from the Deployments tab of the environment where the visual application is deployed.

  8. Click Save.

  9. To run the build job, click Build Now.