Audit Manager
Audit Manager
Publication Number
PLM00022 H
Contents
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
I Audit Manager
The details of the new and old Audit Manager applications are as follows:
Auditing Description
application
• Audit logs are stored in the database. Audit logs are grouped
together depending on the type, such as general logs, workflow
logs, structure logs, file access logs, and schedule logs.
• You can create audit configuration objects such as audit
definition objects, events, and event type mappings using
Business Modeler IDE.
• View audit logs using the Summary view of the supported
Audit Teamcenter applications.
Manager • Enable Audit Manager by updating preferences as follows:
o TC_audit_manager.
Set value to ON.
o TC_audit_manager_version
Set value to 3.
• You can configure audit logs to be stored in files or in the
database.
• You can use the rich client-based Audit Manager application
for configuring audit definitions.
• You can create events and event type mappings using Business
Modeler IDE.
• You can query the audit logs, using the Audit Logs dialog box.
• Enable Legacy Audit Manager by updating the preferences
as follows:
Legacy Audit
Manager o TC_audit_manager.
Set value to ON.
o TC_audit_manager_version
Set value to 2.
Note The legacy Audit Manager application is deprecated and
will be removed in a future version.
Migrating audit data from legacy Audit Manager to new Audit Manager . . . . . 6-1
1 Getting started
1 Getting started
• The Summary view of the following Teamcenter applications shows audit logs
in the Audit logs tab.
o My Teamcenter
o ADA License
o Structure Manager
o Multi-Structure Manager
o Schedule Manager
o Workflow Viewer
o Organization
• You can run predefined audit reports or create new reports, using the Report
Builder application.
• You can create queries of audit logs, using the Query Builder application. You
can run these queries, using the Teamcenter search functionality.
• You can run predefined audit queries, using the Teamcenter advanced search
functionality.
When you create new events, you must associate the event with an object.
Subsequently, you can create audit definition objects for that event and object type.
For more information about associating events to objects, see Create an event type
mapping.
o ADA License
o Structure Manager
o Multi-Structure Manager
o Schedule Manager
o Workflow Viewer
o Organization
• You can run predefined audit reports or create new reports, using the Report
Builder application.
For more information, see Audit reports.
• You can create queries of audit logs, using the Query Builder application.
For more information, see Creating and running audit queries.
• You can run predefined audit queries, using the Teamcenter advanced search
functionality.
Audit objects
The audit functionality in Teamcenter uses the following objects:
• Fnd0AuditDefProperty
Specifies the logged properties object. This object stores logged properties
information.
• Fnd0EventTypeMapping
Specifies the event type mapping object. This object maps an event to an object,
following which you can create audit definitions for the mapped object and event
type combination.
• ImanEventType
Specifies the event type object. This object stores events.
• Fnd0WorkflowAudit
Specifies workflow audit log object. This object stores process and signoff history
audit logs.
• Fnd0LicenseChangeAudit
Stores the license change audit logs.
• Fnd0LicenseExportAudit
Stores the license export audit logs.
• Fnd0FileAccessAudit
Stores file access audit logs.
• Fnd0OrganizationAudit
Stores organization audit logs.
• Fnd0StructureAudit
Stores structure audit logs.
• Fnd0ScheduleAudit
Stores schedule audit logs.
• Fnd0GeneralAudit
Stores the audit logs that are not stored in other audit logs.
• Fnd0SecondaryAudit
Stores additional information or secondary information about objects such as
attachments and attachment properties.
• Fnd0AuditLink
Stores the link between primary and secondary audit logs.
Postupgrade steps required for importing custom event types into a template
project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
For more information, see the Preferences and Environment Variables Reference.
Note After updating the preference:
• Restart Teamcenter server pool manager if you are on a 4-tier
installation.
2. In the BMIDE view, right-click the project and choose Reload Data Model. Make
sure there are no model errors reported in Console view.
log is written for an instance of the business object, the property in this
constant is used to obtain the object’s ID for the audit log (and is written to
the fnd0PrimaryObjectID property on the Fnd0GeneralAudit business
object). For custom objects that have their own property for the object ID, change
this constant to the property that holds the object ID so that the ID of the
business object is captured when the audit log is written.
This constant is placed on the POM_object business object and its children.
There is no default value. Type a value in the Value box to assign an object ID.
This constant is provided by the foundation template file.
• Fnd0ObjectNameToAudit
Specifies the property that holds the object name for the business object type.
The object name property is different for different business object types. For
example, on the Workspace business object type, the value for this constant is
object_name and on the User business object type, the value is user_name.
When an audit log is written for an instance of the business object, the property
in this constant is used to obtain the object name for the audit log (and is written
to the name property on the AuditLog business object). For custom objects
that have their own property for the object name, change this constant to the
property that holds the object name so that the name of the business object is
captured when the audit log is written.
This constant is placed on the POM_object business object and its children.
There is no default value. Type a value in the Value box to assign an object name.
This constant is provided by the foundation template file.
• Fnd0ObjectRevIDToAudit
Specifies the property that holds the revision ID for the business object type.
The revision ID property differs across business object types. For example,
on the ItemRevision business object type, the value for this constant is
item_revision_id. When an audit log is written for an instance of the business
object, the property in this constant is used to obtain the object’s revision ID for
the audit log. For custom objects that have their own property for the revision
ID, change this constant to the property that holds the ID so that the revision ID
of the business object is captured when the audit log is written.
This constant is placed on the POM_object business object and its children.
There is no default value. Type a value in the Value box to assign an object
revision ID.
This constant is provided by the foundation template file.
• Fnd0AuditRecordAccessLevel
Controls how access to a workflow audit record is evaluated. This constant is
placed on the Fnd0WorkflowAudit business object. The default value is 1.
Click the arrow on the Value box to select from the following available values:
o 1
Checks workflow audit record based on the read access to the objects
referred by the fnd0Object property (primary object) and the
fnd0SecondaryObject property (secondary object). If the primary and
secondary objects are deleted, only the administrator user is provided with
read access to the audit record.
o 2
Checks workflow audit record based on the read access to all attachments
for that workflow. Access to the primary object is not evaluated. If any of
the secondary objects are deleted, only the administrator user is provided
with read access.
For information about changing the value of a business constant, see the Business
Modeler IDE Guide.
For information about setting access controls on objects, see the Access Manager
Guide.
• Fnd0AuditRecordAccessLevel=2
The access check on the workflow audit records is evaluated based on the read
access to the current list of attachments for that workflow. Access to the primary
object is not evaluated.
For more information about updating the value of a constant, see the Business
Modeler IDE Guide.
Value = Fnd0AuditLog
This access rule gives administrators read privileges to audit logs of deleted objects
and denies read privileges to the others.
Note If you are installing a new database, this rule is automatically created.
If you are upgrading an existing database, you must upgrade Access
Manager rules.
For more information about upgrading Access Manager rules, see Access
Manager Guide.
• Fnd0RetentionPeriod
Specifies the retention period of the audit log archives in days (for example, 90).
For more information about modifying these business object constants, see the
Business Modeler IDE Guide.
• Fnd0OCC_track_position_orientation_audithandler
Logs the occurrence position and orientation changes of the components in
structures.
• Fnd0PROJInfo_audithandler
Logs project names that are assigned to the project. The project names are
separated using commas.
• Fnd0USER_get_additional_log_info
Logs workflow information to audit logs. For example, for the __Assign
event, this handler logs information such as the process name, task type, user
comments, and the user ID and user name the workflow is assigned to.
• Fnd0WriteSignoffDetails
Logs the workflow signoff history.
• Fnd0WriteSecondaryProperties
Logs secondary properties.
For more information about these extensions, see Audit log extensions.
D. Click Add to the right of the Availability table and perform the following
in the Extension availability dialog box:
i. In the Business Object Name box, select Fnd0AuditDefinition.
b. Click Add to the right of the Audit Extensions table, and select the
P3_CustomAuditLog extension from the Find an Audit Extension dialog box.
c. To save the changes to the data model, choose BMIDE→Save Data Model.
if ( paramCount ==0 )
{
return ITK_ok;
}
for ( int i=0; i<paramCount; i++ )
{
if(strcmp(paramNames[i],"signoff") == 0)
{
signoff=paramValues[i];
break;
}
}
if (signoff == 0)
{
return ITK_ok;
}
ifail = POM_class_of_instance( primaryAuditBOTag, &auditClassId );
ifail = POM_name_of_class (auditClassId, &audit_class_name );
//ifail = EPM_ask_job(targetObjTag, &job_tag);
ifail = POM_string_to_tag(signoff, &signoffTag);
ifail = POM_class_of_instance( signoffTag, &signoffClassId );
ifail = POM_name_of_class (signoffClassId, &signoff_class_name );
isProp = false;
ifail = POM_attr_exists("p3_decisioncode", signoff_class_name, &isProp);
if (isProp)
{
ifail = AOM_ask_value_string ( signoffTag, "p3_decisioncode" ,&propVal);
isProp=false;
ifail = POM_attr_exists("p3_decisioncode", audit_class_name, &isProp);
if (isProp)
{
ifail = AOM_set_value_string(primaryAuditBOTag, "p3_decisioncode", propVal);
}
}
if (audit_class_name)
{
MEM_free(audit_class_name);
}
if (signoff_class_name)
{
MEM_free(signoff_class_name);
}
if(propVal)
{
MEM_free(propVal);
}
return ITK_ok;
}
3. Click the Browse box to the right of the Primary Object box to select the type
of business object you want to audit.
4. Click the Browse box to the right of the Event Type box to select the event you
want to audit for the selected business object.
5. Click the Add button to the right of the Audit Extensions box to select the log
extensions to use in the definition.
6. In the Description box, type a description of the purpose for this audit definition.
8. Select the Track Old Values? check box to enable tracking of the old values
of properties.
9. Select the Audit on Property Change Only? check box to log the information
specified in this audit definition only if the property values change. This
functionality is only enabled if the Track Old Values? check box is selected.
10. Click Next to add primary object properties to the audit. These properties are on
the business object for which the audit definition is being created.
a. In the Primary Audit Definition Properties dialog box, click the Add button
located to the right of the table.
b. In the Add Audit Definition property dialog box, click Browse to the right of
the Property Name box to select the primary property.
c. To change the display name of the property in audit logs, type the new
display name in the Target Property Name box.
d. Use the Target Old Value Property Name box to change the display name of
the old property in the audit logs.
Note The Target Old Value Property Name box and the Enable Tracking?
box are enabled if you selected the Track Old Values? check box in
the Add an Audit Definition dialog box.
e. Click the arrow in the Enable Tracking? box to select the kind of tracking:
• Track Always
Always tracks old and new values of properties even if there are no
changes to the property value.
• No
Does not track changes to properties.
• Track Different
Tracks old and new values of properties only when the property value
changes.
f. Click Finish.
g. Click the Add button in the Primary Audit Definition Properties dialog box
to add more properties as needed.
11. In the Add an Audit Definition dialog box, click Next to add secondary object
properties to the audit log. These properties reside on other business objects
than the business object for which the audit definition is being created.
a. Click the Browse button on the Object Type box to select the secondary
business object.
b. Fill in the boxes as you did for the primary business objects.
c. Click Finish.
13. Verify that the audit definition object can create audit logs.
For more information about viewing audit logs, see the Audit Manager Guide.
3. In the Display Name box, type the name that you want the event to have in
the user interface.
4. In the Description box, type a description of the new event so that others know
what it is used for.
5. Click Finish.
6. Create an event type mapping definition to connect the event to a business object
type.
For instructions, see Create an event type mapping.
inherited by child business object types. For example, instances of the Part business
object type inherit the mapping from the Item business object type.
In the past, the event mapping was created using the install_event_types utility.
Now event mapping is created using the Business Modeler IDE.
1. Choose one of these methods:
• On the menu bar, choose BMIDE→New Model Element, type Event Type
Mapping in the Wizards box, and click Next.
2. Click the Browse box to the right of the Primary Object box to select the type
of business object you want to audit.
3. Click the Browse box to the right of the Event Type box to select the event you
want to audit for the selected business object.
4. Click the Browse box to the right of the Audit Type box to select the type of audit
to use for this mapping. The audit types are represented by business objects that
are children of the Fnd0AuditLog business object.
5. Click the Browse box to the right of the Secondary Audit Type box to select
the Fnd0SecondaryAudit business object. This Secondary Audit object stores
information and properties about the secondary objects that are related to the
main object being audited.
6. Select the Subscribable? check box to specify that the event type mapping
can be subscribed to.
7. Select the Auditable? check box to specify that the event type mapping can be
audited.
8. In the Description box, type a description for this mapping so that others know
what it is used for.
9. Click Finish.
o ADA License
o Structure Manager
o Multi-Structure Manager
o Schedule Manager
o Workflow Viewer
o Organization
For more information, see View audit logs in the Summary view.
• Run predefined audit reports or create new reports, using the Report Builder
application.
For more information, see Audit reports.
o ADA License
o Structure Manager
o Multi-Structure Manager
o Schedule Manager
o Workflow Viewer
o Organization
Legacy audit information is only accessible from a button in the Audit Logs tab in
the Summary view when a legacy audit file is present.
The audit logs are grouped in the Summary view as follows:
Audit reports
The following audit reports are available when you choose the
Tools→Reports→Report Builder Reports menu command in My Teamcenter:
• Audit - Workflow Attachment Report
Displays workflow logs for the specified workflow attachment.
2. To export the audit logs in Microsoft Excel format, click the Export to Excel
button.
To export the audit logs in csv format, click the Export to CSV button.
Depending on the export option you select, the Export to Excel or Export to
CSV dialog boxes appear.
3. In the Export to Excel or Export to CSV dialog box, select the audit log type
you want to export.
4. Click OK.
Depending on the export format you choose, Teamcenter exports the audit logs in
Microsoft Excel or csv format.
Note The Export to Excel option is not available on UNIX clients.
Microsoft Excel opens a temporary file. You can create a permanent file by choosing
File→Save As in Excel to display the Save As dialog box.
If you save a live Excel file, you can open it later in My Teamcenter to reconnect
it to the database.
Note Values that you cannot change in Teamcenter are unavailable in the cells
of the live Excel file.
The export to Excel option is not available on UNIX clients.
• To export workflow audit logs, set the value of the Opt_exp_workflow option
to True.
For more information about modifying transfer option sets, see the PLM XML/TC
XML Export Import Administration Guide.
• Storage media
• Days kept
For more information about importing and deploying Business Modeler IDE
templates, see the Business Modeler IDE Guide.
The following table shows where audit logs are stored in the legacy and new Audit
Manager:
This utility exports audit data from the legacy Audit Manager as a TC XML
file. Import this audit log into Teamcenter using the bulk loader mode of the
tcxml_import utility.
The legacy Audit Manager application is deprecated and will be removed in a future
version.
After system administrators create audit logs in Teamcenter, users can view these
logs from various Teamcenter applications. Users can also audit any workspace
object, administration object, and event type with an audit definition.
If your site has online help installed, you can access application and view help from
the rich client Help menu or by pressing F1.
For more information about rich client perspectives and views, see the Rich Client
Interface Guide.
• Event type
Specifies the type of event belonging to a particular object that must be logged.
• Logged properties
Specifies object properties you select for logging. The value of the property at the
time of writing the audit log is logged to audit logs.
For audit definition objects with event type Modify, the old and new values
of persistent properties are tracked.
• Log handler
A log handler allows you to write data other than those captured by audit logs.
You can create custom log handlers. For more information see Create custom
log handlers.
• Storage
Specifies where audit logs are stored. Depending on your requirements, you can
choose to store audit logs in the database or on a file.
For more information on storage options, see Choosing storage media for legacy
audit logs.
• Archive media
This option appears when you select database as your storage option. This option
specifies the storage media for archiving audit logs.
• TC_audit_delimiter
Specifies the delimiter that separates fields of audit records. This preference is
used only for audit files in text format.
• TC_audit_file_format
Specifies the format of external audit files (.txt or xml).
• TC_audit_log_dir
Specifies the directory where audit log files are stored.
• TC_audit_track_changed_properties_only
Specifies if audit logs are written when there are no changes to any tracked
attribute value.
• TC_audit_display_gmt
Specifies if the logged dates in audit logs are shown in the GMT time zone.
You must restart Teamcenter after you change Audit Manager preferences for the
changes to take effect.
For more information about each preference, see the Preferences and Environment
Variables Reference.
Value = AuditLog
To specify access to audit definition objects, modify the following rule or create a new
rule under Has Class (POM_application_object)→Working:
Value = AuditDefinition
For more information about using Access Manager, see the Access Manager Guide.
event1;event2/event3;event4;event5/event6;event7
event# are valid event types separated by semicolons (;). Separate different groups
by slash marks (/). For example:
GroupsOfEventTypes=
__Check_In;__Check_Out;__Cancel_Check_Out;__Transfer_Check_Out/
__Modify;__Delete/__Assign;__Start
• Group 2 contains:
__Modify;__Delete
• Group 3 contains:
__Assign;__Start
After creating these groups of event types, you can select any of the groups from the
General tab of the Viewing the Audit Logs dialog box. In this example, if you select
Group 1, all four event types are searched in audit logs.
3. In the Display Name box, type the name that you want the event to have in
the user interface.
4. In the Description box, type a description of the new event so that others know
what it is used for.
5. Click Finish.
6. Create an event type mapping definition to connect the event to a business object
type.
For instructions, see Create an event type mapping.
2. Click the Browse box to the right of the Primary Object box to select the type
of business object you want to audit.
3. Click the Browse box to the right of the Event Type box to select the event you
want to audit for the selected business object.
4. Click the Browse box to the right of the Audit Type box to select the type of audit
to use for this mapping. The audit types are represented by business objects that
are children of the Fnd0AuditLog business object.
5. Click the Browse box to the right of the Secondary Audit Type box to select
the Fnd0SecondaryAudit business object. This Secondary Audit object stores
information and properties about the secondary objects that are related to the
main object being audited.
6. Select the Subscribable? check box to specify that the event type mapping
can be subscribed to.
7. Select the Auditable? check box to specify that the event type mapping can be
audited.
8. In the Description box, type a description for this mapping so that others know
what it is used for.
9. Click Finish.
5. If you select Database as the storage type, the Archive Media list appears.
Select the archive media from the Archive Media list.
Note Leaving the Archive Media list blank causes all generated audit records
to remain in the database until you manually delete them.
If there are no values in the Archive Media list, you must create a storage media.
For more information, see Create storage media for archiving.
c. To remove a property from the Logged Properties list, select the property
and click Remove .
7. Click Create to add the object to the database and add the Audit
Definition object to the Audit Definition Objects tree.
You can also create an audit definition object by using the define_auditdefs
command line utility.
c. To remove a property from the Logged Properties list, select the property
and click Remove .
2. Click Delete .
• If you select an object, the object ID, name, revision, and object type are
displayed in the Search Criteria section.
• To select a project, select a project you have access to from the Project list.
• If you want to search for a different object, click the Clear button to clear
the existing search criteria and then type the object ID, name, and revision
in the Audit Log dialog box.
3. (Optional) Specify additional search criteria, such as event type, user ID, and
date created.
4. (Optional) Click the Advanced tab and type criteria to construct a query based
on property values.
Note The Advanced tab does not display any information if there are no
logged properties in the audit definition object.
c. Select the properties for which you require audit logs from the Available
Properties list, and click the button to move the property to the Selected
Search Criteria list.
Note You can add up to 20 properties in the Selected Search Criteria list.
d. To search for properties based on old or new values, in the Selected Search
Criteria list, enter the old value in the Old Value column and the new value
in the New Value column.
e. Click Find.
Audit logs that match your selected criteria appear.
5. Click Find.
The system displays the audit logs that match the search criteria.
Property value changes are shown in the User Data column of the audit log. The
User Data column shows the property name, the old value of the property, and
the new value of the property.
The old value of the property is the same as the new value of the property if
the property value does not change.
Note Only persistent properties of objects are tracked. Run-time, compound,
and relational properties are not tracked by Audit Manager.
2. Type the object ID of the deleted object in the Audit Log dialog box.
3. Click Find.
Teamcenter displays the audit logs of the deleted objects.
• Avoid using object type as the only search criteria. Enter additional criteria
along with the object type.
• Avoid using wide date ranges. If you use a wide date range, select additional
search criteria.
• Avoid using only event type. Generally, an audit log has maximum records for
the Modify event.
• Avoid search only by error code. By default, all values are 0 and may cause
Teamcenter to crash.
For more information about searching for audit information, see View legacy audit
log information.
• ON
View→Audit→View Audit Logs is available.
• If you select an object, the object ID, name, revision, and object type are
displayed in the Search Criteria section.
3. (Optional) Specify additional search criteria, such as event type, user ID, and
date created.
4. (Optional) Click the Advanced tab and type the criteria to construct a query
based on property values.
Note The Advanced tab does not display any information if there are no
logged properties in the audit definition object.
5. Click Find.
The system displays the audit logs that match the search criteria.
• From the Object Selection section, choose one of the following options:
o Choose the Export Selected Objects option to export only the selected
objects from the audit log.
o Choose the Export All Objects In View option to export all objects from
the audit log.
• From the Output Format section, choose one of the following options:
o Choose the Use Excel option to export the audit logs in an Excel file.
Select the Excel export template from the list next to the Use Excel
option.
Note The export to Excel option is only available on Microsoft
Windows machines.
o Choose the Use CSV option to export the audit logs in a CSV file.
Beginning with Teamcenter 10.1, the legacy workflow and reservation auditing
functionality is no longer available. This section documents the functionality
available before Teamcenter 10.1.
The workflow and reservation audit functionality gives you the ability to capture
workflow, signoff, and checkout audit logs. The audit logs are stored in a file.
Note Beginning with Teamcenter 10.1, the legacy workflow and reservation
auditing functionality is no longer available. This section documents the
functionality available before Teamcenter 10.1.
Set the following preference to use the workflow and reservation auditing
functionality:
• TC_audit_manager
Set the preference value to OFF to enable the auditing functionality.
You must restart Teamcenter after you change Audit Manager preferences for the
changes to take effect.
For more information about the preference, see the Preferences and Environment
Variables Reference.
Note Beginning with Teamcenter 10.1, the legacy workflow and reservation
auditing functionality is no longer available. This section documents the
functionality available before Teamcenter 10.1.
Audit and signoff history reports generated for selected data objects or workflow
processes contain details and additional information about each task.
Note Beginning with Teamcenter 10.1, the legacy workflow and reservation
auditing functionality is no longer available. This section documents the
functionality available before Teamcenter 10.1.
2. Choose View→Audit→File.
The system displays the workflow audit file in the View Audit File dialog box.
Note Legacy audit files display information about workflow-related events, such
as when a task is started, approved, or completed. Audit files also display
information about the delegation of tasks using the Out of Office Assistant,
which appears in the log file as Assign Approver events.
IV Appendix
o EPMTask:__Add_Attachment
o EPMTask:__Remove_Attachment
o ADA_License:__Attach_License
o ADA_License:__Detach_License
o BOMView Revision:__Component_Add
o BOMView Revision:__Component_Remove
o ScheduleTask:__ResourceAssignment_Create
o ScheduleTask:__ResourceAssignment_Modify
o ScheduleTask:__ResourceAssignment_Delete
o ScheduleTask:__TaskDependency_Create
o ScheduleTask:__TaskDependency_Modify
o ScheduleTask:__TaskDependency_Delete
• Fnd0OCC_track_position_orientation_audithandler
This log extension enables the logging of occurrence position and
orientation changes of the components in structures. It is attached to the
PSOccurrence:__Modify audit definition.
Note You must not use this log extension in any audit definition except for
audit definitions that log position and orientation changes of components
based on occurrence properties.
• Fnd0CICO_auditloghandler
This log extension applies to checkin and checkout events. It logs the change
ID and reason why the object is checked in or out.
• Fnd0PROJInfo_audithandler
This log extension logs information about objects that are assigned to projects.
The project names are separated by commas.
By default, this extension is not available on any audit definition.
• Fnd0USER_get_additional_log_info
This log extension logs workflow information. For example, for the __Assign
event, this log extension logs information like the process name, task type, user
comments, user ID, and the user name the workflow is assigned to.
This log extension applies to workflow-related events such as __Abort,
__Add_attachment, __Approve, __Assign, __Assign_Approver,
__Complete, __Demote, __Fail, __Notify, __Perform, __Reject,
__Stand_In, __Remove_Attachment, __Resume, __Start, __Suspend, and
__Update_Process.
• Fnd0WriteSignoffDetails
This log extension logs workflow signoff history. For example, for the
__Add_attachment event, this log extension logs information like signoff
decision, job, sign off, user ID, sign off group, and sign off role name.
This log extension applies to workflow related events such as
__Add_attachment, __Approve, __Reject, __Stand_In, and
__Remove_Attachment.
• combine_audit_files
• define_auditdefs
For more information about these utilities, see the Utilities Reference.
• AUDIT_delete_specified_records
• AUDIT_get_records
• AUDIT_get_records_with_specified_col
• AUDIT_initialize_log_query
• AUDIT_insert_record
• AUDIT_log_event
• AUDITMGR_add_audit_properties
• AUDITMGR_create_audit_definition
• AUDITMGR_find_audit_definition
• AUDITMGR_get_archive_media
• AUDITMGR_get_audit_properties
• AUDITMGR_get_auditable_types
• AUDITMGR_get_event_type
• AUDITMGR_get_log_handler
• AUDITMGR_get_max_days_kept
• AUDITMGR_get_object_type
• AUDITMGR_get_storage_type
• AUDITMGR_remove_audit_properties
• AUDITMGR_set_archive_media
• AUDITMGR_set_log_handler
• AUDITMGR_set_max_days_kept
• AUDITMGR_set_storage_type
You can view audit logs for changes to structure from Structure Manager,
Multi-Structure Manager, or Manufacturing Process Planner applications.
To view audit logs in these applications, do one of the following:
For more information about viewing audit logs, see View legacy audit log information.
Teamcenter provides the following audit definitions for viewing changes to structure:
Note For position and orientation tracking, actual values of position and
orientation are not written to audit logs. For position change, old value is
written as Old Position and new value is written as New Position. For
orientation change, old value is written as Old Orientation and new value
is written as New Orientation.
Changes to UG Form are written as changes to UG Dataset.
Property Value
primary object Component object reference
eventTypeName Modify
propertyCount 1
propertyNames NXPartHistory
The signature of the Teamcenter services API to create audit log is as follows:
DataManagementImpl::PostEventResponse DataManagementImpl::postEvent (
const std::vector< PostEventObjectProperties >& input,
const std::string& eventTypeName )
The signature of the Teamcenter services API to get event types for given object
types is as follows:
DataManagementImpl::EventTypesResponse DataManagementImpl::getEventTypes
(const std::vector< ObjectType >& input )
You can find the events that are auditable in the Event Type Mapping editor of
Business Modeler IDE.
For more information about the Event Type Mapping editor, see the Business
Modeler IDE Guide.
The following events are not auditable by default:
• Read_File
• Write_File
For more information about making these events auditable, see Create an event
type mapping.
A AUDITMGR_get_archive_media
function . . . . . . . . . . . . . . . . . . . . . . C-1
Action handlers AUDITMGR_get_audit_properties
Audit Manager . . . . . . . . . . . . . . . . . 8-4 function . . . . . . . . . . . . . . . . . . . . . . C-1
Archive audit files . . . . . . . . . . . . . . . . . 9-3 AUDITMGR_get_auditable_types
Audit definition function . . . . . . . . . . . . . . . . . . . . . . C-1
Creating . . . . . . . . . . . . . . . . . . . . . . 3-1 AUDITMGR_get_event_type function . . C-1
Audit definition objects AUDITMGR_get_log_handler
Creating . . . . . . . . . . . . . . . . . . . . . . 9-1 function . . . . . . . . . . . . . . . . . . . . . . C-1
Deleting . . . . . . . . . . . . . . . . . . . . . . 9-3 AUDITMGR_get_max_days_kept
Modifying . . . . . . . . . . . . . . . . . . . . . 9-2 function . . . . . . . . . . . . . . . . . . . . . . C-1
Audit definitions . . . . . . . . . . . . . . . . . . 3-1 AUDITMGR_get_object_type function . . C-1
Audit log extensions . . . . . . . . . . . . . . A-1 AUDITMGR_get_storage_type
Fnd0CICO_auditloghandler . . . . . . . A-2 function . . . . . . . . . . . . . . . . . . . . . . C-1
Fnd0OCC_track_position_orientation_ AUDITMGR_remove_audit_properties
audithandler . . . . . . . . . . . . . . . . A-2 function . . . . . . . . . . . . . . . . . . . . . . C-1
Fnd0PROJInfo_audithandler . . . . . . A-2 AUDITMGR_set_archive_media
Fnd0USER_get_additional_log_info . . A-2 function . . . . . . . . . . . . . . . . . . . . . . C-1
Fnd0WriteSecondaryProperties . . . . . A-1 AUDITMGR_set_log_handler
Fnd0WriteSignoffDetails . . . . . . . . . A-2 function . . . . . . . . . . . . . . . . . . . . . . C-2
Audit Manager AUDITMGR_set_max_days_kept
Audit definition . . . . . . . . . . . . . . . . . 3-1 function . . . . . . . . . . . . . . . . . . . . . . C-2
Event type . . . . . . . . . . . . . . . . . . 3-4, 8-5 AUDITMGR_set_storage_type
Event type mapping . . . . . . . . . . . 3-5, 8-6 function . . . . . . . . . . . . . . . . . . . . . . C-2
Audit Manager interface . . . . . . . . . . . . 1-1
Audit objects . . . . . . . . . . . . . . . . . . . . . 1-3
Audit reports B
Viewing in HTML format . . . . . . . . . 12-1 Basic concepts . . . . . . . . . . . . . . . . 1-2, 7-3
audit_archive utility . . . . . . . . . . . . . . B-1 Audit definition object . . . . . . . . . . . . 7-3
AUDIT_delete_records function . . . . . . C-1 Viewing audit information . . . . . . . . . 7-4
AUDIT_delete_specified_records Basic tasks . . . . . . . . . . . . . . . . . . . . . . 7-4
function . . . . . . . . . . . . . . . . . . . . . . C-1
AUDIT_get_records function . . . . . . . . C-1
C
AUDIT_get_records_with_specified_col
function . . . . . . . . . . . . . . . . . . . . . . C-1 Combine audit files . . . . . . . . . . . . . . . . 9-3
AUDIT_initialize_log_query function . . C-1 combine_audit_files utility . . . . . . . . . . B-1
AUDIT_insert_record function . . . . . . . C-1 Command line utilities . . . . . . . . . . . . B-1
AUDIT_log_event function . . . . . . . . . . C-1 Configure Audit Manager . . . . 1-1, 7-2, 8-1
audit_user.properties file . . . . . . . . . . . . 8-3 Access control . . . . . . . . . . . . . . . 2-4, 8-2
AUDITMGR_add_audit_properties Archiving . . . . . . . . . . . . . . . . . . . . . 8-2
function . . . . . . . . . . . . . . . . . . . . . . C-1 Audit log archiving . . . . . . . . . . . . . . . 2-6
AUDITMGR_create_audit_definition Audit searching . . . . . . . . . . . . . . . . . 8-3
function . . . . . . . . . . . . . . . . . . . . . . C-1 Business constants . . . . . . . . . . . . . . . 2-2
AUDITMGR_find_audit_definition Custom audit reports . . . . . . . . . . . . . 8-4
function . . . . . . . . . . . . . . . . . . . . . . C-1 Custom log extensions . . . . . . . . . . . . 2-7