Posts tagged community
Adobe LiveCycle forum is a platform where LiveCycle community meets, learns, and discusses experiences about using LiveCycle. We are committed to provide the best user experience to the community when they are on the forum, and we have taken a step in that direction.
The LiveCycle forum, until sometime ago, comprised of 70 forums and sub-forums. We monitored the forums and found that the unnecessary bulk is making it difficult for the community to manage discussions and participate on the forum. As a result, most of the are inactive as it was unintuitive to drill-down to the correct forum for discussions.
As we understand the importance of a close-knit community, we have optimized the forum structure, so that it is easier for the community to search, post, and participate on the forum. The new forum structure is thin, focused, searchable, and easy to manage.
In its new look, the LiveCycle forum has relatively flat hierarchy, but with a logical grouping of discussions. The streamlined new structure includes seven top-level forums, including one forum with 14 sub-forums. The flat hierarchy relies on the tags for filtering discussions related to a specific area of LiveCycle.
Read the complete post at Adobe LiveCycle Help blog.
The Cookbook homepage is here: http://cookbooks.adobe.com/livecycle. Check out the available recipes and contribute your own.
Original article at http://blogs.adobe.com/samartha/2012/03/toggling-between-two-fields-in-a-dynamic-form.html.
– Holly Schinsky
Flex folks, first of all, today there’s a new official statement out on the Adobe website about Adobe’s commitments to the Flash Platform including plans for Flex that you should be aware of. Secondly there’s a new post from the Product Management team out now summarizing the recent Flex Q&A. There’s been a lot of frustration in the community (which I understand and can personally relate to having been part of the community myself for a very long time) and I wish that the sequence of events (and frankly the communication) did not happen as it did, but it is what it is at this point and we need to carry on. I hope people can see this move of Flex to an Apache model with dedicated full-time engineering resources in San Francisco as the good news that it is!! Flex is alive and well and will continue to grow as the dust settles. Even now we can build amazing applications over many other technologies in half the amount of time with it in its current state. And the growth in Flex and AIR for mobile is allowing us to do some super cool and fun stuff which is about to just get better with the upcoming release of Flex 4.6 in a couple weeks!
I know many of you are having to answer some tough questions from your clients and management about all of this, I hope today’s statements can help in that respect. If there was a way I could change how things happened myself or wave a magic do-over wand I would in a heartbeat . This has not been easy for any of us. I just hope we can now start channeling our frustrations into something more positive and productive and get back to having some fun!
I will continue to post any updates on the move to Apache as I find out. Start thinking about how you might be able to contribute !
Original article at http://devgirl.org/2011/11/17/flex-is-alive/.
– Kevin Schmidt
With all the Adobe news lately, I wanted to make sure everyone knew the future of Adobe LiveCycle. Here is the statement from Arun Anantharaman, vice president and general manager, LiveCycle and Adobe Connect.
“Since Adobe’s entry into the Enterprise market in 2002 with the acquisition of Ottawa-based Accelio, we have built a large portfolio of LiveCycle customers. We will continue to sell and support our LiveCycle products in the government and financial services markets, two areas where the LiveCycle value proposition remains especially strong. Outside of those markets, we are now planning to focus our Enterprise efforts on products targeting the digital marketer, including the Digital Marketing Suite and Web Experience Management solution. In addition, Adobe is fully committed to the success and satisfaction of our customers and we intend to build long term strategic relationships with them. We will continue to support all existing and future customers of our solutions.”
So, there you have it, feel free to ask any questions in the comments and I will do my best to get them answered for you.
Original article at http://www.underprise.com/2011/11/11/the-future-of-adobe-livecycle/.
Session re-writing is the practice of adding the session identifier to the HTTP request URL instead of passing the session identifier as a session cookie. Session re-writing is usually used when cookies have been disabled on the client. It is an easy way to let clients that do not allow or support cookies maintain session state with the server but it poses some security risks. The session identifier is passed in the URL which means that it is not encrypted even if the request is made over SSL/HTTPS. Because of the security risks associated with session re-writing, the Open Web Application Security Project (OWASP) recommends that session re-writing only be used for low-value sites. In this article, I will show you how to disable session re-writing in BlazeDS and LCDS to help secure your application.
In BlazeDS and LCDS, the session identifier is typically either the JSessionId (for servlet based endpoints in BlazeDS or LCDS) or AMFSessionId (for NIO HTTP based endpoints in LCDS).
Note that the RTMP protocol doesn’t use HTTP, so the issue of session re-writing doesn’t apply to RTMP endpoints.
When the BlazeDS or LCDS server receives a request with no session identifier (either a session cookie or session id URL parameter) a couple things happen. A new session is created. A Set-Cookie header with the session id is added to the response. Also, an AppendToGatewayURL header with the session id is added to the AMF or AMFX response message.
When LiveCycle became ADEP Document Services all of the existing modules were ported over but I thought it would be useful to revisit them all and see what as new. This post gives a summary of the modules which are available to any Document Services solution (excluding the foundation services which come with all Document Services modules) and should be familiar to those who have worked with LiveCycle ES1/ES2 in the past.
Business Process Management
Adobe Digital Enterprise Platform Document Services – Process Management 10.0
Process Management allows the designer to create processes which assign and move tasks around a business. End users can login using the Workspace web application to view and update any task assigned to them. This module is commonly used in conjunction with the Forms modules in order to create workflows for forms built by the designer. ADEP Mobile also comes as part of this module allowing your end users to interact with their tasks on the go.
As described in one of my earlier posts this one has now been deprecated. It’s still included for legacy purposes but you should really be using the new CRX service.
Adobe Digital Enterprise Platform Document Services – Forms 10.0
The bread and butter of many ADEP solutions, Forms is what allows data to be merged and retrieved from forms rendered to PDF, HTML or Guides. It also allows forms to be assembled from fragments. If you are designing to form to be dynamic and it doesn’t have a fixed layout then you will almost certainly need the Forms module. Together with the Process Management module it allows for some fancy data collection and presentation to your end users!
Adobe Digital Enterprise Platform Document Services – Adobe Reader Extensions 10.0
If you need to distribute those forms you’ve just designed to external parties then chances are you’ll probably run into the need for Reader Extensions. A “rights-enabled” form opened in Adobe Reader allows the end user to perform tasks that are normally reserved for the commercial Acrobat software such as adding attachments, saving a PDF form locally (the most common use case) and digitally signing forms. Can be used standalone or as part of a workflow.
I’ve written a few custom components in my time working with ADEP but recently came across an excellent summary of what exactly these little (or in some cases large!) pieces of code actually are. A recent blog post on the Adobe ADEP blog summarised it nicely:
A DSC is a component that can be installed on a Documents Server and introduces new functionality. It stands for Document Service Component. Most product components are DSCs but customers can write their own DSCs to create new integrations or functionality that require a higher level of sophistication than is appropriate with the use of standard integration options (e.g SOAP) or scripting/process maps. They are basically POJOs with nifty enterprise configurations around them that allow enterprise class life cycle, versioning and configuration (e.g. in an enterprise BPM system you don’t necessarily want a new version of a component to alter the way an inflight process is operating, or how a completed process reports audit data…) or even have to bounce the server to change the implementation of the DSC. It is definitely part of the secrete sauce of LiveCycle/ADEP Document Services.
Original article at http://michaelsteward.com/2011/10/09/defining-document-services-custom-components-dscs/.
New for LiveCycle Workbench 9.5 is the ability to provide you with the latest help dynamically in a manner similar to Adobe Flash Builder Help, which many of you already know and love! How? The Adobe Community Help Client (CHC), that’s how! The CHC is an AIR-based application that replaces the Eclipse Help engine for Workbench and is the platform for the next generation of Adobe Help delivery. CHC features include the following features:
- Search-centricity : Uses Community Help search, adobe.com search, or local search. Community Help search aggregates resources, including those from 3rd party sites. The adobe.com search includes refinements to narrow your scope.
- In-context navigation: Provides a dynamically generated set of related links for key pages.
- In-context commenting: Provides immediate feedback on any page and displays any recent updates.
- Always online: If you have a network connection, the CHC accesses content from the web to ensure that you have the most up-to-date content. However, you can also work in local mode if you have no Internet connection.
Now you are probably wondering, how do you work in local mode? Well, provided you have internet access, you can download a copy of the Help so that you can access the Help if your internet connection fails or if you are temporarily working behind a restricted firewall. To download a local copy of the Help, follow these steps:
- Start Workbench ES2.
- Select Help > Adobe LiveCycle Workbench Help. The Adobe Community Help Client starts and you do not get a prompt that asks to you download the help, continue to step 4. If you do, the help is downloaded after you click update and you should have a local copy when do not have internet access.
- In the Adobe Community Help Client, select Edit > Preferences.
- In the left pane, select Download Preferences.
- Select LiveCycle ES2.5. The LiveCycle Workbench 9.5 Help should be selected automatically as shown in the following illustration:
- In the left pane, select Local Content, select LiveCycle Workbench 9.5 Help, and click Update. After the update, your window should look like the following illustration:
- Click Done.
You now have a local copy of the Help! The next time you connect to the internet, the Help will be updated when a user selects starts the Workbench Help. If you do not have an internet connection, Workbench connects to the local copy.
Note: The PDF version is not available unless you are connected to the internet. If you want, you can save a local copy of the PDF version on your computer, when you have internet access.
Original article at http://blogs.adobe.com/livecycledocs/2010/11/livecycle-workbench-now-using-the-adobe-community-help-client.html.