Bulk Suspension Changes

Começar. É Gratuito
ou inscrever-se com seu endereço de e-mail
Bulk Suspension Changes por Mind Map: Bulk Suspension Changes

1. UI

1.1. DD stop

1.1.1. Is displayed as per the design

1.1.2. Is defaulted to yes

1.1.3. User can change it

1.1.4. If yes

1.1.4.1. and Suspension is fixed

1.1.4.1.1. OD mailstop until will be mandatory

1.1.4.2. and Suspension is inline

1.1.4.2.1. OD mailstop until will be mandatory

1.1.4.3. and suspension is indefinite

1.1.4.3.1. OD mailstop until will be optional

1.1.5. if No

1.1.5.1. for all suspension types

1.1.5.1.1. OD mailstop until is optional

1.2. Allow Facility Group and Multiple Facility selection

1.2.1. Facility and Facility account is not mandatory and user can select a facility group and click Run with no errors

1.2.2. Facility dropdown will be greyed out till user select a facility group

1.2.3. number of facilities less than 50

1.2.3.1. select All and select non options are displayed

1.2.3.2. Select All and none are working properly

1.2.3.3. multiple selection of facilities are allowed

1.2.3.4. if multiple facilities got selected , facility Account dropdown is greyed out

1.2.4. number of facilities more than 50

1.2.4.1. select All and none are hidden

1.2.4.2. multiple selection is allowed

1.2.4.3. user cannot select more than 50 facilities

1.2.4.3.1. what will be the behavior??

1.2.4.4. if multiple facilities got selected , facility Account dropdown is greyed out

2. Functionality

2.1. DD Stop

2.1.1. DB

2.1.1.1. If Account was not suspended or DD Stopped

2.1.1.1.1. Schedule suspension table

2.1.1.1.2. Payschedule record should be created for each suspended account

2.1.1.1.3. Accounts table

2.1.1.2. If Account was suspended with no DD Stop

2.1.1.2.1. Schedule suspension table

2.1.1.2.2. Payschedule record should be created for each suspended account

2.1.1.2.3. Accounts table

2.1.1.3. If Account was previously suspended with DD Stop

2.1.1.3.1. Schedule suspension table

2.1.1.3.2. Payschedule record should be created for each suspended account

2.1.1.3.3. Accounts table

2.1.1.3.4. a912388897725

2.1.1.4. If Account was not suspended but has DD Stop

2.1.1.4.1. Schedule suspension table

2.1.1.4.2. Payschedule record should be created for each suspended account

2.1.1.4.3. Accounts table

2.1.1.5. 2 bulk suspension overeach other

2.1.1.6. does odmail gets overriden?

3. Regression

3.1. Bulk suspension form

3.1.1. valid accounts

3.1.2. invalid accounts

3.1.2.1. Check the failed reasons.

3.1.2.1.1. 'Validation Failed: Account without recurring payschedule;'

3.1.2.1.2. 'Validation Failed: Account provided more than once;'

3.1.2.1.3. 'Validation Failed: Account belongs to different facility from selected;'

3.1.2.1.4. 'Validation Failed: Account closed;'

3.2. Bulk suspension upload

3.2.1. valid accounts

3.2.2. 'Validation Failed: Account without recurring payschedule;'

3.2.2.1. the valid accounts gets suspended and the invalid is mentioned in the sheet

3.2.3. 'Validation Failed: Account provided more than once;'

3.2.4. 'Validation Failed: Account belongs to different facility from selected;'

3.2.5. 'Validation Failed: Account closed;'

3.2.5.1. if account is closed or invalid -nothing gets suspended and the xls has only the invalid ids

3.3. Download excel

3.4. Check audit trail and call notes added

3.5. Bulk unsuspension

3.5.1. is correct for accounts without DD stop

3.5.1.1. account gets unsuspended

3.5.2. is correct for accounts with DDstop

3.5.2.1. if DD stop has bulk reason

3.5.2.1.1. account gets unsuspended

3.5.2.1.2. DD stop until date is updated to end suspension date

3.5.2.2. if DD has no bulk reason

3.5.2.2.1. account gets unsuspended

3.5.2.2.2. DD Stop until date does not change

3.6. check 5000 and 10000 accounts

3.6.1. genesis murray street 1600 account - 1 minute

3.6.2. genesis wantarina standard 4600 - failed first time then passed 3 minutes -inline

3.7. DB

3.7.1. Values are correct in Schedule Suspense

3.7.1.1. Suspension Value in schedule suspense

3.7.1.1.1. Values are correct in Schedule Suspense for RunningPaymentValue and RunningPaymentValuePeriodical

3.7.1.2. Suspension start and end Dates

3.7.1.2.1. indefinite

3.7.1.2.2. fixed

3.7.1.2.3. inline

3.7.1.3. what is Donotsyn ??

3.7.1.4. a record is created for each account under the selected facility account . only if account is has passed the validations

3.7.2. Check all payschedule table values

3.7.2.1. a record is created for each account under the selected facility account . only if account passed the validations

3.7.2.2. values

3.7.2.2.1. Class = schedule suspense

3.7.2.2.2. installment

3.7.2.2.3. startdate

3.7.2.2.4. frequency

3.7.2.2.5. payment type

3.7.2.2.6. pay type

3.7.2.2.7. paymethod