Form location fetching not working as expected in the IOS
Scenario: The user was performing the meeting check-in activity from an Android device, and it is working as expected. However, when I perform the same activity from an iOS device, it throws an error.
Root cause:
In the regex configuration customer has used " ^(true|0)$ " which is compatible for android but not for the IOS, as it takes " 0 " value as a false.
Solution:
Reconfigured regex using ^(true|1)$.
Related Articles
Form Rule With Mavis not Working for Mobile App
Scenario: User has reported that the form rules (Fetching mavis value from DB) are working as expected in the web platform but in mobile application. Root cause: We have two different scenarios: 1. Form configuration setting miss: The field used in ...
Fetching Forms error on Mobile App
Issue: Users get Fetching Forms, please try again later error while marking activity from mobile app. Resolution: This issue arises when users immediately access a form upon logging in. We perform multiple API calls to fetch and store metadata ( the ...
Form Export Issue
Problem - We are unable to find an option to export the form in HTML format. Solution - The visibility of the export form HTML option depends on whether the portal feature is enabled in the account. If the account has the portal feature enabled, only ...
Filter and search only opportunity fields in form rules
Problem: Currently if you try to search form rules containing a particular opportunity field in the search bar, it does not yield any results. This is a bug and will be fixed in upcoming releases. Workaround: Remove the opportunity code in the search ...
Why some form field's data is not pushed to pre-validation Lapp?
Issue: On form submission, not all field values are pushed to pre-validation Lapp. Root cause: In the Dynamic form, under additional setting if the 'Post only modified fields' is enabled, then only the values modified after submiting the form will be ...