Alternate way to show control validation messages

Saroj Panda

December 23, 2016 at 1:59 am #3338

Current implementation uses the tooltip feature to show the validation messages on controls.

Is there any option to change it. Like to the old style to show the messages below the control, which is more easy to highlight the message to user and avoid any mouse movement to each controls.

I’m trying to create custom controls which can do this for me. Any guidance will be helpful 🙂

Regards,

Saroj

SPARK Support

December 23, 2016 at 11:09 am #3341

Hi Saroj,

Unfortunately, there is no option to use something other than the Tooltip for validation errors.  This is hard coded into each control.

A better approach might be to wrap the SPARK control in your own layout with accessible validation methods.  For instance, on one project, we used an Output text control to serve as a Red asterisk, and then simply switched the visibility off.

If you would like to create your own control based on a SPARK control, see the article Creating Your Own Control which discusses adding dependencies, handling visibility and other events, and how controls load HTML elements.

However, as you are one of our Enterprise customers, if you would like clone the control to your own toolkit and attempt to modify the code, I can point in the right direction.  Please submit a ticket by clicking on Get Help in the menu above, then Submit a Ticket. Keep in mind, any modifications to the toolkit will be outside the scope of support.

Regards,

Stephen P.

Saroj Panda

December 28, 2016 at 12:24 am #3351

Hi Stephen,

We don’t want to extend each and every controls to make the required changes. Instead need the minimal efforts for developer to use it and achive the desired design approach.

I have created one coach view which loops through all the “form-control” components (excluding the Output_Text) in the coach and add new domElement of p tag as error component with “class=text-danger” below the control and override the setValid function of the control to write the message in innerHTML of the component and control it’s visibility instead of toggling the tooltip.

Then I have added css style to hide the tooltip controls, which I think I can remove later if this will work properly.

The efforts are minimal for developer, as only one instance of this custom component will replace all the validation tooltips with the validation message below the controls. Developer will continue writing the existing validation codes. Attached are the screenshots of the pre and post validation result of how it looks like.

Please share your opinion and suggestions on this custom coach view.

Regards,

Saroj

SPARK Support

December 28, 2016 at 9:13 am #3367

HI Saroj,

This looks great.  I am happy to see how quickly you have been able to adapt the SPARK Toolkit to your custom needs.

Regards,

Stephen P.

Saroj Panda

December 29, 2016 at 12:44 am #3374

Thanks Stephen.It’s fun to work for custom UI needs and getting it implemented using SPARK Toolkit in BPM. This is indeed a great toolkit for BPM UI controls. But surely will need improvement which you guys are actively working on considering our suggestions and findings.

Regards,

Saroj

SPARK Support

December 29, 2016 at 7:53 am #3381

Hi Saroj,

Yes, we have many improvements planned over the coming months.

I appreciate your enthusiasm.

Stephen