Estie Posted February 7 Share Posted February 7 Hi We have an intelligent capture which includes between date pickers. These are mandatory fields with override flags. It seems that either the start date or end date can be left blank, despite these being mandatory fields. Is it possible to enforce the mandatory option on both dates? Thanks Link to comment Share on other sites More sharing options...
Miro Posted February 7 Share Posted February 7 Hi @Estie If field is mandatory then both dates should be required. Will check it and let you know. Thank you, Miro 1 Link to comment Share on other sites More sharing options...
Miro Posted February 8 Share Posted February 8 Hi @Estie Replicated the problem and will fix it. Should appear in one of next releases. Quote FIX: Intelligent Capture - Between Date picker allow one of the dates to be left blank when is mandatory with override flags Thank you, Miro 1 Link to comment Share on other sites More sharing options...
Estie Posted February 8 Author Share Posted February 8 Great thank you @Miro I will look out for it. Link to comment Share on other sites More sharing options...
Estie Posted February 8 Author Share Posted February 8 Hi @Miro a possible enhancement request for a between date and time picker We have a support booking form and we would like users to add a start and end date and time for the support to be booked. Currently we use separate start and end date/time fields, however this allows a user to add an end date and time which is before the start date and time. The date picker has resolved this issue where only dates are required. Is it possible to have a between date and time picker? Thanks Link to comment Share on other sites More sharing options...
Estie Posted February 13 Author Share Posted February 13 @Miro is there an update on this issue please? It is still occurring on our ICs and I haven't noticed it in any releases. Thanks Link to comment Share on other sites More sharing options...
Steve Giller Posted February 13 Share Posted February 13 @Estie This has been fixed and will be in the next Core UI release. I can see this working on my test Instance so when that build completes the testing cycle successfully and is released to Live you will see the changes. 1 Link to comment Share on other sites More sharing options...
Estie Posted February 27 Author Share Posted February 27 @Steve GillerThanks for your help. I can see that the issue was fixed in Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now