--- title: "3.11 Version" canonical: "https://wiki.soft1.eu/space/SS5EN/blog/189273818/3.11%20Version" format: markdown --- # Key developments in Milestone version 311   **Financials** --- - Has been added new parameter in types of documents relating to Open -Item ![image]() After synchronizing in 3.11, the types of documents will be updated with value based on the trader' s transaction. If a new type is created, the value '0' is the default and will have to be configured properly. This parameter is very important for matching documents. All documents posted having 'Indifferent'  in the field Claims (in the type of the document) will not be available for matching and will not participate in any financial result. Therefore, any document that affects trader's values should not have 'Indifferent' in the field Claims. *Attention: There will be no extra SOFT1 job to convert massive data records and therefore should be given special attention during the parameterization of  the new types of documents.* - Is supported  different Payment terms per invoice which based on data lines (group,business / accounting category, business unit, project). These Payment terms are designed in Payment methods module. - **OPITEM **table is no longer updated - maintained by the previous records - According to the new matching method, **FINPAYTERMS** is the table which will be updated. - Has been added the automatic matching FIFO, based on existed requirements and coverages. - Balance aging report when applied ' Open- Item ' is  only available in the **currency of the trader**. - **Pay-off:** Has been added in the series of documents, in Special data panel, the flag 'Use settlement days '. If this is 'Yes', during the automatic payment, the collection invoice will be obtained on the value of settlements until the date of the document and not for the earlier value. see [Settlements](http://enwikibackup.softone.gr/0500000000/Financial/Settlements) - Follow the link to see what [checks](#) must be made regarding open item in 311 version and the structure of [Finpayterms](http://enwikibackup.softone.gr/0500000000/Customizing/Database_Designer/Database_Tables/FINPAYTERMS_table) table. # **Inventory** --- - Has been adjusted the dialogue in **'Balance per W/H' **report, to display only items with negative balance in W/H, if requested. Specifically, the question type Yes / No has been replaced in to a list of options under the heading  'Only items with negative balance in W/H' . # **Remote Systems** --- ** On / Off Branches Operations ** - Prohibition when posting documents in offline mode, if the branch which the user is logged in has not entered in the documents series. - Has been fixed issue which resulted from the series numbering if the first document was posted in offline mode. - Has been added message that appears if it is not possible to synchronize the local database with a central synchronization file because the local database is in use. # **Mapping Address** --- - Has been added the ability to locate addresses on the map through the application of **Google maps**. This feature is available by right clicking on browsers (and / or related work) and can be applied to multiple records. The search displays the addresses for selected points on the map, while showing columns as the index information of the selected point. Moreover, the choice [Route], suggests the best route to the selected point, using as a starting address the company' s. # **Color zones - New features** --- - Has been added the ability to create and use color zones  according the values of lookup fields . This evolution allows setting colours according to the price. **Default records** --- This new feature allows the dynamic creation of lists of records that are used in different parts of the application, either for direct search or perform work on specific records. The creation and updating of the lists is very simple: ![image]() The lists created in each section are displayed by clicking the arrow button [Favorite]. The selection list shows only those records that have been added. Moreover, the list is available to all selectors  of this section with the right mouse button respectively as the last entries.  E.g. Has created a list entitled [My customers]. > Macro (inline-external-image) This list can be used in the customer selectors to  documents browser to display only documents of customers in this list. ![image]()   Printouts  --- - Has been improved the print layout (html format) to be distinctly the levels of grouping. The **Print Preview **option  in Screen printing is compatible with how was functioned in previous versions. - Has been added new printing formats : **Spreadsheet** (is saved in .xls format), **Document** (is saved in .doc format), **Soft1 web publisher** (can be published in a web page). - Select entries in the browser and then with right-click (or Related jobs) > Add to preselections. If you already created lists, can be updated or created new selection list with [New entry]. Similarly, it can be done to remove selected records from existing lists. # **Credit Controls** ---   - Has been added the possibility to defined credit control per document type. The field Credit control in document type was converted from boolean Y/N to string list with values: *0= No check (old No)* *1= From credit policy (old yes)* *2= Warning always* *3= Forbid always* ![image]() - Has been added two new expressions available to credit checks:CHQOFSDAYS, CHQCRTDAYS .These credit checks are available in the receipts - payments documents.   ![image]() # **Prices - Pricing policies** --- - Added parameter in the types of sales documents determines what would be the basic price to update the sales price (OnLine and Batch). The values of the parameter are: 0= Nominal value 1= Value includes discounts  and expenses ![image]() - A new condition is available in Agreement rules: Trader's branch document - Shortage / Requirement report produces from now on the documents in the currency of the supplier and not the company's. - In the Batch modification of prices job has been added parameter to selectively change alternative prices. **Document Conversion** --- - **Automatic covering mode :** Has been added parameter in documents types which determines the behavior of automatic covering mode. - **0=Indefferent**, (FIFO coverage with traders invoices - compatible with earlier Soft1 versions) - **1= Company Branch**, (FIFO coverage with the trader documents issued by the same branch of the company) - **2= Customer Branch,** (FIFO coverage with the documents issued by the same branch of the trader. - **3= Company Branch and Customer Branch,** (combination of 1 and 2). # **Imports - Exports** --- - Has been added new allocation methods in cost categories. Is allowed the cost-sharing based on given duty percentage. **Custom Views** --- - **Important technical development** From version 311 changes the way of saving custom views in order to save all data (full save). This results at not to be imported custom views(cst files) from earlier versions.  During the upgrade facilities in multilingual version 311, in case of display question marks in titles (caption) of the designed views, you should know the following: The problem occurs only on views that are originally designed when login in Greek language (and the regional settings of the pc are not Greek). To correct it requires the following: 1.Login with the desired language eg English 2. Select the view for correction and then Design View 3. Right-click the panel and type the new title  - Possibility to set for application tables a different alias when designing views. International Edition --- - Romanian - Added XSPELL function - Cancel exc. rate gain and loss calculation job is now available in companies with Taxation laws: Romania - Is supported the distinction of series used to post exchange differences on valuation and matching in general parameters of trading parties. QlikView --- - Has been incorporated newer version of the ocx file (OCX 9) necessary for the proper functioning of the QV scenarios  in 311 version . - **Note: **With regard to the execution file QlikView, may occur problem on the workstation if there are folders with earlier versions of the application. In this case the matter dealt with registration of the new OCX-used in the 311 - to the system as follows:    1. In the new version folder locate the file Qlikocx.ocx    2. With right click select “Register”    3. If the option "Register" is not available, then select "Open with" and locate the file regsvr32.exe, is located in the folder "System32" for Windows It should be noted that after this procedure no longer be supported  ocx of previous versions . That is, if we want to run properly QlikView scripts to eg 310version , the above procedure should be repeated for the 310 installation. # **Search in active browsers** --- - The new search feature in the active browsers allows rapid finding records in indexes using search box on top of the screen. The search is executed in all the fields (columns) of the browser. ***Notice that the fields from memory tables, search is done using code and not the description, for example, should entered the code of Com. category to filter out the records.*** **Approvals** --- - Has been added a new parameter in documents series which defines printing  of the non - approved documents.  (No check-Warning- Prohibition) **Projects** --- - Two new columns has been added in Cards and in Financial data of Projects. Columns Revenues - Expenses of net values. **Retail** --- - Added the possibility of choosing more than one document in conversion process of orders. - Advance payment and transfer of total discount to the new document. - When choosing advanced payment into a new document from retail module is transfered the total      discount value - Transfering temporary customer data in the new retail document **Accounting** ---  **Project, Category and Group as filters in accounting prints** Extra filters have been added in special questions of the following reports and regard to lines and not on centralized data. ![image]() **General & Cost accounting reports:** 1. User defined journals 2. Cards 3. Subsidiary ledger 4. Official journals 5. Detail trial balance 6.General ledger **I.A.S. reports/printouts** 1. User defined journals 2. Cards 3. Subsidiary ledger - In the G/L accounting data has been added button in order to updatw KEPYO data. This feature reduces the time required for the projection of economic data when having a large ammount of transactions. **Branches - facilities** --- In print dialogue for Cards or Cards analysis of cheques has been added filter for branch. ![image]() **Colour - Size** ---  Has been added the possibility to have  different price per supplier for items with attributes. # 311 Version checks **Open Item** ---   After synchronizing in 311 version should be a comparative review between the data regarding the following reports :   - Collection without matcing - Payments without matcing - Customers unpaid document - Suppliers unpaid documents - Customers matched documents - Suppliers matched documents - Special transactions settlements (Customer & Suppliers) - Interest report - Balance ageing (Customer & Suppliers) - V.A.T. for Malta After synchronizing in 311 version should be a comparative review between the data regarding the following jobs: - Exc. rate gain & losses (open item) for Customers and  Suppliers - Interest Calculation (Customer & Suppliers)   After synchronizing in 311 version should be a comparative review between the data regarding the following ratios:   - Average age balance - Average Collection time (In year) -  Average Collection time (History) -  Average Collection time (Cheques in year) -  Average Collection time (History cheques) -  Average Payback time (In year) -  Average Payback time (History) -  Average Payback time (Cheques in year) -  Average Payback time (History cheques)     **Installation and use of data optimization script "Before311_sync.imp"**   The script Before311_sync.imp created to be used optionally for optimization of customer data. It is a useful tool that can be used to identify errors that may exist in the table OPITEM.   The use of the script consists in databases which will be synchronized to a 311.491 version, in which repealed the OPITEM table and the data are transferred in table FINPAYTERMS. The execution of the script and the correction of data-where appropriate-will ensure that after synchronization to the new version FINPAYTERMS the table will be updated with the correct data. For details on what exactly controls the above script, refer to section D.   **A. Where the script is executed** The script runs only on databases that are synchronized in any series of versions 310.482   **B. How the script is inserted in the application (find script attached at the end of this page)** Save the file Before311_sync.imp in the database. 1. 1. Open the file using any editor (eg Notepad, Impedit etc.) 2. Go to the **S1Import** module , create a new entry with name and description Before311_sync.imp and  paste the contents of the file. ![image]() 1. Right click in the menu select **New job.** 2. In the window that appears, copy the parameters of Image 1 and click OK. In the menu will display the job under the name Before311_sync. 3. Right click in the Menu, select Save as a personal menu. 4. Close the application and run it again **C. How the script is executed** 1. After entering the application, select the job that you just saved and you will see the screen work. 2. Click Confirm job and then Execute **D. What do the results** The job creates database views, which are processed and the results are shown in the grid, in the screen work.  The Results screen is comprised of 4 parts:   **1****st**** Part**   If after the job is executed, is displayed data, in the 1st grid then: There are transactions with differences, between the value of transaction and the value of the invoice. In the currency of the company or in the currency trader.   **2****nd ****Part**   If after the job is executed, is displayed data, in the 2nd grid then: There are transactions with differences, between the value of transaction and the value in lines of cash transaction. In the currency of the company or in the currency trader.   **3****rd**** **** ****Part**   If after the job is executed, is displayed data, in the 3rd grid then: There are transactions with differences, between the value of transaction and the value in lines of remittances. In the currency of the company or in the currency trader.   **4****th ****Part**   If after the job is executed, is displayed data, in the 4th grid then: There are overbalanced, matched entries, in OPENITEM table. That means the existence of documents whose value is less than the value of matching.     **E. Correction of entries**   After you find the documents which created a mismatch, you must take appropriate action, ie pairing up again and re-posting documents. Failure to rectify these errors in the synchronization of the database from version 310 to 311, the  OPITEM data falling in the above cases will be transferred as such to the table FINPAYTERMS.     **Custom Views** --- **Save of custom Views.** After synchronizing in 311 version all custom views designed in previouw versions must be checked Special checks should be made to custom views you have created in the subsystem of CRM. The addition of new special area to support work flow,in default screens of the application, would create an oversight (not functional)on your designed views. # Technical Instructions - Version 3.11.497 Respect to installations that use the module Contracts and developed customizations on it. From 311.497.10133 version the field "Special Contract" appearing in purchases/ sales  documents and refer to file Contracts changes position in the database. Specifically: - In previous versions of 311.497, the field was in table  MTRDOC (ie table related 1 to 1 with table FINDOC) - From version 311.497 and thereafter the field is  placed in the table FINDOC. The purpose of this action is the availability of this field in header of every single application documents (eg receipts, payments, etc.). Please note that Contracts have been upgraded significantly on the latest versions - will be equally involved even as a selection criterion in handling of matching documents. The synchronization process of 311.497 will take care  to transfer the values of the field (full name MTRDOC.CNTR),  the new field (full name FINDOC.CNTR). However, there are some cases where once the synchronization finishes should be done some handling. In particular, cases relating to the possibility of using the field MTRDOC.CNTR (or other areas of the file via CNTR) at : - Custom views - Reports - Printing forms - S1 scripts If either of these cases is valid , then the operator immediately after the synchronization process must in all design tools (views, reports,  printing forms or script editors) of Soft1, to replace the MTRDOC.CNTR with FINDOC.CNTR. Otherwise the effects will be: - In custom views, the caption of the field will appear empty. - At print forms and reports will be shown an error message ("Can not find the field ....") Note that it requires no action if the Contracts entity and in particular the "Special Contract" (MTRDOC.CNTR), did not participate in any of the above.  [ ](#)