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

Advanced Search with wildcards should be supported

    Details

      Description

      Current Situation

      • The Advanced Search in a number of views support to search for exact matches and in some cases to search for regular expressions.
        • Searching for exact matches is not too useful in many cases.
        • Use of regular expressions forces a steep learning curve.

      Desired Behavior

      • All input fields for the Advanced Search in any view that allow to search for exact matches or for regular expressions should allow to use the % wildcard character to search for any number of characters. Use of the wildcard character _ to search for an individual character is not supported.

      Daily Plan

      • Regular Expression or Folders: May contain % as a wildcard. The field always will be handles as a regular expression
      • Job Chain: Path can be uncompleted from the left site. May contain % as a wildcard.
      • Job: Path can be uncompleted. May contain % as a wildcard.
      • Order Id: May contain % as a wildcard.

      Job Chains

      • Regular Expression or Folders: May contain % as a wildcard. The field always will be handles as a regular expression
      • Job: % is a wild char. The field always will be handles as a regular expression

      Orders

      • Regular Expression or Folders: May contain % as a wildcard. The field always will be handles as a regular expression

      Jobs

      • Regular Expression or Folders: May contain % as a wildcard. The field always will be handles as a regular expression

      File Transfer

      • Profile Name: May contain % as a wildcard.
      • Mandator: May contain % as a wildcard.
      • Source File Name: May contain % as a wildcard. Can be more than one value
      • Source File Regular Expression: May contain % as a wildcard. The field always will be handles as a regular expression
      • Target File Name: May contain % as a wildcard. Can be more than one value
      • Target File Regular Expression: % is a wild char. The field always will be handles as a regular expression
      • Source Host: May contain % : May contain % as a wildcard. Can be more than one value
      • Source Protocol: Can be more than one value
      • Target Host: May contain % : May contain % as a wildcard. Can be more than one value
      • Target Protocol: Can be more than one value

      Agent Job Execution

      • Agent Url: May contain % as a wildcard. Can be more than one value

      Custom Events

      • Event Ids. Can be more than one value
      • Event classes: May contain % as a wildcard. Can be more than one value
      • Event Exit Codes: Can be more than one value
      • Jobchains/Order: Can be a job chain or an order assigned to a job chain. Can be more than one value
      • Jobs: Can be more than one value

      History/ Order

      • Regular Expression or Folders: May contain % as a wildcard. If containing % field will be used with a DB search. Can be * more than one value. Value is the job chain

      History/ Task

      • Regular Expression or Folders: May contain % as a wildcard. If containing % field will be used with a DB search. Can be more than one value. Value is the job

      File Transfers

      • see: File Transfer

      Audit Log

      • Reason: May contain % as a wildcard.
      • Job Chain: Path can be uncompleted from the left site. May contain % as a wildcard.
      • Order IDs: May contain % as a wildcard. Can be more than one value
      • Job: Path can be uncompleted. May contain % as a wildcard. Can be more than one value
      • Calendar: Path can be uncompleted from the left site. May contain % as a wildcard. Can be more than one value
      • Account: May contain % as a wildcard.

        Activity

        Hide
        XEOPS Datenbank Admin added a comment -

        We agree with the Desired Behavior. Suggestion: would it make more sense to use the * as a wildcard character?

        Show
        XEOPS Datenbank Admin added a comment - We agree with the Desired Behavior. Suggestion: would it make more sense to use the * as a wildcard character?
        Hide
        Andreas Püschel added a comment -

        We allow input of regular expressions and of wildcard characters to the same input field. As the * is a regular expression meta character we prefer to use the % character for wildcard input in order to distinguish from the user input which search mode should be used.

        Show
        Andreas Püschel added a comment - We allow input of regular expressions and of wildcard characters to the same input field. As the * is a regular expression meta character we prefer to use the % character for wildcard input in order to distinguish from the user input which search mode should be used.

          People

          • Assignee:
            Uwe Risse
            Reporter:
            Andreas Püschel
            Approver:
            Mahendra Patidar
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2 days, 4 hours
              2d 4h
              Remaining:
              Remaining Estimate - 2 days, 4 hours
              2d 4h
              Logged:
              Time Spent - Not Specified
              Not Specified