Joget Blog

This post is a follow up from an earlier posting of Joget Workflow Form Builder - More than Just Workflow , in our quest to explore different kinds of form designs. Technical aspects discussed in this posting requires slight elevation of technical know-how, such as database table design and ERD (entity relationship diagram). In this case study, we shall use the default Expenses Claims App that comes bundled by default with every Joget Workflow installation, so that this article can double as a how-to guide for everyone to try it out. Let’s begin! When submitting a new claim, there’s a spreadsheet element to facilitate the entry of claim items. The spreadsheet element is a grid element where it establishes a one-to-many entity relationship between the claim and claim entry entities. Through the use of “Multirow Form Binder”, the claim form would be able to save the multirow data of spreadsheet into the “Expense Claim Entry” form table. “claim” is the foreign ke...

A Condition transition is used part of decision making process for the purpose of routing in a workflow process. What we have below is a typical "Yes/No", "Approve/Reject" routing by using the following expression. status == "Approved" whereby "status" is a declared Workflow Variable . If the "status" variable contains the exact string of "Approved", then the Workflow would then flows to "Send Approved Proposal". Expressing more with the expression In the "expression" field of the transition element found in your workflow process design, one can  actually put in Javascript coding into it. As long as at the end of it, one of the statement would return a true/false value.  Example: var myRegExp = /dog/; var myText = " My dog smells worse than your dog"; myRegExp.test(myText) would return a true . var myRegExp = /dogie/; var myText = " My dog smells worse than your dog...