Derive actor's current Role selected in Ming.le using LPL

Does anyone know how to derive the current Role an actor has selected in Ming.le with LPL?

I have a hard coded link in LPL and at the moment the Role is hard coded in the link, but I'd like to derive the Role the user currently has selected.

I was thinking something like the actor context but haven't found a way to do it so far. Only thing I found in the LPL guide was the ability to check if an actor has a role.

Thanks!
Andy

Find more posts tagged with

Accepted answers

All comments

Legacy Contributor

did you ever recieve a fix for this?

andy

Unfortunately not. Still using hardcoded roles in links.

andy

Not sure if this works prior to LM 34 but it appears for forms you can specify the BusinessClass.Form and it will derive the the full link, including the user's current selected role.

For instance if you wanted to add a button the Payables Invoice to open the Match Recon form you could add the following LPL...

visible when (HasMatchReconQueue)
button of "GoToRecon"
link is external "MatchReconQueue(<Company>,<PayablesInvoice>,_norep_).SmartReconDetailMatchComposite"

and the link returned will be:

LMHOST:PORT/.../MatchReconQueue(COMPANY,PAYABLESINVOICE,_norep_).SmartReconDetailMatchComposite

0712131256598360.doc

andy

link was truncated in previous post...

https:// LMHOST : PORT / DATAAREA / ROLE / form / MatchReconQueue(COMPANY,PAYABLESINVOICE,_norep_).SmartReconDetailMatchComposite

Dr. Awesome

Are you wanting to know the webapp the end-user has selected from the webapp switcher (you say Role) in the menu? Is that right? Can I ask why you need to know this?

Legacy Contributor

For us its to know whether a user has initiated a leave request as a manager , a generalist or self based on that we have diffierent flows to trigger

andy

Affirmative. When there is a desire to add a link to a list or a form, but a defined navigation does not exist on the relative business class, the alternative is to create a link with a hard coded URL. However, that link generally will require a hard coded role, and if different users with different roles need to access the link, but do not share a common role, the link will be broken for the users who don't have the role defined in the URL.

If the user's current role selected in the app switcher could be derived then it could be interpolated in the URL, and this issue could be avoided.

It seems there was an LM change at some point that allows for more dynamic links on a form going to a form, where the host (including the data area and role) is prepended to the link if no host / absolute path is provided in the defined link literal (as described above), but this issue still seems to persist for links from or to a list (though it has been a while since I've looked at this so behavior may have changed).

Alternatively, if there was an option to create navigations, all of this would be moot.

Thanks!
Andy

Copyright © 2025 Infor. All rights reserved.