New features, improvements and bug fixes done for version 2.5.0

Table of Contents

Advanced Search

Done under JIRA issue [HDC-471] - As a user I can use advanced search to find specific objects

See this guide for more information: Advanced Object & Document Search

External documents handling

Done under JIRA issue [HDC-123] - (DV) As a user I want to view selected external document content (PDF, Word, Excell)

HDC can now display external files like MS Office documents in viewer. If you add one as attachment to document object then HDC will convert it's content and display it in special PDF viewer.

Sample .docx document uploaded to HDC:

Accepted formats are:

• doc, docx, xls, xlsx, ppt, pptx, odt, ods, pdf.

If for some reason conversion will fail (not accepted format or corrupted file) then proper information will be presented.

Custom number of decimals

Done under JIRA issue [HDC-1885] - Can we set number of decimals for areas, length, coordinates?

Administrator can now set custom number of decimals that will be shown on dialog across HDC.
This settings will influence areas, length, coordinates and class fields of float type.

In System Settings, General Setting tab new section Field adjustments is present with one new parameter Number of decimals.

Export and Import of Print templates between databases

Done under JIRA issue [HDC-2251] - Export and Import of Print templates between databases

To export print template/s to .json file go to Administrator panel -> Export/Import Config, select export option with Print Templates and click on Export button.

You will be prompted with window in which you can select print templates to be exported.

To import print templates on same or different database click on Import button and provide exported file. 

Skip Matched: 

• if not checked, all print templates from file will be added even if templates of same name exists (content will be overwritten);

• if checked templates of same name will not be updated.
  
  

  If template uses print format that is not present in destination database then such template will not be added.

Save area from vector object to linked hierarchy object

Done under JIRA issue [HDC-334] - As a User I can save area from vector object to linked hierarchy object

Saving area from vector objects on drawing to linked hierarchy object is now possible based on Layer Relations mapping.

First, Layer Relation must be created. It's a relation between specific layer and object's class field.
When invoking new functionality area from spot on layer from Layer Relations will be put into linked object's class field (defined in relation).

Save area functionality can be triggered from context menus in various places:

• On selected Tree object (that is part of layer relation).
  
  Using option from this place will save area from all spots on all layers that have layer relation defined to proper selected object's fields - based on layer relations.
  
  
  
  
• On Drawing context menu (outside any spot area) we can save area from all spots and all layers (or selected layer) to linked objects based on defined layer relations.
  
  
  
  
• On selected spot's context menu or pop-up properties. This will save area from all spots on all or selected layers linked to object from layers relation.
  
  

FI2 v1.3 import from section fi2sender

Done under JIRA issue [HDC-2289] - FI2 v1.3 import from section fi2sender

Custom mapping can be now done for FI v1.3 imports.

Sample XML:

<fi2space_value>
<fi2value_code>Fastighetsbeteckning</fi2value_code>
<fi2value_scheme>
<fi2scheme_name />
<fi2scheme_url />
</fi2value_scheme>
<fi2value_value>264004</fi2value_value>
</fi2space_value>

To import values from <fi2value_value> tag, new class field Fastighetsbeteckning must be added to selected object class in Object Classes for External Domain and then in Object Mappings this field must be mapped with destination field.

FI2 v1.3 - new ways of reading reading External IDs

Done under JIRA issue [HDC-2324] - FI2 import External ID reading

HDC will recognize GUID field of imported objects as External ID. Two ways of providing this GUID in imported XML are possible:

• As imported object's atributte:

  <fi2property id="045" guid="2d51fd43-a5ff-43ec-bb1e-7d6a222dca7a">

• As imported object's child element:

  <fi2floor id="ID000004">
  	<fi2spsys_ids>
  		<fi2_id usage="Planbeteckning" owner="Symetri" origin="">Plan 1, bottenvåning</fi2_id>
  		<fi2_id usage="GUID" owner="Symetri" origin="">F472VAN472U1367@1</fi2_id>
  
  

Bugs fixed and other improvements for this version

• [HDC-2086] - TDXM import with fi2 ver 1.3 does not recognize correct data tags
• [HDC-2279] - Mark subtree selects false perspective
• [HDC-2311] - Bug when trying to open dashboard from administration panel
• [HDC-2315] - Tdxm Import Log Details grid does not display data
• [HDC-2303] - Better visibility for info messages on login screen
• [HDC-2301] - Excel export failure
• [HDC-2320] - Import log does not refresh when selecting another import in list.
• [HDC-2328] - LackOfPrivilegeError when getting class info, if there are no View rights to given class.
• [HDC-2330] - Cannot Edit user name, fullname, description..
• [HDC-2290] - Special characters in object names - error multiprint zip package
• [HDC-2303] - Better visibility for info messages on login screen
• [HDC-2324] - FI2 import External ID reading
• [HDC-2326] - Advanced search improvement
  
  
  

API Changes

(check /apidocs for more details about new/changed webservices)

• Done under JIRA Issue [HDC-XXXX] - JIRA Issue name

  
  

  Old Webservice: 
  

  METHOD /PATH

  New Webservice:

  METHOD /PATH