000036631 - In RSA Identity Governance & Lifecycle, what is the difference between an account's Last Collected Date and Last Collected On?

Document created by RSA Customer Support Employee on Sep 4, 2018Last modified by RSA Customer Support Employee on Sep 4, 2018
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000036631
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.x
 
IssueThere has been some confusion about the date of an account's values for Last Collected Date and Last Collected On, specifically after the last Account Data Collection.
 
For instance, the last Account Data Collection (with no account changes) was on 1 August 2018  at 05:25: 


 


Last ADC run with no account changes
 

 

When the account information is viewed (by navigating to Collectors [Account Data Collector]  > Accounts tab and selecting an account), you will see that the Last Collected On date is the date when the last Account Data Collection ran.  In this example it was on 1 August at 05:25..

However, when you look at the Last Collected Date column in the T_AV_ACCOUNTS table or in the V_AVR_ACCOUNTS view used by your generated Custom Report (e. g., TestAccounts.pdf), you will notice that the Last Collected Date column was not updated to 1 August at 05:25, when the last Account Data Collection ran.


 


Account's 'Last Collected On' vs 'Last Collected Date'
ResolutionThe data for Last Collected Date and Last Collected On are different. 
  • Last Collected On is linked to the last collection run, while
  • Last Collected Date is actually the date a specific account got pulled into the application. 
From RSA Identity Governance & Lifecycle 7.0, we do a delta collection where we change the Last Collected Date of an account only if there is any change from the previous run to the current run. If there is no change, the Last Collected Date would be the date on which it was collected earlier. 

Assuming that in the first Account Data Collection Run #1, we have collected three accounts (acct1, acct2, acct3) on 15 April 2018 at 11:10 and the Last Collected Date (for accounts) and the Last Collected On dates would be 15 April 2018 11:10.

Now Account Data Collection Run #2 is performed on 17 April 2018 at 5:10, there is a change for acct1 (i. e., one of its attributes is changed and that attribute is part of your configuration) and for the other two accounts there is no change. After this run, Last Collected On will now be 17 April at 5:10, while the Last Collected Date for these accounts would be as shown below:
 
acct104/17/2018 5:10 
acct204/15/2018 11:10
acct304/15/2018 11:10


 


For instance, change an attribute of an account your are collecting.  In this eample, it is jausten11.  Then run the Account Date Collection. 


 


Last ADC run with account change



When the account information is viewed (through Collectors [Account Data Collector]  > Accounts tab > [select an account]), you will see that the Last Collected On is the date when the last Account Data Collection run on 2 August 2018 at 08:21.

Now, when you look at the Last Collected Date column in the T_AV_ACCOUNTS table or in the V_AVR_ACCOUNTS view for the specific jausten11 account whose attribute you changed, you will notice that the Last Collected Date column for that account has been updated to 2 August 2018 at 08:21, since that account has changed. 
 


Last Collected Date got updated due to account change


 

Attachments

    Outcomes