Redwood Documentation

Product Documentation

 

›Locating Objects

RunMyJobsGetting Started

Introduction

  • Welcome
  • Introduction to the Help System
  • Text Search

Getting Started

  • Symbols and Icons used in the User Interface
  • Logging in
  • Navigation
  • Navigating with Screen Readers

Basic Actions

  • Performing Basic Actions

Locating Objects

  • Filtering Objects
  • IntelliSearch, Advanced Object Search
  • SQL Functions
  • Custom SQL Filter BNF
  • Specifying Values
  • Searching For Objects using Object Search

User Parameters

  • Setting User Parameters
  • Creating Custom Navigation Bars
  • Documenting Objects using the Documentation Tab

New User Interface

  • New User Interface

Appendix

  • Glossary
  • Usage Data Collection
← Filtering ObjectsSQL Functions →

IntelliSearch, Advanced Object Search

Redwood Server allows you to search seamlessly through objects with the new search box, which is now available for most objects. The search only searches in the current tab and by default searches for the name on most objects. For some objects like operator messages, for example, you would rather search for the Title text, which is the title of the operator message. You can use prefixes to search on object-specific properties, like lmt, which stands for Last Modification Time. The search is case-insensitive. Default objects often have translated field values, you should always search in your session-language.

You can search on multiple properties by just appending a new prefix and search criteria. Depending on the amount of objects which match your criteria, one or more will be listed.

The following prefixes are available for most objects:

PrefixDescription
n, nameName field of the object
c, commentDocumentation field of object
d, descriptionDescription field of object
a, applicationApplication field on object
cb, changedbeforeLast modification date/time before a time/period (accepts ISO-8601 period)

The n or name prefix is optional, all other prefixes are required, so if you want to search on the name of the object, you just enter your search-phrase.

note

You can only use valid prefixes. Not all objects have a Name property, like operator messages for example, in this case the n prefix is not available. The available prefixes are documented in the topic covering the object. Press the F1 key or choose Help from the context-menu to access context-sensitive help with the table of available prefixes.

ISO-8601 Period Syntax

P[<n>Y][<m>M][<o>W][<p>D][T[<q>H][<r>M][<s>S][.SSS]]
  • P - duration designator (for period) placed at the start.
    • Y for number of calendar years.
    • M for number of calendar months.
    • W for number of weeks.
    • D for the number of calendar days.
  • T is the time designator that precedes the time components, mandatory if a time element is to be specified.
    • H for the number of hours.
    • M for the number of minutes.
    • S for the number of seconds.
    • .SSS for the number of milliseconds.
One day (24 hours):
P1D - in days
PT24H - in hours
PT1440M - in minutes
PT86400S - in seconds
PT23H60M - in hours + minutes
PT23H59M60S - in hours + minutes + seconds

One day and one hour:
P1DT1H - in days and hours
...

Wildcards and Exact Matches

IntelliSearch accepts the * wildcard. By default, all searches are performed as <prefix>:*<search_phrase>*, where <prefix> and <search_phrase> are the prefix and search phrase you entered, respectively. If you want to search for an exact match, append e to the prefix, such as jde:MyProc. This example search matches a process from process definition MyProc exactly, a process from process definition MyProcess will not be listed, for example.

The following prefixes of the processes monitor IntelliSearch default to wildcard search and accept the e for exact match in the processes monitor:

  • jd for process definition wildcard search, jde equivalent for exact match
  • q for queue wildcard search, qe equivalent for exact match
  • ps for process server wildcard search, pse equivalent for exact match
  • sapq for sap queue wildcard search, sapqe equivalent for direct match
  • sapps for sap process server wildcard search, sappse equivalent for direct match
  • a for application wildcard search, ae equivalent for direct match

The following prefixes of the Operator Messages monitor IntelliSearch default to wildcard search and accept the e for exact match:

  • lma for last modification time wildcard search, lmae equivalent for exact match
  • lmb for last modification user wildcard search, lmbe equivalent for exact match

The following prefixes allow you to search for processes that ran in a queue or a process server:

  • psId - The name of the process server of processes
  • qId - The name of the queue of processes

Syntax

[<prefix>:]<search_criteria>[,<search_criteria>]* [[<prefix>:]<search_criteria>[,<search_criteria>]*]*
note

There is no space between the: and the prefix or search-phrase.

note

If the search-phrase contains spaces, the search-phrase must be surrounded by double quotes ( " ).

If you just enter the search-phrase, the search will be carried out on the name of the object:

<search_criteria>

Some objects do not have a name prefix, in these cases the default prefixes have been mapped to object-specific prefixes.

Example

To search for a process definition with the description Import Java Archive (JAR) into a Library:

  1. Navigate to "Definitions > Processes".
  2. Enter the following text into the Search Process Definitions box to display only processes and chains with import in the description field:
description:import

In this example, too many processes matched the search! More search criteria needs to be added to refine the search:

description:"import Java" application:SystEm

In this example, another description term is added:

description:"import Java","import definitions" application:System

That is equivalent to the following:

description:"import Java" description:"import definitions" application:System

See Also

Advanced Process Search

← Filtering ObjectsSQL Functions →
  • Syntax
  • Example
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |