Workflows view relies on ordering of numbers provided by database sequence

Current Situation

• The JOC Cockpit makes use of sequences to generate unique identifiers for primary keys in database tables.
• The Workflows view relies on ascending ordering in which unique identifiers are created.
• For use with a clustered Oracle database the ascending ordering of the next identifier from a sequence is guaranteed only if the sequence is created with the ORDER attribute. This is not specified with current sql scripts.
• If the next identifier for the sequence used with the DEP_HISTORY table does not arrive in ascending order, then the Workflows view will pick the wrong, earlier version of the workflow. As a result, after deployment of a new workflow version the workflow is displayed in the Workflows view being "not synchronized" though the latest version of the workflow is in fact deployed to the Controller.
• The problem is limited to use with a clustered Oracle database and can occur arbitrarily depending on the generation of numbers from sequences that are distributed to database nodes.

Desired Behavior

• The JOC Cockpit's Workflows view will use the ordering of deployment timestamps to identify the most recently deployed version of a workflow. The view will not rely on a specific ordering of identifiers created from sequences.

Workaround

• The problem is limited to use of clustered Oracle databases.
• The sequence used for the DEP_HISTORY table must be modified like this:

  ALTER SEQUENCE SEQ_DEP_HIS ORDER