How to replace default App-Open with Customization

I’m attempting to customize the ‘End Activity’ screen in Kinetic MES. I have created a Customization Layer with my changes, saved and published it.

I found the Menu Item in Menu Maintenance (Menu ID PR00019), and set its Kinetic Customization to my new layer.

Unfortunately, when I click the ‘End Activity’ button in MES, the customization layer isn’t shown. It always appears to be the Base layer. (Strangely, when I open the overflow menu for the End Activity dialog and click Application Studio, it opens my custom layer)

The End Activity form is shown as a SlideOut dialog, launched via an App-Open widget. The App-Open widget has a Layer parameter. The default ‘End Activity’ button click event is calling App-Open for the End Activity app, but passing a blank value to the Layer parameter, therefore the Base layer is always shown.

So the question is, how do I achieve my goal? I can’t edit the default events… do I need to create my own ‘End Activity’ button with its own event chain, and hide the default button? I really just want to apply the layer, I didn’t want to change events if I can avoid it…

We have done this earlier this year let me see if I can go find out the exact process

2 Likes

We modified the MES menu in 10.2.700 by adding a custom button to call our bartender dashboard. To do that we created a customization on the MES menu, added code to call the correct menu item for the dashboard, and modified the sysConfig for MES to call that menu customization. We are not in Kinetic yet.

Thanks Julie.

This issue I’m dealing with is specific to Kinetic MES.

We have a custom layer on the main Kinetic MES screen, and it works as it should. However, I’ve also applied a custom layer to the ‘End Activity’ dialog, but is not showing the customization.

The End Activity form is a slide-out menu triggered by a button click event, and I’m not sure how to get it to show our customization.

How important is this to you, and how good at keeping documentation are you?

Very. I’m open to alternatives, but in order to get some info from our employees upon ending a labor activity (that is not already on the End Activity form), I don’t see a way around it.

Decent, could be better. If you have some magic hacky solution, it could inspire me to improve.

I do.

It’s not awful, but if you forget you did it, it might be hard to trace down later :slight_smile:

Is it related to this thread?

Manipulating the Kinetic Web UI from the backend for Fun and Profit

Yep.

OK, I think I know where we’re headed.

I just created a new button then add the widgets that are used in the base event. Here is an idea from start activity. You need to modify this a the main MES screen. You will see where you type in the layer that you want. Look at the info on the default button to create the new one. The base is locked.

Thanks Mike,
This is what I was expecting, but hoping to avoid.

I will now weigh this against @klincecum’s idea and see where I end up.

Doc Brown Fly GIF by Back to the Future Trilogy

You just need the very first part of that post.

Give me a sec, I had another thread with just forcing a layer, which is all you need.

An easier option you can do is just copy the event and then call that copied event of the EndActivity from the new button click with EventNext and call the new copied event. In the new event just modify the layer for your customization.

I like people to play with my code, but I also like this solution :slight_smile:

I think that with the BPM solution I can get Kinetic to behave the way it should by default (in my opinion)…

I already assigned the Customization Layer to the End Activity menu item in Menu Maintenance, and I would expect it to honor that, the same way it does for the main MES screen. Just because it happens to be a slide-out triggered by a button event, shouldn’t mean it ignores the customization layer defined on the menu item.

In the BPM I can look up the menu item in the database, get it’s Kinetic Layer property, and apply it.

Just remember, anything that request that app, even application studio, will pull that layer
with it when that BPM is enabled.

Interesting, I did not see that at first using the BPM to set it. I like that also. I meant the second was easier than my first suggestion.

Yes, I was hoping to find some metadata in the dataset to selectively apply this. I’ll give it a try, I may end up going with the duplicated event approach in Application Studio.