The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Project and Portfolio Management Practitioners Forum
Showing results for 
Search instead for 
Did you mean: 

Notification Issue

Regular Collector

Notification Issue


Below is the field and the notification pattern used in our request type
 Field Name                       Token
Current Environment     P_CURR_ENV
QA approver                     P_APP_QA
Now if we have the value in the Current Environment as QA

Notification Recepient  configured as 
security group ID    [REQD.P.P_APP_[REQD.P.P_CURR_ENV]]

the [REQD.P.P_APP_[REQD.P.P_CURR_ENV]] would resolve to [REQD.P.P_APP_QA], this will contain some security group. So will there be any issue in sending the mail to the security group.


Also, is it better to send notification from Decision rather than configuring them on Execution step, kindly advise on this.

Esteemed Contributor

Re: Notification Issue


It's not possible: [REQD.P.P_APP_[REQD.P.P_CURR_ENV]] --> [REQD.P.P_APP_QA]

Instead, you can use case when in request type rules depend on P_CURR_ENV token value. for example:

case when [REQD.P.P_CURR_ENV] = 'QA' then [REQD.P.P_APP_QA]
case when [REQD.P.P_CURR_ENV] = 'TEST' then [REQD.P.P_APP_TEST]
end case) as env_value
from dual

The rule result has to be written in a token. Then you can use it for send notification.

PS: please inform us if it work for u.

IT Governance Professional
& PPM Solution Architect
Regular Collector

Re: Notification Issue

The one mentioned works properly, but just wanted to know the how good and bad is this method of populating the mail receipeints.

Regarding configuring the notification, which is better configuring on execution step or there any difference in performance when configuring the notification on decision.


Jim Esler
Honored Contributor

Re: Notification Issue

We have used User Defined Tokens to fabricate notification recipient lists and have found them to be very flexible and useful. We put notifications on Decision Steps and Execution Steps bases solely on when the trigger conditions are encountered.  There is no difference in performance based on the kind of step involved.

//Add this to "OnDomLoad" event