Changes Are Made to Business Objects
This release includes changes to six business objects.
New Business Object Attributes
The following business objects have been updated with new attributes.
| Business Object | New Attributes |
|---|---|
| Audit - Contract |
|
| Audit - RcvParametersAuditVO |
|
| Audit - Supporting Reference Audit |
|
Note: There is no way to revise an existing control with the new attribute.
Removed Attributes
The following business objects had attributes that have been removed.
| Business Object | Removed Attributes |
|---|---|
| Audit - Subinventory |
|
Note: Controls become invalid if they use any of the attributes removed from an audit business object.
Attribute Name Changes
The Tax Registrations: Registration Number value in the Supplier business object was moved to another source database table in a previous release that is not considered during data sync of the object. It is also considered sensitive data and not available as part of model or control analysis. If you do see values for this attribute they are not considered current, since they may reflect values entered before the data storage was moved to another table. The label of this attribute was changed to Tax Registrations: Registration Number - Unavailable.
Revised Business Objects
The Time Card Information business object in recent releases was not completely syncing all the available data. It has been revised so that it retrieves all available data based on your criteria. This may cause any controls based off delivered model content IDs of 50002, 50004, and 50011 to return additional incidents.
Business Benefit
Updates to audit business objects are made to support and maintain alignment with records in Setup and Maintenance > Manage Audit Policies.
Steps to enable and configure
When you use business objects that introduce changes to attributes, you must run the Transaction Data Source Synchronization job. Business objects with changes require that the data synchronization job to be run in order to return the related values. Depending upon the number of business objects you are using across models and controls, the data synchronization job may take a little longer than usual.