Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Scope

  • Use Case: a
    • A number of orders that have been added to a job chain - either from a file order source watching incoming files, from Ad Hoc orders or from permanent orders - should be forced into serialized processing in a predefined sort order.
  • Solution Outline: a
    • A single job is added to the top of a job chain and that will
      • suspend all incoming orders and check completeness until a predefined idle timeout is reached and no more orders are expected,
      • sort the orders in alphabetical sequence of the order id and move them to the next job node in the job chain.
  • ReferencesReference: https://sourceforge.net/p/jobscheduler/discussion/486122/thread/a66295bb/

Solution

  • Download sort_orders.zip
  • Extract the archive to any folder within the ./config/live folder of your JobScheduler installation.
  • The archive will extract the files to a folder sort_orders. 
  • You can store the sample files to a any folder as you like, the solution does not make use of specific folder names or job names.

...