Page tree
Skip to end of metadata
Go to start of metadata

New features, improvements and bug fixes done for version 4.1.0

Table of Contents

User related changes

Automatic object labels

Issue [HDC-3133] - Function to automatically add text macro from Room via linked spot on drawing

Dynamic labels can be generated on the drawing to display object metadata, similar to macros but placed automatically for every object that is represented on the drawing. 

Labels can be shaped according to user needs - from simple, single text value to more complex table with labels and header.

Data within the label can be fetched directly form a selected object or from other objects based on data perspectives, e.g. from upper floor or rental unit.

Labels are defined in similar way as visual, color based presentations and follow similar rules:

  • they are displayed as read only element on the drawing
  • they are printed together with the drawing
  • they can be controlled through API, e.g. for HOPA integration calls, for CopyView etc.

For more information on how to use automatic labels, please visit this page: Dynamic Labels

Sample labels:

Editing multiple objects at once

Issue [HDC-962] - I can edit multiple objects of the same class at once

New mode for editing multiple objects of the same class was added. The new function is available in Tree View, Grid View and as a context menu for editing objects linked to spots. 

Regardless of the function source the same dialog is used for editing and the same rules apply. 

Editing from Tree View

  • First, select two or more objects that you want to change. Use Ctrl or Ctrl+Shift keys to perform multi selection.
  • Right click on any of the selected objects
  • A context menu with multi edit menu option will be shown
  • Please note that the selection must consists of the objects of the same class. Otherwise the option will be grayed out. 

Editing from Grid View

  • Select a number of records from the grid using "check selection"
  • Use Object menu to select Multi edit function

Grid View allows editing objects from grouping tabs. For example, multiple document classes can be edited from the Document tab.

In that case a general schema for Document will be used, so only common properties can be updated. 

Editing from Viewer

  • While in Select/Object mode (default) select a number of spots on the drawing (two or more).
  • Right click on any of the spots to show context menu
  • Select Multi Edit function. Please remember that the default objects linked to selected spots must be of the same class

Common Multi Edit View

All the above editing functions will end up showing a common multi edit view:

Specifics of using multi edit view:

  • System will compare all objects and provide common set of properties
  • You can expect the following results
    • <Multiple Values> shown as a field background means that objects do not have the same value in that field. 
      You have an option to enter a common value that will be assigned to all objects or use a Clear button to remove the value from all objects. 
    • Empty field - this means that all objects do no have value in that field
    • Specific value - this means that all objects have this value in that field
  • Required fields will not be validated unless you want to use clear function. Clear function will be disabled for required fields
  • Field validation rules will only be run for modified fields. In specific case when dependent field validation rules are set, 
    the validation might not be triggered on client side. If the rule is not met when values for a specific object are checked, the update might be rejected by the server. 
  • Reset button rejects your unsaved values, but does not remove the "clear" flags,

After the values are saved a simple report is shown describing if all selected objects were successfully updated. 

Object selection in Document Viewer is now synchronized with Grid List

Issue [HDC-3572] - Infoscope like function in grid list

A new functionality has been added that synchronizes spot clicked on a drawing with linked object on Grid list.

Two new options were added to User Profile\Document tab\Drawing Settings section:

  • Viewer - Grid Sync Back: when this option is turned ON, clicking on spot that has an object link, will automatically select corresponding object in Grid View.
    • A new data page might be loaded to allow selection
    • Selected object must be available in current Grid View perspective
  • Viewer - Grid sync: allow class change
    • If this option is disabled, a Grid View synchronization will happen only when object selected is of the currently active class. 
    • If this option is enabled, system will change the active tab (class) to show desired object

Those are default option that are used for user. They can be changed during work in viewer from Setting menu in Document toolbar.

Move vectors including object links from one drawing to another

Issue [HDC-3565] - Move vectors including object links from one drawing to another

When pasting spots from clipboard, there are a new options to paste them with information about original spot's layer and it's link.

Copied or cut spot/s will be placed on same layers as original one/s regardless of chosen layer in Drawing&Layers combo and spot link will be preserved as well if the option is checked in Entity Transfer Options.

Please note that Paste option will not be active (will not work) if at least one spot copied is on a layer that user does not have Edit rights for or is Inactive.

  • Copied/cut spot can be pasted into different drawing but layer preservation will work only for global layers as local layers and redline layers are unique per drawing.
  • Moving spots from overlay to redline (and opposite) is possible but layer and link information will not be preserved. Spot will be added to layer taken from Drawing&Layers toolbar instead.

