If when Microsoft Dynamics GP is implemented, you know that email documents is going to be used, the functionality can be enabled alongside the rest of the system, but for clients who were not, for example, using Purchase Order Processing from the start it needs to be switched on after the fact.
When first discussing it with the client, my initial thoughts were to use a macro to enable merged from the supplier list to step through the vendors/creditors and enable that way.
However, just before I started to explain this, I remembered a feature tucked away on the Vendors/Creditors navigation list. If you click the button, in the Modify section of the area pane, of two chevrons pointing to the right you get a pop-up menu containing an Email Settings option:
Continue reading “Enabling Email for All Master Records”
Microsoft Dynamics GP 2018 RTM has now been released and I have been taking a Hands On look at the installation and configuration of the new version.
I am now going to take a hands on look at the new and enhanced features introduced in Microsoft Dynamics GP. Rather than do this as a continuation of the Hands On series I wrote in December, as originally intended, I am going to split it out into a separate hands On With the features post. The series index is for this new features series, can be found here.
The eighth feature if the day was Workflow Reminder Emails. This feature allows the Workflow manager to define a time after which a reminder email should be sent to the approver.
The Workflow Maintenance window ( ) has has the Workflow Step pane amended to have a Reminder field which allows a number and type of duration to be defined; this field is linked to the Time Limit field:
Continue reading “Hands On With MDGP 2018 RTM New Features: New Workflow Functionality – Reminder Emails”
I had an issue reported with purchase requisitions the other day. I logged on and did a little testing and then, a short wile later, got an email from the client asking about some workflow approval emails some managers had received.
The email to the approvers did not contain the word “test” anywhere in either the subject or body. This lead to me having a horrible moment when I thought I might have done my testing on live; I was able to confirm quickly that I had not.
After this I decided I had better knock a quick script together which the client could incorporate into their live to test copy.
The script is more engineered than it might otherwise need to be as I have included code to only do the update when it is running against a test company (flagged with <TEST> at the end of the Company Name) and where the email subject isn’t already prefixed with the word TEST:
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
EmailMessageSubject = LEFT('TEST: ' + CAST(['Email Messages'].EmailMessageSubject AS CHAR(150)), 150)
SY04901 AS ['Email Messages']
DYNAMICS..SY01500 AS ['Company Master']
['Company Master'].INTERID = DB_NAME()
['Company Master'].CMPNYNAM LIKE '%<TEST>'
LEFT(['Email Messages'].EmailMessageSubject, 4) <> 'TEST'
As always, before running a script against a database, make sure you understand the scirpt and have a good backup of the database.
I thought I had posted about this a littler while ago as part of my Customising Dynamics GP Workflow Emails series, but it seems I missed it. The reason it came back to mind, was when I was onsite with a client doing some training on Workflow, they asked if it was possible to add a company logo to a Workflow task assignment email.
It is. In fact, you can add any image you want to a workflow email. In this example, though, I am going to stick with using a company logo.
In the Message Setup ( ) window load the message you want to amend and simply add the HTML image tag:
Continue reading “Customising Dynamics GP Workflow Emails: Adding An Image”
This post is part of the series I am doing on the Dynamics GP Tech Conference 2017.
There have been new features in other areas, which I will come back to, but Workflow is sort of “my thing”, so I’m going to mention the new features which are being added to Workflow 4.0 (I apparently missed the boat somewhere on the name change to Workflow 3.0?).
The coming new features are:
- Reminder emails for Workflow – this is a feature which has been requested of ym by a couple of clients recently, so nice that I’ll be able to go back and tell them it will be in the next version.
- Copy Workflow Step – nice to see this one added as it was one of my suggestions on MS Connect.
- Reporting for Workflow – I’m not sure what is coming in this, but it would be nice to have some default reports showing the history of documents as they passed through the Workflow.
- Payables Transaction Workflow – additional fields
- PO Workflow Messages – additional fields – there are never enough fields available for the Workflow, so nice to know more will be available by default.
- Add EFT/Bank Details to Vendor Approval Workflow – if this one is as it sounds, that will be fantastic as so many clients want this functionality. I think it only took so long as EFT isn’t anywhere near as big in the US as it is in the UK.
- GL Account Workflow Approval – I have a couple of clients who can ditch some customisations with this one. And a few more who will be delighted so see this added.
- Purchase Receiving Workflow – I have a few customers waiting for this one to be introduced.
- Purchase Enter/Match Invoice Workflow – as above, a few clients are waiting for this one.
I know we can’t have everything we want, and the above are good additions to Workflow, but I still want more!
One point I forgot to make when writing the other posts of this series, which was perhaps obvious to all, is that the formatting I have shown in this series, applies not only to the workflow emails, but also to the standard emails sent by Microsoft Dynamics GP. This would include the emails sent to vendors with a PO or remittance or to a customer with an invoice or statement.
While I haven’t gone much beyond what I have covered in this series, it should be possible to do a lot more in formatting terms to the emails. One thing I have thought of, but not tried yet, is wrapping a table around the fields at the top of the table to align them into a neat layout.
A couple of things I have tried, and which did not work, are:
- Adding styles to the approval links – any style I added to these links, such as padding or line-height, was ignored.
- Adding a div around an image and setting float: left – the image did not float in Outlook.
The final point I would make around formatting the emails, is that just because you can, doesn’t mean you should. If you do format the emails, keep it simple.
I’ve been showing how to format the Microsoft Dynamics GP Workflow notification emails in this series. I’ve covered some formatting to change the font size or weight in the previous posts, but I want to show how you can apply other html tags to a Workflow email.
The example below shows how we could contruct a hyperlink to a web page using the Vendor ID field to make the link unique:
Continue reading “Customising Dynamics GP Workflow Emails: Creating a Hyperlink”
In this series of posts, I am showing how the email notifications sent by Microsoft Dynamics GP Workflow can be formatted using HTML text formatting tags. In this post, I’m going to show how we can appyl formats to mutliple elements within the email by building on the embedded stylesheets I covered in the last post.
In Message Setup (title to the stylesheet at the top of the message body (this time setting the font-weight to 900, which is a bold font), and then wrapped all of the field headers in span tags with a class of title:
), I added a new span class of
Continue reading “Customising Dynamics GP Workflow Emails: Extending Styles to Other Elements”
In this series of posts, I’m taking a look at the formatting of emails sent by the Microsoft Dynamics GP Workflow module. In the first post I showed how the font-size could be changed on the email, and in the second post how an embedded style sheet can be used to format the document line fields.
It is best practice not to use different methods of applying styles within a single page, or in this case email. So with both normal fields and the document line fields needing to be formatted, I revisited the email message and changed the original span tags to use a class and added the format of this to the embedded stylesheet:
Continue reading “Customising Dynamics GP Workflow Emails: Applying an Embedded Stylesheet”
As I mentioned in the series index, on a recent Workflow project I had a few users comment to me that the text on the emails was a little too small to read. My initial reaction was that it was not possible to change the font size. However, while driving a little later, I had a thought of how I could tackle this.
In the first post of this series, I covered increasing the font-size of the email by wrapping a span test formatting tag around the text, but I found when doing this with the task assignment email which had the Document Line Fields mail merge on it, the formatting didn;t work correctly.
On this email I wrapped the span tags around all of the message body:
Continue reading “Customising Dynamics GP Workflow Emails: Increasing the Font Size in the Document Line Fields”