So we are testing 2023.2 in a test environment and one of our Bartender BPMs was not working while testing…And I get this message (Yes I am added to the security groups for both method and data directives as well as I am in the owning company of the BPM)
It shows up in the BPM that was transferred from 2021.1 but now it no longer shows up when selecting a condition. I have access to every option that I can in Kinetic. Is there something I am missing in 2023.2? Anyone else having this issue? I did not have this problem when we had our test environment in 2023.1 and I was testing out BPMs. I have also tried on both the browser as well as the client with no luck.
I reached out to Epicor and they seem confused themselves.
Yep I just figured this one out a few minutes ago…I tried to only do data directive as classic but would throw an error so I had to do the entire BPM folder to launch from classic.
I had noticed this in K2023 but have not gotten around to asking about it . In 2023.2 there is a new access group(s) . Similar to when they came out with Functions, you had to add users to this group to access them ??
Was actually going to ask what a Data Fabric Administrator is for.
They probably haven’t released the features yet and added the security groups prematurely for their own testing is how I would imagine this got this way.
It probably contains something that is not implemented in the version you use. Create new directive in browser and you will see what is avaialble in the moment
It contains the condition I have posted originally which I think is an issue…Updating/Adding/Deleting a row from a table as a trigger is a staple to many BPMs so I am unsure why Epicor would not have this implemented in the latest version 2023.2 for Kinetic!
Currently on 2024.1 in our test environment soon to go live with it in our production environment and can confirm you still have to use Classic for CREATION of the BPMs to not lose certain conditions. The BPMs will still fire in the kinetic views
