Question
Genpact
US
Last activity: 28 Oct 2015 6:14 EDT
How to apply a custom css on a field errored during validation rule.
CSS of text input error format is getting applied when a field is marked as required on section. Can get same applied on validation rule errors too.
Pegasystems Inc.
GB
Genpact
US
Skin settings of text input are effecting on required on section field and label color changed. where as below field label is still in black though having error on it.
Pegasystems Inc.
IN
Hi Sasidhar,
You can perform the following tests:
1. Using LiveUI tool, open the harness that contains the concerned section. Traverse to "Scripts & Styles" tab, and check if there is an addtional css applied to this harness (under Styles sheets).
2. Additionally, open the Skin rule and under Component Styles tab, click on the Dynamic Layout menu. Choose Errors from that list. Now check whether any particular style has been configured for the errors.
Hi Sasidhar,
You can perform the following tests:
1. Using LiveUI tool, open the harness that contains the concerned section. Traverse to "Scripts & Styles" tab, and check if there is an addtional css applied to this harness (under Styles sheets).
2. Additionally, open the Skin rule and under Component Styles tab, click on the Dynamic Layout menu. Choose Errors from that list. Now check whether any particular style has been configured for the errors.
You can compare these settings with any OOTB skin, say, pyEndUser71 or pzDesignerStudio.
Genpact
US
No additional scripts kept on harness. And error component in skin is for page-level/field level error.
Where as my quest is to change field labels and borders on error, And as mentioned earlier, skin setting of text input is working if marked for required on section.
Are you finding that validation errors are being displayed differently to those from required fields? Can you provide any screen shots of what you see the required fields and validation errors currently?
Display options for erros are configured in the Harness rule as shown below (7.1.9 screen shot). In order for the error to be displayed next a field it needs to be present on the screen of course.