Build JDE package cleanup into a controlled change

What changed: Package-cleanup automation developed, technically tested and deployed to production.

The pressure: recurring technical work needs a maintainable approach

A customer needed automated package cleanup in its JD Edwards environment. Allari carried the requirement through analysis, development, technical testing and production package deployment, with design and test documents supporting the change. The objective was maintenance the wider team could understand and support.

Connect requirements to the technical work

Allari prepared the business requirements document and shared it with the delivery team. Development covered analysis, structures, validation and deletion of package-build directories. Coordination and development stayed connected so the people defining the requirement and building the automation worked from a shared specification.

Test the implementation and update its supporting documents

The developer completed the automation and reported successful technical tests. Review then led to updates to the business requirements, functional design, technical design and unit-test plan. The team kept the implementation and its supporting documents connected as the change progressed.

Carry the change into production

Allari carried the package-cleanup report into production: the production package was built and deployed. Analysis, development and technical testing led to a released change in the customer’s JDE environment.

Keep the documentation handoff visible

Documentation had its own follow-up work item, making the handover responsibility visible alongside the technical release. The delivery combined developed automation, successful technical tests, document revisions and production package deployment. Completion of the documentation handover is not established in this record.

Make repeated work easier to support

For similar maintenance work, agree on the intended behavior, validation, production release and ongoing owner together. Keep the design and test context available to the team that will support the result. Allari brings the required specialists together with a dedicated Client Solutions Manager at no additional charge to coordinate the customer’s priorities and budget. The practical objective is a repeatable process whose change history and responsibilities remain understandable after the original developer moves to the next task.

Make the maintenance process supportable.

Bring the repeated technical task and the people who rely on it. Define what should be automated, how it will be checked and who will own the result.

Coordinated expertise across business analysis, support, development, ERP operations, integrations, automation and ERP team mobilization.

Allari at Work

Your IT team.
Backed by an entire delivery organization.

Functional and technical specialists, coordinated around your priorities.

Discuss your next priority →