So, if I may restate your answer:No, AEM (CQ) All Capabilities 6.3" does NOT include AEM Designer 6.3AEM(All), however, includes Sites, Forms, communities etc and the EOL applies to complete suite. Designer being one subset of Forms onlyTherefore, core support for AEM Designer 6.3 DOES NOT end on 4/...

Thanks, Mayak, but that doesn't really answer my question:"I looked at the end-of-life table and found something called "AEM (CQ) Forms" 6.0 and "AEM (CQ) All Capabilities" 6.1 - 6.4. Core support for 6.3 ends 4/30/2020. Is "AEM (CQ) All Capabilities 6.3" the same as AEM Designer 6.3"?

We are looking at the future strategy for our forms (1400+ statewide use). They are currently developed in the desktop application AEM Designer 6.3. We do not use the full server Experience. I looked at the end-of-;life table and found something called "AEM (CQ) Forms" 6.0 and "AEM (CQ) All Capabili...

I found the answer myself:In the XML, I had to change the built-in “short” date pattern from:This could not be manipulated through the Object palette.

Let’s say we want a date that shows the date for termination of guardianship. Today’s date is July 12, 2016.I have added to my Designer form a simple Date object, display pattern specified as date{MM/DD/YYYY}. The user enters – via the calendar pop-up – today’s date and changes that last two year di...

I work with court forms and ES3. Some future dates are +20, +30. Unfortunately, LiveCycle's built-in date field provides a date picker that understands a year where the last two digits are over 30 as "193x" and not "203x". How do I get around this?

Hi Niall!Old thread, same question. I am also tied to the paper form in terms of layout. I have a paragraph with a field in the middle that extends over two lines:some text some text some text some text some text some text some text some text some text some text some text some text some text some te...