Copy or cut selected spots (in edit or redline mode):

Selected Layer is on NTA layer as per status bar indication in the bottom of screen.

Then select proper place on a drawing still being in edit or redline mode and use right mouse button to reveal Paste menu option.

If spot is pasted in Edit mode, it will be created on NTA layer, just as original one despite BRA layer is chosen in Drawings&Layers toolbar. If pasted in Redline mode, it will be created on redline layer chosen in toolbar. 

Entity Transfer Options are set per each user. Default state can be configured in User Profile and System Settings:

Visible indication of objects that have links to vector entity on drawing

Issue [HDC-3571] - Visible marking of objects that have link to vector on drawing

We have added additional Column in Grid called Linked to spot. It will be filled with icon if object from grid has link to vector entity.

Use keyboard short cuts to copy/cut/paste vectors

Issue [HDC-3665] - Use keyboard short cuts to copy/cut/paste vectors

When working with spots in Edit or Redline modes of viewer, users can use keyboard shortcuts to Cut (CTRL+X), Copy (CTRL+C) or Paste (CTRL+V) to perform editing operations.

Dictionary / lookup fields can be used as Label Fields

Issue [HDC-2477] - Use value of dictionary to show it as label field in Tree 

If dictionary field is set as a label field for an object class, then it's value (and not key) will be used in places like window forms, tree, macros etc. 
Here we can see an example, how it looks in Tree and Object Properties, when expanding Floor level to see Rooms beneath it. Rooms uses Function fields as a label and this is a dictionary field.

Marked is a room with "Production" dictionary value set for Function field:

Same value will be seen on Object Info dialog, Edit and Delete forms and Object Set window. It will will also be used as name of the printout if object is printed.

We can also see that there are number of rooms with square brackets and some text within them , like:
Square brackets indicate that field is filled with a value that is not from dictionary scope. This happens when data is imported from external source and values in that field are not found in HDC dictionary. 
We accept them and they are written to database but they not part of dictionary.

Minimize/restore the Advanced search window

Issue [HDC-3658] - Minimize/restore the Advanced search window

An option to minimize and restore Advanced Search window has been added.
It allows users to create search criteria and hide the window when not needed without losing typed conditions.

Then the restore button can be pressed to use search window again, from the point it was left.

Full view:

Minimized view:

Changing panel to any other (like Dashboard, Administration or other) will close Advanced Search window. Saving search query is recommended.

Advanced search - labels for fields

Issue [HDC-3707] - Advanced search, labels are missing

Labels for fields "Search field", "Type" and "Value" were added to Advanced search window.

Possibility to select Auto-Sum function to run only on selected level

Issue [HDC-3658] - Possibility to select on what level a smart field function should be run.

Auto-sum plugin can be additionally run on only-selected hierarchy level instead of subtree mode that run on all objects classes that had plugin configuration.

If Selected option is chosen then plugin will run only for selected object (based on plugin configuration for selected object class).

If Subtree option is chosen then function should work as before - that is for all object classes defined in plugin definition.

Improved sensitivity for vector line selection

Issue [HDC-3620] - Extended selection sensitivity for spot objects

This version introduces improved selection mechanism that will make it easier to select thin lines. So far a line had to be clicked exactly "spot-on" to trigger selection. 

Now, by default, and extended hit range is used. To further configure this option, you can use user settings panel:

  • Extended hit sensitivity - main option to enable this feature.
  • Only without normal selection -an example would be a rectangle with a line going on top of it:
    • when ON: extended sensitivity will be used to select objects only when normal selection did not select anything. When clicked next to line, a rectangle will be selected.
    • when OFF: line will always be selected if its within range. When clicked next to line, line will be selected. 
  • Hit range: this is a "virtual" rectangle that is used around cursor. If a line intersects with this rectangle, it will be selected. Value of 10px is recommended and set as default. 
    If you still have difficulties selecting a line, please increase this value to suite our needs. 

Data Exchange related changes

New version of Tobis integrated into HDC

New version of Tobis (Tessel OBject Identifier Server) has been integrated into HDC. Each object stored in the HDC database can be registered in Tobis by its GUID. If all objects are registered in Tobis HDC can be switch to Strict Tobis mode. In this mode HDC do not allow saving objects without a GUID.

Since object is registered in Tobis each calls for this object may use GUID only, instead of combination of classid and hdid or search field and serach value. 

Main Tobis configuration

