Highlighted
Honored Contributor.
Honored Contributor.
458 views

Change approval notification is not triggering for 2nd approver(future) after the 1st approval

Hi HP Expert,

Good day! I'm still stuck in figuring out how to trigger the htm email notification for the 2nd approver(future or the 2nd sequence approver) in Change Management.

We have added and approval containing 2 approvers (sequence 1 = approver1 and sequence2=approver2). The email is triggerring normally for the 1st approver once landed in the approval phase.

sequence1 or approver1 = field: current.pending.groups

sequence2 or approver2= field: approvals.required

After the 1st approval is completed; the value of  current.pending.groups is now the previous approver 2; in this update after 1st approval. the notification is not triggering.

I have tried defining it in Chm Approval and Chm Update Notifications, but still no luck.

Your guidance is highly appreciated.

Tags (1)
0 Likes
4 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Change approval notification is not triggering for 2nd approver(future) after the 1st approval

Hello,

Change approval notification is not triggering for 2nd approver(future) after the 1st approval Hello, Could you please share SM App version ? Also can you share the notification definition screenshot ? Ideally RAD us.notify is called whenever you trigger any notification. You can call this RAD under format control/process if you are aware of or some RAD calling functions. Easiest way is format control - subroutines. You can define its parameters like name - notification definition name. And $record as $file (current record). A little bit of tailoring here would be needed. You can search for existing processes using us.notify to see how the parameters are called.

Thanks!

Highlighted
Honored Contributor.
Honored Contributor.

Re: Change approval notification is not triggering for 2nd approver(future) after the 1st approval

Hello Kiran - Thank you for the response.

Were having SM 9.33 with process designer. Here is my notification condition below. We are expecting it to be triggered everytime a change record approval is updated. So upon entry in approval phase. This is activated normally but after the approval of sequence 1, the future approver(approval.required) value now becomes the current.pending.groups, from here we expect it to again activated to send email to the 2nd approver.

Notification name: ChM Change Update - The same notification defined in the Object record(cm3r) under Notification TAB> Update field.

Notif2.JPG

At first we are checking it to be activated purely in PD Worflow and ruleset, but I've noticed that the approval it is still using the Notification. I haven't check the mentioned FC and I would like to check that option as mentioned.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Change approval notification is not triggering for 2nd approver(future) after the 1st approval

If you are using PD, do not try FC, it is not recommended. You can try using macros or write a script in trigger.

However your condition looks correct and if it is triggered the first time, indeed it should trigger the next time if the values are correctly updated. There was another issue with html emails sending to a recipient mentioned as a direct email id. Since you receive one email, I do not think second email should be a problem but still you can cross check from this document : KM00482985
I
 suggest try macros instead, the not same condition works a bit with different syntax in macros but surely works. You can check help server for macros if required. 

Highlighted
Honored Contributor.
Honored Contributor.

Re: Change approval notification is not triggering for 2nd approver(future) after the 1st approval

Agree. I dont have issues with the recipient. Please don't mind the recipient in my screenshot, its just for testing. I'm using the value there as - current.pending.groups in $L.file and no issues about this one.

The condition may not be an issue, as mentioned it is working in the first email sent to 1st approver(instantly once the records enters this approval phase).

Please also note that I have tried rulesets based from the value changes in approvals.required but the html sending ruleset is not auto triggerring. Tried setting it in ruleseset, On Update and After successfull update but still no luck. One thing I noticed that some fields from the approval table is not forwarding the values in cm3r tables. Is ther any dependencies from those?

approvals.req.seq, current.req.seq, approved.req.seq

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.