<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Calendar Blockout/disable/hide of Future Dates</title><link>https://community.appian.com/discussions/f/rules/18008/calendar-blockout-disable-hide-of-future-dates</link><description>Has Appian developed this functionality as yet? 
 
 The use case here is i have certifications that are being uploaded, however i do not want to allow the issued date to be a future date. 
 
 There is validation on the field, however from a UX point of</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Calendar Blockout/disable/hide of Future Dates</title><link>https://community.appian.com/thread/70841?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 21:12:27 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:1053e214-c047-48bf-bc4e-8354f26cdabb</guid><dc:creator>Robert Shankin</dc:creator><description>&lt;p&gt;One thing you can do, in addition to your validation is to default the date to a week|month|year in the past.&lt;/p&gt;
&lt;p&gt;With the inclusion of instructions that guide against future dating, this will greatly reduce the likelihood that the date selected is in the future.&lt;/p&gt;
&lt;p&gt;Alternatively, if you really just can’t abide by the functionality of date pickers for your use case, you can construct your own date capture with either a text field or a collection of day, month and year drop downs that comply with your validation proactively.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Calendar Blockout/disable/hide of Future Dates</title><link>https://community.appian.com/thread/70825?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 14:00:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:90785e30-387b-404b-b7fb-648159cc67b2</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;Aside from doing something completely different, like populating specific dates into a dropdown, or implementing your own mini-calendar interface using available components (which is doable but tricky), pretty much your only option is to rely on field-level validations.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>