Siebel Tools >  Data Validation Manager DVM showing un-wanted error message along with custom error message

Data Validation Manager DVM showing un-wanted error message along with custom error message

APPLIES TO:
Siebel Tools - Version 7.7.2.6 SIA [18372] and later

SYMPTOMS
We have a requirement that says, if the account Status = ‘Invalid’ then the user should not be allowed to change the value in the Action field. Here both the fields Status and Action are of type LOV. If the user attempts to do so, an error message should pop-up with text and ‘ok’ button.

I tried using DVM to achieve this functionality, But, while testing, an un-wanted error message was also displayed along with the Custom Error message.
I am attaching the screen shot of error message for your reference.

in order to investigate the un-wanted error message issue, I have tried setting the same DVM Rule on other 2 fields Type Code and XMSR Credit Class (GUI names : Type, Credit Class) where both fields are of type LOV. And, the same un-wanted error message was displayed In this case also.

SOLUTION
Customer had used to Data Validation Manager DVM functionality and had defined a custom message, “You Cannot Activate Invalid Accounts!” to be displayed when the user tries to change the account ‘Action’ field when the status of the account is set as ‘Invalid’. When the message was being displayed in the UI.

They were finding it was being displayed as such:

[1] Wrong field values or value types detected in field Action. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)

[2] You Cannot Activate Invalid Accounts! (SBL-IAI-00402)

Considering the context of displaying the error message, the first error message, a generic Siebel error message, should not be included.

This behaviour was reproducible in an otherwise totally standard environment, and Bug (Enhancement) #10522689 was raised as a result to look to only display the custom error message in future. This Enhancement has been rejected and the Workaround is to use PreSetFieldValue to validate the field and raise custom error text.

Further information regarding configuring DVM Rules and using Runtime Events to capture user interaction, may be found in Bookshelf references:

Siebel Order Management Guide > Data Validation for Order Management > Process of Administering Data Validation Rules

Siebel Personalization Administration Guide > Tracking Run-Time Events