Predecessor Status in JobPlans / Process Flows / Work Flows

Discussion created by Laura_Albrechto_270 on Nov 7, 2013
Latest reply on Jun 15, 2018 by LauraAlbrecht608310


I would like to know if any other customers out there have issues / problems with users not setting the predecessor status in jobplans.

What I mean is when you draw "lines" in a jobplan it automatically sets a dependency to the predecessor job.  However, by default, UC4 doesn't care how the job completes (good or bad). 

We have instructed our users to go to Options => Settings and modify the Process Flow tab so that a default status for predecessor for internal tasks is set to ANY_OK. 

However, this relies on our users to set this, which is not always a good thing.

We have created tools to try and capture this when objects are migrated to PROD, but again, if users create objects manually in PROD (which they shouldn't do - but you know how that goes) then we could have this situation.

If anyone else has this issue - can you let me know how you handle / address it?  I do have a ticket open with Support and we are pursuing SQL to fix this, but just looking for any other solutions out there.