hi Ahmed,
I havent tried it myself but something like this should work:
${submission.portal.getPortalProperty('url')}
where 'url' is your arbitrary form space property name with a value set in it.
I'll just expand here and add on how to get the properties of
form version property eg...
hi Ahmed,
I havent tried it myself but something like this should work:
${submission.portal.getPortalProperty('url')}
where 'url' is your arbitrary form space property name with a value set in it.
I'll just expand here and add on how to get the properties of
form version property eg 'productName':
* $submission.version.getVersionPropertyMap()['productName']
* $func.formProperty('productName') "Return the named form version property value of the job start submission."
organization property
* $func.formProperty('productName') it'll actually search for the named property in form/org/portal first submission/txn is linked with
I hope thats helpful. Please give it a try and let us know if you hit any problems. cheers, Miro
Hi Richard, its been some time you raised the question. Do you still have this problem?
I wonder how do you store the data in the allIndividuals data field. Note that you cannot set complex JSON (arrays, nested structures) into a data field bound to the payload XML (saved data to TJM) and expect...
Hi Richard, its been some time you raised the question. Do you still have this problem?
I wonder how do you store the data in the allIndividuals data field. Note that you cannot set complex JSON (arrays, nested structures) into a data field bound to the payload XML (saved data to TJM) and expect it being prefilled back on resume as a JSON object value. This is not supported in Maestro as far as I know. Any value stored in a (XML bound) data field must be of a primitive type which can be easily serialized as a string (int, float, string, boolean). I noticed that if you do store a complex json to a bound data field, maestro will try to recreate the JSON structure as XML nodes+elements structure. It still gets saved to TJM as form XML but when resuming, Maestro wont recreate the JSON object from the XML data.
Hence my recommendation, for such use case,
* either try to use repeats which you could follow your JSON structure via maestro widgets + bindings .. for data storage
and have unbound data field as the data source for your data drive RB - implement calc rule from the data in the repeat
* or store the JSON to a bound data field as a serialized JSON string via JSON.stringify() but you would need to deserialize it back from the bound data field into another one used as the data source for you data driven RB widget on form load.
Hope that makes sense.
cheers, Miro