Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

SD. "limit field value range by relations" funcionality in UI Rules

SOLVED
Go to solution
Highlighted
Maximo 5
Regular Collector

SD. "limit field value range by relations" funcionality in UI Rules

Hi,

I like to know what is the utility of action "limit field value range by relations" and how it is configured.

Platform SD 4.5 SP18 in HP-UX
Thank you
5 REPLIES
Ruth Porter
Honored Contributor

Re: SD. "limit field value range by relations" funcionality in UI Rules

Hi there,

You can use this to reduce the number of UI limit rules you need to use.

Suppose you want to restrict the range of impacts by the folders SC are saved in. You start by setting up your generic relationships where you associate with each folder the impacts that are allowed. You have to do each one separately which is ot very nice but then you can just use the limit field value range by relations and apply this relation.

Hope this helps

Ruth
http://www.teamultra.net
Maximo 5
Regular Collector

Re: SD. "limit field value range by relations" funcionality in UI Rules

Hi Ruth,

One question. In your example, what values set in fields "Target Field" and "Source Field" and how to make the general relation?

I Attach capture.

Thanks
Ruth Porter
Honored Contributor
Solution

Re: SD. "limit field value range by relations" funcionality in UI Rules

Hi there,

See the attached.

Hope this helps (& if it does points would be nice)

Ruth
http://www.teamultra.net
Maximo 5
Regular Collector

Re: SD. "limit field value range by relations" funcionality in UI Rules

Ok Thanks
Robert S. Falko
Honored Contributor

Re: SD. "limit field value range by relations" funcionality in UI Rules

Maximo,

I'll give you another example of the utility of this function.

We use Work Orders especially for changes and problems. Each category of change or problem work order has potentially a different closure code. For example, if we use a work order to authorize something, we put the authorization in the closure code; if we ask someone to implement a change using a work order, the closure code tells us if the work was succesful or not, whether there was a roll-back or not, etc.

Whew! you are saying. That's complicated!

Yes, it is, unless we restrict the available closure codes based on the category of the work order. If the category is "Authorization", the only closure codes the user sees are "Authorized" and "Rejected"; if the category is "Implement Change", the only closure codes the user sees are "Successful", "Failed - Rolled Back", and "All hell broke loose". etc.

And that is very simple, from the point of view of the user.

-Josh
//Add this to "OnDomLoad" event