Pass data between processes (End Activity)

Kinetic ERP
1

Folks, I’m hoping someone can assist with an issue I can’t find my way around.

In MES, I’ve started production on a Job operation (let’s call this -
Process 1).

Clicking the “End Activity” button launches Process 2 - End Labor Activity - as a slide-out window. From here, I can update a few fields and print a tag with some addit’l custom data elements (modified the MtlTag RDD).

From End Activity, I press “Print Tags” and the system launches Process 3 - the Print Tags process (another slide-out window) and I’m able to send my tag to a printer.

My challenge is that there is information in a text box (PCID) in Process 2 (primary dataview LaborDtl) that I’d like to access in Process 3 (primary dataview ReportParams).

When customizing the UI for Process 3 (Print Tags), I cannot access the dataviews from process 2 (or vice versa). I tried saving the field value in TransView and passing that way, but once process 3 launches, I get a whole new TransView.

I know this isn’t impossible, I just can’t figure out how to get there from here.

Any thoughts will be appreciated.

2

I have not played with MES in the new UX, but for our tags I stuck data in some call context variables and then put them in MtlTag parameters.

3

Thanks Greg. That’s good info and I appreciate it. I’m not sure the call context will be retained as the new process is called, but I’ll test a bit more today and will include (if possible) the “launch form object” that DOES appear to be available in the new/launched process.
Note that this challenge is not MES specific. MES just happens to host the “End Activity” processes.

4

This is my best guess…

Your going to have to copy some base events and set their triggers to “Override” the base event…

The “Print Tags” event in “EndActivity” is pretty big:

image
image1388×506 34.5 KB

Depending on the tags you want to send data for… you may have to repeat this process. (3) of them highlighted in the above snip.

For example the Open_MtlTagsForCurrent event:
image

This is where the program is going to “app-open” the MtlTags report slideout.

You’ll need to include the data your passing in the “Value In” JSON:

image
image417×742 16 KB

To compound the overall issue… if you don’t already have a customized EndActivity layer… there are hoops you have to jump through…

You have to create a new Custom Layer for “EndActivity” (where you make these changes to the above event(s)).

You will also need a new Custom Layer for “MES” (if you don’t already have one). There, you’ll kind of have to do the same thing I’m describing above. You need to override the existing “EndActivity” button onclick event with a new version, which then calls out your customized LAYER of the EndActivity process.

So… from MES, clicking “EndActivity” button will app-open your customized EndActivity process layer. Clicking the Print Tags button there will then app-open the “MtlTags” process with your new events containing your new “value in” criteria.

2 Likes
5

Wow. David, that’s pretty involved, but looks to be exactly what’s needed - assuming I can access the “Value In” data. I’m not sure where to look for this but it may show up in a dev tools trace. I’ll report back with results. Thank you for the response.

1 Like
6

So, it’s confirmed I can’t pass data via BPMData. I also don’t think that the Kinetic customization is going to work because this process will run from both MES and (mostly) from EKW via handheld devices whose user interface, I don’t believe, I can customize.

It looks like I will have to store the values somewhere (UD fields) then retrieve when needed.
It’s not a great solution, but may be the easiest and most reliable (easy to implement and maintain).

I really appreciate the feedback gents. Thanks.

2 Likes
7

Yeah, that’s a tough one. Good luck!!

1 Like