Process Hub · Fields, validation and calculations

Configure required answers, conditions and validation

Guide people to the right questions and test missing or invalid input before release.

On this page

Before you start

  • Have a saved draft with named fields and examples of valid, invalid and irrelevant answers. Decide which rules apply at capture and which apply at a later action.

Validation and access

Conditional hiding is a presentation choice. It does not erase stored values or grant data security. Process/record access and protected fields still apply.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Open the field/question configuration. Set Required for answers needed whenever that field applies. Use suitable types instead of relying on instructions to turn free text into dates or numbers.
  2. Configure conditional field/page behaviour using available rule controls. Choose a source field, an appropriate comparison and the target field/page effect. Keep the first version simple enough to explain.
  3. Check every branch: for example, “Other” should reveal its explanation field, while an ordinary category should allow the user to continue without answering irrelevant questions.
    Question Logic panel with Default visibility, Hide when, Rule and Branch controls.View full size ↗
    Configure conditional visibility and branching in Logic, then test both matching and non-matching answers.
  4. For a later lifecycle action, add its Required fields in the action editor instead of demanding the final resolution during initial intake. A required repeated-row field applies to every existing row.
  5. Use Preview to test blank answers, boundary values, all branches and back/forward navigation. Check that errors identify what the user must fix and that hidden questions do not block the intended path.
    Customer Case form with an empty required Issue description and a validation message.View full size ↗
    The message identifies the missing required answer. Correct it and try submission again.
  6. Save, publish and deploy. Repeat the same tests against a real training record; server checks at submission/action remain authoritative.

Example: explain an unusual issue

Use issue_type with a controlled “Other” option and show other_details only for that option. Test “Damaged”, “Other with detail” and “Other without detail”. Then test resolving the case without resolution_notes to confirm the later action blocks it.

What you should see

A user can complete the applicable questions and sees useful validation before the record or action is accepted.

If something goes wrong

The form submits with a failed quality answer

Required/valid input is different from business failure detection. Enable Identify failed answers and a published non-conformity workflow if the answer should create follow-up work.

An offline submission looks accepted on the device but later fails

Queued changes still need server validation and the current deployed rules. Inspect sync results and correct/retry the record when online.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help