Question
Patient advocate foundation
IN
Last activity: 16 Oct 2024 4:54 EDT
What are the option to trigger email when code change happens in Pega production
What are the option to trigger email when code change happens in Pega production other than deployment manager ?
Thanks,
Ajay
-
Reply
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
CA
I highly recommend locking all the rulesets in Production. The delegation ruleset should be given access ONLY to the Business Access group and restricted access from other access groups.
Thanks,
Ramesh
Patient advocate foundation
IN
To avoid deployment to production without permission. Do we have any other ways ?
Thanks,
ajay
Proximus
BE
If you want an external check of what's happening in your system then you can externally monitor the below tables
pr4_history_rule pr_log pr_data_admin
as well as pr_operators
This way you'll be able to detect a jar loaded, a live change, a change in config as well as whether someone changed or updated its own operator to be able to do something.
This allows to monitor whether anything happens, it won't avoid it to happen but it won't be hidden neither.
Otherwise you could also create 2 different admin access group. One without the grants to upload jar, to change their operator, to change any DSS, etc.. They can more or less see lots of things without being able to modify.
Still, I feel that an external check (when you cannot avoid giving some grants to a set of users) is useful and provides some safety.
Rgeards
Anthony
Patient advocate foundation
IN
Proximus
BE
If you've got no idea while knowing the tables then then it will be tricky
This requires some external scripting and you need a DB access.
Regards
Anthony
Patient advocate foundation
IN
i can able to see entry in this pr4_history_rule table if any changes happens or any deployment done.
How can i trigger email when i have new entry in this table ?
Thanks,
ajay
Pegasystems Inc.
CA
Leverage Deployment Manager to ensure a seamless experience during deployments. Release Admin has the control to deploy the packages to higher environments, and you have traceability for your deployments.
Proximus
BE
Hello,
This is indeed the clean option but this doesn't prevent any admin to push some content which was not requested or to perform an unexpected change.
I understood the request on how to be able to trace any change.
Regards
Anthony