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
Test audit lookup functionality
Applies to User Roles:
Some files may not be configured for Audit Lookup. In that case, you must add Audit Lookup functionality before Audit Lookup will work.
Service Manager invokes Audit Processing using the definitions provided in the Format Control, when a record is added or updated in a file for which auditing has been set up.
Note: Before using Audit Lookup, be sure that the Audit Specifications include all fields that need auditing.
To test Audit Lookup functionality:
- Add a record to the contacts file using the values in the table below.
Field Value Contact Name MILLER, JOHN Employee ID NEW00003 Last Name Miller First Name John Company advantage john.miller@Advantage.com Dept Name Documentation
Note: Service Manager displays the following message: “Contact Information record added.” The audit process is invoked. Service Manager does not open an audit record until a user changes the current field values.
Service Manager has recorded all fields specified in the Audit Specifications record. All Old values are NULL or contain no data because there is no previous version of the record; this is a new record.
Note: Audit Log entries are created in response to any changes made to the current values in this record. These audit records are displayed in the audit.summ form, when accessed using the Format Control option created earlier.
If you check Audit Lookup now, a message informing you that there are no audit records.
- To complete the example, modify the record created in the previous steps by entering new values in the fields of the form that were specified as Unique A-D fields in the audit specifications file. For this example, change the Employee ID to NEW00004.
Click Save to commit the changes to the database.
Service Manager displays the following message: “Record updated in the contacts file. Audit Record successfully recorded and added.” when the record is saved and an Audit Log is created.
Open the More Actions menu and select Audit Lookup.
A record list opens.
Note: The updates you see may vary, depending on how you have your triggers set up for the file.
Select the desired record from the list.
Note: Only those fields which were modified are recorded. Service Manager displays both the Old and the New versions of each modified field in the audit log record. If none of the fields defined in the Audit Specifications Table have been modified, then Service Manager does not generate an audit log entry for that database dictionary file.
For further information regarding the modifications to the contacts file, click Show detail.
The same record is re-displayed in an expanded form audit.g), which shows more detailed information for the arrayed fields, as well as scrollable fields.
- Click End to return to the summary form.
- From the summary form, click the Prev and Next buttons to review any additional audit records in the log for this contacts record.
- Click End to return to the Contacts record.
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.
To use Audit Lookup:
- 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