There is very little explanation of Stateless Form and how to manage their implementation in real-world application. There are some things I need to do that a basic report just can't do, and I can only guess that a stateless form is the only option, but then I come to find you can't do many basic things with a stateless form.
Example, I have a form that gathers fuel purchases in both US and metric means. It stores date, location, odometer, and quantity. I need to be able to present the user with a "form" to select a Begin and an End range, then click "Calculate". This would then gather up the distance travelled, the units of fuel bought, and the MPG or L/100Km fuel economy (depending on user default setting) and then set certain unbound text fields with the appropriate concatenated results. I don't think I can effectively do this with ZC Report Creator.
But the issues I'm having are you can not use a "Button" to assign any field values due to "security reasons" so I've discovered here elsewhere. So I've managed to get an On-Input action to fire the validation and calculation, but I don't like this style of coding and development. Why can buttons not be used to perform processes and assign values to text and number fields, when the user is ready?
And, what happens to the form when I'm done (on a handheld device)? Is it still active in memory and just in the background? If this is the case, Is there a way to "close" the form with a button? (This particular module will mostly be accessed from a smartphone as it is very common, does not require data-entry, and is very basic in it's purpose)
I see the "Cancel" button all through ZC but no idea what the button does in the background and how to implement this on a stateless form.
Below is essentially what I'm doing now. I would prefer to add the calculate option to the button at the bottom but this is not allowed ..