# Epicor Application Studio Layer Checklist > Source: https://netray.co/tools/epicor-application-studio-layer-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist for Kinetic Application Studio layers covering naming, scope, events, rules, security, testing and upgrade impact. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor developer - Epicor consultant - Technical lead ## Tool **Kind:** checklist **Groups:** #### Layer setup and naming **Items:** **Text:** Layer name follows a convention (project, purpose, version) **Critical:** true Layer type is chosen deliberately: customization, personalization or other Target app (for example the specific Kinetic screen) is confirmed **Text:** Layer is created in a Test environment first **Critical:** true Description states the business reason and requester Company and site scope decided, not left at an accidental default #### Design and logic **Items:** Before building, standard configuration options were ruled out Rules and conditions used before custom code where possible Event handlers named clearly and listed in a design note **Text:** Event order dependencies documented **Critical:** true Data views and fields added are named with a consistent prefix **Text:** Server side logic placed in a BPM or function, not duplicated on the client **Critical:** true No hard coded company, site, user or part values #### Security and data **Items:** **Text:** Layer access restricted to the intended users or groups **Critical:** true **Text:** Hidden fields are not the only protection for sensitive data **Critical:** true Field level edits that change data go through the business object UD fields used are defined and published in the right tables Behavior checked for a user with minimal security rights #### Testing **Items:** Happy path tested with realistic data New, edit, delete and cancel flows tested Tested with a blank record and with a record that has many rows Tested in browser and, if used, on a tablet or small screen **Text:** Errors and messages reviewed for clarity **Critical:** true Performance with a large result set checked Regression test of the standard screen features that were not changed #### Promotion and upgrade **Items:** **Text:** Layer exported and imported through change control, not rebuilt by hand **Critical:** true Layer published after import where the process requires it Original screen behavior can be restored by disabling the layer **Text:** Upgrade impact reviewed against release notes for the target screen **Critical:** true Layer retested after each Kinetic cloud update or version upgrade Owner and support contact recorded Unused or duplicate layers retired **Scoring Note:** Application Studio terminology and menus change between Kinetic releases. Use this as a review list and adapt names to your version. ## Content **Intro:** 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. **Sections:** #### How to use the checklist **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is an Application Studio layer in Epicor Kinetic? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms epicor application studio layer, epicor kinetic application studio checklist, epicor kinetic customization best practices, epicor application studio events, epicor kinetic layers, epicor app studio rules, epicor kinetic upgrade customizations --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json