How to prevent the Office MES customization layer from transforming into the full MES Screen?

Kinetic ERP
1

This post specifically concerns a customization of the Office MES screen for the Kinetic UX.

I have created a customization for the Office MES screen because we needed to add some custom UD fields to the “Start Indirect” slide-out. After getting most of this screen working properly inside of AppStudio, I added this customization to the main menu using the Kinetic UX version of menu maintenance.

There is big problem though: The base Customization layer for the Office MES Screen appears to be 100% identical to the base layer which is used by the full MES screen. This causes two issues: 1) A bunch of additional controls now appear inside of customized Office MES screens which we do not need, and 2) The logged-in Employee’s credentials are not automatically passed-through to the full MES screen from the kinetic smart-client, even though the layer has been applied to the Office MES client.

Note: This behavior is not due to the lack of a linkage between the User and the respective Employee inside of Kinetic. All of our User records contain links to their Employee-twin record. And the stock Kinetic Office MES screen automatically brings-up the Employee-twin for the current user exactly as expected.

The big problem with this situation is that Employees must now log-in each and every time they re-open customized Office MES screens inside of a Kinetic session. And this presents a genuine problem when people are clocking-into multiple operations, and/or indirects each day.

Here is a screenshot of the stock MES screen:

image
image1469×501 36.6 KB

By contrast, here is a what the stock base-customization-layer of this exact same Office MES screen looks like when it is launched from app-studio. Please take notice of all of the additional controls, and the fact that the Employee is longer logged-in:

image
image1221×737 37.8 KB

Please note that the above undesirable behavior persists even when Office MES customizations are added to the menu and launched from there.

I have tried hiding some of the extra controls to make the new layer more closely resemble the stock Office MES screen. While this has helped a bit, this has not solved the never-ending re-login issues for Employees who need to use the customized Office MES screen all day long.

My hope is that somebody else has encountered this issue, and that you can tell me what I need to be doing differently to keep this transformation from happening to the Office MES screen.

2

Does it seem kind of like this? MES/Datacollection cloud customers need to be able to publish more than one customization

3

Perhaps my problem is tangentially related to that issue. But that’s not specifically what I’m dealing with so far as I can tell.

I am now assuming that I am just going to be stuck with having to customize the full MES screen until I hear otherwise. So, I am now investigating work-arounds.

I’m presently trying to figure out how to populate the “txtEmployeeId_LogIn” control in the slide-out with the current employee’s ID.

I have added the EmpBasic_Login view inside of appstudio, since that appears to be where the Current Employee ID is likely to be contained.

And I am attempting to inject the EmpID from that view into the control by using the row-update widget.

But I haven’t yet figured-out which tricks are required to automatically insert the EmpID from the data view into the Login control. :thinking: