The Detail_Type table contains a static list of the standard details that can be recorded about audited events. For example, a user logon can fail for a number of different reasons. These reasons are listed as entries in the
Detail_Type table.
The information in the Detail_Type table is equivalent to the information that was recorded in variable AuditStrings in Crystal Enterprise 10.
Event_Type table reference
The following tables list the Event_Type_ID and
Event_Type_Description of all events that can be audited in your system. For your convenience, these events are ordered according to the server that generates each type of event.
CMS audit events
Field Description
Detail_Type_ID Number that uniquely identifies the type of audit detail that the entry represents.
Detail_Type_Description The description of the type of audit detail generated by the audit event.
Event_Type_ ID Event_Type_Description Description
65537 Concurrent user logon
succeeded. The user logged on successfully, using a concurrent user license. 65538 Named user logon
succeeded. The user logged on successfully, using a named user license.
65540 User logged off.
65541 User password has been changed.
65539 User logon failed. Logon failed because there was no valid license key available.
Auditing Reports
Creating custom audit reports
4
Cache Server audit events
65542 New folder created. A new folder is created, or an existing folder is copied. Note that this audit string will not be recorded when a new user account is created, even though creating a user creates a user folder. 65543 Folder deleted. A folder is deleted.
Note that this audit string will be recorded when a user account (and therefore the user’s folder) is deleted. 65544 Folder modified. The name, location, or
description of the folder was changed.
65545 Job failed. Reason: Unresponsive Job Server Child process.
A scheduled report or scheduled program failed to run because communication with the running instance was lost, and the scheduled time for running the job expired.
Note: This action must be audited by the CMS as Job Servers are not aware of losing communications with a job.
Event_Type_ ID Event_Type_Description Description
Event_Type_ ID Event_Type_Description Description
196609 Crystal report viewed
successfully. User successfully viewed a Crystal report that has saved or live data.
196610 A report could not be
viewed. User attempted to view a Crystal report, but was not successful.
Job Server audit events
For scheduled objects, the audit messages give you information about the status of scheduled actions. For example, the audit messages can tell you if a scheduled report ran successfully.
For the Destination Job Server, the audit messages give you information on whether an object was sent to a destination, as requested by a user.
Event Server audit events
Event_Type _ ID
Event_Type_Description Description
327681 Job successful. The object ran as scheduled (or requested) and the job completed successfully. 327682 Job failed. The scheduled job did not
complete successfully. 327683 Job failed. Job will be
retried by the CMS. The scheduled job did not complete successfully. The job will be retried by the CMS at a later time.
For more information on scheduling jobs, see the BusinessObjects Enterprise Administrator’s Guide.
Event_Type_ ID Event_Type_Description Description
262145 Event registered User creates a file-based event that can be used to schedule objects.
262146 Event unregistered User deletes a file-based event.
262147 Event updated Event object was modified by a user, or by the system. Events are updated when a user modifies the name or description of the file-based event.
262148 Event triggered File-based event was initiated.
Auditing Reports
Creating custom audit reports
4
Application_Type table referenceReport Application Server audit events
The Report Application Server (RAS) is used to view reports opened with the Advanced DHTML viewer, and to create reports using custom applications developed with the RAS SDK.
Application_Type_ID Application_Type_Description
1 Unknown Application
8 Web Intelligence Report Server
11 Central Management Server
(CMS)
12 Cache Server
13 Report Job Server
14 Report Application Server (RAS)
15 Event Server
16 Program Job Server
18 Destination Job Server
Event_Type_ ID Event_Type_Description Description
458753 Report was opened for
viewing and/or modification User opened a report for viewing or modification. Note: In a few cases, this
Event_Type_ID may be generated when the report opens but cannot be viewed. This may occur when:
•
There are problems with the database setup for the report. For example, you may see this message when the database driver for the report is not present on the client machine•
A processing extension associated with the report aborts viewing, or fails.•
The report used Business Views and the user did not have permissions to refresh the underlying data connections.•
The machine running the RAS ran out of space in its temporary directory.458754 Report was saved to the
CMS. An existing report was saved. Note: This
Event_Type_ID is generated when a custom application created using the RAS SDK saves a report (using the Save method). Consult your RAS SDK documentation for details.
Auditing Reports
Creating custom audit reports
4
Web Intelligence Report Server audit events
458755 Report was created and
saved to the CMS A new report was created and saved. This Event_Type_ID is generated when a custom application created using the RAS SDK saves a new report (using the Save As method). Consult your RAS SDK documentation for details.
458756 Report could not be
opened. The report could not be opened by the RAS. 458757 Report could not be saved
to the CMS. An existing report could not be saved by RAS. This Event_Type_ID is generated when a custom application created using the RAS SDK cannot save a new report (using the Save As method). Consult your RAS SDK
documentation for details. 458758 Report could not be
created in the CMS. A newly created report could not be saved by RAS.
Event_Type_ ID Event_Type_Description Description
Event_Type_ ID Event_Type_Description Description
6 Get list of universes User accesses a list of universes as part of a document creation workflow.
9 Save document to
repository User saves a Web Intelligence document to BusinessObjects Enterprise. 11 Read document User opens an existing Web
Intelligence document. 13 Selection of universe User selects a universe as
19 Document refresh User manually refreshes a Web Intelligence document, or user opens a Web Intelligence document that has the “refresh on open” document property assigned. 21 List of values A list of values is retrieved
from the database to
populate a picklist associated with a prompt used to filter the data in a document. 22 Edit document User has moved into Edit
document mode.
28 Apply format User applies a formatting change to a document, in a query panel.
40 Get page User action results in a request to server to generate the necessary data and layout to display all or part of a Web Intelligence document.
41 Generate SQL Appears when a user
refreshes a document. 42 Drill out of scope User drills past the scope of
the data currently in memory, and triggers a call to the database for more data.