Just a heads up, there are instances when the form style that you are using can affect the operation of a BPM so it will work in classic but not in the kinetic version of the form…it appears that depending on the form style different Methods are fired.
As an example I have been using a simple Method Directive to set the “Request Move” flag on the Non-Conformance screen to always be false (where EMWW is not being used), this works on the classic form but not on kinetic…when I dug a bit further it appears classic is using “AddNonConf” whereas Kinetic is using “AddNewNonConfRow”
Have also found differences in the Inspection Processing BO as well but there are probably other instances out there
Yeah, they can be different. Before transitioning from classic to Kinetic you have to run everything through your browser’s dev tools to make sure which methods are being called.
We’re still on the client (mostly because we haven’t spun up a new server to test beyond 10.2 yet) but this is one of many items on my future transition checklist. The other big BPM item is that BPMCallContext fields absolutely do not stick around on the web. They’re gone when the method completes, whereas they stick around sometimes on the client.
Is this since you have some users on classic and not kinetic? Or is it UI, We kind of stopped all classic dev and only have a handful of remaining classic screens.
Yeah, I don’t think we should be surprised that development moving forward is not going to be backward compatible. Epicor said as much a few years ago. I hear the client saying…
We have a “Code Bank” of common requests that each time there is a major release we retest on both a local client in Kinetic and Classic and also via a Web Client which is how we are identifying issues where we need to create additional BPM’s to deal with these changes.
This allows us to deploy these to multiple clients regardless of the interface being used as we have a varied client base:
some are locally hosted
some are Epicor hosted
some are other cloud provider hosted
some are on a Kinetic version but using Classic forms as they haven’t yet migrated
some are on a Kinetic version but users prefer the Classic forms
some only use (or have a misc of local client and, )Web Access (which are now predominantly Kinetic Forms)
