Job Properties Are Not Updated

If two users on different client computers change properties of the same job at the same time, one of the changes might not be done.

This happens because whenever you change a job property, the entire set of job properties is updated, not just the one you change. For example:

  1. Two job properties have these values:
    Copies: 1
    Store: Off
  2. User A changes the value of the Store job property. This change submits a new set of job properties with these values:
    Copies: 1
    Store: Store indefinitely
  3. Before TotalFlow Production Manager can process User A's set of job properties, User B changes the number of copies. User B's set of job properties still has the original value for the Store property, so it has these values:
    Copies: 3
    Store: Off
  4. TotalFlow Production Manager processes User A's set of job properties. Because TotalFlow Production Manager has not yet received and processed User B's set of job properties, the new set of job properties has these values:
    Copies: 1
    Store: Store indefinitely
  5. TotalFlow Production Manager processes User B's set of job properties. Because User B submitted a set of job properties with the old value of the Store property, that value changes back to the old value. The set of job properties now has these values:
    Copies: 3
    Store: Off 

User B expects, and gets, three copies of the job. User A expects the job to be stored, but it is not stored.