Vertec version 6.4

Bug fixes

• Error when running reports in the web app: The error when running vertec-generated reports or EOBs in the web app has been fixed. The reports are saved locally and transmitted to the web browser.
• The varParent and varContainer OCL variables do not work for normal folders: this issue has been fixed in this version. For varContainer the designation of the folder is shown, varParent no longer provides an error, but null.

Features

• New Python Stub Files: The Stub Files have been updated due to modifications of Python features and the implementation of new features. They are located in the subfolder PythonStubs the Vertec installation directory or can be downloaded from the article Python stub files for builtin modules .
• Improvement Sage 200 payment reconciliation: The document numbers used in payment reconciliation were not unique. As a result, multiple payments with the same date and amount could not be imported. Starting with this version, payments with the same date, text and amount can be imported correctly via Sage 200 Payment Reconciliation Import .

Bug fixes

• Python feature createoutlookmail: The problem with umlauts in attachment names of  createoutlookmail Fixed Python Feature .
• Reintroduced Log Checkbox for Extensions: 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 receivables interface: The data VAT and country code are written correctly back into the master data file.
• DATEV accounts payable interface: The logic has been supplemented so that the Belegfeld2 uses the first 4 digits of the condition code.

Features

• Passing activity when saving documents to addins: Now the Office, Explorer and Outlook addins 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. This was already implemented in the Sharepoint online dms extension with version 6.4.0.10 and the addins have now been added.
• Cloud-ready Datev accounts payable interface: The Datev accounts payable extension is now cloud-ready. From this version onwards, only the cloud-ready Datev interfaces appear in the Extensions folder, if none was installed before. If a Datev extension is already installed, it remains.
• Script Editor only opens with administrator privileges: From this version, the Script Editor is only shown if the logged-in user has Administrator Rights . Otherwise, an error message will appear.
• The Abacus Web receivable interface 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 correspond to the invoice number. Therefore, from this version there is the setting Rechnungsnummer als Abacus Belegnummer verwenden.

  In order for this option to be set, the Abacus Web Receivable Interface must be uninstalled and reinstalled. If the feature is not used, nothing needs to be done. Invoices posted with a previous version of the Abacus Web receivable extension must be canceled and posted again.

  • If this is Yes, the document 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 receivable interface: For reference type QR and several QR procedures defined in Abacus must additionally be specified on the Abacus invoice the QR procedure corresponding to the IBAN. Therefore, Vertec provides from this version the EZ procedure (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 supplemented and saved again.

Update Vertec Phone App to 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.

Features

• Python Executereport method with return of activity: there is a new Python method executereport2(), which returns the report and the activity as a return value.

  executereport2(rootObj, optarg, berichtObj, [saveAs, showDialog, doPrint, showApp]): (reportDoc, activity)

  The return value of the method is a tuple (reportdoc, activity) where
  • reportdoc is the content of the resulting report document (byte string).
  • activity is the created activity object or None

  The method is called with assignment of the return value to 2 variables:

  reportdoc, activity = vtcapp.executereport2(argobject, None, reportdef)

  For more information, see Vertec Python features.

• Python feature for importing payments: The new Python feature vtcapp.syncpayments() performs a global payment reconciliation. If no debtor interface with payment reconciliation is installed, the feature reports an error. For example,
  the feature can be registered as a scheduled task. For
  more information, see Vertec Python features.
• Change hours/minutes display in Excel EOB to hours decimal: The hour display in Excel EOBs has been changed from the previously used HH:MKT format to hours with 2 decimal places. Note on system settings 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 had 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 is sometimes very precise with the dimensions, although technically unfounded. Therefore, we changed the calculation of the QR code so that if the entire code was scaled to 46 mm, the CH cross would then be 7 mm.
  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 were created and made available. The existing Word templates from version 6.4.0.14 were replaced by the newly created ones.
• Permissions restricted to absences: Users who join the user group Standardbenutzer 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 receives the translated 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 / expense type / expense type instead of the code.
  • The string representation of absences from this version contains the designation instead of the code.
  • The codes of service, expense and outlay types are no longer translated.

• Log checkbox removed for extensions: The Log Checkbox for extensions has been removed. Only if this was activated, 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 selection dialog from requestfilefromclient remains open: The error in the cloud app that the file selection dialog from requestfilefromclient in some cases closed immediately, has been fixed with this version.
• The mistake Vertec.UI.ViewModels.SelectFolderDialogViewModel wurde nicht gefunden the selection of objects has been fixed with this version. Detailed information can be found in the up-to-date support cases.
• Python feature createoutlookmail no longer deletes attachment file: The bug that the file was deleted when an absolute path was specified instead of a file name in the attachments list in the createoutlookemail() feature has been fixed.

Features

• Access to containers and parent objects in OCL expressions in lists: New in OCL expressions in lists you can use 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 ).
• Selection dialogs can be called 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:

  • selectaddress(string title, string classname, string filter)
    • title: Dialog Title (Default: Select addresses)
    • classname: Address class in which to search, e.g. Firma. (Default: address entry)
    • filter: Additional SQL filter condition (Default: empty), e.g. only on active objects
    The address search dialog uses the default search definition according to the System Settings .
  • selectphase(string title, string filter)
    • title: Dialog Title (Default: Select phases)
    • filter: Additional SQL filter condition (Default: empty), e.g. only on active objects
  • selectproject(string title, string filter)
    • title: Dialog Title (Default: Select projects)
    • filter: Additional SQL filter condition (Default: empty), e.g. only on active objects
  • selectobjectintree(string title, list entrylist, string browsefilter, string selectfilter)
    • title: Dialog Title (Default: Select Objects)
    • entrylist: List of Vertec objects that are displayed as root elements in the dialog.
    • browsefilter: Comma-delimited filter for object types (e.g. Ordner, Expressionordner)
    • selectfilter: The selectfilter determines on which entries (classes and their subclasses) the dialog can be confirmed and thus “selected,” also comma-delimited.

  More information and code examples can be found in the KB article about the Vertec Python Features .

