Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Number

Business Rule

Description / Decision

Date

Allocated to

Status

BR-001

Deceased Contacts

Deceased Contacts: It was agreed on to:

  1. reduce report age to 105;

  2. mark the Contact as Do Not Contact until Deceased Contact can be actioned;

  3. find the deceased date from https://ryersonindex.org/ ;

  4. If cannot find in Ryerson Index, then assume deceased - check https://gerontology.fandom.com/wiki/List_of_oldest_living_people_in_Australia to make sure not alive - make the deceased date the action date.

  5. Use Deceased Utility to decease. (Monthly Process)

  6. If deceased, then needs to be removed from any Primary Contact roles.

  •  OUTSTANDING: Can ownership of the utility be opened up to the BI Team Data Stewards for non-donors ? (Donors contact types stays with GA Team) Monica Kluegel , AlainGasquet
  •  Deceased Utility defects system fixes. Track progress TAP-446; TAP-465 preventing actioning, albie.roets ,
  •  DQ Report: Death date / other details, but not deceased. albie.roets , Manpreet Sidhu ,
  •  Death info fields needs to be read only - only via utility. albie.roets

Monica Kluegel

Status
colourGreen
titleopen

BR-002

Accounts with No Primary Contact

Household accounts MUST always have at least a primary contact. Corporations need to have a direct contact to receipt gifts. Not needed otherwise. Contact can only have 1x direct linkage to account.

  •  (Force people to use account create / Can you turn off people create households any other way - rommel.ngo (very hard to create validation rule to stop it - easiest way is DQ reports - await Rommels advice / palm off on Single CRM for solution.) - AVE-150
  •  Create DQ reports albie.roets

  •  rommel.ngo - can we force people to use account create ?

Status
colourGreen
titleopenCLOSED

BR-003

Households without a Primary/Sec contact

Household accounts must always have a Primary Contact. If more than one person on the account, then the one is Primary and the other is secondary. Kids on the account need to have their own account when they turn 18. (Less than 18 cannot have own account).

If only 1x contact and deceased, the account name gets moved to the estate. (Estate of the late …) → Harpreet does that.

Status
titleCLOSED

BR-004

Account Naming Conventions

  •  Present the conventions Account Naming Conventions, jessica.wood

Status
colourGreen
titleopen

BR-005

Address Preferences

Household = Auto Defaulted to ‘Account Mailing’.

Corporation = Business Mailing.

AVE-25

  •  Check ticket / fix for auto default of Address Preference in backlog albie.roets

Status
titleCLOSED

BR-006

Country Picklist

Full due diligence and impact analysis

Status
colourGreen
titleopen

BR-007

TAP-860

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyTAP-860

  • Phone preference be defaulted to mobile (because iMod leads are coming in with Mobile numbers)

  • Email preference defaulted to Personal email.

Status
titleCLOSED

BR-008

Address Type

Default to Home for Household and Business for Organisations.

Status
titleCLOSED

BR-009

Duplicate Accounts

How to resolve large duplicate account backlog?

Next steps:

  1. Gather rules - make decision if rules are accurate or not;

  2. How do 'Duplicate Record Set' functionality work - how to close, etc.

  3. Then make decision on how to fix it.

Status
colourGreen
titleopen

Unit Addresses - people to check as Google API do not deal with it well.

BR-010

Address Formatting

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-365

BR-011

Address input

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-366

BR-012

Address RTS

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-367

BR-013

Student Addresses

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-368

BR-014

Student Emails

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-369

BR-015

Household Primary/Secondary Contacts

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-371

BR-016

Non Household Contacts 

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-372

BR-017

Minimum fields contact/account establishment

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-373

BR-018

Contact Salutations

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-374

BR-019

Household Account Naming Definition

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-375

BR-020

Naming Definitions Contact

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-376

BR-021

Phone number formatting

Jira Legacy
serverSystem JIRA
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyAVE-377

BR-022

Business rules - importing address cleansing (with status to not break UX workflows) 

AVE-378

BR-023

International phone number handling

AVE-379

BR-024

Alternate Channel Archiving

AVE-380

BR-025

Business Rules - Handling preferences

AVE-381

BR-026

Business Rules - Contact Types

AVE-382

BR-027

Business Rules - Grateful Patients

AVE-383

BR-028

Business Rules - Account Relationship (Household)

AVE-384

BR-029

Business Rules - New contact Legal Credit/Recognition Credit

AVE-385

BR-030

Phone/Email Preferences

AVE-386

BR-031

Import Phone/Email Data

AVE-387

BR-032

Business Rule _ Estate Record Establishment

AVE-388

BR-033

<18 Contacts

AVE-389

BR-034

Chinese/Korean English Name Recording

AVE-392

BR-035

Chinese/Korean Names Middle Names Rule

AVE-393

BR-036

Employment End Date / Status

AVE-394