Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Develop
Introduction
The Document Engine comprises a set of tools and methodologies for developing and modifying Service Manager workflows. The Document Engine was originally tasked to develop an underlying set of base functionality that would support multiple modules inside Service Manager, improve consistency of the user interface between modules and reduce the amount of code needed for any new module.
The Document Engine extends the display application capabilities with simplified and more extensive actions especially those involving multiple application calls. In addition, the Document Engine supports the use of joined tables and master format control calls. It is designed to meet the needs of most customers out of the box, yet retain flexibility. The relationship between Objects, States, and Processes is hierarchical.
The Document Engine controls behavior with Objects. An Object is referenced whenever a form opens, and the Object determines the behavior for the state of the form (open, list, search, etc.). Objects define overall table behavior. Within the Object, a State describes where a record is in its lifecycle (open, list, search, etc.). Within the State, different Processes are executed depending on the actions initiated by a user on the record. States also define how the system displays a record and what options (actions) are available at specific times or circumstances. For instance, States can determine an action, such as Save, given a user’s access privileges.
Processes are called from States based on the user's action. The Process uses RAD expressions, JavaScript, and calls to existing RAD applications to perform actions against the current record.