• Write access to verr Attributes no longer possible: On various objects there are so-called verr attributes, which are written when charging the object and fix certain values (see e.g. verr Attributes on the invoice ). For these, write access was now generally denied. This concerns 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 the System Context and if Vertec uses the Parameters /SUPER is started, the attributes can still be written.

• Differentiation of ESR and QR debtor invoices in the Abacus Web receivables interface: Abacus differentiates the reference types ESR and QR and needs them for the assignment of the documents. In order to make a correct assignment possible, 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 Receivable Interface .
• Support of more than 200 sites in Sharepoint extension: Starting with this version, Sharepoint instances that support more than 200 sites can be used.
• Support of country code mapping in the Abacus Web extension: Starting with this version, the country code mapping is supported, which uses an Abacus compatible ISO code and as default CH. See KB articles Abacus Web Receivable Interface and Abacus Web Accounts Payable Extension .
• Support of ESR invoices in the Abacus Web Payable extension: Up to now, the Abacus Web Payable extension transferred 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 reconciliation 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 sent to Vertec. Starting with this version, all payments with the same amount and the same date are taken into account when importing payments: instead of the document number, the sequence number is now used as identification.    

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 to the current Vertec interface language. For more information, see the article OCL on the KB.

Bug fixes

• GetLinks OCL operator updates correctly: Fixed the problem that when using GetLinks some values were not updated automatically (or only after restarting Vertec or reloading the object).
• Printing Excel EOBs with formulas that refer to blank bands is possible again: The problem in Vertec 6.4 and later versions, when printing Advanced Office Reports with Excel output format, the error message Excel EOB Formula updater could not update new row could appear, is fixed.

Features

• Display checkbox for keyword folders and simple folders in lists: Keyword assignments can now be displayed and edited directly in lists. Keyword folders or normal folder structures that are not marked as Ix folder can be processed. 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.

• Show a list of open and charged services for service entry: Services were previously entered under Open services and no longer displayed 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 icon disappears. More information can be found in the article Services, Overall View . The containers for expenses and outlays on the user behave analogously.

