Rules

Rules let you set up what happens when someone selects an option or clicks a button. For example, you can set up a submit button that sends the submitter a confirmation email and sends the form request through a workflow approval process. You can add as many rules as needed.  

Rules consist of conditions, answers values, and actions. Example. To set up a rule, you must add it to a question or field. Rules must ALWAYS have an If answer value is condition in the first statement of the sequence.

Condition Types

Condition Type

Description

If answer value is

Tells FormFlow to execute the action if the answer value matches the value you specify. Rules must ALWAYS have an If answer value is condition in the first statement of the sequence. To execute the action if any answer is entered, or if you are setting the action to trigger when a button is selected, enter * in the answer value field.

Else if answer value is

Tells FormFlow to execute the action if the answer value matches the answer value you specify when the "If" condition fails.

Else

  Tells FormFlow to execute if no previous conditions were met.

And

Tells FormFlow to execute the action in addition to any other action that is set to execute in the previous rule condition.

Action Types

Action Type

Description

Alert: Show Message

Shows a popup window with text you enter when the condition is met. For example, when the user clicks a submit button and a notification message appears letting them know their vote for the homecoming court has been submitted.

Email: Send

Sends an email based on an email template you can set up. This action can be triggered when the form has been saved or submitted. If campus portal has been configured to log emails (Site Settings > Framework settings > Email settings), these emails will be stored in the FWK_LoggedEmail tables.

Email: Cancel

Clears the flag indicating an email should be sent if the condition is met, effectively cancelling the previously queued email.

Form: Submit

Submits the form putting it in a “Submitted” status.

*Save functions automatically execute before Submit functions when using the Submit event. There is no need to include both Save and Submit actions within the same conditional block.

Form: Save

Saves the forms putting it in an “Active” status.

Form: Print

Sends the current page to the printer.

Form: Quit

Closes the current form and signs out the currently logged in temporary user if applicable. This does not log out a user authenticated into the campus portal.

Grid: Add

Adds the input values from all source questions to their respective grid. Requires the same question have the “Add Button” Grid Function.

Group: Clear

Clears values from all questions with the specified Group Name.

Group: Disable

Disables the specified question group if the user’s answer matches the value you specified in the rule. When questions in a question group are disabled, form users will still be able to see the questions, but they will not be able to enter any information into them. 

Group: Enable

Enables the question group if the criteria matches what you specified in the rule. This is only needed if you have a rule that disables the same question group.

Group: Hide

Hides all questions on the form with the specified Group Name.

Group: Make Not Required

Removes the required asterisk and makes the question optional.

Group: Make Required

Applies the required asterisk to the specified question group and prevents the form from being submitted until the answers are provided.

Group: Show

Shows all questions on the form with the specified Group Name.

Group: Toggle

If the questions with the specified group name are visible, this action will hide them. If they are hidden, this action will show them.

Payment: Use Profile

Indicates which profile should be used to process the payment submitted with this form. This is required to accept form payments.

Payment: Clear Profile

Clears the flag indicating a profile should be used if the condition is met, effectively cancelling the previously queued payment.

Payment: Override Balance

Sets a static value for the final balance and ignores any other calculated balances for the form payment.

Tab: Change

Causes the specified tab to be displayed if the tab is in a visible state. For example, this action can be applied to a "Next" button to display the next tab.

Tab: Show

Makes the specified tab visible, but not necessarily active.

Tab: Hide

Hides the specified tab.

Tab: Update Progress

Evaluates requirements on the specified tab. If all the required questions have valid responses, a checkmark appears on the tab. If not, the checkmark is removed. NOTE: This action has been deprecated. Jenzabar now recommends using the Form: Save action, as tab progress is now automatically updated any time the Form: Save action is use.

Workflow: Use Track

Indicates the Workflow track the form should be submitted to for review.

How to

Add a Rule to a Question

Automatically Send an Email When a User Submits a Form