Epicor Application Studio Layer Checklist
Application Studio makes it easy to change a Kinetic screen, and just as easy to build up layers nobody understands. This checklist keeps each layer small, secure and upgrade friendly.
0 of 32 items complete
9 critical items still open - these are the highest-risk gaps.
Layer setup and naming
Design and logic
Security and data
Testing
Promotion and upgrade
Application Studio terminology and menus change between Kinetic releases. Use this as a review list and adapt names to your version.
Inventory your Epicor customizations
Optional: discuss how a private AI assistant could summarize your layers, BPMs and reports for an upgrade plan.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Run the list when you start a layer and again before promotion. The setup items prevent the classic problem of unnamed layers with unclear scope. The design items push you toward the simplest solution first: configuration, then rules, then code. Export the completed list as evidence for change control, and store it with the layer description so a later developer can see what was verified.
Keep layers small and purposeful
A layer is easiest to support when it solves one business problem. Large layers that mix field changes, event code and layout adjustments are hard to test and hard to upgrade. Prefer several small layers with clear names over one that does everything, and retire layers that no longer have a requester. Duplicate layers on the same screen are a common cause of puzzling behavior because two event handlers may fight over the same data view.
- One business problem per layer
- Clear, consistent names
- Retire layers when the need ends
- Avoid two layers editing the same event
Security is more than hiding a field
Hiding a control in a layer does not stop a user reading the data through another screen, a BAQ or REST. If the data is sensitive, protect it through security groups and field level controls on the server. Test with a low privilege user, since a developer account often hides permission problems. Anything that changes data should go through the business object so server rules and directives still run.
Upgrade impact
Cloud updates and version upgrades can change the screens your layer sits on. Read the release notes for the apps you customized and retest after each update. Layers that use only documented events and rules usually survive better than those that depend on internal control names. Keep the ability to switch a layer off quickly while you investigate a regression.
Frequently Asked Questions
What is an Application Studio layer in Epicor Kinetic?
A layer holds the changes made to a Kinetic app in Application Studio, such as added fields, rules, events and layout edits. It sits on top of the standard app, so it can be enabled, exported or disabled without editing the base.
Should I use rules or code in a layer?
Use rules and conditions where they cover the need, because they are easier to read and upgrade. Use event code when the logic is too complex for rules, and keep server side logic in a BPM or function.
How do I move a layer from Test to Live?
Export the layer from Test and import it into Live following your change control, then publish it if your process requires that. Avoid rebuilding the layer by hand, because small differences are easy to introduce.
Why did my layer stop working after an update?
The base screen may have changed, so an event, control or data view your layer depends on moved or was renamed. Check release notes, test with the layer disabled to confirm the cause, then adjust the layer.
Planning a Kinetic upgrade and unsure how many customizations will break? Netray can talk through using a private assistant to inventory and summarize them from exports.
Related Tools
Epicor SSRS Report Template Checklist
A pre-release checklist for custom Epicor SSRS reports covering report style, data definition, layout, parameters, security and testing.
EpicorEpicor Function Library Design Template
A design document for an Epicor function: signature, inputs, outputs, logic notes, security, test cases and sign off.
EpicorEpicor Customization Migration Estimator
Count your customizations, BPMs, reports and BAQs and get an hours and cost estimate for retesting and rework in an upgrade or Kinetic move.
EpicorEpicor UD Table Design Worksheet
An editable worksheet for planning user defined tables and fields before you build them in Epicor, with a column count and key check.
More Epicor tools
See all- Epicor Kinetic Customization Change Request Form Template
- Epicor Kinetic Go-Live Cutover Plan Template
- Epicor Kinetic User Access Request Form Template
- Epicor Kinetic BPM Directive Inventory Worksheet
- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Kinetic Custom Report Inventory Worksheet
- Epicor Kinetic Data Migration Mapping Worksheet
- Epicor Kinetic Data Load Effort Calculator
- Epicor Business Object Services Reference
New to Epicor ERP? Start with the Epicor ERP guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- Epicor Kinetic Upgrade ChecklistA phase-by-phase upgrade checklist covering inventory, testing, integrations, cutover and rollback for Epicor Kinetic.
- Epicor Kinetic Customization Change Request Form TemplateA fill-in change request form for Application Studio customizations, BPM directives and Epicor Functions, with test and rollback sections.
- Epicor Kinetic Private AI Layer Blueprint GeneratorGenerate a shareable private AI architecture plan for Epicor Kinetic on-premises, with components, security controls, rollout phases and open questions for IT.
ERP fixes and how-tos
- Epicor Application Studio: understanding customization layersHow Epicor Kinetic Application Studio's layer model works: base, customization, personalization and extended layers, load order, and why changes sometimes do not appear.
- Convert Epicor Classic Dashboards to KineticHow to convert Epicor Classic dashboards to Kinetic during an upgrade: what carries over, what must be rebuilt, and how to verify each dashboard.
- Epicor Kinetic UD Tables and UD Fields: Setup, Studio Binding, BAQ and SecurityHow to create and use UD tables and UD fields in Epicor Kinetic: setup, binding in Application Studio, reading them in a BAQ, and securing access.
AI on your ERP
- Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant BoundaryRun a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.
- AI for Epicor Kinetic Job Shops: Quote History, Job Variance and Schedule RiskPrivate AI for Epicor Kinetic job shops: quote-to-job history, JobHead and JobOper variance, subcontract delays and schedule risk, via REST and BAQs.
Integrations
- How to add a mobile app to Epicor KineticBuild or choose a mobile app for Epicor Kinetic: barcode scanning, labor reporting, inventory moves and approvals over the REST API, with offline handling.
- How to add AI agents to Epicor KineticHow to add AI agents to Epicor Kinetic: a tool layer over the REST v2 API and BAQs, MRP exception triage, PO expediting, and human approval before any write.
Software
- Epicor KineticEpicor Kinetic explained for manufacturers: modules, REST API, BAQs, deployment, strengths, limits and alternatives to compare before choosing or upgrading.
- Epicor CPQEpicor CPQ is a cloud configure-price-quote product with visual 3D configuration for manufacturers. Modules, ERP integrations and alternatives explained.