Activating Google Integration in the New Year database


Overview

The New Year Rollover settings have the option of disabling Google Integration in the current year and rolling them over to the new year database, or keeping the Integration active in the current year and not updating them in the New Year.



Keep Google Integration active in the current year?

Checking the box: Yes

  • Leave Google DPT record alone
  • Do NOT Roll ScheduledProcesses Like 'Google%'

Not checking the box: No

  • Disable Google DPT record
  • Roll ScheduledProcesses


If the box is not checked to keep the Integration active in the current year, two things happen:


1. The JSON Private Key file name in DPT is appended with '_DisabledDuringRollover'.  This prevents Aeries from finding the file and the Google sync stops for that database.




2. In ScheduledProcesses, the DatabaseYear is updated to the New Year




If the box is checked to keep the Integration active in the current year these changes do not occur and the Integration continues to sync in the current database. In the New Year database the Integration will continue to show as active, but the databases will still be pointing to DbYear '20'.


Activating Google Integration in the New Year database ↑


To move the integration to the New Year database:

  • Rename the JSON Private Key File in the current year database so it won't be found. This can be done on the Google Service Account Settings tab. You can rename the file to anything you prefer.



This needs to be done on both the Google Apps Integration page and the Google Staff Integration page.


  • Update the DbYear in ScheduledProcesses to the new year.
    • This can be done through SQL or, in the new year,  by clicking 'Save' in the Directory Sync tab settings on the Google Apps Integration  and Google Staff Integration pages. This will update the DbYear to the database where the settings are saved.



This needs to be done on both the Google Apps Integration page and the Google Staff Integration page.