Vancouver Patch 5
We set up a project checklist as a survey with a trigger condition on the project table defined as 'demand is not empty and state changes to pending'. This seems to be working as expected.
However, we recently ran into a situation where a project manager changed the status of a project to Work in Progress then changed it back to Pending a short time later. This caused a second checklist to be created which we do not want. I don't see an obvious way to prevent this.
Is there any way to do this on the trigger? Or do I need to add something to the Auto Assessment Business Rule that checks to see if there is an existing checklist for the project? Or is there some other way to do this?
Thank you
