The phone (and address) are actually seperate blocks .. you can enter client details without phones and addresses or with and it's a master-detail. In Contact Center you usually use 'Create Person' or 'Create Organization' button and what we did there is make the email address required at the contact level ..
In Contact Center you have the advantage that you cannot directly create anything in the screen, but you have to use the create buttons.
Can you see if there is a when-validate-record trigger firing if you save the first/last name? Maybe you can use that trigger and check if the phone is entered before the person can save?
Thanks for the quick response, PamNL
Actually if you see the header block each has been divided into different triggers.
First Name & Last Name - AST_CU_PERSON
Contact Type & Phone - AST_CU_PHONE
Email - AST_CU_EMAIL
As you have told i have personalized the WHEN-VALIDATE-RECORD Trigger Event and made a condition like When Last name is not null. Trigger object AST_CU_PHONE and made the Phone Number column as required one in the Actions.Moreover when i try to save the form by just entering the First name and Last Name. Its not throwing any error.
Can you kindly suggest me in this. Hope the issue has been mentioned clearly. If please let me know i will clarify the issue clearly in the next p
Thanks PamNL, Looking forward for your update.
Can you show me a screenshot of what you've tried?
I will try to replay your requirement .. what I would try first is something like
Block: AST_CU_PERSON and another one on AST_CU_PHONE
:AST_CU_PERSON.Last_Name IS NULL OR :AST_CU_PHONE.PHONE_NUMBER IS NULL
Action: Message with Error
Ok, so now it should fire when the Phone is validated and only if a last name is entered. That's what your personalization would you ...
And your personalization would mean it would Always show the message whenever the last name is entered .. where actually you want to check if the Phone number is entered and not null (at least that is what I think).
But if you don't enter a Phone it makes sense it's not validated, because the trigger on AST_CU_PHONE never fires ..
I would build a personalization on AST_CU_PERSON with WHEN-VALIDATE-RECORD and condition
:AST_CU_PHONE.PHONE_NUMBER IS NULL OR :AST_CU_PERSON.LAST_NAME IS NULL
If any of these are null you get a warning message. I would remove the required property on Phone number, since your message already validates when you try to save.
Try this first .. then still it may not work if WHEN-VALIDATE-RECORD is not fired. So to be sure enable show custom events to see what happens if you try to enter invalid data. Then you know which events you can use and when.