Kinetic Forms - Epicor Function Structure

Kinetic ERP
1

Hi

We are just about to start the migration off Classic and onto Kinetic.

We are scrutinizing every piece of code within the customizations and deciding whether or not the functionality needs to ported to the new Kinetic screen.

Whilst I’m keen to keep this to a minimum it is inevitable some functionality will need to come across.

Epicor functions are going to play a key role in this and I wondered what approach people have taken to the structure of the Epicor Function libraries.

At one extreme we could have every function in a single library and at the other a library for every form.

Cheers,

Andrew.

2

Hi
The idea behind Epicor Functions is to create “re-usable” code that you can share across your requirements.

We are holding a webinar on Epicor Functions on 16/11/2023 to show how you can utilise this functionality in various areas.

If you want to attend or receive notification of the recording location then please email emma.phelan@epaccsys.com

3

Thanks Emma - will do.

4

I created libraries by business function - so User Functions Library for user-based functions, Customer functions for Customer-centric functions, etc…

5

One library for every single function. It’s ridiculous but you can’t look at your library without demoting, so for the time being this is my approach.