Use Deceased Utility to decease. (Monthly Process)
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
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
rommel.ngo - can we force people to use account create ?
Status
title
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.
We need some rigour around international numbers; - Where do they go ??
We need a clear view of how the phones fields are populated and to review why (eg why SITS populates Account and not Contact),
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
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)
Next steps: Auto update the field when user updates: Set default based on contact and account type - engage community giving - prepare options (exhaustive) - albie.roets ,
Done ticket
Jira Legacy
server
System JIRA
serverId
e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
key
TAP-1018
already completed.
Prepare address preference options for auto population based on account type, albie.roets ,