Question

Where are Project Configurations on Deployment? (without Robot Manager or Package Server)

Hi- our end user would like to be able to make changes to deployed solutions via Project Config Files. (Such as variables set in Runtime Config files).

Where are these files located? How can they be modified after deployment without Pega robot manager or Package Server?

Currently we are deploying our solution by moving the .manifest and .openspan files to a production drive. The user then accesses these files via Runtime. If the end user wants to make changes to the configuration file deployed in the solution- how can he do this without Pega Robotic Manager? Everything I have seen requries PRM.

Steps to Reproduce

I deploy my solution to my local. Then i copy and paste my .manifest and .openspan files to a shared drive. Then I launch runtime on a different machine and open those files on the shared drive.

Correct Answer
October 21, 2019 - 10:46am

Project Configurations cannot be modified by the end user. To change them, you must build a new package. If you would like some setting sot be external, then you should create your own config file to store them in. You'd then need to write automations or code to read/write to that new file in whatever location you place it. If they are user-specific settings, then I prefer to use the CredentialStore component to store user setting. It already can read/write to a file on the user's machine for you. When using the CredentialStore, you just need to be sure to place whatever value you are storing in both the user and password fields as it is expecting both to be supplied.

Comments

Keep up to date on this post and subscribe to comments

Pega
October 21, 2019 - 10:46am

Project Configurations cannot be modified by the end user. To change them, you must build a new package. If you would like some setting sot be external, then you should create your own config file to store them in. You'd then need to write automations or code to read/write to that new file in whatever location you place it. If they are user-specific settings, then I prefer to use the CredentialStore component to store user setting. It already can read/write to a file on the user's machine for you. When using the CredentialStore, you just need to be sure to place whatever value you are storing in both the user and password fields as it is expecting both to be supplied.