Epicor Kinetic Customization Change Request Form Template
Most Epicor problems after a customization trace back to a change nobody wrote down. This form captures what is changing, where it will run, what else it touches and how to undo it, so the person who inherits the system can understand it.
Fill in
Epicor Kinetic Customization Change Request Form Template
Epicor Kinetic Change Request
Company: Acme Precision Ltd Change request: CR-2026-041 Requested by: J. Rivera, Production Control Date: 2026-10-20
Change summary
Type: Method directive Target object: JobEntry.Update, pre-processing directive Environment path: Test then Pilot then Live Risk level: Medium
Description: Block release of a job to the shop floor when the engineering revision is not approved.
Business justification
Two jobs were released last quarter against an unapproved revision, causing rework.
Impact assessment
| Area | Affected (Y/N) | Notes |
|---|---|---|
| Other customizations or directives on the same service | ||
| Reports, BAQs or dashboards using the field | ||
| Integrations (REST, DMT, EDI, third-party) | ||
| Security groups and menu access | ||
| Upgrade impact (next Kinetic release) |
Test plan
| Test case | Expected result | Actual result | Pass/Fail |
|---|---|---|---|
| Normal path | |||
| Boundary or error path | |||
| Regression of related screen |
Rollback plan
Disable the directive in Method Directive Maintenance and re-export the previous layer from the Test environment.
Approvals
A starting point for your change control process. Adapt the environment names and approvers to your own policy.
Customization inventory review
Send us an export of your directives and layers and we will suggest how to document and clean them up.
Optional. The tool and every export work without this. No spam.
How to use the form
Fill the fields at the top, review the preview and export to PDF or Word. Attach it to the ticket or store it with the exported customization layer. One form per change keeps the audit trail clean. For emergencies, use the Live only option but still complete the rollback and approval sections afterwards so the record exists.
- One request per object or tightly related group
- Name the exact service and directive type
- Record who approved before the move to Live
Why Epicor changes need their own control
Kinetic customization is spread across several layers: Application Studio layers on screens, method and data directives that run on the server, Epicor Functions, BAQs and report styles. Each is edited in a different place and none of them shows up in a normal code review. A short form forces the author to list the layers touched and to think about the next upgrade, when old directives are the usual source of surprises.
Sections to treat seriously
The impact table is where most real risk is found. A field added to a service call may be consumed by a REST integration or a dashboard that nobody remembered. The rollback section should be concrete: which directive to disable, which layer to revert and who can do it at night. If the rollback plan is vague, rate the risk higher and test longer.
Common mistakes
Teams often test only the happy path in Test and then promote to Live on a Friday. Others describe the change as 'fix the screen' with no object named. Avoid both. Name the object, test an error case and schedule promotion for a window when someone can watch the system monitor and the first transactions.
- No named target object
- No regression test of related screens
- Rollback left as 'restore backup'
Frequently Asked Questions
Do I need this for every small change?
Use judgement. Cosmetic layout tweaks for one user rarely need approval, but anything that writes data, blocks a transaction or is shared across all users should be recorded. A short form is cheaper than a day of troubleshooting later.
Where should I store completed forms?
Keep them in the same system as your tickets or in a shared folder with the exported layer or directive file. What matters is that someone can find the form from the object name a year later.
Can this replace a ticketing tool?
No. It is a document for the change record. Use it alongside your ticketing or ITSM tool so the approval and test evidence travel with the request.
Does it cover cloud tenants?
The structure applies to any Kinetic deployment. In Epicor-hosted cloud, available tools and release timing may differ, so check what your environment allows for directives and functions.
If you maintain hundreds of directives and customizations, we can help build a private assistant that inventories them and answers questions about what changed and why.
Related Tools
Epicor Kinetic BPM Directive Inventory Worksheet
An editable register of your Epicor directives with owner, purpose, risk score and review date, exportable to Excel.
EpicorEpicor Kinetic Go-Live Cutover Plan Template
A fill-in cutover plan covering system freeze, opening balance loads, validation and go/no-go decisions for an Epicor go-live.
EpicorEpicor Kinetic User Access Request Form Template
A fill-in form for requesting, changing or removing Epicor user access, with security group, company and approval fields.
EpicorEpicor Kinetic Custom Report Inventory Worksheet
An editable register of custom reports, BAQs and dashboards to support upgrade testing and clean-up of unused items.
More Epicor tools
See all- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Kinetic Data Migration Mapping Worksheet
- Epicor Kinetic Data Load Effort Calculator
- Epicor Business Object Services Reference
- Epicor BAQ Performance Tuning Checklist
- Epicor Administration Maturity Assessment
- Epicor BAQ Calculated Field Examples Reference
- Epicor Function Library Design Template
- Epicor SSRS Report Template Checklist