What's new on JourneyApps

Release notes for JourneyApps features.

CloudCode
Runtime
Container
January 01, 2020

Welcome!

This is where we announce new releases on JourneyApps.

You can subscribe for updates by clicking the button on the top right.

For older release notes, please go here.

Runtime
May 17, 2021

Runtime 4.80 (latest stable)

We're excited to announce that 4.80 stable has been released. It includes a new multiple photo capture feature, significant updates to our capture-file and display-file components, and numerous other updates developers and app users will appreciate.

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.80.2

Fixed:

  • A regression with object-table where sorting columns with a show-if bound to a function would break on-state-change.
  • An issue when object-table displayed no results.

4.80.1

Fixed:

  • An issue with multiple photos' max photo limit calculation.

4.80.0

Added:

  • Developers can now allow app end users to take multiple successive photos to be taken with a single tap or click, saving time. Here's a link to the docs.
  • Developers now use the XML attributes align-content and fullwidth on UI components that work with media (i.e. display- and capture-photo, signature and file) to control their alignment and width.
  • App end users can now preview and view PDFs on display-file and capture-file components.
  • Developers can trigger that a PDF attachment is opened programmatically without using display-file using journey.files.viewFile(my_attachment) in the JS / TS.
  • Developers can access the metadata of a file bound to the capture-file component using the new JS component method called .getMetadata(). Along with that, we've also added other component methods to media components (i.e. display- and capture photo, signature and file) to open, close, delete or capture new media.
  • App users can use drag-and-drop to upload their files with the capture-file component.
  • Developers can control whether and how labels should be capitalized.

Improved:

  • The capture-file and display-file UI components have been updated to be more consistent with other new components.
  • The display-image component is also now more consistent with display-photo and other UI components.
  • The pinch, pan and zoom gestures for photo- and signature components have been improved.

Fixed:

  • An issue where object-table fullscreen mode would show an error.
  • An issue where a dynamic limit would cause object-table to show an error.
  • An issue where apps accessed through a browser were not able to download attachments.
Thanks for your feedback
Runtime
May 17, 2021

Runtime 4.79 (supported stable)

We're excited to announce that 4.79 stable has been released. 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.79.8

Fixed:

  • A regression with object-table where sorting columns with a show-if bound to a function would break on-state-change
  • An issue when object-table displayed no results.

4.79.7

Fixed:

  • An issue causing copy and paste to break after copying content from object-table version 3.

4.79.6

Improved:

  • We've added the oldValue and newValue parameters (similar to editable cells in object-table) to on-change for single-choice-dropdown.

4.79.5

Improved:

  • We've added the oldValue and newValue parameters (similar to editable cells in object-table) to on-change for object-dropdown.
  • The UI of single-choice-radio when a user hovers their cursor over it.

Fixed:

  • An issue that caused toggle with a null value to be validated incorrectly.
  • An issue with display values on text-input when disabled (i.e. disabled="true").

4.79.4

Fixed:

  • A regression where object-table filter dialogs were not applying number or date filters.

4.79.3

Fixed:

  • A regression with object-table where the enter/return key did not create new lines in edit-text cells.
  • An issue with object-table causing it to automatically scroll when users selected a filtered row.
  • A regression with toggle where null values would fail on validation.

4.79.2

Fixed:

  • A regression where date or datetime would always resolve to false when used in show-if and hide-if.

4.79.1

Fixed:

  • A regression with capture-file causing an error when uploading a document.

4.79.0

Added:

  • We've updated the info-table component to add support for icons, as well as text color and icon color for rows. Read more in the docs.
  • We've added an align-content attribute to various input-type components (e.g. capture-photo, date-input) as well as heading, info, button, and button-group.
  • We've added support for descending order in app indexes.
  • This version correctly ignores backend indexes that have been specified in the data model. Previous versions of the runtime may show errors in the console.
  • Added support for on-long-press on a dialog's button-group.

Improved:

  • When a user leaves their app, and another user signs into the same app, the app data will be synchronized faster than before.
  • Developers can specify that their app should ignore broadcasts (via the Broadcast API) when the app is in the background.

Fixed:

  • An issue with the date picker where its display year value would not update correctly when changing months.
  • An issue with object-table causing it to break when filtered column is hidden programmatically.
  • An issue where app indexes were not used for "field = ?", null queries.
  • An issue where actionSheet would be positioned incorrectly when triggered from a static list-item.
  • The touch area for radio buttons and checkboxes (e.g. single-choice-radio, multiple-choice-checklist) has been made smaller to only contain the button and adjacent text. Previously the touch area was the entire width of the containing view or column.

Thanks for your feedback
Container
May 12, 2021

Container 21.5.1

We're happy to announce that 21.5.1 of the JourneyApps Container has been released.

This version meets new requirements for containers uploaded to the iOS App Store.

Thanks for your feedback
Runtime
May 03, 2021

Runtime 4.78

We are excited to announce that 4.78 of the JourneyApps Runtime has been released. 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.78.7

Fixed:

  • An issue causing copy and paste to break after copying content from object-table version 3.

4.78.6

Fixed:

  • A regression where date or datetime would always resolve to false when used in show-if and hide-if.