• 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 Entry Id via entry ID: 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 links.
• New template for cloud-ready debtor interfaces: The previous FibuTemplateExtension.py was approved by the FibuExampleExtension.py replaces, which implements methods for on- and offline (file-based) interfaces as well as a payment import. It is explained in the article Template for cloud-ready debtor interfaces and is available for download. On-premises customers can also find this version in the Extensions subdirectory in their Vertec installation directory.
• Importing payment data for the cloud-ready DATEV receivables interface: The existing DATEV payment import feature has been replaced by payment reconciliation. If an earlier DATEV interface 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 receivables interface article.
• Topal Solutions accounts payable extension with QR invoice: The Topal Solutions accounts payable extension has been extended so that a creditor entered in Vertec via QR code can be posted via the Topal Solutions accounts payable extension.
  • When posting, the creditor.ESRparticipant (the payment account) field is checked for an entry.
  • In Topal, it is checked 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.
• Old Abacus extensions are no longer included: The AbaConnect Webservice receivables and AbaConnect Webservice accounts payable extensions are no longer included with new installations. They are still available for existing customers.

Bug fixes

• BI Generator no longer uses supported shadow attribute: 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 did not use the Shadow Attribute sqlValutaDatum which has been removed since version 6.4.0.17. The code has been modified to fix the problem with this version.
• Multiple Absences of the same type on one day: In the special case of entering two absences of the same type on one day, until now only the absence entered as the second or last one was deducted from the standard hour. With this version, the absence with the higher quantity of minutes is now taken into account. See also Absence Priority .

Bugfixes

Only concerns on-premises customers. The bug that invoices can no longer be opened in the cloud clients if a non-cloud-capable accounts receivable extension is installed was introduced with version 6.4.0.17 and could be fixed with this version. It led to the following error message appearing when opening an invoice in the cloud app or the web app:

Die Aktion kann nicht durchgeführt werden, da keine Debitoren-Schnittstelle installiert ist.

The error occurred only when Restricted Scripting was not enabled.

Features

• Abacus accounts payable Webservice Extension: The Abacus Web accounts payable interface has been completely redesigned and is cloud-ready. All information can be found in the KB article Abacus Web Accounts Payable Extension .
• Support for multiple class settings: Starting with this version, several Class Settings can be managed in parallel per class. This is particularly relevant for Additional Features 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
    • Show Class Name
    • string representation
  • For the (default) list settings, the oldest class settings are always applied. The Save as Default 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-ready accounting interfaces: The handling of invoice addresses and personal accounts in list-based (all cloud-ready) accounting interfaces has been adjusted. This is due to the fact that 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 personal account of a superordinate address makes it impossible to determine reliably whether a new address has to be created in the 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 personal account is implemented in a similar way, so 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 an invoice address is assigned (via xRechnungsadresse), but no personal account is given at this address, delivers rechnung.personenkonto the personal account of a higher level (project or customer).
  • New: There is a new (derived) property buchungsadresse on the invoice, which always provides the address to be used when posting. The property rechnung.personenkonto then always provides the personal account of rechnung.buchungsadresse. This corresponds to rechnung.rechnungsadresse, unless this is a contact. Then 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.
    • Regarding the following extensions:
      • Abacus Web receivable interface
      • BMD accounts receivable extension
      • DATEV receivable interface
      • Run my Accounts receivables interface

• Removed shadow attributes from the invoice: The shadow attributes, which are used to save values in the database that are actually derived, cause that when certain values are read access then also a write access to the database takes place. On the invoice there are two of these shadow attributes, 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 display of budget details has been optimized by preloading the budget values.

Bug fixes

• Open a favorite in a new tab: If a favorite is selected while pressing the CTRL key at the same time, the favorite entry will open in a new tab. Previously, the entry might have opened in the same window.
• The problem 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 Up-To-Date Support Cases .
• Blocking the cloud app that could occur since version 6.4.0.15 has been fixed with this version. If the connection is lost, an error message is shown and the cloud app is completed as in versions prior to 6.4.0.15.

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 a ZUGFeRD PDF with version 2.0.1 or with the specified XMP scheme as before. 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: Our invoice reports have been changed with version 6.4.0.16 so that they use the fixed invoice address.
• Additions to the Abacus Web receivable interface: The Abacus Web receivable interface has been added. Please use version 6.4.0.16 for operation.

