What's new on JourneyApps

We're excited to announce that runtime version 4.83.2 stable has been released.

Version 4.83 introduces a new way to customize the styling and default behavior of UI components using extendable themes and component configuration. Additionally, it includes many small fixes and improvements. Version 4.83.2 includes additional minor fixes.

You can use this version of the runtime by selecting it from the list of stable runtime versions under App Settings/Runtime Version in OXIDE.

4.83.2

Fixed:

• An issue with an object-table's typeahead cell type, where background (default) colors were missing.
• A bug with the list component, where its heading would wrap to a new line mid-word.
• A bug with the button-group component, where buttons were not referencing the default style, color, etc. attributes correctly.
• An issue with the toZPL() function when using the capture-signature component, causing it to return "No path in SVG".

4.83.1

Added:

• Support for password protected PDFs in the file preview within the display-file  and capture-file components.

Fixed:

• An issue where a HTML component's height was no longer automatically calculated when no height was specified.

• A bug with the capture-coordinates component that caused markers to break.

• A bug with the capture-coordinates component that caused and on-location to fire when zooming.

• A bug resulting in no longer being able to update the time within the datetime-input component on Android and iOS.

• A "TypeError: Cannot read properties of undefined" error that occurred in certain cases when a view initializes after an app update.

4.83.0

Added:

• We have added more ways for you to customize the look and feel of apps using extendable themes. Themes can be applied across the entire app, on specific views, or specific components can also be styled. In addition, you can specify default values for UI component fields (e.g. whether controls should be visible by default on object-table). You can read more in the documentation.
• single-choice-radio and multiple-choice-select options can now be displayed in a row using the mode="row" attributes.
• text-input component has a clear() method to programmatically clear the inputted value. Usage: component.textInput({id:"name"}).clear()

Improved:

• Underlying improvements to the database and sync system which results in a limitation when downgrading from runtime version 4.83.0+. Please see further details in this developer community post.
• The first input component that fails validation will now scroll into view.
• The initial placement of very wide or high images when users view them full screen.
• The 1000-parameter limit was removed from the in query operator. E.g. DB.myobject.where('id in ?', myLargeArray). This prevents a "too many SQL variables" error.
• Performance improvements when using .include() on queries.
• Apps with runtime version 4.83.0+ will always have the JSON1 query engine enabled.

Fixed:

• Clicking Cancel on the Leave App dialog no longer signs out the user.
• Long words wrap correctly on info-table and list components.
• Long titles wrap correctly in the action-sheet component.
• The app no longer goes into a broken state when users repeatedly tap / click on the hardware back button (Android).
• South African ID number validation is now fixed for 29 February birth dates.
• The context menu will now correctly show indicators when defined in the app.xml.
• Disabled buttons in a split button-group now trigger the configured disabled-message.
• object-table now renders all objects in an array, even if there are duplicate objects.
• on-change, on-scan and other on- actions now show a loading spinner until the triggered functions stop executing.
• The language selector is legible in dark mode.
• A regression that affected the default-sorting behavior in object-tables
• A bug that resulted in the following error: Uncaught TypeError: Class constructor JourneyError cannot be invoked without 'new'.
• A bug that resulted in a "this is undefined" error when performing an action via an on-change function.
• An issue with the toggle component on mobile devices where touch events were not always handled correctly.

We're excited to announce that runtime version 4.82.5 stable has been released.

Version 4.82 includes support for controlling apps via voice commands, as well as new map feature updates to display markers. Version 4.82.5 includes additional minor fixes.

You can use this version of the runtime by selecting it from the list of stable runtime versions under App Settings/Runtime Version in OXIDE.

4.82.5

Fixed:

• A bug that resulted in a "this is undefined" error when performing an action via an on-change function.
• An issue where a HTML component's height was no longer automatically calculated when no height was specified. This resulted in a scrollbar appearing in most HTML components.

4.82.4

Fixed:

• The context menu will now correctly show indicators when defined in the app.xml.
• The language selector is again legible in dark mode.

• South African ID number validation is now fixed for 29 February birth dates.

4.82.3

Improved:

• When an object-table resizes, an embedded button-group now changes to collapsed mode.

Fixed:

• Issues related to the size and fit of object-table controls on smaller screens.

4.82.2

Fixed:

• Issues related to view-state that were caused by rapidly triggering back on device back buttons.

4.82.1

Added:

• Realwear® HMT voice control support using the new journey.voice API. Please read the docs for more info.
• capture-coordinates has been updated, and we've added a new component called display-coordinates. Both can display markers on a map (statically define, or defined using DB objects), including tooltips and more. Please read the documentation for display-coordinates and capture-coordinates to learn more.
• Both the runtime and container versions are now reported and returned in the Sessions API. You can also access them using journey.runtime.version and journey.container.version.

Improved:

• The Update and Later buttons for app update notifications have been swapped around to follow usability best practices.