JOC - JobScheduler Operations Center
  1. JOC - JobScheduler Operations Center
  2. JOC-518

Job Chains view refreshes too frequently to allow a user to perform any operation

    Details

      Description

      Current Situation

      • When an order is running, and you view it the Job Chains view, it continually resets/refreshes such that a user cannot correctly select an action from the "Action Menu" for any job or job node.
      • This behavior occurs if either a number of orders are running in parallel for job chains that are visible with the Job Chains view and/or if orders move quickly between job nodes.

      Desired Situation

      • At the point in time when the user hits the "Action Menu" then all refresh operations should be delayed. Incoming events during the period when the "Action Menu" is open are queued. After the "Action Menu" is closed the queued events are processed and a refresh occurs.
      • This behavior could cause errors: if a user e.g. tries to "suspend" a running ad hoc order but requires more time to find/hit the "suspend" action menu item than the order needs to complete, then the "suspend" operation might not be successful for the completed ad hoc order. In this situation the user should be presented the respective error message.

        Activity

        Hide
        XEOPS Datenbank Admin added a comment -

        For us it would be enough if the Action menu would just remain open (no matter what) until the user selects an action or closes the menu manually.

        If something in the background changes (example: the order moves to the next node) and the user selects an action that is now no longer valid (because the order moved to the next node), then the user should just receive an error and the action menu can then close.

        Show
        XEOPS Datenbank Admin added a comment - For us it would be enough if the Action menu would just remain open (no matter what) until the user selects an action or closes the menu manually. If something in the background changes (example: the order moves to the next node) and the user selects an action that is now no longer valid (because the order moved to the next node), then the user should just receive an error and the action menu can then close.

          People

          • Assignee:
            Sourabh Agrawal
            Reporter:
            Mahendra Patidar
            Approver:
            Mahendra Patidar
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1 day
              1d
              Remaining:
              Remaining Estimate - 1 day
              1d
              Logged:
              Time Spent - Not Specified
              Not Specified