|
<< Click to Display Table of Contents >> Navigation: »No topics above this level« Auditing user management |
mapp Services V5.16
Events for these components can be recorded using MpAudit. For more information about how to create an entry, see section Defining the event text.
The identification number can be incorporated in the respective entry using the token %act.
The following events can occur for these mapp components:
This section lists the different user events:
This event type allows user management events such as deleting/adding a user to be recorded.
Event ID 2 |
Components |
||||||||||||||||||||||||||||||||||||||||||||||||
Events |
|||||||||||||||||||||||||||||||||||||||||||||||||
op |
Name of the user who was logged in when the event occurred |
||||||||||||||||||||||||||||||||||||||||||||||||
ev |
Event ID |
||||||||||||||||||||||||||||||||||||||||||||||||
idx |
Returns the index of the currently generated event. The value is incremented on each new event. The first generated event in the event list thus has value 1; the 50th event has index 50 and the 100th has index 100. |
||||||||||||||||||||||||||||||||||||||||||||||||
map |
Name of the mapp component to which the event is assigned via MpLink |
||||||||||||||||||||||||||||||||||||||||||||||||
usr |
User who is affected by the event (e.g. user who was deleted) |
||||||||||||||||||||||||||||||||||||||||||||||||
act |
Action that was executed in a mapp component. The ID for the action is returned (e.g. 10 for "Invalid username entered"). For additional information, see the following table:
|
||||||||||||||||||||||||||||||||||||||||||||||||
Table: User management event
For information about how to specify the event text, see section Using the new format.
Example of the new format:
•"{&op} - Action: User {&usr} was deleted" evaluated: "Admin - Action: User Mike was deleted", which means that user Admin deleted user Mike.
Example of the old format:
•"[%op] - Action: User [%usr] was deleted" evaluated: "Admin - Action: User Mike was deleted", which means that user Admin deleted user Mike.
This event type allows events involving the electronic signature to be recorded.
Event ID 3 |
Components |
|||||||||||||||
Events |
||||||||||||||||
cmt |
Comment specified by the user for the signature |
|||||||||||||||
id |
Name of the mapp component to which the event is assigned via MpLink |
|||||||||||||||
idx |
Returns the index of the currently generated event. The value is incremented on each new event. The first generated event in the event list thus has value 1; the 50th event has index 50 and the 100th has index 100. |
|||||||||||||||
err |
User management error number (can be used to display whether the username or password was incorrect, for example) |
|||||||||||||||
act |
Returns the action ID that must be specified in the configuration for a signature |
|||||||||||||||
type |
Action that was executed in a mapp component. The ID for the action is returned (e.g. 2 for "Electronic signature canceled"). For additional information, see the following table:
|
|||||||||||||||
Table: Electronic signature event
For information about how to specify the event text, see section Using the new format.
Example of the new format:
•"Signature ID {&act}: {&typ} ({&typt})" evaluated: "Signature ID 3: Electronic signature was successfully executed (OK)", which means that the signature was successfully executed with ID 3.
Example of the old format:
•"Signature ID [%act] : [%typ] ([%typt]" evaluated: "Signature ID 3: Electronic signature was successfully executed (OK)", which means that the signature was successfully executed with ID 3.