When creating a new affiliation on a request, don't automatically default it to the contact that is already the Primary Request Contact
•Brief Description: Client requests that Primary Contact not appear as default when creating new Affiliation for a Request •Current Function: Currently, when going to New>Affiliation from a Request record, the affiliation contains the Primary Contact as the default value •Desired Function: The client wants the Contact to be cleared so that they may enter the contact of their choice rather than retain the Primary as the default. •Reason for Function: The reason for this request is that it is more intuitive to the client and comprehends to their workflow - they do not see many examples where the Primary Contact fulfills multiple roles •Priority: Medium
Improvements to "New Affiliation" workflow
Merged