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.
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:
The fourth workflow enhancement is the addition of a new workflow for approval of modifying security tasks. As with the security roles workflow there is an audit retained so that any changes need to be approved before they take effect:
This workflow type works well with amended tasks needing to be approved before any of the changes take effect.
The third workflow enhancement is the addition of a workflow approval for the modification of security roles. This means that you can amend a security role, but it doesn;t take effect until after the changes have been approved. This is accomplished by holding the changes in an audit table until approved.
The workflow process is maintained in the same way as any other workflow process:
This workflow process works well; I tested by amending a security role and the user it was assigned to could not see any of the tasks added to the role until after the changes had been approved.
The second workflow enhancement is the addition of a user security workflow type. With this workflow, any change to a user’s security needs to be approved before it becomes active. There is an audit of the changes held, so that the users current security access is not impacted by the changes, until after they are approved. The workflow is created and maintained in the same way as any other workflow:
I did some testing and this workflow worked well. I was able to update the roles for a user and not have them take effect until approved. The fact the user workflow doesn’t work is, I believe, irrelevant as tghis is the workflow which will control what the user can do in Dynamics GP.
The first of the workflow enhancements is Workflow approval for the adding of new or amending of existing users. The workflow process is created in the same way as existing workflows:
I created and tested this workflow type and cannot get it to have any effect. Whether I create a new user or amend an existing one, the user account is fully usdable without any approval being done, even when the user shows that it is pending approval.
A Happy new Year to everyone in the Microsoft Dynamics GP and ClassicPress communities and to anyone else reading this.
Following on from my Christmas music video, here is Dougie MacLean, OBE, a Scottish singer-songwriter, composer, multi-instrumentalist and record producer with the traditional Scottish song Auld Lang Syne:
The seventh, and last, financial enhancement is the display of the check or card number in the Apply Sales Document window (Sales area page » Transactions » Apply Sales Document) which was was entered on the payment at the time of entry:
The addition of the field has meant a little shuffling of existing fields on the window, but the addition of this field improves visibility and allow users to be sure they are applying the correct payment.
In yesterday’s article, I posted a script which can be used to download and delete files from a folder on an FTP site. When I tested it on one computer it worked fine, but on another it failed as the running of PowerShell is restricted. To avoid this error the PowerShell script can be saved to a file with a ps1 extension and then executed using the following (replace the highlighted section with your filename):