Auditing changes to imported objects
FileNet® Deployment Manager includes options to capture a record of changes to imported objects into an audit file and generate an audit report from that file.
When you configure the options for an import, you can an audit option that generates a record of changes for the imported objects, known as an audit file. The audit file includes before and after information for each of the objects in the selected deployment data set. You can use audit file to generate an audit report that contains a more consumable version of the audit file data. The audit report can be used to view and understand detailed differences between the objects in the deployment data set and the objects in the destination environment.
You can choose from three different audit modes, import only, import with audit, or audit only. For the audit-only mode, a simulated import is done, but no objects are created or updated and only the audit file is produced. The audit-only mode captures proposed changes; the destination environment is not modified. In this situation, certain objects with dependencies on other objects in the deployment data set might not be able to be audited completely. Additionally, a successful audit-only import run does not guarantee a subsequent import operation to be error-free. The destination system might change before the actual import operation is performed. There can also be side effects to the import operation if the destination environment is modified. For additional information about the audit modes, see Import options.
- Indication of the objects in the deployment data set whose import causes changes in the destination environment.
- Values for all scalar properties with both the before and after values when they are different.
- IDs of all object-valued properties.
- If those objects also appear in the deployment data set, they are among the objects that are captured in the audit file and the ID can be used to locate them in the audit report.
- If those objects do not appear in the deployment data set, they must exist in the destination environment for the import operation to succeed. The ID can be used to locate them in the destination environment.
- Accounting of new objects that include their properties.