Vertec version 6.8

Features

• Search results enhanced: When searching for phases, outlays, services and expenses, the relevant project is shown in the list of search results as of this version.
• Python function extractplaintext extended: The Python function vtcapp.extractplaintext has been extended with the optional attribute extension. If an extension is passed, it is used to determine the file type. Otherwise, it will try to determine the file type based on the file content passed. Valid extensions are .pdf, .docx, .doc, .eml/mime and .txt. You can find further information in Vertec Python functions.
• Python function setdocumentcontent extended: The Python function activity.setdocumentcontent sets the creation date of the activity (createdate) as the modification date (documentmodifiedon) by default when saving the document. If you want to change this, you can now use the optional parameter ModifiedDate mit Default None, which can override the modification date. For more information, see Vertec Python functions.
• Moved activity types to other folders: From this version onward, the activity types are saved or managed under Settings > CRM, instead of projects.
• Adjusted the default settings in the zip code folder properties: In the property of the zip code folder (Settings > CRM) the Expandable checkbox is now deactivated by default, instead of activated.

Bugfixes

• Fixed error message in query folder: The error message "Unknown table (...)" appeared when defining queries, if a folder of a class was selected that existed in the data model (class with table mapping "parent") but does not directly exist in the database. The issue was fixed with this version.
• Fixed errors due to overwritten identifiers : With the implementation of the English model language, all identifiers (entry ID for objects or propertyName for properties) have been translated. Importing config sets could lead to overwriting them, (DE > EN) and thus, for example, existing queries with string comparisons resulting in error messages. 
  As of this version, identifiers found in the target database are no longer overwritten and identifiers not yet found are created with a new entry ID or a new propertyName.
• DB convert timeout extended: The DB convert could abort with a timeout when reading the source database on larger Microsoft SQL databases. Therefore, we have increased the timeout when reading the source data to 24 hours per table.
• Query of objects with the same entry ID: If two objects with the same entry ID, but different classes, are queried with the Python function vtcapp.getobjectbyentryid, it could happen that the object of the correct class was not returned, but instead the topmost object in the cache. With this version, the query checks for the correct class and, if it does not match, the query uses the database to return the correct object.
• Fixed incorrect behavior when entering services via Vertec Outlook App: When entering several services via appointment in the Vertec Outlook App, the service could be unintentionally assigned a service type, or the second service entered applied the service type of the first, even though no service type was selected. We have fixed this issue with this version.
• Fixed Excel export error: The OCL variable varContext could cause an error in Resource Planning when executing an Excel export. This issue has been fixed with this version.
• Removed unintentional checkbox on expression folders: When a query was defined in an expression folder, the Active only checkbox appeared below the search field. This was unintentionally displayed and had no effect. We have fixed this bug with this release. See also: Active only in expression folders.
• Corrected typo in extension code: We corrected a typo in the code of the Abacus Web extension..

Bugfixes

• Create schema with MS SQL is possible again: You can create the Vertec database schema for MS SQL Server via /DC. The exact procedure is described in Microsoft SQL Server.
• setresourceplanvalue() creates new objects instead of overwriting the existing ones: Setting resource plan values via setresourceplanvalue() no longer creates multiple (identical) objects, but overwrites the existing ones. See also: Custom Resource Planning with Python setresourceplanvalue().
• Python dialog shows selection again: The dialog, which is called via the Python function vtcapp.selectobjectintree(), shows the selection in the tree in color again. See also: Current support topics
• Saving receipts on outlays is possible again: In addition to creditors and expenses, receipts can now also be added to outlays. See also: Current support topics
• Texts with more than 32766 UTF-8 characters can be indexed again: Indexing for full-text search was not possible for texts with more than 32766 UTF-8 characters. Consequently, the relevant object could not be found in the search. We have fixed this issue.
• vtcapp.sendmail() fixed: With Vertec installations where vtcapp.sendmail() was not used before 6.7.0.4, the error SetMemberOutOfDate, obj argument is nil could occur when executing the function. We have fixed this issue.
• Improved performance of selection fields in lists: When the spellcheck was activated, some delays were experienced with selection fields in lists, e.g., when selecting a project for time tracking via cmbProjekt. We have fixed this issue. See also: Current support topics
• BI number output in Cloud App with regional setting Germany corrected: In the Cloud App, incorrect values could be shown in the BI view when the Windows regional settings were set to German(Germany). We have fixed this issue.

Features

• Template folder for project search: Start with this version, a separate SQL folder can be defined for project search. It can be stored in the system settings project > Template folder for project search is stored and appears in lists when using the edtProject control. For detailed information, see the article SQL Search Dialog for Project References.
• SQL Logging fully extended: The ability to write log output to the LOGDATA table in the database has been fully extended as announced in the 6.8 release notes. If there are still settings in the Vertec.ini file (SqlLogTable), these are ignored.

Bugfixes

• Full-text search now also possible with / in the search term: The full-text search crashed when searching for terms that a / included. The problem has been fixed with this version.
• Full-text search Sort by relevance corrected: When sorting search results by relevance, there was some ambiguity due to the score displayed in the tooltip, as it is also sorted by date, which could result in a higher score being shown further down. This problem has been fixed and the display of the absolute score has also been removed.
• System setting “Show totals” is taken into account: If the system setting Show totals is disabled, the totals are still shown. This has been fixed in this version.
• Expressions of constraints are no longer overwritten: The expressions of built-in constraints were translated to English in an update to 6.8 and also overwritten existing (and possibly modified) constraints. With an update from version 6.7 to 6.8.0.4, this no longer happens. Installation already updated to 6.8, where the expressions have been changed, has to be manually adjusted again.
• List settings editable in Resource Planning: List settings could not be edited in Resource Planning. The problem only occurred with model language German and has been fixed with this version.

Features

• Python function for full-text search has been extended: The Python function vtcapp.search() now includes the property onlyactive, which you can use to define whether only active or also inactive objects should be found. You can find comprehensive information about this in Vertec Python functions.
• Indexing of phases is now possible: Members of phases can now also be indexed for full-text search.

Bugfixes

• Scheduled task “Recalculation of index statistics” without BI check: The scheduled task threw an error with an unlicensed Business Intelligence module. This has been fixed with this version.
• Fixed the issue with Excel reports: Creating standard Excel reports could trigger the following error message in the Vertec Desktop App and the Vertec Cloud App: The file " could not be saved. The file type " is not allowed to be saved without user dialog. This has been fixed with this version.

Bugfixes

Number format is now correct in Vertec clients. Fixed the problem that the regional settings were not set correctly by the sessions to the value supplied by the client.