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

Clicking the link for non-current JobScheduler instance in any view results in an error

    Details

      Description

      Current Situation

      • Assume a user has to manage two JobScheduler instances "Scheduler1" and "Scheduler2" with JOC Cockpit.
      • The "Scheduler1" instance is selected from the top right drop-down list and is the current JobScheduler instance.
      • When the user opens the Audit Log view then the option "Current JobScheduler" is unchecked. If the Advanced Search is used to search for a job chain, e.g., /sos/dailyplan/CreateDailyPlan, then audit log entries from both JobScheduler instances are displayed.
      • When the user clicks on audit log entries of "Scheduler2", e.g. follows the link with the job chain name to navigate to the Job Chains view then the exception JOC-400 is displayed
        JOC-400 jobSchedulerBadRequestException: SCHEDULER-161 There is no job_chain '/sos/dailyplan/CreateDailyPlan'

      Desired Behavior

      • When JOC Cockpit displays audit log entries from multiple JobScheduler instances and a user clicks on the object name then navigation should work for all objects similar to the objects from currently selected JobScheduler instance.

      Maintainer Notes

      • A number of views, e.g. the History view, behave similar to the Audit Log view, therefore the solution is applied to all views.
      • The solution includes to remove links on objects from the result list that are not available from the currently selected JobScheduler instance. Following links from a result list should not perform implicit switching of the JobScheduler instance.

        Activity

        Hide
        XEOPS Datenbank Admin added a comment -

        XEOPS is in disagreement with this point under Maintainer Notes:
        "The solution includes to remove links on objects from the result list that are not available from the currently selected JobScheduler instance. Following links from a result list should not perform implicit switching of the JobScheduler instance."

        We feel that if the results from multiple schedulers are shown it is because the user wants to see them (otherwise the user would not have unchecked the "Current JobScheduler" box). If the user wants to see the entries, then it is probably because they also want to be able to click on them and be navigated to the corresponding object (even if that means that the JobScheduler instance will be switched).

        Imagine if this link were not available and the user wanted to go there. They would have to switch the scheduler themselves and then re-execute the previous search (which might be tedious if they entered lots of criteria).

        Show
        XEOPS Datenbank Admin added a comment - XEOPS is in disagreement with this point under Maintainer Notes: "The solution includes to remove links on objects from the result list that are not available from the currently selected JobScheduler instance. Following links from a result list should not perform implicit switching of the JobScheduler instance." We feel that if the results from multiple schedulers are shown it is because the user wants to see them (otherwise the user would not have unchecked the "Current JobScheduler" box). If the user wants to see the entries, then it is probably because they also want to be able to click on them and be navigated to the corresponding object (even if that means that the JobScheduler instance will be switched). Imagine if this link were not available and the user wanted to go there. They would have to switch the scheduler themselves and then re-execute the previous search (which might be tedious if they entered lots of criteria).
        Hide
        Andreas Püschel added a comment -

        I get your point, however, consider that switching the JobScheduler instance includes a number of implications:

        • The user might not have permissions for the view in the target JobScheduler instance.
        • The object, e.g. a job chain, might not exist any longer in the target JobScheduler instance (has been renamed, removed etc.)
        • Implicitly switching the instance when following a link for e.g. a job chain, could be confusing. This includes change of the theme, And this includes a certain delay for loading permissions and theme for the target instance.

        All views offer a list box in the right upper corner to switch the Master instance. This translates to the fact that you can e.g. remain in the Audit Log view and with a single click switch the JobScheduler instance to a different Master to follow links.

        Show
        Andreas Püschel added a comment - I get your point, however, consider that switching the JobScheduler instance includes a number of implications: The user might not have permissions for the view in the target JobScheduler instance. The object, e.g. a job chain, might not exist any longer in the target JobScheduler instance (has been renamed, removed etc.) Implicitly switching the instance when following a link for e.g. a job chain, could be confusing. This includes change of the theme, And this includes a certain delay for loading permissions and theme for the target instance. All views offer a list box in the right upper corner to switch the Master instance. This translates to the fact that you can e.g. remain in the Audit Log view and with a single click switch the JobScheduler instance to a different Master to follow links.
        Hide
        Vicky Patidar added a comment -

        Issue is being Fixed
        Tested with snapshot release

        © 2002-2018 Software- und Organisations-Service GmbH.
        All right reserved.
        JOC Cockpit9153d379a56df77885a56c80d8cd4b8b0ecc8b5f 1.12.6-SNAPSHOT (2018-10-02)
        
        Show
        Vicky Patidar added a comment - Issue is being Fixed Tested with snapshot release © 2002-2018 Software- und Organisations-Service GmbH. All right reserved. JOC Cockpit9153d379a56df77885a56c80d8cd4b8b0ecc8b5f 1.12.6-SNAPSHOT (2018-10-02)

          People

          • Assignee:
            Sourabh Agrawal
            Reporter:
            Mahendra Patidar
            Approver:
            Mahendra Patidar
          • Votes:
            1 Vote for this issue
            Watchers:
            5 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