Main Tobis configuration dialog box is available in HDC Administration: System/System Settings, TDXM tab, TOBIS subtab:

This dialog box consists of two panels: Object Classes and Unregistered objects.

  • Object Classes pane - contains list of all available object classes defined in the database. 
  • Unregistered objects pane - contains list of unregistered objects of class selected on Object Classes pane.

Commands available on this dialog box:

  • Auto register all objects - register all objects in Tobis with randomly generated GUID.
  • Enable Strict TOBIS - enable strict Tobis mode. Since strict mode is enabled status indicated on the right side is changed from Inactive to Active. 
  • Register by field - register in Tobis objects of selected class by GUIDs taken from selected field:

    In that case data taken from selected field will be used to register object in Tobis.
  • Auto Register - register in Tobis objects of selected class with randomly generated GUID.

Tobis configuration for internal domain

Two new columns in field configuration for classes in internal domain have been added: GUID field and Search field. 

GUID field - indicates that field is set as default source for GUID registration in Tobis. This means that during automatic registration of objects in Tobis data taken from this field will be used to register GUID in Tobis. 

Search field - indicates that field is set as default search field. Queries for objects without field name will use this field by default. 

Tobis configuration for external domains

Two new columns in field configuration for classes in each external domain have been added: GUID field and Search field. 

GUID field - indicates that field is set as default source for GUID registration in Tobis. This means that during import data from this domain objects will be registered in Tobis with GUID taken from this field. 

Search field - indicates that field is set as default search field.  

Raster file can imported in IFC import

Issue [HDC-2918] - Raster file to be imported with IFC package

A single raster file can be now be imported along with IFC import. Important things that needs to be done so the raster file is imported:

  • upload a zipped package with folder containing .ifc file and single raster file + optional .taf file.
  • raster will be attached to the document linked to any floor objects (IfcBuildingStorey in .ifc file) imported from package.

ObjectData import - add new objects via registered path

Issue [HDC-3377] - ObjectData import, add new objects via registered path

There is a new way to add objects of same class via ObjectData import.

Additional columns in excel sheet: Parent Object Hdid and Parent Object Class can be used to select parent or parents for the imported objects.

  • Parent Object Hdid is HDC internal system id (hdid field).
  • Parent Object Class is name of parent's object class that used in External Domain mapping.
  • Each of imported objects can be linked to different parent object.
  • Only single class of object can be imported (single tab in excel).

External Domain configuration 

(details for mapping parent class of imported objects - parent objects must already exists in database).

  • New columns represents parent classes so those classes must be added on Object Classes tab along with column's names as Class Fields:

  • On Object mapping tab parent classes should be mapped but only Parent Object Hdid field should be mapped with internal hdid

  • On Object Identity (TOBIS) tab, Parent Object Hdid field should be marked as Identity field for parent class


New import option was added to ObjectData import type called "Link to root only objects without parent".

If turned ON, object with filled parents columns in excel sheet will be linked only to those parents and objects without it will be linked to chosen Context Object (if any is chosen). 

Import option Context object option still will work as before. So new objects can be linked to single chosen parent object without using Parent Object Hdid and Parent Object Class columns (excel file can be without those columns or they can be empty).
If both ways are used in import (excel have Parent columns given and Context object is chosen), objects will be linked to both parents unless new import option will be used - Link to root only objects without parent.

Improvement to reports generation

When creating an excel Report with single object class (like from Advanced search for example), new columns Parent Object Hdid and Parent Object Class will be added automatically. To have them filled up, Administrator must set new system parameter Report Perspective Set in System Settings\General Settings. Then Parent hdid and Class Name will be filled in report cells based on chosen Perspective.

Parent hdid and class are taken based on chosen perspective in system settings. If the object is linked more than once in this perspective, first parent is taken only (PATH columns will still show all links for object).

Please also note that for exporting Documents with filled parent hdid and class, chosen perspective should be of "All" type (that is Tree classes in Perspective should have document classes as available classes).

System Administration related changes

Improvements to Security Audit interface

Issue [HDC-1788] - Log filtering (security audit) by date range

Filtering by Operation Type and by Date has been added to Security Audit panel.

Choose a filtering option that is desired and click on Apply Filter button to narrow the results. 
If you want to see all, click on the Show All button. 

Antivirus (AV) scan for uploaded files

Issue [HDC-1788] - Antivirus (AV) scan for uploaded files

Antivirus program will monitor all uploaded files to HDC. If malware is detected, a pop-up message will be shown:

