last_logged_in_date changes for inactive accounts that created Action Items

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Steps to Reproduce: 

1. Create a Process. Create an Action Item within it. Configure the Process in such a way that the Process moves to Finish step, only when all assignees approve this Action Item
2. Create or use an existing account at Administration > Resources. Provide it all access rights in the system. Set it to status = Active
3. Login via the account at step 2. Navigate to Home > Organizers > Processes > Available Processes > Trigger the Process from step 1. Logout of this account
4. Log back in via the admin account. Navigate to Administration > Resources > Open the account from step 2 > Set it to status = Inactive
5. Check the last_logged_in_date column of the cmn_sec_users table now. Note down the time stamp shown in it
6. Restart the BG service of this system
7. Wait for about 3 to 5 minutes

Expected Results: last_logged_in_date should not change for the account from step 2, since it is inactive

Actual Results: last_logged_in_date for this inactive account changes because it has an open Action Item that was created by it

Environment

Clarity 16.3.2

Cause

DE173913

Resolution

This issue is fixed in:

• Clarity 16.4.0 Patch 1 (16.4.0.1)
• Clarity 16.4.1

A new system option is introduced, called BPM_SKIP_LASTLOGIN_UPDATE_FOR_INACTIVE_USERS. This system option has to be set to True for the application to not update last_logged_in_date of inactive or locked users.

Additional Information

The toggle mentioned above only works with respect to Processes.