Smart-Send
DXC Smart Business Form Email Manager - Release notes
DXC Smart Business Form Email Manager - Release notes
This document describes the features that are either new or changed in the release version mentioned.
DXC Smart Business Form Email Manager 10.0.34 runs on the following Microsoft releases
| Base | Version | Release |
|---|---|---|
| Microsoft Dynamics 365 application | 10.0.34 | What’s new or changed in Dynamics 365 application version 10.0.34 |
| Microsoft Dynamics 365 application | 10.0.35 | What’s new or changed in Dynamics 365 application version 10.0.35 |
| Microsoft Dynamics 365 application | 10.0.36 | What’s new or changed in Dynamics 365 application version 10.0.36 |
| Microsoft Dynamics 365 application | 10.0.37 | What’s new or changed in Dynamics 365 application version 10.0.37 |
| Microsoft Dynamics 365 application | 10.0.38 | What’s new or changed in Dynamics 365 application version 10.0.38 |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 12885 | Sales agreement - Confirmation issues error TTSBEGIN/TTSCOMMIT | When posting a Confirmation on Sales agreement form and you set print to Yes, the “TTSBEGIN/TTSCOMMIT” error will no longer be displayed. |
| 13553 | Final recipient missing semicolon in email address | When using the “Both” Selection under recipient for purchase order confirmations the final recipient would not have the semi colon prior to the email address. With this correction all email recipients are formatted correctly, and emails are delivered as per standard behavior. |
| 13707 | Error on customer payment journal when processing Smart Send Email | When making multiple payments to a single Customer account in the customer payment journal only the first line will process the correct attachment. This has now been corrected and each individual line will send to the related Smart Send contacts with the correct attachment. |
| 14831 | Centralized payment only utilized set up from creation legal entity | When utilizing the Centralized Payment Functionality for Vendor Payment Journals Smart Send would utilize set up from the current legal entity. This has been updated and centralized payment now can utilize Smart Send templates from multiple legal entities when making centralized vendor payments. |
| 13707 | Smart Send does not recognize difference between free text invoice and customer invoice on Invoice Journal | When issuing a Free Text Invoice utilizing the Tax Invoice Journal (Accounts receivable>Enquiries and reports> Invoices >Invoice Journal) a “Report is not setup for Smart Send” Error would appear if the Legal entity did not have a Customer Invoice report set as well. This has been corrected and both Free text and Customer Invoice can be issued with independent templates. |
| 16073 | The BankPaymAdviceVendController class has become obsolete by Microsoft in version 10.0.37 and mandatory in 10.0.34 | Smart Send now will only support BankPaymAdviceVendController V2. Activate “Enable batch processing for bank payment advice reports” via Feature management if not auto enabled. This feature lets you use batch processing for both the customer and vendor bank payment advice reports. To use this feature, you must use BankPaymAdviceVendV2 and BankPaymAdviceCustV2 bank payment advice, and set them up as the customer and vendor report formats in print management. |
| Number | Name | Description |
|---|---|---|
| 16329 | GER payment advice - Duplicated lines and wrong recipient | When payment journal contains two lines (two different vendors), when both are lines selected the ‘Smart send payment advice’ functionality created an email to only the one vendor and it sent the other vendor’s payment advice to the wrong vendor. The settled invoices lines were also duplicated. This previously applied to customer and vendor payments and has been corrected. |
New features
| Number | Name | Description |
|---|---|---|
| 9233 | Additional fields in organizational email template data entity | Additional fields have now been added to the Organization email template Data Entity to incorporate the To, CC and BCC fields from the Smart Send email templates. |
| 9483 | Company logo placeholder for email template | You can now incorporate your company logo into your Smart Send email template. Note you must use Tag <img src="data:image/bmp;base64,%CompanyLogo%" alt="logo"/> to render image correctly. |
| 9735 | rich html editor | New ability to use HTML editor when building content for Smart Send email templates. |
| 12731 | Additional placeholders | 2 additional placeholders have been added. For Purchase order confirmation (PurchTable.PurchName) %VendorName% For Sales order Confirmation (SalesTable.SalesName) %CustomerName% |
| 14174 | key vault is now in drop down menu | key vault has now been updated to a drop-down menu. Azure Blob storage will be deprecated in the future. Date to be announced. |
| 14961 | change to option “PRINTER DESTINATION IF NO SMART SEND RECIPIENT FOUND” | When no Smart send recipient has been selected you now have the option to set documents to not print via the renamed menu option “PRINTER DESTINATION IF NO SMART SEND RECIPIENT FOUND”. This setting works in conjunction with the Save to Azure Storage options and Alternate Email in email parameters. When “do not print” is enabled documents are not routed if no recipient is found. By Default, this field is set with no option (Blank) which follows standard Smart Send logic and allows for both Azure storage or Alternate Email delivery. “Do not print” if enabled will override alternate email and azure storage options and document will not be routed. Only occurs if no smart send recipient found. |
| Number | Name | Description |
|---|---|---|
| 6735 | Support the use of Rich HTML editor | HTML editor is included for editing the body of the organisational email template. To start editing select Email Message from the top menu to open the template then switch the “use HTML editor” toggle button to yes to allows editing fucntionality. |
From 10.0.34.20231026 Smart Send can be enabled via Feature management Enable the following feature in D365 Feature management:
If above feature is not visible, press Check for updates to refresh the feature management list.
| Number | Name | Description |
|---|---|---|
| 12650 | Payment Advice not issued when multiple payments for same vendor | When there are multiple payments for a single vendor within the one journal previously only the first record would issue the payment advice document when using the Smart Send button, this has now been corrected. |
| Number | Functionality | Reason |
|---|---|---|
| N/A | License manager | License manager version 10.8.32.10171 Enhanced Licensing capabilities to assist with licensing support and scaling. Note: Required to upgrade all installed DXC products to at least the following versions: • EDI 10.0.29.202305053 • Finance utilities 10.0.29.202305051 • SmartSend 10.0.29.202304142 • Core extensions 10.0.29.202304142 • DocuSign 10.0.29.202304211 • Item creation 10.0.29.202304211 • PLM 10.0.29.202304211 • Forex 10.0.29.202305101  |
| Number | Functionality | Reason |
|---|---|---|
| 9929 | Support for Electronic Report formats | Visibility of Display electronic reports within the Smart Send email parameters form New print destination Smart Send for use with electronic reporting destinations and electronic reporting named destinations. Support for electronic reports generated through print management or using the Smart Send button. Supports saving of the business document to Azure blob storage. Full functionality of placeholder tokens in line with SSRS formated reports. |
| Number | Functionality | Reason |
|---|---|---|
| 11641 | Smart Send button sends the default report format | When using the Smart Send button, the email parameter configuration that is used should be the Default record. The email parameter configuration does not use the default, it uses the report format defined in print management |
| Number | Functionality | Reason |
|---|---|---|
| 11122 | Vendor payment advice report blank when run with Smart Send button | Report data is not included when the vendor payment advice report is run using the Smart Send payment advice button present on the vendor payment journal. |
| Number | Functionality | Reason |
|---|---|---|
| 10231 | Support Vendor Tax Invoice report formats | The report type Vendor Invoice and the standard report formats VendInvoiceDocument.Report and VendInvoiceDocumentModern.Report are now available in the Smart Send configuration form ECL_AutoPrintReportMgmt |
| 10288 | Legal entity name placeholder token | The token placeholder %CompanyName% can now be used to return the name of the legal entity from which the report was generated. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 12650 | Payment Advice not issued when multiple payments for same vendor | When there are multiple payments for a single vendor within the one journal previously only the first record would issue the payment advice document when using the Smart Send button, this has now been corrected. |
| Number | Name | Description |
|---|---|---|
| 10230 | Sales invoice not dispatched using the Smart Send button | Resolution for error message received when selecting the Smart Send button on a customer tax invoice. |
| Number | Functionality | Reason |
|---|---|---|
| 9654 | Override purpose | Override configurations for print management are currently supported by Smart Send when using different report versions. Where the same report format is used, the email purpose used to identify the email recipient is always sourced from the default report. Print management configuration for an override condition now allows for an override purpose to be defined against the Smart Send destination. If this is entered the override purpose will supersede the purpose configured under email parameters. |
| 9713 | Key vault added for Blob storage connection string | As an alternative to the blob connection string field, users can now select to use a key vault value. This is configured on a record level under Azure blob storage setup. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 9797 | Intercompany payment advice | Smart Send did not support BankPaymAdviceVendV2.Report for the processing of a payment advice for one legal entity from within another legal entity. Support for this has been added, allowing the email address to be sourced from the account in the posting company |
| 9866 | Custom versions of the updated payment advice report were not recognised by the Smart send button | The Smart Send payment advice button processes the default smart send configuration outside of print management. Customized versions based of BankPaymAdviceVendV2.Report were not processed. This button now supports all SSRS payment advice reports. |
| 9947 | Sales return | For a sales return report to send successfully the user needed to have previously run the report, creating usage data. Without this the report would error. The report will now run without the cached data. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 9266 | Email fallback not triggered | In the absence of an email with the appropriate purpose, the fall back options of an alternative email and/or saving to blob storage are available to be configured in email parameters. These were not being triggered. The absence of an email will still provide a warning, however the configured fallback option will now also be actioned. |
| Number | Functionality | Reason |
|---|---|---|
| 5145 | Payment Advice (Vend/Cust) - V2 introduced | In D365 10.0.13 Microsoft introduced Payment advice V2. Payment advice V2 is now supported when using the Smart Send payment advice button within the vendor payment and customer payment journals. |
| 9506 | Payment Advice V2 Report – Payment history | Payment advice V2 is now supported when using the Smart Send payment advice button within the payment history form, accessible from the vendor. |
Deprecation
| Number | Name | Reason |
|---|---|---|
| 9161 | Feature Removal: Email Destination fields removed from print destinations email tab | Fields on the email tab of the print destinations page used in Email Destination Defaults remained following the deprecation of the feature. The field Email ID and File name have now been removed. Email destination defaults feature has been removed. This feature provided the ability to specify an email template and filename using placeholder tokens for a business form has now been removed, and instead, Smart Send Override email ID (Template) and Override file name features, can be used in print management conditions. Email destination defaults feature had been marked as deprecated since 19 March 2020. |
| Number | Functionality | Reason |
|---|---|---|
| 6019 | Smart Send Purchase Order- Add Requestor’s/ Orderer’s email to Email Template Tokens | The email template tokens list has been updated for the Purchase Order report being sent via Smart send. Four new tokens have been added which now include the Requestor’s and Orderer’s name and email address. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 5999 | ‘Test azure blob storage connection’ not working correctly | The ‘Test azure blob storage connection’ button on the Email parameters>Smart Send form was not working correctly. It used to display ‘Test connection successful’ in most scenarios of the Blob connection string, even when an incorrect string was passed. This has now been resolved and appropriate errors will be displayed if the string is incorrect. |
| 8785 | Report title not visible | The document title for customer invoice was not set and displayed as blank when the report was sent via Smart Send. This has now been fixed. |
Deprecation
| Number | Name | Reason |
|---|---|---|
| 6041 | Feature Removal: Email Destination Defaults | Email destination defaults feature has been removed. This feature provided the ability to specify an email template and filename using placeholder tokens for a business form has now been removed, and instead, Smart Send Override email ID (Template) and Override file name features, can be used in print management conditions. Email destination defaults feature had been marked as deprecated since 19 March 2020. |
To align with MS best practice and to protect our IP the following applies to the release process.
Depending on the installation history follow one of these guides to install the new release.
If you’re installing the new release in an installation that already has a previous version of the product installed and you’re not using it for debugging or extension. We recommend that you;
If you’re using our model source code for extension or debugging and would like to continue using it, please do the following to apply the new release with the source code.
If you don’t follow these instructions and continue building your installation deployable package using the license model source code, the installation will continue using the same license model as before applying the release.