Antivirus settings can be controlled in Admin Panel\System\System Settings\Antivirus tab.

For customers in server and port should not be changed. If needed, AV scanning can be disabled but it's not recommended.

Not supported field types hidden in object class configuration

Issue [HDC-3676] - Fields of type "currency" are not viewed in object edit form.

Some types of field available for object classes were added to list before they were fully implemented. They are no longer available in the UI:

Unsupported Fields

  • Currency,
  • Area,
  • Quantity
  • Length
  • UserPicker,
  • ColorPicker

Supported Fields:

  • None
  • Text
  • Float
  • Integer
  • DateTime,
  • Boolean,
  • Dictionary,
  • Serial,
  • GUID

Produced PDF's are of PDF/A standard

Issue [HDC-1004] - As a user I can get PDF that is ISO-standardized version of PDF (PDF/A)

All PDF's file that HDC will produce starting from version 4.1.0 will be created in PDF/A-2b standard.

This can be seen, for example when a file is opened by Adobe Reader.

Note a  blue header that informs about file being in PDF/A standard:

Service-level agreement (SLA) reports for each cloud based site

Issue [HDC-3643] - SLA Reports

We have added a way for customers to see site availability metrics from HDC application. 
This functionality require HyperDoc Administrator role.

Reports are available under User Profile\About\SLA Report tab

Interesting time frames can be chosen and then report can be downloaded as a file using Download button at the bottom of window.

Report can then be opened. It should look like this sample one:

Export and import of users via excel file

Issue [HDC-2578] - user+password list can be imported from Excel to FM Access
Issue [HDC-3663] - Administrative function to export user list to excel file

New options to import and export users via excel file have been added to Users Panel:

Export All Users 

Creates a .xlsx file with list of all users registered in the database along with data from all columns. This includes both active and inactive users (filtering in excel file can be done to distinguish them).

Import Users 

Allows to create one or more internal users based on data from excel file. Template format for import operation can be based on sheet created from Export All Users function.
Columns that are used when importing users are:

  • User Full Name,
  • User name  - must be unique,
  • Email - must be unique,
  • Description (optional).

Below is an example of data ready for importing to HDC that will create new users.

Please note that users that were created users using import function, must set their password before being able to log into system.
As there is no password required in the sheet (for security reasons), it must be set by the user, using activation token link from the welcome email or using forgot password function from the login page.

User input sanitizing - Strict whitelist mode (security improvements)

Issue [HDC-3649] - DEV: HTML tags are rendered in the interface

New strict security feature was implemented to prevent potentially harmful data input. When enabled, a so called whitelist user input check will be made.
This means that only allowed type of data can be added, for example as object name or other metadata. 

When enabled, this option will only allow for text and some basic special characters like text formatting: b, em, i, strong, u.
All other HTML (tags and attributes, scripts etc) will be removed.

Should this mode be too restrictive, it can be disabled. A basic input sanitizing will still be made to prevent potential XSS or SQL Injection attacks.
When disabled, only input recognized as dangerous will be cleared (that includes scripts, SQL, image tags and more).

(warning) For maximum security, we recommend leaving this option enabled.

Filter out users and/or sensitive user data in user picker dialogs

Issue [HDC-3667] - Filter function for viewed users in "share " lists

Users can be given "hidden" status.


Setting user to be a hidden one will make it not available in any "Share with" or "Assign to" dialogs.

On screen above we can see that users "Administrator 3" and "Administrator 4" are given hidden status. On a screen below, on User Picker those users are not available.

Also new security options has been added to System Settings that allows to hide user's username and/or e-mail in all non admin "share with/assign user" dialogs.
This way users without hidden state can be more secure by showing less data to other users.

User Picker with filtered out sensitive information will only provide user's Full Name data.

Settings for layers to set one layer "always below" others

Issue [HDC-3567] - Option in settings for global layers to set one layer "always below" others

We have added new parameter for Layers called Index. It can take value of any natural number.
It will decide about order of spots on a drawing when multiply spots from different layers are placed in the same area.

If index is changed, all layers will move to new index value.

  • Remember that layers are being versioned - their Index too.
  • When using option Change Order (Bring to Front or Send to Back) - those options will work only within spot's layer. It will not influence order of spots on different layers as this is now controlled by Index parameter.

Local layers and Redline layers also have this parameter - it can be controlled from Composite Drawing Manager. 

Extension functionality of Math Basic operation plugin

Issue [HDC-3469] - Extension of Math Basic Operation plugin

