Setting Up Inquiry Audit

Setting Up Audit for Portals and Zones

The zone parameter Audit Service Script controls if information about the record being inquired upon will be captured for audit. In order to turn on inquiry audit for a zone, you will need to update the Override Parameter Value with the following:

The name of the service script responsible for capturing the audit data and storing it on the Inquiry Audit table.

The base includes the service script C1-ZoneAudit
Additional scripts can be developed if your implementation requires something more specific such as add audit records only if VIP records are viewed or where certain criteria is used.
The mnemonic ss= is used to define the name of the service script. For example ss='C1-ZoneAudit'.

Define the input elements to the service script by using the mnemonicinput=. These can include the user id, zone, portal, user filter values, hidden filter values, any literal value, any portal or global context field.

See the zone's help on more information.

Setting Up Audit for a Search Page

A user exit is needed to turn on inquiry audit for an old style search page or control central. You will need to do the following:

Determine the service name of the page.
Create a search page extension to capture the audit information. . The following extension codes are provided as samples:

ext_ multiSearchNameData.jsp - Control Central Search by Name
ext_ multiSearchAddressData.jsp - Control Central Search by Address
ext_ accountSearchData.jsp - Account Search

The search pages have grid elements that display the result rows. To capture the search criteria, the service script C1-PageAudit should be called upon load of the grid element, to add the inquiry audit record.
The business object to use when calling the service script is C1-PageAuditInquiry

Setting Up Audit for a Maintenance Page

A user exit is needed to turn on inquiry audit for an old style maintenance page. You will need to do the following:

Determine the service name of the page.
Create a page maintenance page extension to capture the audit information. . The following extension code is provided as a sample:

CMAccountMaintenanceExtension.java - Account Page Maintenance

The page maintenance extension method afterRead should be overridden to call the service script C1-PageAudit to add the inquiry audit record.
The business object to use when calling the service script is C1-PageAuditInquiry

Inquiry Audit Restrictions

Certain portals are designed to include a zone with a list of records and buttons that allow quick editing of a record. This technique invokes a BPA script that displays the data in a UI map, rather than broadcasting a value from a query or info zone. This bypasses the ability to capture the audit for this record. There is currently no ability for an implementation to include a user exit in a BPA script to allow storage of an audit record.

The above applies to any administrative portal that uses the "all in one" portal design that includes a list zone showing all existing records. The list zone typically includes edit, duplicate and delete buttons.

Note For customized portals that call a customized BPA script, an implementation has the ability to include a step to store an Inquiry Audit record.