Send Email Policy and Timer Question
We've added a Send Email policy to the Approved state for an asset with a timer set at 2 months. No other options are set (entrance to state, save, etc are all blank). I would expect that this would result in an email being sent once two months has elapse but this is not what is happening.
An email is being sent as soon as the asset enters the approved state. This isn't how it should work. Does this need to be set differently?
Thanks,
An email is being sent as soon as the asset enters the approved state. This isn't how it should work. Does this need to be set differently?
Thanks,
4 answers
I tried to replicate this issue, but was unable to do so. Does the Review page indicate that the policy ran? It should contain the text 'Email sent successfully.'
The email policy does not stop other emails from being sent. For example, reviewers may still receive a notification indicating that the asset entered the approved state. The policy only sends an additional email that is defined in the policy configuration.
The email policy does not stop other emails from being sent. For example, reviewers may still receive a notification indicating that the asset entered the approved state. The policy only sends an additional email that is defined in the policy configuration.
Hi Sheehan,
I think I described it badly. What seems to be happening is that once the timer value is reached, RAM is sending the email every day. It's not just a one time thing which is what was expected. Is it supposed to continue the send the email every day once the timer expires?
Thanks,
I think I described it badly. What seems to be happening is that once the timer value is reached, RAM is sending the email every day. It's not just a one time thing which is what was expected. Is it supposed to continue the send the email every day once the timer expires?
Thanks,
It is supposed to repeat at what interval you set while it is in that state.
If you set it to two months then it should repeat every two months as long as it is in that state.
If you have it set to two months and it waits two months for the first notification, and then it does daily after that then there is some error occurring after the policy was run but before it updated the database to say run again in two months. In that case the timer policy job runs once a day and it would see that the time to run policy has not changed and it is now past that time so it runs it again.
Rich
If you set it to two months then it should repeat every two months as long as it is in that state.
If you have it set to two months and it waits two months for the first notification, and then it does daily after that then there is some error occurring after the policy was run but before it updated the database to say run again in two months. In that case the timer policy job runs once a day and it would see that the time to run policy has not changed and it is now past that time so it runs it again.
Rich
Comments
Hi Rich,
It doesn't seem to be waiting. We set the time for 6 months out. The next day it started sending one email each day.
Then that is a bug. We will need the logs for around 10PM thru 1AM of the last time a mail was sent. Timer Policies are processed in the evening around that time. There must be an error occurring at that time because it should be resetting the timer to another six months. Please open a defect and attach the logs.
Hi,
I confirm this behavior in RAM 7.5.1.1
Is a defect already opened for this? If yes is the problem solved in newer versions?
I confirm this behavior in RAM 7.5.1.1
Is a defect already opened for this? If yes is the problem solved in newer versions?
Comments
Hi
Could this be related to the APAR:
PM73536: [wi 73620] RAM - policy is executed without following its timer's schedule
http://www-01.ibm.com/support/docview.wss?uid=swg1PM73536
Regards,
François
1 vote