RO | EN

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 when it's not needed anymore.
  Experimental 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 

Other improvements

• 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.

• 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.
  
  

Specific improvements for the Romanian version

e-Transport enhanced with accompanying document number

In the reporting data for e-Transport there is an area called Transport documents where you can choose the type of document with which you are delivering the goods (notice, CMR, invoice, etc.), together with the document’s number and issue date.

A more robust TRN verification mechanism

We have introduced a new mechanism for verifying the TRN of a trading partner by using the TRN verification service provided by the SBS’s API, as opposed to the old one which called directly the ANAF' static web service, and which in some cases was not reliable enough. In addition, in this way we will have four more query parameters: the start and end dates of the VAT purpose as well as the start and end dates for the VAT on receipt. 

INNOSHIP integration – a platform for integrating courier services

This courier services integration platform was added to the couriers available in the application. Now you can have one INNOSHIP account that allows the shipment with any courier operating on the Romanian and European markets. The INNOSHIP API is also integrated with the WMS application.

Instrucțiuni privind integrarea curierilor, inclusiv referitoare la Innoship, gasiți aici.

EBS-RO documentation and translations improvements

For more info, browse this site.

We constantly update it with instructions and documentation in Romanian language.

We also constantly update and correct all translation or localization errors, so that the application will better serve the Romanian users. 

Documents

• In the "documents" tab, in the import folder, selecting "+" to add a new document while the form was already open, did not display the document in front of the user screen, but in the background. An appropriate correction has been made, so that it appears in the foreground and the user can proceed with creating the document.

• Fixed an incorrect update of the Information line field, that would occur when a consumable item would be found in the BOM of the produced item, which is also produced with a BOM which has no analysis.

• Fixed a bug where an OSS intra-community sales document, with article 47a, 47b & 47c could not be sent via a provider.

• Resolved an error in the conversion of trade documents (e.g. AEV Delivery Note) that have resulted from a transit document (e.g. TRM Delivery Note).

• Fixed the message that appears when creating a document, concerning an overdue amount under Credit Policy. This message (a) takes into account the Minimum overdue amount of the Credit Policy and (b) does not take into account the amount of the invoice entered at that time, since it is not (yet) considered as an overdue amount.
  
  
  

Processes

• Resolved a problem that would occur when transferring projects from one company to others, when that was carried out through actions in the project form. The same process would succeed in the projects list.

• Resolved an error that would occur when closing a fiscal year in the warehouse system, when the item monitored color & size with an alternative measurement unit as a service unit and said service unit was not fixed.

• Resolved an issue in a specific installation where, when saving the data type, e.g. an X export/import scenario, the system first uploads the new files with folder name _X, then it erases the old X and renames the folder from _X to X.

• Resolved an error in summary download, that would cause the process to run through time schedulers with the Advanced option.
  
  

MRPII

• Resolved an error that would occur when activating a plan through the scheduler. 

POS

• Resolved a problem that would occur when canceling a POS transaction that was successfully executed by redeeming points, that resulted in only one line of the two generated due to loyalties being deleted.
  
  

Automation – Business Rules

• Resolved a problem when reporting an error in VB expression: the line number to which the error refers would not display.
  
  

Miscellaneous

• Resolved an error that would occur when executing a budget report cube.

• Corrected the wrong translation of the “FocusLess” property. The problem occurred when a user would log in with Romanian in the item, customer, supplier, fixed asset, person & trade document.

• Fixed an incorrect item display that would appear more than once in a search made in the multiple code field. The issue would occur in case the supplier code of the item had the same value with the value of field “Item codification” in the Alternative suppliers detail of tab: Item organization.

Bug fixes specific to the Romanian version

• Fixed an error occurring when opening the automation files "Create Shipment" regarding sending vouchers to a Transportation Company. The error was appearing exclusively in the automations for couriers SAMEDAY and INNOSHIP.

• Fixed an error regarding the lowest value of VAT in calculating the reverse VAT on the automation CreateVATProtocolforReverseTaxation.

• Fixed some errors regarding the parametrization of the automatic creation of a new fiscal year on the Romanian version.

Related cases:

PS-106472, PS-108950, ΥΠΘ_SUP-191030, PS-108855, PS-26701, PS-108808, PS-108846, ΥΠΘ_SUP-202669, ΥΠΘ_SUP-203772, PS-104224, PS-108935, PS-109415, PS-108928, PS-109491, PS-100959, PS-107307, PS-108886, ΥΠΘ-SUP- 203178, PS-67688, PS-106136, ΥΠΘ_SUP-190902, #1096874, #1090458, #1091457, #1084002 PS-94427.