From one major version to the next, various intermediate versions appear, which implement features and fix bugs in a timely manner.
The setup in the download above always includes the latest Vertec version available.
Version
description
Date
6.4.0.25
Bug fixes
Error when executing reports in the Web app: The error when executing vertec generated reports or Eob in the Web app has been fixed. The reports are saved locally and carried over to the Web browser.
The varParent and varContainer OCL variables do not work for normal folders: This issue has been fixed in this release. For varContainer the designation of the folder is shown, varParent no longer provides an error, but null .
18.08.2021
6.4.0.24
Features
New Python Stub Files: The Stub Files have been updated due to modifications of Python functions and the implementation of new functions. They are located in the subfolder PythonStubs of the Vertec installation directory or can be found in the article Python Stub Files for builtin Modules
can be downloaded.
Improvement Sage 200 Payment imports: The posting numbers used in payment imports were not unique. This prevented multiple payments with the same date and amount from being imported. Start with this release, payments with the same date, text and amount via Sage 200 Payment imports
imported correctly.
Bug fixes
Python function createoutlookmail: The problem with umlauts in attachment names of createoutlookmailPython Function
has been fixed.
Reintroduced Log Checkbox for Extension: With Vertec version 6.4.0.22, we removed the Log Checkbox. Since then, all log output from Extensions is always output to the Python console, which has proven impractical in some cases. Therefore, we reverted the changes and reintroduced the Log Checkbox for Extensions.
DATEV debtors Extension: The data VAT and country code are written correctly back into the master file.
DATEV creditors extension: The logic has been supplemented so that the Belegfeld2 uses the first 4 digits of the condition code.
09.08.2021
6.4.0.23
Features
Passing activity when saving documents to add-ins: Now the Office, Explorer and Outlook add-ins also pass the activity as an object when saving documents to a DMS such as e.g. Sharepoint. This allows the corresponding metadata to be written. SharePoint Online DMS extension
implemented and the add-ins now followed.
Cloud-capable Datev creditors Extension: The DATEV creditors extension
is now cloud ready. From this version onward, only the cloud-capable Datev extensions appear in the Extensions folder, if none was installed before. If a Datev extension is already installed, it remains.
Script Editor opens only with administrator privileges: The Script Editor
will only be shown from this version if the logged-in user Administrator rights
has. Otherwise, an error message will appear.
The Abacus Web debtors extension again offers the option “Use invoice number as Abacus posting number”: In order to import ESR or QR payment data, the posting number in Abacus must match the invoice number. Therefore, from this version onward, there is the setting Rechnungsnummer als Abacus Belegnummer verwenden .
For this option to be set, the Abacus Web accounts receivable Extension
uninstalled and reinstalled. If the feature is not needed, nothing needs to be done. Invoices that were post a previous version of the Abacus Web accounts receivable extension must be canceled and posted again.
If this is Yes, the posting number of posted invoices corresponds to the invoice number in Vertec.
If the setting is set to No, the posting number is assigned by Abacus as before.
Setting the EZ procedure when posting with the Abacus Web Debtors Extension: For reference type QR and several QR methods defined in Abacus must additionally be specified on the Abacus invoice the QR method corresponding to the IBAN. Therefore, Vertec provides from this version the EZ method ( PaymentOrderProcedure ) based on the Vertec payment type used. The allocation is based on:
In Abacus, a suitable EZ procedure must be defined, whose deposit account must correspond to the payment account (VESR participant number for ESR, IBAN for QR).
The Code of the payment type in Vertec must correspond to the number of the TR procedure in Abacus. If the code is not numeric, no TR procedure will be passed.
Vertec determines the payment type based on the payment account. If an IBAN is defined, we search for the payment type based on this IBAN. If a payment type is found, the EZ procedure is set in Abacus.
ShowApp = false now also works if no document is saved: Since vtcapp.executereport() since version 6.4.0.8 returns a report object, it is no longer useful for the application to open if it is not saved, since the report can now also be processed in other ways.
Bug fixes
Cloud app reopens report documents directly: Advanced Office reports and vertec-generated Word reports are also reopened in the Cloud app directly from the storage path (no longer from the Temp directory) and can thus be added and saved again.
23.06.2021
Update Vertec Phone App
on Android , version 1.0.18. This is an adaptation for an Appstore compliance, there is no change to the product scope.
The update will appear on Google Play in the next few days.
27.05.2021
6.4.0.22
Features
Python Executereport Method with Activity Return: There is a new Python method executereport2() , which returns the report and the activity as a return value.
Python Function for payment import: The New Python Function vtcapp.syncpayments() performs a global payment import. If no debtor interface with payment import is installed, the feature reports an error. For example, the feature can be registered as a scheduled task. For more information, see Vertec Python Functions.
Conversion of hours/minutes display in Excel EOB to hours decimal: The hours display in Excel Eob has been changed from the previously used HH:MKT format to hours with 2 decimal places.Anzeige Minuten : The option Stunden Minuten is ignored and as Stunden Dezimal output. The option Minuten is displayed as minutes as usual.
QR Code Swiss Cross Dimensions improved: Previously, the QR code has different numbers of “logical” pixels depending on the amount of data, but we always drew the Swiss Cross the same size. This led to problems depending on the banking institution, which are sometimes very precise with the dimensions, although technically unfounded. Therefore, we changed the calculation of the QR code so that if the entire code is scaled to 46 MKT, the CH cross would then be 7 MKT. We changed the existing QR code for this purpose. This means that there may also be differences in existing uses.
QR payment part in invoice reports Postfinance-compliant: In this context, we have also adapted the QR payment part in the invoice reports provided so that they are Postfinance-compliant. This applies to the reports Rechnung mit Leistungsliste , Rechnung mit Bearbeitersummen and Rechnung mit Phasensummen . Similarly, the Word templates for the article Prepare invoice templates for QR code have been created and made available. The existing Word templates from version 6.4.0.14 have been replaced by the newly created ones.
User rights restricted to absences: User who joined the user groupStandardbenutzer from this version onward can only view their own absences. The user group Projekt-Supervisoren has read and write permissions on all absences of other users. Group absences can be read by all user groups, but cannot be modified.
At various points, the display on the interface has been changed as follows:
If an activity is created when printing a standard report without a subject, it gets the translate name of the report.
The designations of the communication channels will be translated from this version onward.
From this version, the string representation of services, expenses and outlays contains the translated designation of the service type / expense type / expense type instead of the code.
As of this version, the string representation of absences contains the designation instead of the code.
Service type, expense and outlay type codes are no longer translated.
Removed log checkbox for extensions: The Log Checkbox for extensions has been removed. Only if this was enabled, the extension wrote the log output to the Python console, but had to be reset each time on the interface. What is new is that the extensions always write their log output to the Python console. Whether a log output is also written to the log file can be controlled via Debug Categories as before.
Bug fixes
File selector dialog of requestfilefromclient remains open: The error in the Cloud app that the file selector dialog of requestfilefromclient requestfilefromclient in some cases closed immediately, has been fixed with this release.
The mistake Vertec.UI.ViewModels.SelectFolderDialogViewModel wurde nicht gefunden the selection of objects has been fixed with this release. Detailed information can be found in the current support cases.
Python function createoutlookmail no longer deletes attachment file: The bug that the file was deleted if an absolute path was specified instead of a file name in the attachment list for the function createoutlookemail() has been fixed.
17.05.2021
6.4.0.21
Features
Access Container and Parent Object in OCL Expressions in Lists: New in OCL Expressions in Lists varContainer to the container (folder or Linkcontainer) and varParent the object to which the container belongs (parent object of the link container). In addition to the column expressions in the list, the ListExpression and GhostRowListExpression of a control access to these context variables (see: ComboBox expression for star row
).
Calling dialogs from Python: The different search and selection dialogs for addresses, projects, phases and the tree can now be called directly from Python. For this purpose, the following new methods are available on the vtcapp Module:
selectaddress()
selectphase()
selectproject()
selectobjectintree()
The methods support the following optional keyword arguments:
selectfilter: The selectfilter determines on which entries (classes and their subclasses) the dialog can be confirmed and thus “selected,” also comma-delimited.
Further information and code examples can be found in the KB article on the Vertec Python Functions
to find.
Write access to verrAttributes no longer possible: On various objects there are so-called verr attributes, which are written during the charging of the object and fix certain values (see e.g. verr Attribute on the invoice
). These are now generally denied write access. This affects the following attributes:
Project Entry
CONTRACTUAL ACCOUNT
TASTING OFFICE
VAT RATE
VERRVAT CODE
VERRMINUTEXT
VERBAL TEXT
downpayment
IMPREST ACCOUNT
invoice
RATE OF INPUT VAT
VAT RATE
EFFECTIVE AMOUNT OF ADVANCE
VAT CODE
VAT CODE
ACTUAL ADVANCES WITH VAT
VERRTOTAL
SHELTER AXE
REVENUE EXPENDITURE
TRAILING VALUE TEXT
SETTLEMENT ADDRESS TEXT
SETTLEMENT LETTER ADDRESS
SETTLEMENT GREETING FORMULA
VERRIBAN
PARTICIPANTS
VERRESRREFERENCE27
DISTRIBUTION OFFICES
VERRESRPLUS
VERRBESR
VERRBESRBANK
CONTRACTS
VERRCOMPANYNAME
VERRCOMPANYORT
VERRCOMPANYPLZ
VERRCOMPANYADDRESS
VERRCOMPANYLAND
VERRCOMPANYADDRESSTEXT
VERRCOMPANYVAT NO
PROJECT MANAGER
VERRHB
Write access to a VERR attribute results in the following error: AccessDeniedError: write access denied on Objekt.Attribut .
Exception: In System context
and when Vertec is combined with Parameters/SUPER is started, the attributes can still be written.
Differentiation of ESR and QR debtor invoices in the Abacus Web Debtors Extension: Abacus differentiates the reference types ESR and QR and needs them for the assignment of the postings. In order to ensure a correct assignment, QR invoices with the reference type QR are posted in Abacus from this version by: PaymentReferenceLineType=QR is set if the entered IBAN number is a QR-IBAN number. Further information can be found in the KB article Abacus Web accounts receivable Extension
.
Support for more than 200 sites in Sharepoint extension: Start with this release, Sharepoint instances that support more than 200 sites can be used.
Support for country code mapping in the Abacus web extension: From this version onward, the country code mapping is supported, which uses an Abacus compatible ISO code and as default CH. See the KB articles Abacus Web accounts receivable Extension
and Abacus Web creditors extension
.
Support of ESR invoices in the Abacus Web Creditors accounts payable extension: Up to now, the Abacus Web Creditors accounts payable extension took over the payment account and the reference information only if the payment account was a QR-IBAN. From this version, ESR invoices can also be posted in Abacus. The number externally ( kreditor.nummer ) is added to the field in Abacus. Belegreferenz-Nr. written.
Bug fixes
Abaco’s payment import takes into account several payments on the same day: If two payments with the same amount were posted on one day, only one payment was carried over to Vertec. From this version onward, all payments with the same amount and the same date are taken into account in the payment import: instead of the document posting number, the sequence number is now used as identification.
30.03.2021
6.4.0.20
Features
OCL Translate Operator: Analogous to Python, there is now a Translate Operator for OCL. This allows you to translate a string value in an OCL expression via .translate into the current Vertec interface language. More information can be found in the article OCL
on the KB.
Bug fixes
GetLinks OCL operator updated correctly: Fix an issue where some values were not updated automatically when using Getlinks (or only after restarting Vertec or reloading the object).
Printing Excel EOB with formulas that refer to blank bands is possible again: The issue in Vertec 6.4 and later that the error message appears when printing Advanced Office Reports with Excel output format Excel EOB Formula updater could not update new row could appear, is fixed.
09.03.2021
6.4.0.19
Features
Display Checkbox for Keyword Folders and Simple Folders in List: Keyword assignments can now be displayed and edited directly in lists. Keyword folders or normal folder structures can be processed, which are not IX folder
are marked. In the list column the corresponding subfolders (the keywords) are displayed and the entries can be assigned or removed by clicking in the checkbox. This is done using the rndKeywordFolder renderer.
Display a list of open and invoiced services for service recording: Services were previously entered under open services and are no longer shown after charging. From this version, the folder on the user is called services. When a service is charged, it remains visible in the list under services, but changes can no longer be made and the timer symbol disappears. More information can be found in the article Services, overall view
The containers for expenses and outlays on the user behave similarly.
Invoice reports without salutation: The salutation has been removed from the following templates:
Invoice with list of services (Invoicewithlist)
Invoice with Operator Sums (InvoiceWithUserSums)
Invoice with Phase Sums (InvoiceWithPhaseSums)
However, the field still exists in the code and therefore has no impact on custom templates.
LinkRoles in GetLinks Operators and Methods via entry IDIdentifiable: The Getlinks operators and methods have been extended so that the link role to be used can be identified not only by its designation (as before), but also by the Entry ID of the link type. A detailed description can be found in the KB article Operators and Methods for Link.
New template for cloud-capable debtor interfaces: The previous FibuTemplateExtension.py was approved by the FibuExampleExtension.py replaced, which implements methods for on- and offline (file-based) extensions as well as a payment import. It is explained in the article Template for cloud-enabled debtor extensions and is available for download. From this version onward, on-premises customers can also find them in the Extensions subdirectory in their Vertec installation directory.
Importing payment data for the cloud-capable DATEV Accounts accounts receivable extension: The existing DATEV Payment Import function has been replaced by payment import. If an earlier DATEV extension is used with DATEV Payment Import, the existing DATEV Payment Import script has to be removed manually. More information can be found in the DATEV Accounts accounts receivable extension article.
Topal Solutions accounts payable extension with QR invoice: The Topal Solutions accounts payable extension has been expanded so that a account payable entered in Vertec via QR code can be posted via the Topal Solutions creditors extension.
When posting, it checks whether the creditor.Esrparticipant (the payment account) field contains an information.
Topal checks whether a transaction method (technically Paymentmethod ) on the creditor address. If yes, this payment method is added to the Topal creditor object. If not, a new transaction method is created and the account number is used.
Payment method is QR , if it is a QR-IBAN, IBAN if it is an IBAN, and ESR in all other cases.
BI Generator no longer uses supported shadow attributes: Invoices that were set to charged with Vertec 6.4.0.17 or later were missing in the BI evaluations
. The reason for this was that the InvoiceGenerator Shadow AttributesqlValutaDatum which has been removed since version 6.4.0.17. The code has been modified to fix the problem with this version.
Several Absencesof the same type on one day: In the special case of two absences of the same type on one day, only the absence entered as the second or last one was deducted from the standard hours. With this version, the absence with the higher quantity of minutes is now taken into account. See also Absence Priority
.
10.02.2021
6.4.0.18
Bugfixes
Affects on-premises customers only. The bug that invoices cannot be opened in the Cloud Clients if a non-cloud-capable debtor extension is installed was introduced with version 6.4.0.17 and could be fixed with this version. It caused the following error message to appear when opening an invoice in the Cloud app or the Web app:
The action cannot be performed because no accounts receivable interface is installed.
Abacus accounts payable Webservice Extension: The Abacus Web accounts payable extension has been completely redesigned and is cloud ready. All information is available in the KB article Abacus Web creditors extension
to find.
Support for multiple class settings: From this version onward, multiple class settings can be used per class Class Settings
parallel. This is especially important for Plug-ins
relevant to avoid conflicts between imported class settings and existing customizations. The class settings are taken into account as follows:
The order of precedence for different applicable class settings is determined by sorting by the Internal ID. Higher IDs correspond to newer objects.
The following properties use the value of the latest class settings:
Document Path
Icon Index
Display Class Name
string representation
For the (default) list settings, the oldest class settings are always applied. The Save as Default save button in the List Settings Editor therefore always writes to the oldest class settings.
If there is customization of pages on several class settings, all are combined to form a page definition. If the same elements are defined, the most recent class settings are applied.
Purification Address handling in cloud-enabled accounting interfaces: The handling of invoice addresses and personal accounts in list-based (all cloud-enabled) accounting interfaces has been adjusted because the list-based accounting interfaces decide whether to generate a new address or update the existing one based on the presence of a personal account number. However, the previous fallback logic on the Personalaccnum of a superordinate address makes it impossible to determine reliably whether a new address has to be created in the financial FAR:
Previously: The previous logic uses the two properties rechnungsadresse and personenkonto on the invoice object. The invoice address is a typical “cascaded” attribute: It provides the valid address for an invoice and supports overriding options at different levels (customer > project > invoice). The Personalaccnum is implemented in a similar way, i.e. its value is not determined strictly on the basis of the invoice address, but goes through the “cascaded” hierarchy of the invoice address and returns the “best possible” personal account number. For example, if a billing invoice address is assigned on an invoice (via xRechnungsadresse ), but no personal account is given at this address, delivers rechnung.personenkonto the Personalaccnum of a higher level (project or customer).
New: There is a new (derived) property buchungsadresse on the address to be used for the post. The property rechnung.personenkonto then always provides the Personalaccnum of rechnung.buchungsadresse . This corresponds to rechnung.rechnungsadresse , unless this is a contact. In this case, the contact’s company is used instead. If blank, a new address is written and the personal account number is entered on rechnung.buchungsadresse registered.
Removes Shadow Attributes from the invoice: The Shadow Attributes, which are used to save values in the database that are actually derived, cause a write access to certain values to take place in the database. There are two of these Shadow Attributes on the invoice, which leads to performance losses when loading long invoice lists. Therefore, the two Shadow Attributes are Rechnung.SqlRabattBetrag and Rechnung.SqlValutadatum no longer written and used since this version. The database fields are still there, but then disappear definitively with version 6.5.
More efficient loading of the budget page on project: The show of budget details has been optimized by preloading the budget values.
Bug fixes
Opening a bookmark in a new tab: If a bookmark is selected while pressing the CTRL key at the same time, the bookmark entry will open in a new tab.
The issue of the Vertec Phone App with iPhone (iOS 14.2) has been fixed. The Phone app version 1.0.18 is available in the app Store. See also Current support cases
.
Blocking of the Cloud app, which could occur since version 6.4.0.15, has been fixed with this release. If the connection is lost, an error message is shown and the Cloud app completed as in versions prior to 6.4.0.15.
06.01.2021
6.4.0.16
Features
Support for Zugferd 2.1: Vertec now supports the Zugferd 2.1 standard, which resolves the differences between Zugferd 2.0 and Factur-X as well as the profile Xrechnung. The backward compatibility is guaranteed. Already customized reports still work and create as before a Zugferd PDF with version 2.0.1 or with the specified XMP schema. If you want to use the new Zugferd standard for already customized reports, the code must be adapted accordingly. The Vertec standard report invoice with list of services is delivered with the new standard. Further Information can be found in the KB article invoices according to Zugferd Standard (X-Invoice).
Invoice reports with fixed invoice address: With version 6.4.0.16, our invoice reports have been changed to use the fixed invoice address.
Additions to the Abacus Web debtor extension: The Abacus Web debtor extension has been added. Please use version 6.4.0.16 for operation.
Bug fixes
Posted creditors cannot be canceled: This bug was introduced in version 6.4.0.15 and fixed in this version.
Drag and Drop to Detailview Icon works again: The problem introduced with Vertec 6.4 that drag and drop from icon to icon (in Detail window) no longer works has been fixed.
Phone app now only displays active absence types for selection: With version 6.4.0.16, both inactive and invalid objects are no longer offered when entering a new absence in the Phone app.
The new version of the Phone app will be available in the app Store and Google Play in the next few days.
15.12.2020
6.4.0.15
Features
Abacus Web debtor extension: The Abacus Web debtor extension has been completely redesigned and is cloud ready. All information can be found in the KB article Abacus Web account extension.
Python Stub Files for builtin modules: Code editors (e.g. VSCode) now have good static analysis capabilities, which allow to detect many errors before execution. One problem is the built-in Python modules, which are not available on the filesystem. To make these available for the Type Checker, we provide new Stub Files of the built-in Python modules vtcapp , vtcextensions and ziputils with. These are placed in the subfolder Pythonstubs in the Vertec installation directory.
Bugfixes
SQL folders no longer display deleted objects: Due to the fact that the SQL folders are not calculated “ad hoc,” but have to be called explicitly for the calculation, the unattractive result was that deleted objects remained in the list as long as the list was not called again. This has now been improved with the current version – deleted objects are no longer shown.
Entering new creditor receivables via QR code: A new account payable receivable including address (supplier) can be created directly on the basis of a QR code. The exact process can be found in the article Accounts payable posted with Vertec
described.
Support of invoice date in QR codes for creditors: If the invoice number, due date and invoice date are known in the QR code, the information is set on the account payable when reading (see above).
Support of invoice date in QR codes for debtors: If the invoice date or payment term of an invoice is known, the additional information is encoded in the QR code and output as a visible string in the payment part of the invoice. The invoice templates invoice with service list, invoice with operator totals and invoice with phase totals output the corresponding information as additional information:
See also: Prepare invoice templates for QR code
User rights for BI Kpis: User rights can now be assigned per BI Kpi. The exact procedure is in the article Business Intelligence
As part of this innovation, the OCL operator was also hasBiDataRight modified. It now expects as argument a string with the internal name of the Kpis, e.g. projekt->hasBiDataRight('MinutesExt') . This is not backward compatible, so any calls have to be adjusted. See also the description in the article OCL
.
BI API: From now on there is an API (Application Programming Interface) for querying BI data from external applications. The detailed description can be found in the KB article BI API
to find.
The criteria for who sees which folders in the BI tree have been adjusted. The detailed description can be found at Business Intelligence
to find.
Sharepoint Online DMS extension – metadata example extended: The implementation for setting Metadata in the Sharepoint Online DMS extension
has been extended. If an activity is written, metadata will be written for reports that are executed on the user, invoice, Address, or project. The activation will be the same as before, only the underlying example implementation has changed. If this example implementation is used in another extension, it will have to be adjusted accordingly.
”Copy to clipboard” removed: The In Zwischenablage kopieren Button for code reference dialogs (e.g. for extensions) only worked in the Desktop App and was therefore removed again. The functionality is still available with Ctrl+A, Ctrl+C available.
Aid program FastviewerUpgraded to the latest version: The Fastviewer Client installed by Vertec Setup now has version 3.20.0060. It is called in the Desktop App and the Cloud app via Menu Settings > Start Fastviewer...
Bug fixes
The problem in the Web app with calling the URL via address entry without a schema prefix (http: or https:) has been fixed.
The issue with endlessly running Excel EOBs introduced with version 6.4.0.9 has been fixed.
23.11.2020
6.4.0.13
Bugfixes
Correctly detect suspended TaskRunner processes: There have been cases where TaskRunner
Processes were stuck but not detected correctly by the Cloudsever. This has been fixed in this release.
07.10.2020
6.4.0.12
Features
Currencies in rate table hidden in Standard: The table with the currencies in the rate table is no longer shown in the Standard line because there are no currencies there.
Restricted Session Process: It is now possible to configure the Vertec.Cloudserver to start session processes with restricted capabilities. This is done by settings in the [Cloudserver] section in the Vertec.ini file:
Restrict Session Process=True
For more information, see the description of the parameter. In the Vertec Cloud Suite from this version onward, this setting is automatically enabled.
Support for Loggly in the Desktop App: Affects on-premises customers only. The option introduced with version 6.4.0.9 to send the log output from the server-based Vertec processes (Vertec.Cloudserver, Vertec.Session, Vertec.Taskrunner) to the cloud-based logger service Loggly (see article Logging) has now also been implemented for use with the Vertec Desktop App. If the corresponding parameters are set in the Vertec.ini file, the operations in the Vertec Desktop App are now also sent to Loggly. No additional setting is required.
Phases Lookup Renderer in weekly table: If there is a column for phase in the weekly table Capture with the renderer rndMainPhaseLookup, the phase was not set when entering a new row. This issue has been fixed.
Generic Link Container could prevent the application from starting: If a Generic Link type (precursor of Custom Link type) is defined and the corresponding container is shown in the tree above the performance measurement by the user, and if the Save session settings option is not set, Vertec will not start. This issue has been fixed.
24.09.2020
6.4.0.10
Features
Reports without a file system: The report templates are now no longer located on the file system, but directly in the Vertec database. The standard reports are supplied by Vertec as resources. Exist customer-specific report templates are imported from the file system into the database during the update. A detailed description of what exactly happens during the changeover can be found in the article Migration 6.4.0.10: Report templates are no longer described on the file system.
DMS Sharepoint extension: Pass activity when saving report documents. The method Storedocument(self, vertecFilePath, content, activity) prepared with version 6.3.0.12 now passes the activity as an object. The corresponding metadata can be written in Sharepoint. The exact description can be found in the article Sharepoint Online DMS extension.
System settings can be created using the config set: Up to now, system settings could be changed, but not created. System settings can now be passed as normal objects in a config set, with all their properties specified. The exact functionality is described in the section Create new system settings in the article about the config set XML.
Python method vtcapp.executefile() now supports commandline parameters: Optional arguments can be passed for this. The previous simple case still works. The exact procedure is in the article Vertec Python Functions
described.
The payment type Combobox (PaymenttypeComboBox) allows you to select only active payment types. This applies in the following places: “Default” page on addresses, “Accounting” page on project and project type, and for payments.
Bug fixes
Create addresses in all clients at account payable extensions works again: The problem introduced with 6.4.0.1 that create addresses in all clients only created the address in default client has been fixed, see Open addresses in all clients / Sage50 system setting.
Handling of Sage 200 Encoding Bug in extension : The problem of Sage 200 returning values containing umlauts is now intercepted.
BI Excel Export now uses the user path for saving: When an Excel export from the BI, the file is saved in the Temp directory of the user instead of in C:\Windows\temp as before.
The BI Excel export no longer replaces 'NaN’ with empty string.
17.09.2020
6.4.0.9
Features
Translation of configuration data into business logic: In order to be able to make the standard configuration objects available in all languages, Vertec automatically translates the so-called string representation (i.e. the display names of the objects) into the selected interface language. Since Vertec used to do this at runtime on the interface, this sometimes led to problems with the customer’s payload data, namely whenever it happened to be the same. For example, “PML” is always shown as “PL” in the tree in a German Vertec (because “PML” is interpreted and translated by the translation mechanism as “project manager”). For this reason, the translation of the configuration objects has been moved to the business logic. Exist customers usually do not notice any of the changes, except that the translation problems mentioned above no longer occur.
Send Log Output to Loggly Service: Vertec on-premises only. Allow you to send the log output from the server- based Vertec processes (Vertec.Cloudserver, Vertec.Session, Vertec.Taskrunner) to the cloud-based logger service Loggly. For detailed information, see Logging.
Expanded BI URL: The URL support for Business Intelligence (BI) shows has been expanded with the following properties:
Date range
Selected display
Selected key Kpis incl. sorting and coloring
For more information, see the article on the BI Anz own.
Saving the configuration of BI Views in Favorite: It is now possible to save BI Views as Favorites. These are displayed with all parameters (see above) when called. BI Shows saved as Favorites are granted a designation according to the pattern Node (BI): Display Name, i.e. project (BI): User. In this way, the BI Shows in the Favorites can be identified at a glance.
TAPI Extension also works without Calleridname: Vertec on-premises only. With a TAPI provider, no Callerid Name is supplied when the call is made. The Vertec TAPI extension has always expected the Calleridname field. This has now been adjusted, so that incoming calls via TAPI with providers that do not supply a Calleridname field can be handled correctly and shown in Vertec.
Saving PDF posts in the Phone app: Now you can also save PDF posts for expenses with the Vertec Phone App. The exact procedure is described in the article Phone app: Operation and Use.
Performance optimizations:
When starting Vertec, the following objects are preloaded:
Settings objects such as Righttype, Currency, Vattype, Payment type, Revenue Type and Activity Type
Once the logged-in user is known, the corresponding user groups and the objects that depend on them
Class settings are loaded via SQL each time they are used. This means that there is no caching in the object layer. Since the total number of ClassSettings objects is always small, they are loaded again and all at once.
Bug fixes
Fixed an issue where lists with many invoices with invoice discounts could lead to a batch overflow.
The issue introduced in 6.4.0.1 that Advanced Excel Report no longer applies the column widths from the template has been fixed.
The Abacus web service payment import returns the correct date instead of 0.
Simplified selection of bottom entry in the tree in Web app: The bottom entry was hidden by the enlarged scrollbar when mouse over. This has been fixed.
The Web app shows the reason for invalid entries in the list views again. This worked in the Web app since 6.1 only in the detail views.
BI calculation via Python also for one month: Calls of the type vtcapp.processbi('2020-04', '2020-04', “ServicesGenerator.ServicesGenerator”) do not bring any more errors.
Fixed typos for Query folders (“Exclude”).
The new version of the Phone app will be available on the app Store and Google Play in the next few days.
17.08.2020
6.4.0.8
Features
Support for pinned columns in list settings: The first columns in the lists can be pinned again by setting a check mark for pinned in the list settings.
Upload of DMS document to Web app activity:
In the file selection dialog on an activity with DMS Docpath, a local file can be selected. This is then uploaded to the DMS. The folder path corresponds to the Docpath of the activity, the file name corresponds to the selected file.
For both variants, a dialog appears where the file can be selected.
Python method executereport returns report output in memory: vtcapp.executereport() returns the report output as a byte string. This can be further processed and attached to an email via vtcapp.createoutlookmail().
Additional logging:
1. Loading objects from the database: Using the value DebugCategories = Vertec.PMappers in the [Log] section of the Vertec.ini allows you to observe the loading of objects from the DB. The Persistence Mapper log entries only appear if they are enabled via DebugCategories (category DEBUG) . Note that this type of logging should only be enabled temporarily, as there may be a loss of performance by writing the log data to the log file.
2. Conversion, Initdata: Log output when executing version-dependent convert logic. The log entries always appear (category INFO).
Detecting and stopping suspended Taskrunner processes: There are cases where a Vertec.Taskrunner process does not complete correctly. These processes persist and unnecessarily block memory on the server. Therefore, in Vertec.ini under [Cloudserver], the maximum running time for a scheduled task can now be specified under Task Scheduler Max Minutes. The default value is 1200 (20h).
If a process runs longer than the maximum time, Cloudserver automatically completes it.
Completing Vertec.Cloudserver also completes all started Taskrunner processes.
The setting of Objectproperties is now also possible via vtcapp.setpropertyvalue. Previously, the assignment had to be done via the member objectBoldID.
Convert Code removed from Outlook Extension: The code responsible for converting the reference field from Yomifirstname to Vertecid has been removed from the Outlook interface.
Bug fixes
List-based accounts receivable interfaces (all cloud-capable accounts receivable interfaces) take into account successful postings line by line: Only the postings of a list that are actually posted are now shown as posted. Until now, the entire list was marked as posted, even if some of the postings in the accounting system failed.
The Run my Account extension now posts the settlement of downpayments correctly. The downpayment is posted negatively during reconciling.
Web app: The Index field in the Properties folder appears again.
07.07.2020
6.4.0.7
Bug fixes
Multi-line addresses lead to invalid QR codes: If invoice addresses or the address of the payee are entered in multiple lines and with line breaks, the QR code will move rows and invalidate the code. To prevent this, two new derived attributes on invoice have been introduced:
qrAddresstext contains the invoice address (Payable by) with only one address line
qrcompanyadresstext contains the payee (account / Payable to) with only one address line
As of 6.4.0.7 the QR code uses these fields and is therefore automatically valid for existing reports.
If you work with multi-line addresses and would like to display the addresses that are printed in the QR number and recipient parts in the same way as they are integrated in the QR code in existing reports, please refer to the article Preparing invoice templates for QR code.
18.06.2020
6.4.0.6
Features
New property Icon Index for subfolders on folders. If an icon index is used there, each newly created subfolder automatically receives this icon.
Fixes the problem that Vertec.Taskrunner processes were started in the background even if the Business Intelligence module was not licensed or no Vertec user was registered for the scheduled recalculation task.
When installing the Desktop App via Client Setup, a complete Firebird Client Setup is now executed if Firebird is used as the database. This prevents errors when loading the Firebird database driver on client machines. As a consequence, when uninstalling a Vertec installation on the client machine, the Firebird must be uninstalled separately, since this is not possible automatically for security reasons.
11.06.2020
6.4.0.5
Features
Set icon for IX folders: If a folder is marked as Inclusive/Exclusive, the IX icon was always displayed, even if an icon index was explicitly specified. New this is no longer the case, now, if present, the specified icon is used, and only if -1 (unspecified) the IX icon is used.
Change properties are no longer exported via config set: The objects in the Configset no longer contain the following members: Creationdatetime, Modifieddatetime, Creator and Modifier.
Improved performance in lists with no active member: Lists evaluate whether an object is active or inactive to show it with the gray bar in the first column. For objects that have no active member at all, this check has been disabled.
Caching Webapp resources can cause errors when changing versions: The static resources of the Web app are usually cached by the browser or by an intermediate caching Web server. This is important and improves performance during the initial loading of the Web app, since the static content does not have to be carried over several times. However, when changing versions, this can cause some resources to become obsolete. To fix this, the resources Url now contain a version sangabe.
New Fastviewer Version: Setup 6.4.0.5 contains the latest version (3.20.058) of Fastviewer.
Improvement in OCL optimization of short lists: In the OCL optimization of column expression when loading object lists introduced in Vertec 6.4, the optimized loading is normally done in sections according to the loading behavior of the list (approx. 2 visible list pages). For shorter lists up to 300 rows, a special handling has been introduced, so that in these cases the whole list is optimized (and thus loaded). In the former case, the list is loaded faster, but when scrolled down, objects have to be reloaded. In the second case, the first loading of the list takes longer, because the entire list is loaded immediately, but when using the list there is no longer any delay, because all objects are already loaded. Now it has been shown that this is perceived as annoying during running operation and the user feels variant 1 as performing better or has to wait too long for variant 2. Especially if the entire list is not used afterwards, this is a problem. Therefore, this special treatment has been extended again in version 6.4.0.5.
Bug fixes
The problem that caused problems when converting Vertec versions of 6.2 and older to MS SQL Server has been fixed. The conversion can be performed as usual with the Vertec.Dbconvert.exe. See also the current support cases.
An error that could occur during payment import and lead to an error message “... Inf not a valid date” has been fixed.
03.06.2020
6.4.0.4
Features
Comment field in list settings: In the list settings, there is now one comment field per column:
Python method for creating email in Outlook: There is a new method in Python vtcapp.createoutlookmail(to, subject, body, [cc, bcc, attachments, show]), which allows you to create an email message on the client via Outlook. Vertec Python Functions
.
Remove Test Data and Execute button on Advanced Office Reports. Remove the Test Data field and the Execute button in the report definition of Advanced Office Reports, as this has repeatedly led to problems, e.g. when using link containers instead of folders.
Bug fixes
Error in context menu for invoiced invoices in Web app: The issue that could lead to an error in the context menu on invoiced invoices in the Web app as of Vertec 6.4.0.1 has been fixed.
Evaluating ValueExpressions in TableColumn Controls (XML Customizing): ValueExpressions in TableColumns were not evaluated. This issue has been fixed.
26.05.2020
6.4.0.3
Bug fixes
Fixes a performance issue related to the Business Intelligence module where more objects were loaded in the background than needed, even if the BI module was not licensed.
Installs the Config file provided in the current support cases by default in the Vertec installation directory.
08.05.2020
6.4.0.2
Features
Changing Data Type for Custompages: Text instead of Blob. In Class Settings > Page > Customization, the data type of the field has been changed from Blob to Text. This fixes an error in older config sets imported into Vertec 6.4.0.1 (and vice versa) that include Page Customizing.
