Resource engagement exception (unexpected behaviour) RRS feed

  • Question

  • Scenario:  I have 4 waterfall type tasks, each following on the other.  Each has a set of resources assigned as per schedule template.  All resources require approval.

    Problem:  When creating engagements for 1 of the 4 tasks, the second one, they go straight through to assigned with a 'No conflicts here!' message.  The other 3 behave as expected, creating an engagement request that needs to be submitted.  (I have used the same resources with the same units of work across the tasks.)

    Question:  Has anybody seen this, and could you perhaps point me in the right direction to stop this from happening?  Here is a link to demonstrate the behaviour.


    Wilhelm van der Merwe | Sydney, Australia

    Thursday, March 15, 2018 3:32 AM