I was testing our customizations in Kinetic 2022.1.9 and discovered that BPM data forms are not correctly receiving character fields that have been set in the directive workflow (ie Set the BPM
Character01,Character02,etc). I know we need to eventually move away from them since they are not supported via Kinetic, but just curious if anyone found a simple way to address this?
No, unfortunately the case we opened with Epicor (CS0003243573) got tied to a problem that was not the correct one (PRB0253777). We ended up just working around it with other customizations. Sorry!
I created a case. This could be a showstopper for us to upgrade.
We were going to upgrade to use classic, and then update customizations (we have a few dozen) in Kinetic. Not being able to use BPM forms as intended will be an issue as we have been using BPM forms a bit more to collect data from users.
I have power running to the server and the code compiles. It works!!!
We want to upgrade and sell our story of success. This just makes it a bit more difficult to do. Its not like we are able to just move to the browser day one.
Ken–what’s your endgame with setting the context beforehand? Is it to pre-populate fields with something? As much as I dislike the suggestion–what about moving it to a BPM Form customization and pre-populate the fields in the UI code?
That is what I am looking into now. When is the callContextBPMData data getting cleared out.
If it means enhancing the customization, then that won’t be the end of the world. As the form already has a customizations (part/job/serialnumber adapters for lookups)
Right, but isn’t that why you’re trying to set it in the customization?
What’s in ShortChar01/02? Is that something that can be coded into the UI or is it specific from the calling form?
See if this screen video works. I am passing part and rev as shortchar01/02 from the dashboard to be used by the BPM. The message box are the CallContextBpmData values before the BPM Form call.
Tried a few different things with no joy, so I’ll have to defer to support on this, buuuuuuuuuuuuuuut…
If you want a truly awful work around…
From your BPM, write the values you would normally send to the call context to a UD table and commit it, then in the UI code of your BPM Data Form you could get the latest record and do the thing.
Gross? Sure, but it’ll also keep you moving forward towards an upgrade if that’s a showstopper for you.