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

Advanced Search in Audit Log view should consider the profile parameter "Max. number of Audit Log entries"

    Details

      Description

      Current Situation

      The profile parameter Max. number of Audit Log entries is not used to limit the results in the Audit Log view independently from the current filter or "Advanced Search" operation.

      Also in subviews like the Jobs View the parameter is not considered. In the subviews the value for Max. number of Audit Log entries per object is considered.

      Desired Behavior

      In the Audit Log view, when a user uses the "Advanced Search", a Customization or a one of the build in filters like last 12 hours then the profile parameter Max. number of Audit Log entries should be considered to limit the resultset.

      As Sub-views do not include a search function but display Audit Log entries related to the current object, e.g. the job chain the lists also should be limited. When Max. number of Audit Log entries per object is greater than Max. number of Audit Log entries then the smaller value Max. number of Audit Log entries should limit the resultsets.

      Further Considerations

      The Advanced Search, the customization and the build in filters like "Last 24 hours" are searching in the database without limits. Only the resultset will be limited. The value for the limitation can be defined in the profile and should be "very high". Unlimited resultsets are not feasable in the gui. There must be a limit. When entering the view the resultset will be limited by the build in filter "Today". When the user clicks the "All" button to get unfiltered resultsets it is expected that the search may take some time. Therefore the limit can be set to a very high value.
      Please note that the "Search in Results" field searches in the resultlist (as the label indicates) and is not a search in the database. You can mix the advanced search or the customizations with the "Search in Results" field.

        Issue Links

          Activity

          Hide
          XEOPS Datenbank Admin added a comment -

          This change request is the opposite of what we want. JOC-512 was supposed to deliver the functionality that we want, but it doesn’t. The profile parameter “Max. number of Audit Log entries” IS CONSIDERED when using the Advanced Search or customized filters in the audit log tab. It should NOT be considered. It should be completely ignored. The only time when this parameter should be considered is when the user opens the audit log tab and the initial results are displayed.

          Show
          XEOPS Datenbank Admin added a comment - This change request is the opposite of what we want. JOC-512 was supposed to deliver the functionality that we want, but it doesn’t. The profile parameter “Max. number of Audit Log entries” IS CONSIDERED when using the Advanced Search or customized filters in the audit log tab. It should NOT be considered. It should be completely ignored. The only time when this parameter should be considered is when the user opens the audit log tab and the initial results are displayed.
          Hide
          Uwe Risse added a comment - - edited

          We will implement it in the way as described in JOC-653. We will rollback JITL-512.

          Please see Further Considerations where the reason for this explained.

          In JITL-512 you commented

          "Currently, this is the only method we have to search the entire audit log because the profile parameter Max. number of Audit Log entries is hindering us from using the regular search."

          This maybe is a misunderstanding on your site. When you mean with "regular search" the search in resultset option then this search is not a database search. The database search in in Advanced Search is umlimitted. Only the resultset is limited. You can set the limit to a very high value in you profile. Then execute the Advanced Search will result with the (limited) list of entries. We think that lets say resulting 10.000.000 records makes no sense for a GUI like JOC Cockpit.

          The initial result is already limited by the today filter. That means when you open the view, you only see records from today. This is usually much less than the given limit in the profile.

          I see only one use case that might not be covered with the actual options. This is when you have a high number of audit log entries each day. Then the "very high" limit + the todays filter in the initial view might return to many entries. For this use case the solution is to introduce a new profile setting especially for the initial view.

          Show
          Uwe Risse added a comment - - edited We will implement it in the way as described in JOC-653 . We will rollback JITL-512 . Please see Further Considerations where the reason for this explained. In JITL-512 you commented "Currently, this is the only method we have to search the entire audit log because the profile parameter Max. number of Audit Log entries is hindering us from using the regular search." This maybe is a misunderstanding on your site. When you mean with "regular search" the search in resultset option then this search is not a database search. The database search in in Advanced Search is umlimitted. Only the resultset is limited. You can set the limit to a very high value in you profile. Then execute the Advanced Search will result with the (limited) list of entries. We think that lets say resulting 10.000.000 records makes no sense for a GUI like JOC Cockpit. The initial result is already limited by the today filter. That means when you open the view, you only see records from today. This is usually much less than the given limit in the profile. I see only one use case that might not be covered with the actual options. This is when you have a high number of audit log entries each day. Then the "very high" limit + the todays filter in the initial view might return to many entries. For this use case the solution is to introduce a new profile setting especially for the initial view.

            People

            • Assignee:
              Sourabh Agrawal
              Reporter:
              Uwe Risse
              Approver:
              Aditi Dubey
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: