I migrated to ClassicPress last year and created ClassicPress versions of all of my plugins. This wasn;t just a case of creating an alternate versions, but extensively rewriting them in order to both add new functionality and to improve their security.
I've recently made changes to them all again to further improve them. If you use any of my plugins list on my Development site, you should download and install the latest version.
ClassicPress v2 is to include a Plugin Directory which is meant to be available in the second-half of 2020 which will mean automatic updates will then be available.
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features - Workflow Enhancements series where I am going hands on with the workflow enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The fifth workflow enhancement is not a new workflow type, but the long overdue addition of the ability to import and export a workflow process. With this new enhancement, you can now export a workflow to a json file which you can use to import into an entirely separate Microsoft Dynamics GP implementation.
This means that you can copy a workflow from a development server into a live environment or, in the case of someone like myself who works for a partner, from our development system to a client's system.
When you import a workflow process from a json file, you must specify the name of the new workflow (it defaults the name from the selected json file, but you can override the default name).
To export a workflow process, open the workflow to export and click Export/Import and then click Export:
Continue reading "Hands On with Microsoft Dynamics GP October 2019 Release New Features – Workflow Enhancements: Export and import workflows"