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 37 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.

  • 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 system fixes. Track progress TAP-446; TAP-465, albie.roets ,
  • DQ Report: Death date / other details, but not deceased, Manpreet Sidhu ,
  • 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 ?

CLOSED

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

  • Present the Account Naming Conventions, jessica.wood

CLOSED

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 - difference between SITS and Jarvis (Google Based)

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 Address” for Household and “Business Address” for Organisations.

CLOSED

BR-009

Duplicate Accounts

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

  2. Analyse how do 'Duplicate Record Set' functionality work, Rules, audit the rules to make sure they are accurate, Manpreet Sidhu , → TAP-1214 Jarvis Duplicate Rule Sets

OPEN

BR-010

Mobile Phone Field

What details should be in the mobile phone field ? Aust mobile vs international mobile

Present: rommel.ngo , Monica Kluegel , jessica.wood , Yeng Sembrano , Nick Kellaway , Polina Nikulina ,

FYI: AlainGasquet Manpreet Sidhu

Agreed in principle:

  1. Mobile phone should be for Australian mobile phones;

  2. Account phone should be for Australian landline numbers;

  3. We need some rigour around international numbers; - Where do they go ??

  4. We need a clear view of how the phones fields are populated and to review why (eg why SITS populates Account and not Contact),

  5. The preference of the business is to create new fields for international landline and mobile numbers as the alternate channels are not used by the majority of users but we need to decide if it is feasible

OPEN

BR-011

Contacts Address Preference

  • If Address is blank on Contact & Account, should Address Preference be Blank too ? (Next Steps:- create a validation rule for address preference, should be blank for blank addresses)

Present: Monica Kluegel , AlainGasquet , Nick Kellaway , albie.roets , Manpreet Sidhu ,

  • Set to blank,

  • Once updated: Set default based on contact and account type - engage community giving - prepare options (exhaustive)

BR-012

Student ID

  • If the student ID cannot be verified, then should we mark it as type='other'? or leave it as it is i.e, type='Sydney Student ID'.

Present: Monica Kluegel , AlainGasquet , Nick Kellaway , albie.roets , Manpreet Sidhu ,

BR-013

Staff are associated to which faculties

  • Is there a way to map Development Staff to faculties in Jarvis? (Does anything exist)

BR-014

Address Status for Deceased = Deceased ?

  • ?

BR-015

Unit Addresses not Unit x<space>, but “/”

Address Formatting Business Rules

BR-016

Address Type consolidation

TAP-1021 - Getting issue details... STATUS

Address Status Rules

Define statusses

  • No labels