Epicor Application Studio Layer Checklist (Free)

0%

0 of 32 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Layer setup and naming

Layer name follows a convention (project, purpose, version)CRITICALLayer type is chosen deliberately: customization, personalization or otherTarget app (for example the specific Kinetic screen) is confirmedLayer is created in a Test environment firstCRITICALDescription states the business reason and requesterCompany and site scope decided, not left at an accidental default

Design and logic

Before building, standard configuration options were ruled outRules and conditions used before custom code where possibleEvent handlers named clearly and listed in a design noteEvent order dependencies documentedCRITICALData views and fields added are named with a consistent prefixServer side logic placed in a BPM or function, not duplicated on the clientCRITICALNo hard coded company, site, user or part values

Security and data

Layer access restricted to the intended users or groupsCRITICALHidden fields are not the only protection for sensitive dataCRITICALField level edits that change data go through the business objectUD fields used are defined and published in the right tablesBehavior checked for a user with minimal security rights

Testing

Happy path tested with realistic dataNew, edit, delete and cancel flows testedTested with a blank record and with a record that has many rowsTested in browser and, if used, on a tablet or small screenErrors and messages reviewed for clarityCRITICALPerformance with a large result set checkedRegression test of the standard screen features that were not changed

Promotion and upgrade

Layer exported and imported through change control, not rebuilt by handCRITICALLayer published after import where the process requires itOriginal screen behavior can be restored by disabling the layerUpgrade impact reviewed against release notes for the target screenCRITICALLayer retested after each Kinetic cloud update or version upgradeOwner and support contact recordedUnused or duplicate layers retired

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.

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Epicor Application Studio Layer Checklist