Skip to content

Aggie Enterprise Migration

Jump to bottom
Jason Sylvestre edited this page Aug 29, 2023 · 4 revisions

November/December ish

  • Merge Dev into Master
  • Deploy / Verify the deployment. Remember, prod deploys go into a staging slot.
  • Keep the use COA as false
  • Update the other config setting to use the correct AE endpoints.

Config settings Defaults:

"AggieEnterprise": {
"GraphQlUrl": "[External]",
"Token": "[External]",
"ConsumerKey": "[External]",
"ConsumerSecret": "[External]",
"TokenEndpoint": "[External]",
"ScopeApp": "Anlab-Web",
"ScopeEnv": "Test",
"UseCoA": "false",
"AnlabCoa": "3110-12100-ADNO033-775000-62-000-AR06023201-000000-0000-000000-000000"
"NaturalAccount": "770003"}
  • Confirm values in the Portal AppSettings have not been changed and these are correct.
  • ScopeEnv should be Prod

End of December? (Last year, there were 9 Sloth Txns from Dec 16 to Dec 22 (Looking at up to jan 1)

  • Process any sloth txns pending approval.
  • Change UseCoa to true
  • Change sloth to use COAs

If we change the sloth settings in prod to use the COA, that means any CreditCard txns will be processed by Aggie Enterprise. But If we don't update sloth's AE settings, these will fail until we do.

Once the useCoa is set to true 2 things will happen:

  1. Users will need to enter a COA for new orders using a UCD account
  2. Orders that have a KFS account will use the KFS convert when the order is finalized, then try to send that to sloth. If any of this fails, the order will not be finalized and they will get an error message.
Clone this wiki locally