I've been rummaging around on community but I'm still hitting a brick wall on a process. I'm really hoping someone will come up with something to fix this.
After speaking to another LANDesk customer we pinched their idea of having the ability for EndUsers to be able to add themselves as an affected user to a Major Incident via SelfService.
So the theory is once the user clicks the Action - I am Affected not only is a child incident created but they populate an I Am Affected Collection. Using this collection I put a precondition before my I Am Affected action to check they weren't already there to hide the action and prevent them adding themselves numerous times (pesky users can't be trusted, have to stop them from being able to do things!!). This works great, however, once the child incident is created and flows down through the process it passes my condition as the collection is on the Parent Major Incident not the child - so yes LANDesk is working but not as I want it.
I have tried numerous things but all involve the 2 things LANDesk won't let me do, have 2 preconditions in a row or be able to reference $CurrentUser$ from a calculation (not planning the upgrade to 7.6 for a while where I'll be able to avail of that). I've added a screenshot of the process - hopefully it'll make more sense. Basically want I want is for the action I Am Affected to only be available when the incident is a Major Incident and when the user hasn't already used it.
many thanks for any suggestions