Can a boolean checkbox be changed to a Y/N drop down?

Sort:
You are not authorized to post a reply.
Author
Messages
dcasper70
Basic Member
Posts: 14
Basic Member

    First post, so Hi and thanks for all the help you don't know you've already provided.

    v11.0.1.43,  single tenant, cloud, SQL Server.  Early stages of implementation.


    Per our business model, manager terminations do not go through HR for approval.  With 22k+ employees, HR relies on managers to handle their own terms with the expectation that they will do it correctly...

    In GHR, on the Terminate form, the delivered 'Eligible for Rehire' Boolean field is a rendered as a checkbox.  Our HR leads are pushing to change that to a required Y/N drop down.  Their reasoning is that managers will not properly change the default value and incorrect values will result in improper future hiring decisions.

    With a Y/N drop down, the default value could be blank, forcing managers to actively make a selection.  Seems like a reasonable ask.  Coming from a .Net background, this strikes me as something that should be simple. Y/N drop down, 0/1 value, drop it in the table, move on, nothing to see here....  

    I've spent the better part of a day trying to find some config console method of rendering the field in this way.  The best I can come up with is creating a new user field and adding it to the form, replacing the check box.  

    This doesn't sit right with me.  I don't want to have a new field to hold a value that already exists in a delivered field.  I don't like the idea of searching for all locations the delivered field is referenced and switching the reference.  I also don't like the idea of creating a field on a form for the sole purpose of updating the delivered field behind the scenes.  Just seems hokey to me.  

    Can't see how to do this?!?  Am I overlooking something obvious, or is this really my new world?

     

    Woozy
    Veteran Member
    Posts: 709
    Veteran Member
      Hi dcasper70,
      I don't think this is possible, because that field is actually 1/0 rather than Y/N. The Landmark Pattern Language doesn't really allow you the flexibility of .Net, so you can't really add logic like this. I suppose you could do something like this:
      - Create a Boolean or Y/N UserField named "ConfirmNotEligibleForRehire"
      - Create a constraint on the form that will not allow the "Eligible for Rehire" checkbox to be unchecked unless the userfield has the appropriate value (1 or Y)

      This would allow you to use the delivered field as intended, but would require the manager to take action if they don't check the box.

      NOTE: Constraints are very confusing - If I remember correctly, the constraint message only fires if the constraint is FALSE. So you'd want to do something like this:

      constraint(!EligibleForRehire and ConfirmNotEligibleForRehire = "Y")
      "PleaseConfirmEmployeeIsNotEligibleForRehire"

      Good Luck!
      Kelly

      Kelly Meade
      J. R. Simplot Company
      Boise, ID
      You are not authorized to post a reply.