Configure a Build Job to Manage Deployed Visual Apps

If your visual application is deployed to a different identity domain or your application URL includes the version, you'll need to add and configure steps in a build job to perform lifecycle operations. VB Studio provides these options as Visual Application steps that you can configure in a build job and include:

Importing and exporting business object data to and from deployed visual applications
Locking and unlocking live deployments
Rolling back updates to a live version
Auditing and testing visual apps before deploying them
Undeploying visual apps when they're no longer needed

To configure these options in a build job:

In the left navigator, click Builds .
Depending on the option, decide if you want to configure an existing job or create a new one. For example, you might want to audit and test your visual app either as part of the package job, or more likely as a separate job that you'll run before the package job or as part of a merge request.
- To add an option to an existing job, click Configure for the job.
- To add an option as part of a new job, click + Create Job. Give the job a new name and a description, select the build executor template, then click Create.
See Create and Manage Jobs for details.
On the Job Configuration page, click Steps.
Click Add Step, select Visual Application, then choose the option you want to add.

While each option has its own set of parameters, they are all Grunt-based commands that automate the task of continuous integration and delivery for you. See the following for more information about each option:
- For Audit and Test, see Configure a Job to Audit and Test Your Visual Application.
- For Export Data and Import Data, see Configure a Job to Import Data to or Export Data from a Visual Application.
- For Lock, Unlock, and Rollback, see Configure a Job to Lock, Unlock, or Roll Back a Deployed Visual Application
- For Undeploy, see Configure a Job to Undeploy a Visual Application.
When you are done, click Save.