Bug fixes

• Posted accounts payable cannot be canceled: This bug was introduced with version 6.4.0.15 and fixed with 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 appear in the App Store and Google Play in the next few days.

Features

• Abacus Web accounts receivable extension: The Abacus Web accounts receivable extension has been completely redesigned and is cloud-ready. All information can be found in the KB article Abacus Web accounts receivable extension.
• Zeep whitelist for Restrict Scripting: The webservice Library Zeep (https://python-zeep.readthedocs.io/en/master/index.html) used for the Abacus Web accounts receivable extension has been whitelisted for Restrict Stripting.
• 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 show 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 ugly 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 displayed.

Features

• The app portal for cloud clients has a new design: As part of the redesign of the website, there is also a new design for the portal page. See the article about the App portal for cloud clients .
• Entering new accounts payable via QR code: A creditor including address entry (supplier) can now be created directly on the basis of a QR code. The exact process is described in the article Post accounts payable with vertec .
• Support of invoice date in QR codes for payable accounts: If the invoice number, due date and invoice date are known in the QR code, the information is set on the creditor when reading (see above).
• Support of invoice date in QR codes for receivables: 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 processor totals and invoice with phase totals output the corresponding information as additional information:

  

  See also: Prepare invoice templates for qr code
• Permissions for BI measures: Users can now be granted rights per BI measure. The exact procedure is described 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 measure, 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 .
• The criteria for who sees which folders in the BI tree have been adjusted. The detailed description can be found under Business Intelligence .
• Sharepoint Online DMS interface – 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 user, invoice, address or project. The activation is the same as before, only the underlying example implementation has changed. If this example implementation is used in another extension, it must be adapted 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.
• Fastviewer Fastviewer upgraded to 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 problem with endlessly running Excel EOBs introduced with version 6.4.0.9 has been fixed.

Bugfixes

• Detecting suspended TaskRunner processes correctly: There have been cases where Taskrunner processes were stuck but not correctly detected by the Cloudsever. This has been fixed in this version.    

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 setting the [CloudServer] section in the Vertec.ini file:

  Restrict Session Process=True

  For more information, see the description of the parameter. This setting is automatically activated
  in the Vertec cloud suite from this version.

• Support for Loggly in the desktop app: Applies only to on-premises customers. 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.
• Upload of open Word Templates possible: When using the report templates directly from the Vertec database introduced with version 6.4.0.10, the templates had to be closed before they could be uploaded to Vertec (explicit access). This hurdle has now been eliminated, now open templates can also be loaded.

Bug fixes

• Phases lookup renderer in weekly capture table: If there is a column in the weekly capture table for phases with the rndMainPhaseLookup renderer, the phase was not set when capturing 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 to the user in the tree above the service entry, and at the same time the option Save session settings is not set, Vertec will not start anymore. This issue has been fixed.

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. Existing 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 Changeover 6.4.0.10: Report templates no longer described on the file system.
• This also eliminates the system setting Template path for Word reports: scripts that access this system setting must be rewritten accordingly. The exact procedure is also described in the article Conversion 6.4.0.10: Report templates no longer on the file system.
• DMS Sharepoint extension: Passing activity when saving report documents. The StoreDocument(self, vertecFilePath, content, aktivitaet) method prepared with version 6.3.0.12 now passes the activity as an object. With this 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 until now, system settings could be changed using the config set, but not created new ones. System settings can now be passed as normal objects in a config set, with all their properties specified. The exact procedure is described in the section Creating 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 described in the article Vertec Python Features .
• The payment type ComboBox (PaymentTypeComboBox) allows you to select only active payment types. This applies in the following places: “Settings” page on addresses, “Accounting” page on project and project type, and for payments.

Bug fixes

• Create addresses in all clients with creditor extensions works again: The problem introduced with 6.4.0.1 that create addresses in all clients only created the address in default clients has been fixed, see Open addresses in all clients / system setting Sage50.
• 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 to save: 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.

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 name 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 customer payload data, namely whenever it happened to be the same. For example, “PM” is always shown as “PL” in the tree in a German vertec (because “PM” 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. Existing 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. Allows 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. Detailed information is described in the Logging article.
• Expanded BI URL: The URL support for business intelligence (BI) ads has been expanded with the following properties:
  • Date range
  • Selected display
  • Selected measures incl. sorting and color

  For more information, see the article on the BI Anz own.

• Saving the configuration of BI views in favorites: It is now possible to save BI views as favorites. These are displayed with all parameters (see above) when invoked. BI ads saved as favorites receive a designation according to the pattern Node (BI): Displayname, for example Projekt (BI): Bearbeiter. In this way, the BI ads 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 interface has previously 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 receipts in the phone app: Now you can also post PDF receipts 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 entitlement type, currency, VAT type, 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 all 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 applied column widths from the template has been fixed.
• The Abacus web service payment reconciliation 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 appear in the App Store and Google Play in the next few days.

Features

• Support for pinned columns in list settings: The first columns in lists can be pinned again by checking fixiert in list settings.
• Upload of DMS document to web app activity:
  • In the file selection dialog on an activity with DMS dock path, a local file can be selected. This is then uploaded to the DMS. The folder path corresponds to the dock path of the activity, the file name corresponds to the selected file.
  • vtcapp.requestfilefromclient can also be used in the web app.
  • 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().
• Supplementary logging:
  • 1. Loading objects from the database: Using the value DebugCategories = Vertec.PMappers in the [Log] section of
    Vertec.ini allows you to observe the loading of objects from the DB.
    The Persistence Mapper log entries will only appear if they are activated via DebugCategories (Category DEBUG)
    . Note that this type of logging should only be temporarily activated, 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).
• Detect and stop 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 run time for a scheduled task can now be specified at Task Scheduler Max Minutes. The default value is 1200 (20h).
  • If a process runs longer than the maximum time, Cloudserver automatically completes it.
  • Exiting 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-ready accounts receivable interfaces) take into account successful posting line by line: only the posts of a list that are actually posted will now appear as posted. Until now, the entire list was marked as posted, even if some of the posts in the accounting system failed.
