EXP-RO01-4.0.40.1
Entersoft Business Suite® | Entersoft CRM®
Περιεχόμενα
New Features & Functionality (Outline)
This document aims to report the new features and extensions of Expert Version 4.0.40.1. First, the newly added functionality and features are briefly listed and, then, a detailed presentation follows. User guidelines and examples are provided where necessary. Entersoft ERP
- Full monitoring of serial number to third parties
- Outlook Add in upgrade and Office 2016 support
Entersoft ERP
Inventory
Serial Number to Third Parties
The sub system of Serial Numbers has been expanded in order to support the detailed monitoring of the position, for those sent to third parties.
Data management screen for Serial Number
A new property has been added to Serial Number elements: Third parties Warehouse (to third parties premises).
In this case, the fields Position and address updated (as it was so far) with company’s branch code and third parties warehouse but moreover, the new fields 3 party location and Third parties Address has been activated with trade account’s relevant code and his branch where the serial number pointed out.
The abovementioned fields should be updated ALWAYS by the relevant document types and not with direct data entry to the relevant screen from the user. This is the only way for the correct maintenance of that data, while the automated recall of the previous position in case of deletion or canceling transaction is feasible.
The out of the box implementation take care of the abovementioned elements and not further actions required in order to start the detailed monitoring of serial numbers.
- New fields in the documents
The new field “Trade Account’s Address” has been added to analysis entries (ESMMAnalysisEntry). This field along with the existent field Trade Account, utilized for Serial Number’s position update for those sent to Third Parties.
The new field “Trade Account’s Address” has been added to the available fields of the item line.
The new field Warehouse has been added to documents adjustments. This field replaces the usage of the field Default W/H of the series (used for different internal transfer scenarios to Third Party e.g. ATR, DRD, etc.). The upgrade to current version, take cares for correct update and activation of the new field.
- Document Controls at Transfers
After having activated in item control policy the option “check S/N position” for documents adjustment with position type ‘Trade Account’, the check takes place not only for the position at Header’s W/H (Third Party) but also to the specific Trade Account – address that filed out at the position. In the same way operates serial number’s investigation in order mistakes to be avoided.
- Print Outs
The following views have been modified in order to exploit the NEW POSITION TYPE and to appear the specific position to Third Parties (does that mean the “third” trade account):
Serial Numbers
Serial Number Log
Serial Numbers per item
Serial Number Directory
Ability for grouping by “Trade Account Branch” provided in report Serial Number Status in 3rd Part W/H
Other Improvements
- The main view of Inventory Items have been improved.Grouping by item type provided, along with additional columns with accounting info and dimension monitoring (color, size, etc.) elements.
- The field property profiles 3-CheckThirdWH and ES-3-THIRDWH utilized at transitions related with Third Parties rectified in order to take into account document header’s W/H instead of series W/H. You can import them from \EsMasterConfig.
Financials
Liquidity Account’s connection with Trade Account
The ability to fill in the relevant trade account have been provided at liquidity’ account’s elements independently if it is relevant with card or not. This information could be utilized for inflows forecasts related with “rendering to Third party” or “Transfer of claim to Third party” or in general to different scenarios related with cash flows. Because of this new functionality the data management screen of liquidity account has been modified properly.
Moreover, the code and the name of the relevant trade account are available in the grid of payment settlement as columns in order to support such kind of implementations providing to the user the ability of visible confirmation of the correct liquidity account.
Exchange Differences
The process of exchange differences calculation for year-end opening balances, from now on, executed always analytically updating the document lines with calculated value of exchange differences.
Accounting
Documents Numbering
In case of independent ledger entries data entry utilizing ‘accounting document types’, the numbering update (per document type) happens when the ledger entry saved and not during the selection of the document type. This way, minimized the probability for non-sequential ledger entries.
Setting user rights for no deletion of ledger entries (in general) we are protecting the installation for non-sequential ledger entries.
Other Improvements
Documents Insert from xml
A new possibility provided in the process for auto insert-update of documents from xml in order to be defined that in case of transactions update, new lines import will happen only after deletion of the existing lines.
This is done in declaring at the section “ESFIDocumentTrade” of xml:
<DeleteAllRowsOnUpdate>1</DeleteAllRowsOnUpdate>
Entersoft Retail
Custom Version Synchronization
Provided new ability for customization of the synchronization method for not mandatory custom versions. Specifically, at \ESConfig\ES00RetailParams.xml of the client, you can add the following parameter
CLIENTSYNC_NONREQUIRED_CUSTOM_VERSION
which determines the synchronization mode when a new custom version launched ‘not required’ at the application server.
The parameter values are:
True (default) Synchronization starts automatically (at next login)
False Manual synchronization, selection by user
Confirm Confirmation message appears to the user if he wants to upgrade or not
It is useful in environments where a lot of clients exists and where one change (e.g. one print form) may concerns only one group of clients (and that’s the reason declared as optional – ‘not required’).
Entersoft CRM
Outlook Integration
The Outlook add in has been upgraded in order to be compatible with last version of Outllook 2016 and some improvements related with its functionality have been implemented.
Support of Outlook 2016
New settings per user
From the Outlook and selecting Settings / additional / Entersoft CRM Add in you will make visible the window with Outlook Add in settings. There new settings have been added:
- Option for user’s certification method where at the available choices, apart of the typical method of certification through codes the network certification option provided. This feature presupposes that is already defined at the application level that the user can connect through this certification method.
- New action for copy of settings & data of add in in user’s profile folder. This way, all archives utilized by add in transferred at the roaming profile of the user in the folder %appdata%\Entersoft\CRM Outlook Add in. After action’s execution is possible to restore the archives back at the application folder, executing again the same action which now will have a new description updating for the reverse process.
Protocolling from Outlook
New ability provided to the action for protocolling and synchronization from outlook where the mapping between outlook fields and fields from CRM entity is now feasible. Mapping configuration through ESOtlFieldMappings.xml found at csconfig folder (CSConfig\ESOtlFieldMappings.xml). Sample of the file and the structure found at ESConfig application folder.
Updates opposite direction (CRM entity to outlook), is not supported through this process. Lastly, assignments at the entity through relations are not supported. This procedure supported for mails, contacts, appointments and tasks only.
Attention: the file ESConfig\ESOutlookFieldMap.xml found at previous versions is not related with outlook add in. It relates to new outlook contact (new & update) through specific action of person’s screen and is not presupposes the existence of outlook add in at the system.
Horizontal Features
SQL Paddings Support
In constructing queries at the Data Base for usage at views (scrollers) and dashboards many times required the usage of Hints, tokens etc. in order to guide the execution plan and to achieve better performance executing the query. This one, now supported from the query builder mechanism in dashboards and views.
The implementation of new feature is based on custom parameters which we define the desired paddings. When executing the query, if found completed, added at the beginning or at the end of the query (through ESSTRTOEN) with their perspective values. In detail the configuration process of the option is as follows:
Step 1: Parameters Definition
The parameters defined at the relevant page of the designer under the assumption that its names will be or will begin from:
- ES_BOSQL = Beginning of SQL
- ES_EOSQL = End of SQL
Step 2: Parameters usage at the query
The parameters defined at Step 1 is necessary to be used at the query, otherwise they will be deleted once the query is being saved. That’s the reason that they have to participate in one declaration which doesn’t modify query’s results. At the following example the parameter @ES_EOSQL used in the query along with the expression: ISNULL({@ES_EOSQL}, ) <> 'dummy'
Step 3: Default parameter value
At this point we define the word/ hint to be added at the beginning/ end of the statement.
