- Introduction to WorkXpress
- Building Your Application
- Examples and Best Practices
- Technical Manual
The selected file /tmp/file48f45r could not be uploaded, because the destination sites/default/files/css/css_a91cd284035e73ba34d112bfed2f5a16.css is not properly configured. The selected file /tmp/fileM4BowC could not be uploaded, because the destination sites/default/files/css/css_de1aa27776f1462d2b0d83a80ce4b92d.css is not properly configured.
A checkbox is probably the simplest Field Type in existence, yet it is still quite useful. Basically, a checkbox allows users to answer “yes” or “no” to a simple question.
A checkbox is allowed to show another Field when it is checked as well as when unchecked. For details, see Checkbox Settings.
The checkbox has five output formats.
The checkbox Field Type can be filtered according to the standard two checkbox-type filters. To learn more about these filters, see the “Checkbox-type filters” section here.
The checkbox is also useful to hold a string of actions which need to be reused, much like a function. For instance, in a CRM application, you might want to track an opportunity's values as it progresses through its stages. Perhaps you'd want to create a related Opportunity History Item any time any of five different Fields were changed. You could create a checkbox called “Create Opportunity History” and attach an Item-Create Action (and all proper local Actions) to it and create a nested series of if-then statements (evaluations) to say:
if Field A changed
check Create Opportunity History else if Field B changed check Create Opportunity History else if Field C changed check Create Opportunity History...
and so on, which is much simpler (and more efficient) than re-creating the Item-Create Actions under each if statement.