The issue LDAP: error code 12 – Unavailable Critical Extension commonly occurs when asking an LDAP Server to return paged results but the LDAP doesn’t support the PagedResultsControl extension.
- SunOne 5.2 and 6.3 don’t support PagedResultsControl extension.
- Active Directory and other LDAP servers support PagedResultsControl extension.
Working of pagination during LiveCycle sync from an LDAP server
In LiveCycle, users and groups are synched from an LDAP server in batches of 200.
When the results returned from an LDAP server is >= 200, then an AutoDetectionLogic is automatically enabled.
This AutoDetectionLogic seeing that the LDAP server is SunOne, automatically disables paging.
This AutoDetectionLogic seeing that the LDAP server is AD or non-SunOne, automatically enables paging.
There have been cases where an Enterprise has a proxy server in between which acts as Active Directory but the ultimate LDAP server running behind is SunOne.
In such a scenario, the AutoDetectionLogic is forced to enable paging because of the proxy server acting as Active Directory.
Hence, when the communication ultimately happens with SunOne, we get the error and sync fails.
---Read the complete post at Amit Pugalia's blog.
All the latest Quick Fixes of LiveCycle ES2 version and above will be posted regularly on Adobe website.
If you are a LiveCycle customer and encounter any issue , You may reach to QuickFixes page check if the issue is listed here
In case it is listed on the above mentioned QuickFixes page , then contact Adobe LiveCycle support team to provide specific quickfix installer
We are proud to announce our next and major release of LiveCycle a.k.a Adobe LiveCycle ES4 with loads and loads of new features.
Significant features include :
- Mobile forms support
- Mobile Workspace application
- Forms management capabilities
- Integration with Adobe Experience Manager
- Extended rights management
- Addition of new features in Correspondence Management
- Inclusion of new features that are added as CCR on previous releases which will be available for upgrade customers
For more information go to official press release of Adobe
Also watch a cool 5 minute video that showcases and explains most of the new features of LiveCycle ES4
You can now see LiveCycle ES4′s new capabilities to extend processes to mobile devices in action on Youtube. View this video for an end-to-end demonstration http://www.youtube.com/watch?v=SPZTXfnsMpw&feature=youtu.be
I am thrilled to be able to blog that today we announced LiveCycle ES4!!, The new release has innovations that make it easier to create, manage, and publish large numbers of forms on websites. But the biggest news is how mobile clients and workers can now actively participate in business processes, improving engagement and productivity.
To add a bit more detail, here are the highlights of the new capabilities:
Mobile forms support
LiveCycle ES4 extends self-service options to users with mobile devices and a web browser by rendering forms to HTML5, PDF, and paper from a single XFA template. LiveCycle ES4 preserves scripting logic, so you can use existing XFA templates to extend forms to mobile devices. This capability is supported in the LiveCycle ES4 Forms Pro module and the Forms Portal Solution.
Read the complete post at LiveCycle blog.
LiveCycle Correspondence Management solution users often use text content from MS-Office applications like Word and Excel.
The text content can be copied from MS-Office applications and pasted to Rich Text Editor of Correspondence Management.
Currently the content copying is supported but any rich text formatting applied to the text in external applications like MS-Office applciations will not be retained.
If the user copies (to clipboard) below content from MS-Word
and pastes it in CM text content area of Rich Text editor , the text would appear like
Lot of customers are asking us to provide a functionality to copy paste content from MS-Office applications that supports copying of text content along with the formatting. This is currently on the roadmap but there are no fixed timelines when this feature would be available in the product.
stay tuned …….
LiveCycle Correspondence Management is certified on four different languages (English, French , German & Japanese)
Out-of-the-box deployment of Correspondence Management permits usage of characters of asset names to 0-9 A-Z & a-z via keyboard typing but any language characters can be used in description and comment properties and as part of actual text content as well.
A user can type the characters in description and comment but no in the Name field. An easy way to use such characters for asset names is to type it in description field , copy the word and paste it in Name field but in any customer environment if the organization wants the asset authors to allow usage of such characters for asset names the below steps can be followed to allow users type such characters for asset names.
- Log on to CRXDE Lite http://<hostnameOrIPAddress>:<port>/crx/de/index.jsp as administrator
- Navigate to content/cm/ and double-click tbxeditor-config.xml on left hand side panel
- tbxeditor-config.xml file opens in edit mode on right hand side panel
- search for customAssetNameCharset tag
- Include the special characters that you would like the users to use for asset names, Eg. If you would like to allow users to use Ф in asset name , then include this character in tbxeditor-config.xml file and save it
- In case there is a range of characters that you would like to allow, then specify starting charset and ending charset separated by a hyphen, similar to 0-9
Now the users are allowed to type new characters that are specified in tbxeditor-config.xml
This blog is just an extension to our online docs about this topic which is available at click here
In case of any confusion or more questions feel free to post your query on LiveCycle community forums
While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form. If you then click Save, it again offers to reload the current form. After clicking “Yes” to reload the form, you may notice that Designer hangs.
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes
This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3. If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.
If you are importing a multi-page PDF into LiveCycle Designer ES2 to create a form using the “…Flowable Layout > Place Content In > Master Pages” method you may notice that the content of the pages are placed in a single Master page causing overlap.
This is an issue in LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3. If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.
If you are editing older XDP forms from LiveCycle Designer 7.1, or 8, in Designer ES2, and you have hidden rectangle objects in the form design, you may notice that when selecting these hidden objects in the hierarchy, visible corners suddenly appear on these objects. These hidden rectangle objects are created automatically when importing Word documents into Designer to create a form.
The problem is caused by the import from doc/PDF where the edge property for the rectangle is created and set to hidden, but no corners property is created. When you create a new form in Designer (without importing), the edge and corner properties for a rectangle are always created together and the presence for both usually kept in synch.
It seems that when Designer finds a rectangle without a corner property it creates it automatically with visible corners.
Rectangle in XML after import from word:
<edge thickness=”0pt” presence=”hidden”/>
Rectangle in XML after selecting it on canvas:
<edge thickness=”0pt” presence=”hidden”/>
Rectangle in XML after manually fixing it in Designer (XML Source or Object Palette):
<edge thickness=”0pt” presence=”hidden”/>
<corner radius=”5.08mm” presence=”hidden”/>
You can change the line style to “solid” and back to “none”, and then the corners property in XML is synchronized (presence=hidden) with the line edge property as expected.
This is an issue in LiveCycle Designer ES2 and will be fixed in Designer 10 and later versions. If you require a quickfix for Designer 9 you should contact the enterprise support team.
The logic has now been changed, so that when Designer creates the corner property, it checks if the relevant edge is hidden, and sets the presence for the corners to match.