Form validation script fails on conditional fields when accessed via mobile app

We have custom validation scripts on a case form that work perfectly in the desktop web app but fail completely in the Creatio mobile app. The validation logic checks conditional fields that become visible based on case type selection.

Here’s a simplified version of our validation script:

if (caseType === 'Technical') {
  if (!technicalDetails || technicalDetails.length < 10) {
    return 'Technical details required (min 10 chars)';
  }
}

On desktop: Field becomes visible when case type changes, validation fires correctly on save.

On mobile (Creatio 8.1 app): Field visibility works, but validation script throws undefined errors. The conditional field values aren’t accessible to the validation function even though they’re visible and populated.

Is there a different approach for mobile vs desktop validation? The built-in required field validation works fine on mobile, but our custom conditional logic fails. Do we need separate validation methods for mobile forms?

In mobile validation scripts, use this.get('FieldName') instead of direct field references. The mobile app’s validation context is bound differently. Also, conditional field visibility in mobile has a slight delay - the field might not be fully initialized when validation runs. Add a null check before accessing field values.

Another consideration - are you using business rules or script-based validation? Business rules are more reliable across mobile and desktop because they’re evaluated server-side. Script-based validation runs client-side and has different implementations. For cross-platform consistency, I always recommend business rules for conditional logic when possible.

Mobile forms in Creatio use a different rendering engine than desktop web forms. The validation context is more restricted. Your script is probably trying to access DOM elements directly, which doesn’t work the same way in the mobile app. Try using the form’s data context instead of direct field references.

That’s helpful. How do I access the form data context in mobile? The documentation examples all show desktop web form patterns.