1
0
-1

The Dropdown (Years) component includes a "Starting Year" property which allows the definition of the earliest year on the list, but the latest year always defaults to the current year. Many consumer banks impose age limitations on applicants (16+, 18+, etc) and their existing dropdowns are configured to only allow the selection of valid years. Defining this as an offset rather than an absolute value would result in zero maintenance across the year-end.

(Example: if applicants must be 16 or older, then the "starting year" might be 1900, but setting the "ending year offset" to 16 would lead to an upper limit of 2000 (= current year - offset) to disallow those born after this date.)

TIA

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      You can raise product feature requests here: Avoka Community Ideas

      In the mean-time you could handle this with a validation rule on the value, or alternatively Maestro enables you to build your own Re-usable Components.

      There are also techniques for limiting date values in the date picker as described here: Grey out invalid dates in date picker widget

       

        CommentAdd your comment...