JOC denies "Remove order" for a file based order on a distributed job chain

General

• The function "Show Configuration" in JOC should available exclusively for file-based orders.
• The function "Remove order" in JOC should available exclusively for temporary orders.
• JOC expects a @file attribute in the <file_based> element of the order to decide if it is file-based or not.
• A file-based order of a distributed job chain provides the @file attribute in the <file_based> element of the JobScheduler answer iff the order configuration file is stored in the live directory of the respective JobScheduler.
  It is recommended that the file-based order is stored in every JobScheduler member of a cluster.

Current Situation:

• The function "Show Configuration" is inactive if the file-based order doesn't stored in the live directory of the respective JobScheduler.
  This is ok because the respective JobScheduler cannot send the content of the order configuration file to JOC.
• The function "Remove order" is active if the file-based order doesn't stored in the live directory of the respective JobScheduler which is not intended.
  So it is possible to remove file based orders by JOC.

Desired Situation:

• File based orders should not be removed by JOC