Paul (and David), I too had a requirement where I needed a field's default value (the field's id="inp_Type" and the field's name = "Type" as shown below) to be made available on the form at the time of submitting, -BUT- I didn't want it to be visible in the UI (also the reason why I didn't code for a label) .
I tried using the 'loaded="true"; attribute of the <xp:inputText> control while not making the field "visible" as suggested, but my managed bean wasn't seeing it.
The below snippet shows the last 2 fields (from a total of 7 UI fields being used) appearing just before my 'Submit' button. The 'Submit' action is nothing more than a call to my JAVA save() method used by my bean, i.e. --> person.save(). This is from my UI that ultimately creates a Person document within the NAB.
In order for the newly created Person doc to be visible in the NAB's hidden '($Users) lookup view, the doc needs (among other fields being present) the field named 'Type' to be set to a value of 'Person'.
When I made my 'Type' field control 'visible', the bean sees the value and it gets pushed onto the Person document that I'm in the process of creating within the NAB. However, if I make it NOT visible, through use of the Edit Box attributes, it doesn't get picked up.
I ended up doing the same hack as Bill did (unless he discovered a different way since his last post). I hard-coded a style of "display:none" to the edit box and allowed the Edit box to be 'visible' to the form' design and bean, but not visible in the UI.
This is being used in a 'New User Registration' UI modal dialog using a managed bean. This is running on Domino 9.0.1FP9 on top of Windows 2012 R2 Standard server with the XPage design using Bootstrap v3.3.7, jQuery v3.2.1, Font Awesome v4.6.3 and Bootswatch v3.3.7.
value="Re-enter your Password:" />