• The Run my Accounts extension now posts the settlement of advances correctly. The downpayment is posted negatively during settlement.
• VisibleExpression on TableRow is now evaluated.
• Web App: The Index field in the Properties folder is shown again.

Bug fixes

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

Features

• New property Icon Index for subfolders on folders. If an icon index is used there, each newly created subfolder automatically gets this icon.

Bug fixes

• Fixes a number of issues with Advanced Office Reports and Restrict Scripting (especially cloud suite). Affected were running Advanced Office Reports via Python Script, calling vtcapp.rendertemplate, and returning date values from Python dialogs.
• 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 avoids errors when loading the Firebird database driver on client machines. As a consequence, when uninstalling a Vertec installation on the client machine, Firebird must be uninstalled separately, since this is not possible automatically for security reasons.

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 (no specification) 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.
• Performance improvement in lists without aktiv members: lists evaluate whether an object is active or inactive to show it in the first column with the gray bar accordingly. For objects that do not have aktiv members, this check has been disabled.
• Caching web app resources can lead to 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 transmitted several times. However, when changing versions, this can cause some resources to become obsolete. To fix this, the resources URLs 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 loads faster, but when scrolling down, objects must 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 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 hindrance. Therefore, this special treatment has been extended again with 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 up-to-date support cases.
• An error that could occur during payment reconciliation and lead to an error message “... is not a valid date” has been fixed.

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. The exact description can be found in the Vertec Python Features .

• Removed Test Data and Execute button on Advanced Office Reports. Removed 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 problem that could lead to an error in the context menu on invoiced invoices in the web app since 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.

Bug fixes

• Fixes a performance issue with 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 up-to-date support cases in the Vertec installation directory by default.

Features

• Change data type for CustomPages: Text instead of Blob. In Class Settings > Pages > Customization, the data type of the field has been changed from Blob to Text. This fixes that older config sets imported into Vertec 6.4.0.1 (and vice versa) that include Page Customizing cause an error.