If you are already using the legacy screener, you can migrate to Progressive Screener (V2) at any time.

Migration Steps

To migrate to Progressive Screener (V2):

1. Enable the Screener (V2) toggle.

2. Review your existing screener configuration.

3. Resolve any validation errors displayed in the setup.

4. Publish your changes.

You can switch back to the legacy screener at any time, if required.

Important Rules to Understand

Required Questions

Required questions determine what users must complete before entering the platform.

• If a required question already has a value, it does not appear.

• If a required question does not have a value, it appears during onboarding.

Optional Questions

• Optional questions never appear during onboarding.

• Users can complete them later, after login.

Auto‑Filled Questions

When data is available through Single Sign‑On (SSO) or SFTP uploads:

• The system treats the question as already answered.

• The question does not appear during onboarding.

Hidden Questions

If a question is hidden:

• Users never see it.

• If the hidden question is required, it must be auto‑filled.

Dependent Questions

Dependent questions rely on a parent response.

• If a child question is required, the parent question must also be required.

Validation Errors You May See

Validation errors prevent incorrect configurations during migration.

• Example 1: Required Question Is Hidden but Not Filled

  Cause: A required question is hidden without an auto‑filled value.
  Fix: Enable auto‑fill for the question.

• Example 2: Required Child with Optional Parent

  Cause: A child question is required, but its parent is optional.
  Fix: Mark the parent question as required.

• Example 3: Auto‑Filled Question with Regex Validation

  Cause: Regex validation is applied to an auto‑filled field.
  Fix: Remove Regex validation. Regex is not supported for auto‑filled fields.

Common Scenarios

• All Data Exists

  If all required data is available through SSO auto‑fill or SFTP uploads, users skip the screener entirely.

• Partial Data Exists

  Users see only the required questions that are missing.

• Admin Adds a New Required Question Later

  Users are prompted to complete the new required question after login.

• User Refreshes the Page

  The system saves progress automatically.

• User Logs Out

  Onboarding restarts at the next login.

Best Practices

Do

• Keep required fields to a minimum.

• Use existing user data wherever possible.

• Test your configuration before publishing.

Don’t

• Mark too many questions as required.

• Create unnecessary or complex dependencies.