Mobile Onboarding for iOS v10.0.3

  • Release version: Mobile
  • Updated June 1, 2020
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Mobile Onboarding for iOS v10.0.3

    The iOS v10.0.3 release enhances the Mobile Onboarding application with critical fixes. Users are encouraged to download the latest version from the Apple App Store and can access a demo account to explore the app's features.

    Show full answer Show less

    Key Features

    • Dependency Fix: The dependency of fields based on UI parameters has been corrected, ensuring that dependent fields function properly when configured correctly.
    • Search List Input: Issues with the Search List input type for UI parameters have been addressed, improving user experience when navigating and canceling selections.
    • Bug Fixes: Additional minor bugs have been resolved to enhance overall application performance.

    Key Outcomes

    After updating to this version, users can expect improved functionality in handling dependent fields and a more reliable experience when using Search List parameters. This ensures that the Mobile Onboarding application operates smoothly, enhancing the onboarding process for users.

    The iOS v10.0.3 release provides fixes for the application.

    Download the latest mobile app version

    To download the latest release, visit the Apple App Store. Users can launch a demo to try the Mobile Onboarding app. You can use a demo account from the initial post-download screen or the instance list screen.

    Fixed in this release

    Problem Short description Steps to reproduce

    Mobile iOS (non-classic)

    PRB1406196

    		 The dependency of the field on a UI parameter does not work unless the dependent field is also added as a UI parameter on the action screen
    1. Navigate to the instance and open the function named 'Reassign incident'.
    2. Remove the UI parameter for Assignment group and also remove the parameter mapping for the same so that Assignment group does not show up on the action screen.

      This leaves Assigned to as the only parameter visible on the action screen.

    3. Add another UI parameter (anything apart from Assigned to) on the function so that Assigned to is not the only one.
    4. Open the applet Active incidents and use the swipe function Reassign on a record that already has an assignment group on it.
    5. Tap on the Assigned to field.

    Expected behavior: The user records associated with the Assignment group should show up since Assigned to is a dependent field of Assignment group.

    Actual behavior: When Assignment group is not added as a UI parameter on the action screen, all user records show up, and the dependency is not honored.

    Mobile iOS (non-classic)

    PRB1406059

    		 When Search List is added as a UI parameter, navigating to the parameter and then cancelling is removing the value on the action screen
    1. Navigate to the instance and open the function named 'Reassign incident'.
    2. Navigate to the UI parameter for Assignment group and change the input type to Search List.
    3. Save the record.
    4. Open the applet Active incidents and use the swipe function Reassign on a record that already has an assignment group on it.
    5. On the action screen, observe the two parameters, Assignment Group and Assigned To.

      Notice that Assignment Group has a value in it.

    6. Tap on Assignment Group.

      The list of groups shows up.

    7. Cancel this screen without any new selection.

    Expected behavior: Since no selection is made, it should retain the prior value.

    Actual behavior: Previously stored value for Assignment Group on the action screen is gone.

    This version also includes other minor bug fixes.