Come join us on November 27-29, 2018 at the Gartner Application Strategies & Solutions Summit 2018 in Las Vegas, USA.

Skip to end of metadata
Go to start of metadata

The URL seems to be different

If you have any (hardcoded) link that points directly to a userview page (e.g. https://samplejoget.com/jw/web/userview/leaveApp/leaveUV//applicationInquiry) that is working in Joget Workflow v5. The same link will no longer work in v6. This is due to the upgrade of Spring framework in Joget Workflow v6.

There is double forward slash in the link. We will need to add a (userview key) value in between them (e.g. _ )

The new working link would be https://samplejoget.com/jw/web/userview/leaveApp/leaveUV/_/applicationInquiry with an extra underscore in it.

Custom CSS

If you have written any CSS before based on v5, you will need to check again to ensure a consistent look and feel across when upgraded to v6.

Check for Missing Plugin

If you have been using plugins from the marketplace, you may want to check if those custom plugins have been properly loaded into your new installation of Joget Workflow v6.

There are certain plugins that are first made available in the marketplace and have been incorporated into the official bundle of Joget Workflow v6.

These are the non-exhaustive list of plugins that are known:-

  • JDBC Load Binder
  • JDBC Store Binder
  • JDBC Form Options Binder
  • Form JSON POST Tool

Check for Plugins Compatibility

Plugins that have been working fine with Joget Workflow v5 are not always guaranteed to work with newer version. You should test it out by importing your plugins into the newer version and test them out.

Perform Cursory Test

We highly recommend that you spend some time to perform a cursory test on the Joget apps that you have created based on older versions. A quick test can quickly determine if your app is fully compatible with the new Joget Workflow v6. Be sure to check the server log also as it would generate error logs on possible missing/incompatible plugins.

  • No labels