Learn how integrated end-to-end grants-related transfer payments management system helps Government of Ontario website provide streamlined services to organizations. The solution is based on Adobe Experience Manager (AEM) Forms, part of Adobe Marketing Cloud.
Tired of missing out on updates in the AEM community – follow @4Point_ on Twitter and stay atop industry news such as the newest digital trends, creative competitions and social events! >>>
You have just arrived at your office and you open your email. You discover that your AEM system is down and you are getting dozens of messages from staff that are asking you what is happening. You know from that moment on its going to be a rough day. Now what do you do?
We invite you to come visit and subscribe to 4Point’s Youtube channel where you’ll find videos about our most successful Adobe based solutions. There you can find 4Point’s webinar records, customer showcases, and other content that will be regularly updated! >>>
The purpose of this blog is to create an environment where our technical team can share their insights, knowledge, opinions and experiences with you. Questions such as how do we move to a mobile platform? Has anyone one else done it? What are the pitfalls? Does it actually work? Read more >>>
Here we are; our servers are set up and configured we have our LDAP configured. All that is left is to create our policies and identify the specifics of how we want to control the distribution of our documents.
Although this sounds straightforward the decisions around Policies can take some thought to work through and the decisions you make can have an impact of the effort required.
In the last blog post, we discussed the two main types of signatures (Electronic and Digital). We then explored some examples of each. In this continuation, we will continue to explore different types of signatures that you can leverage in your form based business processes.
There are two kinds of signatures today:
• Electronic Signatures
An electronic signature, or e-signature, refers to data in electronic form, which is logically associated with other data in electronic form and which is used by the signatory to sign or confirm their approval of a document or transaction.
• Digital Signatures
These are a subset of electronic signatures because they are also in electronic form. Digital signatures, are a cryptographic mechanism often used to implement electronic signatures. Digital signatures go much further in terms of providing security and trust services.
Let’s consider the differences between electronic signatures and digital signatures in more detail.
Part 1 - XFA Stitching
Most LiveCycle/AEM form developers know that the source code for an XFA form template is XML. Many experienced form developers regularly inspect the XML source and modify it directly either via the XML Source tab in LiveCycle Designer or by opening the XDP in their favorite editor. Some things can be done a lot quicker this way: batch changes, text tweaks, etc. Also, sometimes debugging tasks can be helped greatly by going directly to the source. Of course, since the source is XML, we can do much more to it: transform it with XSLT, load it into a DOM and manipulate it – delete nodes, move nodes, and add nodes, etc., - anything that we normally do with XML data.
While recently developing a web site for a large financial services client, the requirement emerged to have common components on all pages of the web site with the same data on each. Creating a header section with these components was relatively easy; getting them all to have the same configuration values but not configuring each page individually, not so much.
When I entered my first swim race, I trained hard to become a better swimmer. Time spent on stroke, breathing, all the necessary parts. Then, when the race started, I found out we needed to dive in to start. That was news to me and rather slowed down the rest of my race! We’ve all had the experience of realizing we could have done something better if only we had better knowledge. That is where training (with some guidance!) comes in. Training helps not just the individual, but their group and organization as well.
You decided to take the plunge and invested in a full stack AEM development environment. To keep things compact, AEM author, publisher, and dispatcher are installed on a single server. Because you care, you have taken the extra time to set AEM to run as Windows services.
Everything is working as expected. Development workflow has improved and best of all your team can finally test client libraries and caching behaviour in a real world setting.
But something isn’t quite right. One day, after restarting the AEM Author service you get an error message that looks like this: