JITL - JobScheduler Integrated Template Library
  1. JITL - JobScheduler Integrated Template Library
  2. JITL-527

When copying/moving a job or an order then all assigned calendars are removed

    Details

    • Type: Fix Fix
    • Status: Released (View Workflow)
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.12.6
    • Fix Version/s: 1.12.8
    • Labels:
      None

      Description

      Current Situation

      • If a job or order that is assigned calendars and periods is moved (by modifying the file name) then all run-time definitions are removed in the renamed job or order.
      • The assignment of calendars and periods is stored in the CALENDAR_USAGE table. This is the leading location for this information. When renaming the job or order then two events are created by JobScheduler Master. One is the delete_oldJob event and one is the create_newJob event. Currently the record in the CALENDAR_USAGE table is deleted with the delete_oldJob event. Therefore the renamed job or order does not have any run-time definitions.

      Desired Behavior

      • When moving a job or order then the run-time definitions should be maintained.
      • The database is still the leading system
        • That means: If changing the meta data or the run time in the xml configuration file, this will have no effect if a calendar usage is found in the database
      • Moving a file should not overwrite start time definition e.g. when moving from test to prod the start times from prod should be used
        • Please note that also run times in local configuration will not be overwritten if a calendar usage is found in the database (see JOC-502).

      Use cases

      • Calendars: The calendar definition
      • Calendar Usage: The asssigned calendars, periods and restrictions for one order/job.
      • Starttime. The calculated starttime of an order/job

      Job/Order x ---- >copied/moved to y, y is new

      Same environment (e.g. renaming a job/order):
      Starttime: Same as x
      Calendar Usage: will be created for y. When moving will be deleted for x
      Meta Data in y: same as x

      Other environment (e.g. deploying from test to prod):
      Starttime: Will be recalculated on the base of the calendar definitions in Other environment.
      Calendar Usage: Will be created for y. When moving will be deleted for x. Calendar assignments for calendars that are not found in the db will be removed from the calendar usage.
      Meta Data in y: will be updated.

      Job/Order x ---- >copied/moved to y, y is already there and will be overwritten.

      Same environment:
      Starttime: Will be unchanged for y (because the db is the leading system. Also see JOC-502)
      Calendar Usage: Will be unchanged (because the db is the leading system. . Also see JOC-502)
      Meta Data in y: will be unchanged

      Other environment:
      Starttime: Will be recalculated on the base of the calendar definitions in Other environment.
      Calendar Usage: Calendar assignments for calendars that are not found in the db will be removed from the calendar usage.
      Meta Data in y: will be updated

      Note

      This only works with starttime that have been assigned with the a realase > 1.12.8

      Impact

      • When moving a job or order that is assigned calendars then the job or order will have no run-time definition any longer. The run-time configuration has to be reassigned manually with JOC Cockpit.

        Issue Links

          Activity

          Hide
          Patrick added a comment -

          Hi,

          I don't understand why this bug has been closed ?
          Thanks for your answer.

          Show
          Patrick added a comment - Hi, I don't understand why this bug has been closed ? Thanks for your answer.

            People

            • Assignee:
              Santiago Aucejo Petzoldt
              Reporter:
              Uwe Risse
              Approver:
              Uwe Risse
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: