Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

Change Description Impact
Add a table Users that still use the old settings do not audit some transactions.
Remove a table Some transactions that must not be audited with the new settings are still audited by users that use the old settings.
Change the audit type for a table or field Some transactions are audited according to the old settings, and other transactions are audited according to the new settings.
Add or remove a field After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN.

Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Using Country of Origin for Purchase Orders
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
28101 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

FirstLast

Tips: LN | Baan

Categories