Hello; We have a request whose demand owner is person A. And request status is waiting demand owner approval. In this status each day a reminder email is sent to demand owner. Person A changes his department and I changed demand owner to person B. But the system still sends reminder email to person A. How could I disable sending email to person a or replace person a wih person b. Regards
Our experience has indicated that tokens are evaluated when the step is entered and are not reevaluated if they are changed. We have seen this behavior with tokens set for notifications and security. Even when the Approval Details list shows the new person, security only is enabled for the user specified by the token when the step was enabled.
If the token specifies a security group, access is more dynamic in that the security group membership is evaluated at the time of page load. At least this is the behavior for security access. I don't know for sure it works this way on notifications but my guess is that it would.
as a workaround for this specific situation, you can create a new transition for this step, implement it in the workflow as a transition to the same step, log on with an admin user (the admin user should be set in the step security) and execute the transition. In this manner, PPM will re-resolve the tokens and reset the timeout. After you execute the transition, you can disable it in the step source definition.
--remember to kudos people who helped solve your problem
You can configure a timeout on the step, then have the timeout loop back to the step. This would reevaluate the tokens and pick up the new values. The notifications would not be reminders but rather new notifications but the addresses would be changed. You would not want a short timeout on this kind of setup. Maybe you could send daily reminders, then have the step time out and reinitialize weekly or something similar that would meet your needs.
Another thought: you can configure a notification on the request type to send email whenever the seeded Assigned To field in the request header changes. This could be used to notify the new assignee that the request should be looked at.
Please remove reminder selection from the step and clear reminder cache from database(db table is knta_notif_txn_parents. change reminder flag). don't use reminder selection to send reminder to users. apply workaround solutions. For example, you can add one more step and put timeout to send reminder. There is a bug in ppm about reminder.
Jim is right. HP doesn't take this as a Bug. In fact, if I remember correctly, the reminder process has been working the same way ever since 5.5. I wish they could provide us some easier options because currently, once the Reminder starts, the only way to stop it :-
- Transition the Request out from that step once somehow (approval, delegate or even a loop to re-set would do)
- Clean up the entries related to that particular Notification in these 2 tables. knta_notif_txn_parents & knta_notif_txn_recipients