Managing deployment levels

Administrators can manage deployment packages through the levels within a development life cycle, where an automation package moves from the development environment to the production environment. An administrator must perform specific actions for each package based on corporate guidelines that outline when to add or adjust the package deployment levels. You can deploy a package to a level and assign that level's package version to a department, user or work group. After you assign the package, Pega Robot Runtime can execute the assigned deployment package on the desktop or virtual machine. 

Pega Robot Manager™ provides the following default deployment levels:

• Development – The level where developers update and maintain the package
• User acceptance testing (UAT) – The level where business users test the package functionality
• Production – The level where case workers use the final package version in a live environment

1. On the Pega Robot Manager dashboard, in the Development level header, click the arrow and select Add deployment to add a new level between the Development and UAT. 
   
2. Click the new level header to edit the name.
3. In the field, enter a name for the new level, for example, QA.
   
4. Press the Enter key to add the new level name. 
   

On the Pega Robot Manager dashboard, click and drag the new deployment level header to adjust the level position.

1. On the Pega Robot Manager dashboard, on the new deployment level header, click the arrow and select Rename.
   
2. In the field, enter a new level name, for example, PHASE 1.
3. Press the Enter key to add the new level name.