ERP-RS01-5.10.0.2

Από

Entersoft Business Suite®

New features and extensions

Brief description of contents

Horizontal Functionality

  • Email delivery
  • Other improvements

Various Improvements

Horizontal functionality

Email delivery

A number of improvements and corrections have been made in Email deliveries due to changes in the authentication method. In detail:

  • The process of attachment creation was improved in all delivery methods.
  • Gmail (Client): Fixed a problem that would occur upon loading the Client Info file declared in the communication profile. If the file path was relative, it would fail to load without an error message.
  • Gmail (Server)
    • Fixed a problem that would occur upon loading the Client Info file declared in the communication profile. If the file path was relative, it would fail to load without an error message.
    • if a "delivery user" is declared in the communication profile, then this user is used. Otherwise the email sender (from recipient) is used.
    • Fixed a problem occurring when mass sending emails, where only the user of the first in order email would be impersonate
  • Fixed several points that would display "case by case" error messages. One of these concerns the use of a reply-to address when sending emails via Office 365.
  • Fixed the display of erroneous messages. The messages were slightly mixed, resulting in "failed to send message" messages appearing as "failed to create attachment."
  • Improved the display of email information and delivery settings in error messages.
  • Added error messages that were missing in email delivery via Outlook.
  • SMTP v2: If a network authentication was declared, the default network credentials would not be used. As a result, the authentication and relay were not properly performed.
  • SMTP v3:
    • PLAIN and LOGIN authentication mechanisms are now supported. These are automatically activated when a basic authentication method is specified.
    • Fixed an error that occurred upon connection to SMTP when SSL TLS encryption was specified. As a result, the server would not return authentication mechanisms.
    • The SMTP protocol logger is now supported, which allows you to see all communications between EBS and SMTP. The logs are created in the ESNoSync\SMTPLogs folder, as long as you add and activate the following experimental features. You must turn it off if when its not needed.

Experimental feature

<Feature id="smtp-logging-enabled">

<Title>Enable SMTP logging</Title>

<Description>It enables the SMTP protocol logger for the v3 adapter only.</Description>

<Options>

<Option id="true">

<value>true</value>

</Option>

<Option id="false">

<value>false</value>

</Option>

</Options>

<Value>true</Value>

</Feature>

  • Delivery via CRM
    • If the delivery method is not supported, an error message is displayed.
    • Delivery methods SMTP v3, Office 365, and Gmail are now supported
  • Email delivery to automations
  • New entity actions were added for delivery via SMTP v3, Office 365, and Gmail
  • SMTP v2 | SMTP v3
    • Added an experimental feature that allows you to bypass the server certificate check for test purposes

Experimental feature

<Feature id="smtp-disable-server-certificate-validation">

<Title>Disable SMTP server certificate validation</Title>

<Description>

<![CDATA[

WARNING: FOR TEST PURPOSES ONLY !!!

Enabling this feature will skip the validation of the server's certificate.

Any expired, revoked or self-signed certificates will be considered valid.

Use this feature only if you're suspicious that a certificate problem exists

and you need a proof that the emails are sent correctly.

]]>

</Description>

<Options>

<Option id="true">

<value>true</value>

</Option>

<Option id="false">

<value>false</value>

</Option>

</Options>

<Value>false</Value>

</Feature>

Other improvements

  1. It is now possible to translate the entry values of Zoom tables. Initially, the translation tool was able to define that such a table needs translation and then, through EBS, it was made possible to translate its entries.
  2. Visual improvements were made to the export of the view results in excel. In detail:
  • Hierarchical display (where supported) - The hierarchical - children fields are displayed in blue in the header
  • Set lines display - Sets lines that concern a) groupings b) the entity total are now displayed in gray
  • Groupings display - The grouping columns now appear in blue

Miscellaneous improvements

  • A change was implemented so that the document lines, and in case the item is monitored with dimensions (color, size, etc.), the dimensions are displayed in the order specified in the SEQ.NO field of the item dimension chart. The feature was already available on the F12 of the line and is now available in the drop down list on the document lines. Company parameter “Items/Bar-codes: Dimension chart field to be used in sorting Sizes / Colors in F12” must have the SEQ.NO as value.
  • The Inactive field for the selected Colors was added to the color item dimension charts
  • The “Periodic VAT Statement - Codes” table was updated to add new entries and change descriptions to existing ones.
  • The alternative document field has been added to the transitions display. It can now be directly visible to users, especially in cases of sales documents, where communication with the supplier regarding the documents is based on the alternative code, instead of the document code provided by EBS.
  • Improved the process of adding entries to a Price list, where an error would occur if Item dimension 1 was not populated. The error was not logical, since the necessary condition for adding lines in the price list is to have either an Item or a Pricing group.
  • It is now possible to add and save related entries in the vouchers.
  • In the “Not counted items (with and without dimensions)” view, the Item designation criterion was added, with default value: All. The criterion was added so set items can be de-selected when needed.
  • It’s not anymore possible to change the date of a note payment document to a date prior to its collection. This check was considered necessary, since as long as it was allowed it created a problem in the note status.


PDF Version