Slide Out Customization

I need some help applying some changes in application studio for a slide out.

We want to customize the slide out for Part Lot Attributes.

How does one apply kinetic customizations on slide outs that are being called by Process calling.

I’ve tried setting the menu arguments via a baq, the menu maintenance doesn’t seem to have the customization.

Short of modifying all the kinetic event calls to point to the new slideout customization there has to be a better way.

Main issue is how to get customizations to stick/load for process slideouts?

1 Like

What is your trigger for the slide out?

I’m not at my PC, so i can’t look for exact steps easily… but this thread should hopefully help:

Basically you have to make a custom layer of the slide out form (process).

Then you need a custom layer of the base form (the linked example above was using MES, but I would assume it would be the same). In that layer you’ll need a new event which loads the target process, with your new custom process layer applied.

1 Like

Sorry I need to be more clear.

In Receipt Entry, When we enter a new part lot with attributes it opens the slide out for part lot attribute entry. It is a seperate kinetic page.

Application studio allows me to make customizations to that slideout.

But now I need to find out a way to apply that layer so when receipt entry calls that page it is the customized page vs the default page.

10.2.700.8 Process Calling Maintenance For Lot Attributes - New Issue - Epicor ERP 10 - Epicor User Help Forum (epiusers.help)

or
Modifying Lot Attribute Entry screen from Receipt Entry - Epicor ERP 10 - Epicor User Help Forum (epiusers.help)

are similar issues but I need a more recent breakdown that works.

1 Like

Right. The base event on the base form calls the base process.

You need to customize the base process to include whatever you’re looking for.

You then need a custom layer of the base form. Receipt Entry. This is because you need to alter the event… but you can’t change base events. So you need a custom layer of Receipt entry. Then copy the base event and where it calls the attribute process (app-open), you can enter a layer to apply. You’ll tell it to apply your custom process layer.

So, in the end, you’ll have a custom form layer (Receipt entry) with a customized event to call the app open (lot attributes… or whatever) with your custom process layer applied.

You can hopefully copy the base event and set the trigger to override the base event.

… i know it sounds like a lot, and there should be a better way… but this seems to work. I can test it out in detail tomorrow morning if it helps.

2 Likes

How does one override the base event?

I managed to get the page to load the customization layer but after it closes the original base event fires.

The trigger I believe is
CallChkForNeedsLotAttrsUpt

this is the one event that I’ve managed to insert a “before” event to call my own app.open

It opens up Erp.UI.LotNumberAttributesEntry as a slide out

You create a new event with trigger Type as Event, Hook is Override, then the Target is the name of the event you are overriding.

You could copy the event first, then just change the Trigger to achieve this – and then, of course, make your changes to the event.

1 Like

Check This Out Cookie Monster GIF by Sesame Street

Its a little confusing because CallChkForNeedsLotAttrsUpt uses a rest-erp to call

image

It doesn’t seem to want to let me hook to this one or override it

The app-open is the one I think I need to update.

but this one I think is the parent to all of it

What are you customizing that you cannot just edit the existing slideout?

1 Like

There are slideouts that open a separate screen (application) - like an iFrame of a different web page. You can pass it values and which layer to use, but it runs independently from the main page you have open (I’m not sure it even has access to the data views of the current page, either)x

In this case, Receipt Entry opens an instance of whatever application handles Lot Control in a side panel…

1 Like

I would override that event then, since that has your app-open… That’s what you’re trying to change so it opens your layer.

Make a copy of this event… alter the app-open to include your layer.

The trigger on your new “copied” event will be as @jwphillips described:

So, anytime that event is called… YOUR copy of the event will be used instead.

1 Like

Then why not create a layer on that app and specify the layer to use? It is in app studio.

image

You DO have to do that step.

But the base event in Receipt Entry (which you can’t edit) calls the base layer of the LotNumberAttributeEntry application.

So, you need to create a copy of the base event in Receipt Entry so you can apply your customized layer to the app-open call.

2 Likes

I just re-read, I thought the OP was creating a custom screen and not putting a layer on the existing.

3 Likes

image
Is this the right way of calling it?

I’ve throw in a dialog box and I’ve restarted my application studio, but the override doesn’t seem to want to trigger.

1 Like

Should be. Looks correct. :thinking:

It is odd that the base events seem to call the app-open within two different events.

I don’t know if you’d need two different override events to make sure you capture both cases?? Tough to follow from a distance, and we don’t use lot attributes so I can’t really test this exact scenario out.

You can force a custom layer using a bpm on GetApp method.

I’ll drop the code tomorrow, unless @klincecum beats me.

3 Likes