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 >>>
With all the recent advances in technology, we may discount the value of our legacy systems. Based on old technology, these systems are considered incapable of meeting today’s business needs, and many argue they should be replaced. In some cases, that’s true. Most of the time, however, it’s possible to get much more out of an existing legacy system—and yet provide richer, more effective experiences for your users.
An Adobe Experience Manager (AEM) “wrapper” can extend most legacy systems, transforming them into up-to-date systems with all the functional and performance capabilities you need.
After all, most legacy systems still do what they were designed to do. They’re extremely valuable corporate assets. Their business logic and integration points work. Your legacy system, developed and adapted over time, offers the best representation of your current business processes.
While implementing a whole new system is always expensive, it’s never risk-free. And it won’t necessarily solve all your problems. At least not quickly: established applications transferred to a new platform often don’t work as expected for quite some time.
Many legacy systems perform poorly in three key areas: access, navigation, and ease of use. Today’s users are frustrated by applications that can’t access the Web, that force them to navigate through multiple screens to complete one task and that present an unfriendly, complicated interface.
Here we consider an approach that allows you to resolve those issues while maintaining the best features of your existing system— and while offering users the benefits of the Web and other new technologies.
Firstly, let's consider the topic from BUSINESS point of view.
History shows that completely replacing the system that drives your business does involve risk. Several potential hazards may be involved:
Of course, a complete replacement is sometimes necessary so you can meet your business goals or remain compliant. A poorly structured database won’t perform any better when accessed through a web browser, and maintenance costs may become impossible to justify.
In most cases, however, you do not have to rewrite the legacy system. Make those functioning core components accessible from the Web, and you can dramatically improve your end user experience—without changing the parts of your legacy system that are sound.
Wrap it instead
The AEM wrapper approach involves an iterative software development process, which results in manageable bite‑sized projects. These provide immediate business value, with minimal risk. The core, stable capabilities of the legacy system are maintained and front-ended (i.e., wrapped) with an intuitive web user experience that will work on various types of devices: desktop, tablet and mobile.
Since your organization’s business goals are unique, your legacy system will present its own unique set of technical challenges.
The first step is to find out what your users need. What functions and information do they consider essential? What are their pain points? You need to have a thorough understanding of your users’ requirements and their business needs before IT gets involved.
In the next blog post we will continue discussing the topic and will take a look at the problem from TECHNOLOGY perspective.