Can you limit access to certain fields and tabs on a form based on a users Mingle role?

For example, on the manage contracts form, we would like to disable or hide certain fields and tabs on the form based on a users Mingle role. Is this possible through LPL? If not, what is the best way to selectively provide different security access to the same form i.e. manage contracts?

Some users need full access and some need read-only selective access to certain fields and tabs based on Mingle roles.

Thanks.

Jeff

Find more posts tagged with

LSF/Landmark Development

Accepted answers

All comments

don-kintzle

You could do this by creating a conditional user field then on the form/panel you can use a "visible when" to display the fields.

Here I created a Conditional field is true when actor has the role of Admin_ST or AdminLTM or BenefitAskHR. In this instance the fields only display when the actor has one of the three roles I indicated on the Conditional User Field.

Then on form or panel you would add the visible when

cleverly

Don answered from the perspective of the form. His advice is 100% spot on the way to do the form customization you asked for.

I'm only writing elaborate my thoughts in response to the end of your first paragraph where you wrote "what is the best way to selectively provide different security access to the same form i.e. manage contracts".

Form customization doesn't truly "secure" the underlying data. Only security classes assigned to security roles can do that.

Assuming your users don't have the right roles (such that your custom condition would make the section of the form visible) but they do have roles that grant them access to inquire on the underlying business classes without any further field restrictions, then there are several ways they could defeat the "security" of your form customization.

The ones I can think of off the top of my head are:

If you allow users to personalize forms they could simply personalize the form and remove your "visible when" check, or change it to "visible when (true)" (so that it is always visible).
If you allow your users to use Infor Spreadsheet Designer, they could download the contents of the business class, including the sensitive fields.
If your users knew the syntax for a Landmark web service URL they could use a web browser to retrieve the data from the business class.

So while making a more efficient, friendly UI experience is a good way to go, if you have certain users who truly shouldn't see the contents of certain fields on certain business classes then you'll need to custom tailor the LPL behind the security classes that your roles use. The two approaches can work in tandem with each other, but the former isn't a true substitute for the later.

don-kintzle

Good point Michael, I glossed over the security aspect of the request. You are correct, if they truly need to be restricted from updating specific fields, then more than likely a custom security class/role would be in order to restrict those fields. My suggestion only addresses the cosmetic aspect of it.

Jeff Johnson

Thank You Michael. Good points.

Jeff Johnson

This is great Don. I understand the security concerns at the class level.

Legacy Contributor

You may want to try something like this on your User security class to hide the values on a form.

All Fields for Employee BusinessClass

excluding

TestEmployee2 // User field

for all actions

unconditionally

Dr. Awesome

Excellent recap of what we internally refer to as surface or perimeter level security vs deeper structural data & action security. Both have their place. Perimeter security is usually about UX and tends to be "security by obscurity" mostly, so watch out!

Copyright © 2025 Infor. All rights reserved.