Are you tired of retrofitting your UI customizations to EnterpriseOne applications during your continuous adoption journey? Are you struggling to identify customizations made to applications that you have done in your code base? Are you looking to reduce your customization footprint and reduce continuous adoption costs?

The Decustomizer Analysis Report enables you to do just that. It helps identify and target simple UI customizations. The report also gives you easy-to-consume information on EnterpriseOne application customizations that can be replaced with Personalization Frameworks. It helps track and reduce your stay current baggage with each update cycle.

How It Works

Decustomizer Analysis Report scans your EnterpriseOne applications across two path codes to identify customizations. For example, you might want to compare the production path code and the pristine path code to identify the customizations. The report stores the identified customization information in an EnterpriseOne table. The customization information is published using batch reports.

Generating the Decustomizer Analysis Report is a two-step process.

1. Run a UBE to load the table.
2. Run a UBE that reads from the table to produce a report in PDF format.

The Decustomizer Dataload Report (P9540DC) loads the Decustomizer Dataload Table (F98881DC) with a list of all of the customized application EnterpriseOne objects. The Decustomizer Analysis Report (R9540DCR) creates a summary and detailed report from the data in the table.

The Decustomizer Analysis Report contains information about the customizations pertaining only to the application EnterpriseOne object type. The report gives an overview and a detailed summary of customizations to the application objects.

It is recommended to use the Decustomizer Analysis Report periodically throughout your continuous adoption journey to identify customizations and reduce the cost of staying current.

The report will help you meet your requirements by using the Glass frameworks. It will also enhance your user experience and reduce the cost of staying current with EnterpriseOne by reducing your customization footprint.

For the purposes of the video, an example was given where the Case Management application was customized using the traditional design tool. To walk through the example and see how to use the report and Personalization Frameworks to reduce your customization footprint, check out the full video below.

Additional Resources

To learn more about the available Personalization and Extensibility Frameworks that will help reduce EnterpriseOne customizations, visit the Citizen Developer frameworks page on www.learnjde.com. You can also check out the additional Quest resources below for more information on eliminating or avoiding customizations and how to get and stay current.