I don’t know the complete answer, but have used some of them in the expression debugger, which made things a little clearer for me.
Example:
String:field_fieldtype(“contacts.contact_name”) → novulodatastructuretypes:load(“string”)
→ Sometimes I don’t want to look it up in the datamodelbrowser
String:field_fieldname(“contacts.contact_name”) → “contact_name”
→ If this results in string:getnull() then I know a field does not exist in this database
String:field_id(“contacts.contact_name”) → “contacts~n_contact#a1f1fca8-cb11-4c1b-88c8-09d5e30e4940.contact_name”
→ This I use when implementing workflows for quickly accessing the concept-UUID
boolean:field_is_function(“contacts.contact_name”) → false
→ I’m not sure why, because it is a cached function from contact_name() so I don’t use this. Maybe it is useful in architect is you want to enter data in a dynamic field to check is it ends in ()
This is a start, but I think the one who’s responsible or who created these plugins is also responsible for proper documentation. I think in general, documentation for all plugins should be visible in the architect. Is this on the roadmap somewhere at Novulo?
This is great. I haven’t looked at it yet, but I’m sure this will help all Novulo users that will use this plugin! When I have some questions about the documentation, I will reply on the documentation thread it self!