Robotic configuration files

Consider a solution that uses a web application. During the application discovery, you realize that the application has three different URLs for training, testing, and production. How does a developer adjust the project and solution for deployment? While the developer can create three different solutions that adjust the start page URL for the web application, it raises issues of maintainability and consistency between the solutions when other changes to solution take place.

To address such a scenario, Pega Robot Studio™ provides a Configuration project item. The Configuration project item stores different configurations for a single solution. As a developer, before creating a deployment package for the solution, you can add configuration files to create different deployment packages based on each configuration file.

You can use the Configuration project item to set the properties of a control to different values and run or deploy a single project using each of the property-value configurations. In this way, you use a single solution to create multiple deployment packages of the solution.

You can add any configurable value, property element, and match rules values to the configuration project item.

When using Interaction Framework and Configuration project items in a multi-project solution, it is a best practice for all projects to have configuration project items that share the same name. Doing so ensures that the controller project has all the necessary configuration property values.