Before, this plugin took a value from selected object's field and perform chosen math operation with given value (selected in configuration). And the result was put into desired field of same object.

We have now extended this Smart Field so the result put into desired field of chosen object class can be taken from result of math operation of two values that both comes from object's fields. It means that there is a possibility to set value for a chosen field by performing math operation on two other fields of same object as selected or their ancestors in given Perspective.

  • Fields chosen for math operation cannot children to the main object class. You can either choose fields from same object class as destination field or their ancestor in given Perspective
  • If object has more than one ancestor and chosen field for math operation is to be taken from ancestor class then first one (random) will taken for the operation.
  • Empty fields are treated as 0 for math operation.
  • Fields with text will make plugin run end with Failure.
  • Current configuration should be saved and working as before after upgrade to new version.

Mobile Application

Possibility to edit shape style and Edit layer style

So far only simple fill color change was possible on a mobile device. 

Now a new way of changing all style parameters is available. Select a shape and use style (palette) icon to open up a style dialog:

Here you can change fill and stroke color as well as line (border) thickness by specifying units and value:

Note the "undo" button next to each style option. If this button is active it means this shape has individual style assigned to it. 

You can use the undo button to revert this property to layer style. If the button is grayed out, it means the dialog is already showing a layer style applicable to this shape. 

In the same way a shape style can be changed. Please open up Drawings and Layers manager, select a drawing and then a layer. Swipe layer to the left reveal style edit button. 

Increased sensitivity for line selection

As for desktop version, mobile client also supports extended line and poly-line hit sensitivity.

On a touch device, the hit region is automatically enlarged to allow for smooth selection of thin lines using a finger tap.

A line closest to tap location will be selected (within detection range):

Navigation from Activity List and from Change Requests console

Activity list on a mobile device now supports object navigation or other "action buttons". Please select activity by taping on it. Appropriate action will be visible on the bottom toolbar:

If the event listed on the activity list originates from a different system version, a user will be prompted for possible version change. 

An example would be a redline that is shared on a document. If that redline was made in a different system version, or maybe a draft,

a user can automatically change current version to the correct one and perform auto navigation to object:

(warning) Note: a version change might not be available to given user if, for example a Draft is not shared with that user and is therefore unavailable. 

In similar way navigation form change requests is available. Now the navigation also supports post navigation actions. like changing mode. 

When navigating to Change Request, a mode will be automatically changed to Change Requests mode. Now mobile app also supports single request mode, for showing resolved requests.  

Bugs fixed and other improvements for this version

    • [HDC-2736] - Links added in wrong direction during import
    • [HDC-2917] - Case insensitive object identification in TOBIS could lead to wrong IFC imports
    • [HDC-3209] - Strange links 
    • [HDC-3362] - Empty zip file generated by the export function
    • [HDC-3588] - Xpandexports are registered under Import instead of export
    • [HDC-3611] - Why can not Filterwindow be closed in HDC? (in this case)
    • [HDC-3624] - Wrong paths prepared from existing links
    • [HDC-3657] - HOPA call not working until order of parameters are changed
    • [HDC-3675] - Error in Excel report
    • [HDC-3676] - Fields of type "currency" are not viewed in object edit form.
    • [HDC-3678] - PDF print not as viewed in FMA or preview
    • [HDC-3685] - Object report with template
    • [HDC-3693] - HDC failover with multiple ldap servers
    • [HDC-3694] - Path is not being filled
    • [HDC-3696] - Client viewer freezes when adding new document from grid when attachment was viewed
    • [HDC-3705] - Ad-hoc filter ignores stroke-with from filter definition and default tool
    • [HDC-3456] - SSO: Restart of FMA application if new customer certificate is found
    • [HDC-3578] - Support for large data sets export to Excel (chunked mode)
    • [HDC-3583] - Load 3D model in solid mod
    • [HDC-3584] - Zoom to selected object i 3D model
    • [HDC-3585] - Load 3D model in Skyviewer just by click of button
    • [HDC-3659] - User list filter function to support Description field
    • [HDC-3684] - New HOPA parameter for displaying labels
    • [HDC-3686] - Attachment Converter fix - Damaged XLS attachments
    • [HDC-3707] - Advanced search, labels are missing

API Changes

Embedded Viewer API changes

Clear View


Function used to clear the viewer content on demand. 

Show Multi Object

HD.EmbeddedApi.showMultiObject(gridObject, viewerObject, domain, viewPreference);

