Question
Virtusa Consulting Services
IN
Last activity: 23 Apr 2023 21:57 EDT
How to avoid warning for Email Account related to User principal name reference with D_pxGetApplicationSettingValue
Hi Everyone,
This mail is regarding my query related to Microsoft Graphs configuration in Pega 8.7.1 version:
We upgraded from Pega 8.36 to 8.7.1 last week. The main purpose of going for an upgrade is to make use of the Microsoft Graphs functionality for email configuration in order to enable more security. We were using the basic authentication in our older version of pega. Now we are facing a lot of challenges in configuring the MSGraphs. We are reaching out to the pega team for a few solutions, but here I am talking about a way to just avoid the warnings in the email account rule. Below is the list of warnings to use the D_pxGetApplicationSettingValue instead of the constant value for User principal name (email id) and Authentication Profile in the format =D_pxGetApplicationSettingValue[OwningRuleset:"Test:01-01-01",Purpose:"TesAppSettings"].pySettingValue
Hi Everyone,
This mail is regarding my query related to Microsoft Graphs configuration in Pega 8.7.1 version:
We upgraded from Pega 8.36 to 8.7.1 last week. The main purpose of going for an upgrade is to make use of the Microsoft Graphs functionality for email configuration in order to enable more security. We were using the basic authentication in our older version of pega. Now we are facing a lot of challenges in configuring the MSGraphs. We are reaching out to the pega team for a few solutions, but here I am talking about a way to just avoid the warnings in the email account rule. Below is the list of warnings to use the D_pxGetApplicationSettingValue instead of the constant value for User principal name (email id) and Authentication Profile in the format =D_pxGetApplicationSettingValue[OwningRuleset:"Test:01-01-01",Purpose:"TesAppSettings"].pySettingValue
Here the challenge comes. We have around 70 email listeners in our application for creating cases for different countries. If I follow the best practice to avoid the warning I will end up in creating 70 Application Settings rules. Is creating 70 application settings rules the only way to achieve this or do we have any alternative? It Really requires some expert comments on this. Kindly post your comments.
Thanks
Blue Rose Technologies
NL
For the warning related to the use of D_pxGetApplicationSettingValue.
There is a concept called Application Setting where you will define a value for all the environments (dev, UAT, SIT, Prod) in one rule and at runtime based on the environment it will pick the value. This is the recommended approach in new versions of Pega (You can think of this concept as something similar to Global Resource setting but with a better feasibility as you don't have to define the DSS with different values in different environments).
So if instead of hard-coding the value if you use this concept then this warning will be gone.
Please check the below link to understand this concept in detail:
https://academy.pega.com/topic/application-settings-feature/v2/in/29846/29871/31541
Virtusa Consulting Services
IN
@VikashK99 Hi Vikash, thanks for the response.
I understand that usage of Application Settings rules, can solve this problem. But the actual concern is creating 70+ Application Settings rules for all the Email Accounts in our application.
So checking if there is any alternative to acheive this.
Thanks
Blue Rose Technologies
NL
@SeshuKesan Ideally this is a recommendation from Pega and even if you have so many applications my recommendation would be to create this application settings for all the rules as if you dont do this then if future there might be some new implementation which related to this which might impact your application. Also all the recommendations from Pega are to make sure your application runs smoothly and you face least performance issues so better to go for this change even if it takes time. If you still want to just suppress this warning then there is a way to suppress OOTB guardrail warnings of Pega. Even though it is not recommended at all but if you want you can check the below link for the same:
https://support.pega.com/discussion/how-customize-add-or-remove-guardrail-warnings
Tranzformd
AU
@SeshuKesan Pega now recommends to use Application Settings (earlier Rule-System-Settings) and refer the same using OOTB Data page D_pxGetApplicationSettingValue[OwningRuleset:"Test:01-01-01",Purpose:"TesAppSettings"].pySettingValue. Referring the Global Resource Settings (GRS) with Data Page other than this will also throw informational warning.
Virtusa Consulting Services
IN
@smothe Hi Santhosh, thanks for the response.
Since we have 70+ email listeners in our application, we are required to create those many number of Application Settings rules (considering one Application Settings rule per one email account).
I am trying to check if there is any alternative approach to achieve this by eliminating creation of those many rules.
Thanks
Areteans
AU