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.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
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.
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||
|A combination of search types||
- Database record auditing
- Invoke auditing
- Invoke auditing from Format Control
- Invoke auditing from the file in Database Manager (Change Management only)
- Start database record auditing
- Test Audit Lookup functionality
- Audit processing
- Determine if a file has audit processing
- Audit log file
- Open the audit log file
- Verify the field name
- Verify the file name
- Add an audit specifications record
- Open the audit specifications table
- Define an audit specifications entry
- Audit specifications file
- Audit specifications file description
- The Subroutines form
Define an audit specifications entry
Applies to User Roles:
The system validates Filename and Field Name values every time you update an existing record or add a new record. The Audit utility safeguard system prevents records with misspelled and incorrect file names or field names from being processed. Such errors potentially could cause faulty communication within the database.
Note: The name of the file and one field name of this example have been entered incorrectly to illustrate error-correction process built into the Audit utility.
To enter data in the Audit Specifications file:
Click Tailoring > Audit > Audit Specifications.
A blank Audit Specifications Table form opens.
To select the file to create the specifications for.
Enter information in the Filename field and Unique A through Unique D fields, as necessary, to parallel the Unique key in the source file with the Audit Log.
Note: see the related topics and read the topic "Audit specifications file description" for more information on input fields.
For this example, enter
contactsin the Filename field, and then click Search.
Caution: Making changes to the contacts file to cause it to invoke auditing will cause two audit records to be generated when a file is updated. To prevent this, use a backup, and restore the original file when finished with the example, or create a different file to practice on.
- Define those fields you want Service Manager to audit and any aliases.
If a field name is invalid, a list will open up allowing you to copy a valid name and use it to replace the invalid name.
For this example, enter:
Field Name Alias contact.name Contact Name user.id Employee ID first.name First Name last.name Last Name dept.name Department Email Address location Location
- Click Add. to retain this record and commit it to the database.
The topics below comprise an example of how to use Database record auditing. Follow the steps in this order. If you skip a step, the example will not work.
- Open the audit specifications table.
- Add an audit specifications record.
- Define an audit specifications entry
- Invoke auditing.
- Set up event triggers
- Add lookup functionality to Format Control.
- Test audit lookup functionality.