(warning) Grid Object or Viewer Object must be provided in the following form:

	objectId: 123,
	classId: 456

When domain ID is used, classId can also be your external class name.

gridObjectObjectOptional object that will be loaded into grid view.

Optional object to be loaded into Viewer

(warning) If this object is present, initial load will not be synced between Grid and Viewer!

The grid might have selected an object that is different from the object in the Viewer.


If floor object is given as first, it will load a default document for it in the grid.

If a Room object is given to Viewer (as second parameter) it might load entirely different document where the rooms spot is located.

If a Room has multiple spots on multiple documents, Viewer will provide interface for navigation between views (only when Toolbar is visible).


See viewPreference for showObject(); for base options

For this function, when Grid View is enabled, additional parameter can be used:

  • autoSyncGrid

Using Auto Sync Grid View Preference

When View Preference parameters include {autoSyncGrid: true} value, it will result in the following behavior:

  • A Grid object must not be given explicitly (it will be skipped)
  • When Viewer Object is resolved, for example for room we will find a document where the room is located, it will be used as an argument for grid sync.
  • To display this specific object (document) in grid view, we will search for parent object of this document, typically a Floor.
  • The Floor object in this case will be used to populate grid view.

(warning) Note: this mode will work fine in simple linking scenarios. If a Document that was located via Room spot is linked to multiple Floors, the first Floor will be selected. 

If the linking situation is uncertain, use explicit object to load Grid. 

(warning) Grid sync will only be performed on full viewer load (when a document is changed). Sync will not be done when context object (e.g. different room on the same drawing) is selected and shown. 

Possible use cases for showMultiObject:

HD.EmbeddedApi.showMultiObject(null, {objectId:'6993874f-d13b-47be-a281-cfee3af58ace' , classId:'fi2space'}, 523, {autoSyncGrid: true});
Grid Object: nullGrid Object is not given so it will not be loaded explicitly
Viewer ObjectViewer object is given. Its a Space object that will be loaded via InfoScope mode when spot link is present.
Domain ID: 523Domain Id is given, so Viewer Object will be looked up by using this domain config
viewPreference{autoSyncGrid: true} auto sync is set to true. This will trigger grid sync.

HD.EmbeddedApi.showMultiObject({objectId:'c3e1192e-57cf-4ecf-a857-e77b6ed98524' , classId:'fi2floor'}, {objectId:'6993874f-d13b-47be-a281-cfee3af58ace' , classId:'fi2space'}, 523);
Grid Object

Grid will be populated with child objects of this object according to perspective.

(warning) A default document will be selected but it will not be synced with Viewer, as the Viewer has its own argument object.

Viewer ObjectViewer will attempt to show this object using basic resolving logic (for document via spot or default document)
Domain ID: 523Domain used for Grid and Viewer object lookup.

HD.EmbeddedApi.showMultiObject({objectId:'c3e1192e-57cf-4ecf-a857-e77b6ed98524' , classId:'fi2floor'}, null, 523);
Grid Object

Grid will be populated with child objects of this object according to perspective. A default document will be selected and it

will become an argument to Viewer.

Viewer Object: nullViewer will accept selected object in the Grid View.
Domain ID: 523Domain used for Grid and Viewer object lookup.

Function changed


Now this function will clear the viewer if conversion of object fails (object is not found in internal domain)


new PageBus type event:

  • ui.docview.document.clear 
  • ui.docview.document.ready  

can be used together with existing event:

  • ui.docview.document.load

(warning) Document "load" will only be fired on actual document load and will not be fired when only object context was changed.

Context change happens when the same document is used to show another object, e.g. Room. Instead, you might want to use 'ready' event, unless you are interested in actual load event. 

Behavior changes

The viewer will be cleared of content in case:

  • conversion of object fails (object is not found through given domain parameters)
  • object does not exists or cannot be shown 

Layout Options

New parameters are added to control visibility of the GridView.

When EmbeddedViewer mode is used, additional parameter can be added:

ParameterAccepted values



Grid View in embedded mode runs in a headless mode (no toolbar) and uses default perspective set to load data. To change the perspective set, please change a default assigned to your integration user. 

General API changes

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

  • Issue [HDC-3377] - ObjectData import, add new objects via registered path

    Old Webservice: 

    POST /api/tdxm/import/ObjectData/<package_id>

    New import option available for ObjectData import: link2RootOnlyObjectWithoutParentLink (boolean)

  • Issue [HDC-XXXX] - Issue name

    Old Webservice: 


    New Webservice:


  • No labels