Capturing AddOper and ModOper for Web Transactions

Prior to 7.4.0, the system used the logged in PSM user to update ADDOPER/MODOPER auditing information. As of 7.4.0, you can now store the ID of the customer who updated the information over the web, using our e-Business solution or via customer site using our APIs. To make this possible, the APIs and e-Business core were modified to allow end users to update which value should be used for the auditing log fields.

To do so, you must set EnableAddModOperatorAlias to “True” in the config.xml to enable this functionality to set WebUserId from e-Business. The default value for this is “True”. If the value is not found in the configuration, the system assumes “False” value.

<Item Name="UserInterface"

SplashScreen="False"

ApplicationHostType="MDIMain"

. . .

. . .

EnableAddModOperatorAlias="True"

/>

Personify recommend using MasterCustomerId|SubCustomerId combination for the auditing fields on BusinessObjectCollection. However, it could be anything as long as the value complies with the DB column size. Internally, the system will prefix this value with "WEB_" so that it can be distinguished from standard PSM User.

For example, if the logged in customer ID is 000000000012 and the sub customer ID is 0, then you can set this value to a collection as follows:

oCollection.AddModOperatorAlias = “000000000012|0”

The system will store this value as “WEB_000000000012|0” and this will be used to set the ADDOPER / MODOPER.

This functionality is only applicable to DNN web modules and canNOT be used for .NET controls.