Record acivivity of user
- kda
- Topic Author
- Offline
- Platinum Member
- Posts: 603
- Thank you received: 3
I heard that in T24, It has file record the activity of user did in system. What file that it store and If there is that file, Do we have way to avoid (Mean: do not record activity) of sign on.
Thanks
Please Log in or Create an account to join the conversation.
- pavisk
- Offline
- New Member
- Posts: 7
- Thank you received: 0
Regards,
Please Log in or Create an account to join the conversation.
- kda
- Topic Author
- Offline
- Platinum Member
- Posts: 603
- Thank you received: 3
Please Log in or Create an account to join the conversation.
- VigneshGautam
- Visitor
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired
- Posts: 2859
- Thank you received: 649
SIGN.ON.OFF.LOG
Specifies whether or not a record should be written to the PROTOCOL file recording every time this User SIGNS.ON or SIGNS.OFF.
Note: Unsuccessful attempts to SIGN.ON are always logged, regardless of the value in this field.
APPLICATION.LOG
Specifies whether or not records should be written to the PROTOCOL file recording every Application accessed by this User.
If Y is entered, a record is written to the PROTOCOL file every time this User accesses a different Application.
Validation Rules
Y (Yes) or N or NO (Mandatory input)
Security Violations are always logged, regardless of this field.
It must be NO if SECURITY MGMT LOG (Field 26) is NO.
SECURITY.MGMT.L
Specifies whether or not a record should be written to the PROTOCOL file everytime this User accesses any of the Security Management Applications.
If Y is entered, a record is written to the PROTOCOL file everytime this User accesses any of the following Applications:
PASSWORD PASSWORD.ENABLE PASSWORD.RESET USER PASSWORD.RESET
Note: Security Violations are always logged, regardless of the values in Fields 25-28.
FUNCTION.ID.LOG
Specifies whether or not full details of every Application, Function and record ID accessed by this User should be recorded in the PROTOCOL file.
Validation Rules
Y (Yes) or N or NO (Mandatory input)
It must be NO if APPLICATION LOG (Field 27) is NO.
Security Violations are always logged, regardless of this field.
Please Log in or Create an account to join the conversation.
- kda
- Topic Author
- Offline
- Platinum Member
- Posts: 603
- Thank you received: 3
thanks all
Please Log in or Create an account to join the conversation.
- Chan
- Offline
- New Member
- Posts: 6
- Thank you received: 0
Please Log in or Create an account to join the conversation.