I am facing very peculiar problem. We are using 71. SP8. We have configured our server for Demand Management and has defined workflows. In this we have many stages, Open, business approval, ready to merge, sign-off etc etc.
Issue is - Whenever a task is done, user progresses it by changing the next responsible PM, adding a note with description and clicking the "Done" button. This triggers a mail to the new PM with a note added by previous PM. However, this note is always 2 stages previous one and not the lates one. Say for ex in the following sequence 1. User-A changes PM, addes note1 and progresses 2. User-B receives no messgae. Then this user changes PM, adds note2 and progresses 3. User-C recieves note1. Then this user changes PM, ads note3 and progresses 4. User-D receives note2.
So you can see in above sequence ideally User-C should have recieved note2 but he is receiving note1.
Can anyone guide me what is happening here, why always one step old message is being sent? Any issue with our exchange server?
The behavior you describe indicates the notification of the Assigned To change is sent when the field value is changed. The note, though, is saved when the Save button is clicked. Try entering the note, click Save, then set the Assigned To field to the new value.
yeah, the steps mentioned by Jim worked. But I wonder what if we need to- 1. Write a note 2. Change the Assigned to field 3. click Save.
From end user perspective this should be the ideal scenarion - isn't it? This is because there might be a case where after adding note, the decision gets changed and he doesn't want to change the Assigned to field. In this case, the last saveed note will become invalid, isn't it?
Yes you are right, there is a limitation in PPM. Even i tried to replicate the scenario and was finding the same problem. Also i was trying to update some of out of box fields using trigger on event of save.
But still the mail notification is having old remarks itself :-(