New Accelerator: Field Validation Messages

The task of validating a field can be a very simple process, but, it can also be a repetitive and unproductive use of a developer’s time. Nowadays, whether you’re developing a web application, or virtually any kind of software that contains input fields, their validation is usually a standard feature. 

As promised in our first post about our platform’s accelerators, the development of new variations is, and will be, a continuous and ongoing process. That said, we got a brand new accelerator to share with you, already available with our platform’s latest version, 3.0.244.

Introducing the “Field Validation Messages” Accelerator.

Funcionality: allows the developer to quickly set a condition for a specific field, define its value, and set an output message to be presented, if the condition is met.

UI and Inputs:

(Main User Interface)

In order to exemplify the benefits of using our new accelerator, we’ve developed an common example that illustrates its usage. For the purpose of continuity, we’ll be using the same Purchase Order Document we’ve used in previous blog posts.



Context: Let’s suppose you’ve developed a B2B Web Application that your company shares with its clients, with the purpose of facilitating their Purchase Order process, and drive more sales. You have one condition that will provide delivery with free shipping, and the condition is that the order must be above 99€ (100 or more). If the order is under 100€, a message should communicate that the client’s order will not enjoy free shipping, if it’s above or equal to 100€, a message should communicate that it will.

Details: In order to correctly develop this condition, let’s break down its specificity. The condition should not trigger for empty orders (total > 0). It should trigger if the “Total” value is above or equal 100 (>= 100) and present a success message. It should trigger if the value is under 100 (< 100) and present a warning message.

Step 1: Use the accelerator to develop your base condition, the element that will trigger it, and the desired message;

Step 2: Adjust the code so that it meets your condition details;

Step 3: Deploy and Test your condition;