Skip to main content

Project Explorer properties

Suggest edit Updated on December 9, 2021

The property grid on the Project Explorer shows basic properties for each component the project contains, as well as project-level properties for deployment, Pega platform integration, references, and runtime messages.

Project-level properties impact the deployment of the project, including Pega platform integration and runtime messages, as shown in the following figure:

Project properties
Figure showing project-level properties on the Property Grid.

When a project component is highlighted in Project Manager, the properties grid shows high-level information specific to that component, as in the following figure:

Figure showing the project-level property grid for a specific component like an
                    automation.

To show the project-level properties, click the Information icon beside the project name.

i icon
Figure showing i icon on the Project Manager.

Deployment properties

Deployment properties define the version number of your project when deployed and if the version gets incremented for each deployment.

Deployment will create a deployment package file, with the format [project name].pega. The deployment package is an assembly file, which is a compiled version of the project for use with the Runtime/Agile Desktop application.

  1. Check Increment Version to have each deployment increment the version number.
  2. Enter a Version number for your project.
    The Version has two parts: MajorVersion.MinorVersion. Both parts must be numeric. If you choose Increment Version, the MinorVersion number is incremented. The MajorVersion must be updated manually.

Pega platform integration properties

In the Pega platform integration properties, specify options for using Assisted Sign-on (ASO) and Start my day services with Pega platform.

ASO and Start my day properties affect the applications that Robot Runtime or Agile Desktop runs every day.

Integration options

ASOAllows Pega platform to integrate with AsoManager.
ASO queueAllows AsoManager activities received from Pega platform to be queued by the Interaction Framework.
Start my dayAllows Pega platform to integrate with StartMyDay.
Start my day queueAllows StartMyDay activities received from Pega platform to be queued by the Interaction Framework.

With ASO, you can quickly implement assisted sign-on, which reduces the amount of time required to sign into the applications Robot Runtime users work with every day.

  • When starting Robot Runtime, you can use an Enter Credentials window to enter and maintain all of the persisted user ID and password information.
  • You can enter non‐persisted or changed information before proceeding or choose persisted information. Optionally, the Enter Credentials window can be reopened via an automation for credential modifications and it can show all credentials for all applications or the credentials of one application at a time.
  • When individual applications present their login screen, the user ID and password fields can be automatically filled and the Login button clicked.

Note: You can configure the Assisted Sign-On component to prevent user IDs and passwords from being stored on the hard drive.

With Start my day properties, you can specify activities that a Robot Runtime or Agile Desktop user sees when launching Runtime/Agile Desktop. This list can include non‐Pega programs and URLs, as well as Pega Robot Studio solutions. Users can use the Manage Applications dialog to prioritize the order in which applications are launched.

In addition, each Runtime/Agile Desktop user can add to and remove from the list of processes to be started by Runtime/Agile Desktop. The items on the list are specific to the user.

Project references

You can add references to your project that are required for your C# scripts.

When you click the More icon, the Manage references dialog displays, as in the following figure:

Manage references dialog showing references you can add for C# scripts.

The Current tab shows the references used in the Project. You can also add references from:

  • .NET (GAC or Global Assembly Cache)
  • Pega (installation folder)
  • PublicAssemblies folder (in AppData)

Runtime message definitions

Create message definitions to give users important information during Robot Runtime.

  1. Click the More icon to open the Message definitions dialog, as shown in the following figure.
    Message definitions
    Figure showing the Message definitions dialog.
  2. Click Add to create a new message definition.
  3. Enter a Code to identify the message definition.
  4. To show the Code in the message window, click Include code in dialog.
  5. Add a Caption to to display as the message window title bar.
  6. Add an icon to display in the message window, if desired.
  7. From the dropdown list, select the buttons that should display on the message window.
  8. Use Default button to specify the button that should be highlighted when the message displays.
  9. Type the message in the Message box.
  10. You can Test your message to see if it displays as you want.
  11. Click Submit to save your message and add it to the message manifest.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us