Aggie Enterprise Migration

Cutover Steps

December ish

Update Config settings:

Defaults:

        `<add key="UseCoa" value="false" />`
	`<add key="SlothAutoApprove" value="true" />`
	`<add key="AggieEnterprise:GraphQlUrl" value="[External]" />`
	`<add key="AggieEnterprise:GraphToken" va		`<add key="SlothAutoApprove" value="true" />`
	`<add key="AggieEnterprise:GraphQlUrl" value="[External]" />`
	`<add key="AggieEnterprise:GraphToken" value="[External]" />`
	`<add key="AggieEnterprise:ConsumerKey" value="[External]" />`
	`<add key="AggieEnterprise:ConsumerSecret" value="[External]" />`
	`<add key="AggieEnterprise:TokenEndpoint" value="[External]" />`
	`<add key="AggieEnterprise:ScopeApp" value="CRP" />`
	`<add key="AggieEnterprise:ScopeEnv" value="Test" />`lue="[External]" />`
	`<add key="AggieEnterprise:ConsumerKey" value="[External]" />`
	`<add key="AggieEnterprise:ConsumerSecret" value="[External]" />`
	`<add key="AggieEnterprise:TokenEndpoint" value="[External]" />`
	`<add key="AggieEnterprise:ScopeApp" value="CRP" />`
	`<add key="AggieEnterprise:ScopeEnv" value="Test" />`
	`<add key="AggieEnterprise:ClearingFinancialSegmentString" value="3110-13U20-ADNO003-410000-43-000-0000000000-000000-0000-000000-000000" />`
	`<add key="AggieEnterprise:FeeFinancialSegmentString" value="3110-13U20-ADNO003-410000-43-000-0000000000-000000-0000-000000-000000" />`

• AggieEnterprise:ScopeEnv = Prod
• AggieEnterprise: Use SIT settings for now so we can validate COAs
• Confirm COAs for fee and holding accounts (Holding account must match sloth)

Update Prod database

DB Change:

• FinancialSegmentString - new
• Account and Chart now nullable

Deploy Prod

Update config

• Sloth BaseUrl should not end with version (Can be done later after code is deployed)
• Verify txns continue to go through Sloth's KFS

Have Brian contact Registration admins and:

1. Have them check the KFS accounts they use. Find out what the COA string would be using finjector Explain some of the Registration specific rules for those:

• Department portion of the Financial Segment String must roll up to CAES or ANR
• Fund portion of the Financial Segment String must be 13U20
• Natural Account portion of the Financial Segment String must be 410004
• For PPM, Task's GL funding code must be 13U20
• For PPM, Expenditure Type (Natural Account) must be 410004

2. If they are "system" KFS accounts, they can provide us with the COA to replace it with and we can make that change. If they are user added KFS accounts, they will be responsible for updating their events to the correct COA around the last week of December. If they don't, their users will not be able to register for their events until it is corrected.
3. Update the Financial Account settings that we have COAs for

Last week of December or sometime...

Update Config settings:

• UseCoa = true
• SlothAutoApprove = false

Set all Financial Accounts that don't have a COA to inactive

Have Brian contact Registration amdins and have them update any of their active events to have a correct COA

We can update Sloth settings to use COAs ONLY if we point it to prod endpoints and prod is live. Or we could also do this if the AE settings in Prod Sloth do not have any values so the upload would fail.

After go live

• Go into Sloth and approve all pending txns (They should all have COAs)

Update Config:

• SlothAutoApprove = true

Watch to make sure everything in sloth and registration is working.