Uploaded image for project: 'JOC - JobScheduler Operations Center'
  1. JOC - JobScheduler Operations Center
  2. JOC-1692

Order names should allow more than 30 characters

    XMLWordPrintable

Details

    Description

      Current Situation

      • Users who operate JS1 (branch 1.x) have the option to specify the Order ID individually.
        • JS1 orders are stored in *.order.xml files and carry the Order ID from the file name. Users can specify up to 255 characters for the full path including directories and the file name of the order.
      • JS7 introduces Order IDs that include 
        • an identifying part
        • an optional part that is called the Order Name.
      • JS7 limits Order Names to 30 characters.
        • Users who are used to have more characters available in JS1 orders tend to add a lot of information to Order Names that they can look up using a search operation for orders from the GUI.

      Desired Behavior

      • Users would like to find up to 100 characters for the Order Name as this allows to compatibly use Order Names to classify and to search orders in the JOC Cockpit GUI.

      Maintainer Note

      • The feature request is dismissed.
      • Reasons include that
        • the JS7 Order ID is used for child orders that occur in nested Fork Instructions. Nesting levels include up to 15 instructions. Child orders have to carry the parent Order ID to which the given Branch ID of the Fork Instruction is added. This denies use of Order Names of arbitrary length as they are part of the Order ID.
        • there can be similar instructions in the next future for branching orders that require a consistently limited Order ID.
        • searching for parts in an Order Name makes limited sense: if more than one information item is coded to an Order Name then users have to use ever more complex search expressions to receive results. This is too limited to allow the Order Name to become a candidate for carrying user-defined classifications of orders.
      • Dismissal of the issue does not invalidate requirements, but the proposed solution. Requirements are picked up with issue JOC-1693.

      Attachments

        Issue Links

          Activity

            People

              ap Andreas Püschel
              ap Andreas Püschel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: