UserField with States

We currently have a user field that has been used for several years. I am needing to "hide" one of the states so it is no longer used but want to keep any history of when it was chosen in the past.

Concerned if I would remove the state, it would cause issues on Employees who have that as a value in the field when updating their record.

If I just change the label to say Do Not Use, it updates the information on the Employee Records that have that value/label currently.

Is there a way to hide the stated or on the form that it is used hide that choice?

Thank you

ppendixa.xls

Find more posts tagged with

LSF/Landmark Development

Accepted answers

Dr. Awesome

Cool new capability that came with 2024.10 is "LimitedStates".

LimitedStates ::=

(Allowed | Suppressed) States

<StateName>… // must be a valid State

This is specified where you use the state field on forms (vs. where you define it.)

Example:

TaskType
Allowed States
   Form
   Instructions
   Content
   SendEmailAndComplete
   URL

You could see how using Allowed or Suppressed makes sense depending on your situation.

Here is the full definition of TaskType (on TransitionTask) itself:

TaskType is Numeric 1
States
   Form value is 1
   Instructions value is 2
   Content value is 3
   SendEmailAndComplete value is 4
   URL value is 5
   TaxForms value is 6
   FormI9 value is 7
      default label is "FormI-9"
   HRSDContent value is 8
   Activity value is 9
   default label is "L&DActivity"

Give that a shot and let me know how it goes.

All comments

smodarressiyazdi

I think you can green out the LPL using // on the field. Might want to check that in your DEV/TRN environment.

0712131256598360.doc

Debra Ford

Thank you, I will test and see what it does

Debra Ford

If I comment it out using //, then make an update on that Employee who already has the value I get an error stating that value is not listed, so would need to change the original value.

0911060553270289.pdf

Debra Ford

If I comment it out using //, then make an update on that Employee who already has the value I get an error stating that value is not listed, so would need to change the original value.

Dr. Awesome

Cool new capability that came with 2024.10 is "LimitedStates".

LimitedStates ::=

(Allowed | Suppressed) States

<StateName>… // must be a valid State

This is specified where you use the state field on forms (vs. where you define it.)

Example:

TaskType
Allowed States
   Form
   Instructions
   Content
   SendEmailAndComplete
   URL

You could see how using Allowed or Suppressed makes sense depending on your situation.

Here is the full definition of TaskType (on TransitionTask) itself:

Give that a shot and let me know how it goes.

Debra Ford

Thank you that was exactly what I was needing!

cleverly

That is cool!

It isn't documented in the current version of the LPL Reference Guide; were there other cool new features like this that we should know about?

andy

@andrew-lipetzky

I had the same question lol The published LPL Reference Guide seems to be from 2023. Is there an updated guide available somewhere?

https://docs.infor.com/lmrk/2025.x/en-us/lmrkolh/lmrklpltg/inforlandmarkconfigurationconsolelpl.pdf

Dr. Awesome

I had the same concern when I posted this originally. LPL Reference Guide will be updated soon for the April 2025 release and we'll republish with the October/April feature releases going forward.

0911060553270289.pdf

Dr. Awesome

A new guide updated to the 2025.04 release is published now.

I plan for a "what's new" (since 2023 actually) post that calls out the new LPL that I thought would be most interesting.

Copyright © 2025 Infor. All rights reserved.