Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

Business Rules Meetings Minutes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 18 Next »

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 TAP-446; TAP-465 preventing actioning
  • DQ Report: Death date / other details, but not deceased. albie.roets
  • Death info fields needs to be read only - only via utility. albie.roets

Monica Kluegel

OPEN

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 ?

OPEN

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.

CLOSED

BR-004

Account Naming Conventions

OPEN

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

CLOSED

BR-006

Country Picklist

Full due diligence and impact analysis

OPEN

BR-007

TAP-860

TAP-860 - Getting issue details... STATUS

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

  • Email preference defaulted to Personal email.

CLOSED

BR-008

Address Type

Default to Home for Household and Business for Organisations.

CLOSED

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.

OPEN

BR-010

Address Formatting

AVE-365 - Getting issue details... STATUS

BR-011

Address input

AVE-366 - Getting issue details... STATUS

BR-012

Address RTS

AVE-367 - Getting issue details... STATUS

BR-013

Student Addresses

AVE-368 - Getting issue details... STATUS

BR-014

Student Emails

AVE-369 - Getting issue details... STATUS

BR-015

Household Primary/Secondary Contacts

AVE-371 - Getting issue details... STATUS

BR-016

Non Household Contacts 

AVE-372 - Getting issue details... STATUS

BR-017

Minimum fields contact/account establishment

AVE-373 - Getting issue details... STATUS

BR-018

Contact Salutations

AVE-374 - Getting issue details... STATUS

BR-019

Household Account Naming Definition

AVE-375 - Getting issue details... STATUS

BR-020

Naming Definitions Contact

AVE-376 - Getting issue details... STATUS

BR-021

Phone number formatting

AVE-377 - Getting issue details... STATUS

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

  • No labels