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.
We're happy to announce that 21.2.1 of the JourneyApps Container has been released.
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.
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 March 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.
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.
1. Deprecation: 15 February 2021
2. Removing support to manage developer access: 15 February 2021
3. App editing capability removal: 15 March 2021
4. Complete removal: Latest 1 December 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
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.
Your app needs to be integrated with Github, or use our new OXIDE-compatible JourneyApps revisions system.
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.
Unfortunately, these dates are final. Please speak to us about specific blockers that prevent you from adopting OXIDE by the above dates.
We have APIs that allow you to deploy your app if it is OXIDE-compatible. Contact us for more information.
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.
All input components with on-change will now report oldValue and newValue if specified as parameters, e.g.
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.
Loading performance on web.
We are excited that v4.77 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.
We're excited to release that you can now quickly configure CloudCode to run on a schedule with only a few clicks:
For more granular control you can still configure the schedule using a CRON string in Advanced scheduling mode.
We'd like to remind all developers that request rate limits to our backend APIs will be enabled on 1 February 2021.
Please refer to our previous notice for an explanation of how our rate limits work, and what you can do to handle rate limits in your app.
Please contact JourneyApps Support for questions, raising limits, or extensions.