fr:control-string-value()(see above), but it returns:
array()of all the values found
valuesuffix as we anticipate future versions of Orbeon Forms to associate to the workflow stage a label, and also possibly a description, for cases when the workflow stage needs to be made visible to users. Thus the value will be only used to keep track of the current workflow stage, while the label and description will be user facing, and if needed localized.
true(): when the form runs in offline mode (for example using the "Test Offline" Form Builder button)
false(): in all other cases
portlet: if passed, returns true if embedding is done via the Form Runner proxy portlet
java-api: if passed, returns true if embedding is done via the Form Runner proxy portlet
trueif the user is currently editing a draft,
map(xs:string, xs:string?), where keys map to values as follows:
path: the path to the PDF template in the persistence layer
name: the name of the PDF template, or the empty sequence if none was provided
lang: the language of the PDF template, or the empty sequence if none was provided
xxf:component-param-value(), but is designed to be used in XBL components that are expected to run in the context of Form Runner. It searches parameters in this order:
xxf:component-param-value('theme')called from the
fr:recaptchacomponent uses the value of the
oxf.xforms.xbl.fr.recaptcha.theme.*.*, following wildcard rules
oxf.xforms.xbl.fr.recaptcha.themeproperty, as done by
fr:component-param-value()while maintaining backward compatibility.
createpermission for the current app/form name (detail page only).
deletepermission for the current form data (detail page only).
readpermission for the current app/form name (detail page only).
updatepermission for the current form data (detail page only).