4.78.5

Fixed:

  • An issue where an option in an actionSheet would sometimes be clicked automatically, causing users to unintentionally select an option.

4.78.4

Improved

  • The position of where an actionSheet pops up for an app user has been made more intuitive.

4.78.3

Fixed:

  • An issue in object-table v3 causing the table to break when specifying a limit dynamically.

4.78.2

Improved:

  • Developers can specify that their app should ignore broadcasts (via the Broadcast API) when the app is in the background.

Fixed:

  • An issue where actionSheet would be positioned incorrectly when triggered from a static list-item.

4.78.1

Added:

  • All input components with on-change will now report oldValue and newValue if specified as parameters, e.g.

on-change="$:handleChange(oldValue, newValue)"

Fixed:

  • An issue with the date picker's year not updating correctly when using keyboard shortcuts.

  • An issue where Object Table 3's typeahead did not correctly handle null values.

  • A regression where the hardware back buttons (Android) would break the app on Action sheets and Dialogs.

Improved:

  • Loading performance on web.

4.78.0

Added:

  • Support for opening TCP Socket connections from the app. You can read the docs for more information.

Improved:

  • We've implemented performance improvements for apps running on iOS, specifically focused on improving memory usage over time.
Thanks for your feedback
notice
April 15, 2021

Notice: We’re deprecating the App Editor in favor of OXIDE (updated)

Update (15 April 2021): The App Editor can no longer be used for editing apps. Please ensure that your app is migrated to be compatible with OXIDE, and use OXIDE to build and deploy your app.

After the successful launch of OXIDE in September 2020, we are deprecating the App Editor (build.journeyapps.com) and will be removing it from JourneyApps in 2021.

This notice describes the timeline for the removal of App Editor, guides you through the steps you may need to take if you are affected by the deprecation, and answers questions you may have.

What you can expect

As of 15 February 2021 JourneyApps will only provide support for critical issues in the App Editor. You will only be able to manage developer access using the Admin Portal. You will also no longer be able to create new apps in the App Editor.

As of 15 April 2021 we will be removing the capability to make and deploy changes to apps from the App Editor. After this date, the App Editor will only be able to migrate your app to be compatible with OXIDE, and cannot be used for building apps, or managing users.

No later than 1 December 2021, the App Editor will no longer be accessible.

How to migrate your app

To ensure that you can continue to make code changes to your app, you need to migrate your app to be compatible with OXIDE. To do this you a version 4 syntax app which is integrated with Github or our OXIDE revisions source control system:

1. Version 1 and version 3 syntax apps will need to be migrated to the version 4 syntax.

- You can do that by accessing the Version Management menu under App Settings and following the steps to migrate your app.

- There are some code changes required to ensure that the app works as intended with the version 4 syntax. Please see our guide.

2. Your apps need to be migrated to be compatible with OXIDE. Do this by going to the Admin Portal, and clicking Migrate.

Once you’ve migrated your app successfully, you can edit and deploy changes using OXIDE.

Summary of dates

1. Deprecation: 15 February 2021

2. Removing support to manage developer access: 15 February 2021

3. App editing capability removal: 15 April 2021

4. Complete removal: Latest 1 December 2021

Common questions

What happens to apps that have not been migrated by 15 April 2021?

You will no longer be able to edit or deploy your app, but it will still be accessible in the App Editor. App users will be able to use the app without any interruption, though you will not be able to deploy updates to them until the app is migrated. Please migrate your app by going to the Admin Portal, and clicking Migrate. You can find the Admin Portal by clicking on the OXIDE logo on the top left when in OXIDE

What happens to apps that have not been migrated by December 2021?

App users will no longer be able to use the app. We will place the source code of your app in cold storage. If you wish to reactivate the app and edit it in OXIDE, there will be a cost involved.

Do I need to use Github to be able to use OXIDE?

Your app needs to be integrated with Github, or use our new OXIDE-compatible JourneyApps revisions system.

What are the biggest changes for using OXIDE above the App Editor?

You can read more about OXIDE here. It is designed to be a more productive app editing IDE, saving you precious time during development, and giving you more control over your app editing environment. To get the most out of JourneyApps, you should use OXIDE.

I cannot use OXIDE by the date you have communicated. Can you extend the dates?

Unfortunately, these dates are final. Please speak to us about specific blockers that prevent you from adopting OXIDE by the above dates.

How do I deploy my OXIDE app programmatically?

We have APIs that allow you to deploy your app if it is OXIDE-compatible. Contact us for more information.

Thanks for your feedback
notice
March 23, 2021

Backend Data Browser URL updates

We’re updating our backend URL structure for the Data Browser from /app/{app_slug}/acc/{backend_deployment_id} to /databrowser/{backend_deployment_id}.

For example, /app/my-app-name/acc/605a2696d6276b6143d72eb1 will now be /databrowser/605a2696d6276b6143d72eb1.

When you open the legacy URL you will be redirected to the new URL format described above. If you have a browser tab open with the old Data Browser URL, please reload the page and check that the new URL is used before making any changes to your data.

Also note, that the backend API and mobile apps are not affected by these changes.

Thanks for your feedback
We are ⚡by Beamer