How to initialize a DatePicker widget
Comments
-
[font=Roboto, Arial, Helvetica, sans-serif]I have a form with two DatePicker widgets: Start Date and End Date. I would like to INITIALIZE the second DatePicker (End Date) to be the same date as the date selected by the first DatePicker (Start Date), but ONLY if the user has not already selected a date for the second DatePicker (End Date). This would be useful when the user is selecting a date many months in the future (or past) and would otherwise have to scroll the calendar widget many time to get to the desired year/month/date[/font]
-
Yes, Decisions has this capability. It can be configured utilizing a "data flow" to set the end date equal to the start date only if no selection on the end date was made. A way you can do this is by utilizing the "isNull" rule step, two "Create Data" steps. Have the inputs of the start step by setting two datetime variables to represent the initially picked dates. Have the rule check if the start date is null. If it is have the 1st create data step maintain the end date selection. If it is NOT null than configure the second "Create Data" step to set the end date value to the start date value. Attached is a screen shot and the example project for training purposes only.
[img]att1[/img]
[i]edited by jared@decisions.com on 11/27/2019[/i]
Howdy, Stranger!
Categories
- 4.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 491 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions