-
Notifications
You must be signed in to change notification settings - Fork 1
Aggie Enterprise Migration
Jason Sylvestre edited this page Sep 13, 2023
·
8 revisions
- Update config settings.
- If we don't have the prod AE endpoints yet, we can use UAT as we just use it for validation
- Set UseCoA to true
- Update to AE prod settings when available
- In sloth, only approve txns that have KFS accounts
- Update all rates to use COAs (Me: Possibly use a DB script to update as there are only about 22 unique accounts in the rates) or manually Brian/Financial people
- Once all rates have been updated, go here and update any unprocessed expenses that have KFS accounts: /System/UpdatePendingExpenses
- Review logs for KFS accounts that do not auto convert successfully.
- Approve AE Txns (at this point, the different harvest teams in sloth can approve on any time schedule)
"AggieEnterprise": {
"GraphQlUrl": "[External]",
"ConsumerKey": "[External]",
"ConsumerSecret": "[External]",
"TokenEndpoint": "[External]",
"ScopeApp": "HRV-Web",
"ScopeEnv": "Test",
"UseCoA": "false",
"NormalCoaNaturalAccount": "770006",
"PassthroughCoaNaturalAccount": "770002"
}
- When UseCoA is turned on, project accounts will try to use the KFS account convert if applicable. The NaturalAccount portion will be populated with the config setting NormalCoaNaturalAccount
- COAs must be valid to be sent to Sloth (this includes KFS converted ones), email will/should be generated if invalid
- The /System/UpdatePendingExpenses menu choice shows pending expenses. There is a column that shows if the account on the expense is different from the account in the associated rate. You can click on the project and accounts to go there. The update button will updated the unprocessed expenses with the account in the associated rate.