R28753 PartyContactMechanism - Contact Mechanism Type And Purpose Contact Mechanism Type Cannot Be Different
Code | R28753 |
Entity | General.Contacts.PartyContactMechanisms Entity |
Name | ContactMechanismTypeAndPurposeContactMechanismTypeCannotBeDifferent |
Attribute | ContactMechanismPurpose |
Layer | Back-End |
Events | Commit |
Priority | Normal |
Modify | NO |
Action | Validate that:
IF there is a value in ContactMechanismPurpose field The value in ContactMechanism.ContactMechanismType is the same as the value in ContactMechanismPurpose.ContactMechanismType OR ContactMechanismPurpose.ContactMechanismType has no value |
Description | If the purpose of the party contact mechanism is defined, the purpose’s contact mechanism type
must be the same as the selected contact mechanism's type or must be null.
The purpose of the contact mechanism may be for example - "Email for invoices". So as a ContactMechanismType of the purpose "email" is selected. And then if a PartyContactMechnism sets its purpose attribute to the "Email for invoices" purpose, its ContactMechanism cannot be of type different than "email". |
Message | The contact mechanism type of the "{ContactMechanismPurpose}" purpose is different than
type of the selected contact mechanism - {ContactMechanism.ContactMechanismType}.
Please, select a proper purpose. |
Version | Introduced: 2018.2
Updated: v.24 |
Revocable | NO |
* For more information about the Business Rules Documentation Template and a short explanation of each column, see topic System Business Rules.