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

New features, improvements and bug fixes done for version 2.8.0 and 2.8.1

Table of Contents

Application State Management

Done under JIRA issue [HDC-2216] - Adjustable field width for columns in grid view
Done under JIRA issue [HDC-965] - As a User I can change order of columns in Grid View Tesslet so that it remains this way even after reload
Done under JIRA issue [HDC-2545] - Improvment for loading new default version (keep selected objects on application reload)

Main application window features state management capabilities that help the user to maintain current layout settings that include:

  • Main panels layout and collapsed state 
  • Object data grids - column order, sort direction, width and visibility

Settings like width of the window will be restored each time a user logs in or switches view between different application windows. 

Please note that settings are saved in a given browser only. The same user on different machine/browser will have independent settings.

Application state is saved in local browser storage and as a result will be dependent on that browser.
The advantage is that it provides high performance and is dependent on a specific screen so that a user can have different settings on main work computer and laptop for example.
The down side is that settings like column order will not follow the user between devices.

Modifications in Grid View are saved per class chosen. Different settings are for e.g. Architect tab and different are for Document grouping tab.

Application will also sync last selected object data to URL visible in the browser. Object selection will be restored after reloading version or changing application views. 

Reseting all saved settings to defaults is possible using new Clear layout button available from User's button.

If the local storage capability is disabled by the user or an administrator, application will try to fall back to storing state in cookies. If they are disabled as well, this functionality will not be available. 

Local storage is available in the following browsers by default: IE11+, Edge 16+, Firefox 58+, Chrome 49+, Safari 11+

Improved Text editing options

Done under JIRA issue [HDC-2224

Grips available for text elements

A set of nine grip points are displayed over text entity when selected. In editing mode, you can drag each grip causing proportional change of text size.

Grips are displayed at corners of text box, on text baseline, and in the center of such defined constructing lines.

Text alignment

One of three points on baseline is displayed as small circle and marks text anchor point. You can move the whole text dragging its anchor point. You can right-click on any other point and choose option "Set as anchor point" from right-click popup menu. Resulted anchor point will be set on corresponding point on text baseline. It changes behavior of horizontal alignment.

Changing horizontal alignment doesn't change text position. However, in individual but multi-line texts, each line would become aligned left, centered, or aligned right, accordingly.

Currently there is no possibility to redefine vertical text alignment.

Try changing the Anchor Point (right click on any grip) and observe how the text size is changed depending on the location of the anchor: left, center or right:

Proper control of text alignment is especially important for dynamic texts. Text will expand differently, depending on selected anchor point. The anchopr point, or alignment, can be also controlled by using three dedicated buttons on a text edit popup:

Text size

On text editing dialog, there is numeric control allowing you to enter text size.

It's important to remember, that font size is presented in units associated with the entire composite drawing. This may lead to some ambiguity when placing text e.g. on floor plan. Letters of readable size would have height expressed in meters, e.g. 1.2 m. If composite drawing has units in mm, it would be 1200 mm and so on.

Having diferent drawing sizes and scales, it's impossible to sugest single values that will always give the same results. A system will try to automatically suggest a proper text size that is readable at the given drawing and zoom level. 

To help keep consistent font size during text editing, following rules have been implemented:

  • first text placed on the drawing has a size deducted from system defaults;
  • successive texts obtain the same size as recently defined text;
  • after changing size of some text, it becomes default for next texts;
  • after loading previously saved drawing, size of most recent text becomes default one.

Editing group of texts

After selecting several texts, or group containing texts, on right-click popup menu there is an option "Edit group of texts". You can choose this option to edit these texts in a common way.

You can apply font family and text style (bold or italic) to all selected texts at once. You can increase or decrease text size in common way, or enter common value for all texts at once.

You can adjust text anchor for group of texts. It causes all individual texts to be aligned left, centered, or aligned right, accordingly.

First, select a group of random texts, right click and select Edit Group of Texts:

When a group editor is shown, select common values and alignment to achive desired look and text positioning. 

Group of texts that are randomly placed at the beginning, become arranged consistently and uniformly using alignment and spacing buttons.

Additionally, you can adjust vertical spacing between lines of text using additional buttons controlling line spacing, by increasing or decreasing it:

During editing, you can move the whole group of text by dragging its "diamond" central point, adjust individual texts by dragging its anchor point, or even change text succession one under another, and then level out these changes using alignment and spacing buttons.

Default settings for new texts

New texts are created with default settings that can be set as global defaults by an Administrator or changed by each user to reflect their preferences.

To change text defaults, go to your User Profile and change navigate to Redline - Text tab like so:

Special object field types to build custom string/numeric values based on other fields or objects

Done under JIRA issue [HDC-2475] - Use special object field types to build custom string/numeric values based on other fields or objects

Description can be read here.

New system macro "Document label"

Done under JIRA issue [HDC-2503] - New system macro for getting object class label for used object (document)

New system macro "Document label' is now availble. 

It can be added to each print template and when such template is used for print it will resolve into label of document class containing shown drawing.

HOPA DocForSpot fallback

Done under JIRA issue [HDC-2531] - HOPA DFS=1 fallback to DFS=0 when there is no spot link

Using DFS=0/1 will now only proritize HOPA mode. HOPA is first called with chosen parameter but if no document to show is found then second mode is tried.
If DFS is not added to URL then default value (0) is used first, if it fails then DFS=1 is used. 

Configurable response image for failed HOPA call

Done under JIRA issue [HDC-2519] - Configurable response image for failed HOPA call

New HOPA Settings option have been added called Error text. If HOPA call fails to locate drawing to display then value of this parameter will be shown. 

Please do not enter signs &, < or > as values for this field.

Failed HOPA calls will response with blank image in requested format with text from HOPA settings.

New HOPA options: OutFormat and Download

Done under JIRA issue [HDC-2453] - HOPA new options: Return print in image format or regular HOPA call as PDF

Parameter OutFormat with values set to PNG or JPG will now work with TemplateID and TemplateName.
Result image will be wrapped in print template. Default value is still PNG but PNG/JPG format will not force use of print template.

New paremeter is now introduced: Download. If value is set to then it will sent requested hopa result directly into your browser for donwload.

New types of Object Fields: Serial and GUID 

Done under JIRA issue [HDC-2365] - Field of type "serial number" for object class configuration.

We have introduced two new object's field types: Serial and GUID.

Common features for both:

  • If there are not set during object creation then they are filled out automatically by system. 
  • There is additional constraint set on Serial and GUID fields to make sure that they are unique
  • Please note that conversion of objects with Serial or GUID attributes to another class could result in generation of new values for those fields (if they are present in new object class). 

  • It is recommended to combine usage of new field types with FLS subsystem - so they could be marked as read only and be handled by system automatically.

    Changing type of exisitng field to one of new type is not handled currently. If such request is needed it must be reported as special request to be perfromed on client database.

Serial fields

Serial fields are of integer type.
They have set a start value, to start numeration from it. This value is automatically incremented  (with step of 1) with every new object added.

GUID fields

GUID fields are of type text (so it is possible to set them manually with custom identifiers).
They are filled automatically with uniqe random numbers in format of XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.

Default perspective choice improvement 

Done under JIRA issue [HDC-2427] - Import option - Context Object Perspective to be more clever

For import dialog option Context Object and for Object Security, perspective initialy chosen is the one set as default for Tree View  in Layout Manager.

Links to spot visible in "Show link" window

Done under JIRA issue [HDC-1847] - Links to spots should be shown in "Show links" dialog

When checking selected object's links we will see additional tab "Spot Links" that will show list of spots linked to chosen object.

Removed dependency on external font downloads (missing icons)

Done under JIRA issue [HDC-2580] - Change font based icons to SVG based

Some icons in the user interface required download of external fonts to funtion properly. This dependency was removed.
All icons are now either image or SVG based.

(warning) Important note for custom menu items - icon syntax has changed. For more information please refer to Custom Menu Items

The dependency for text editor remains - fonts are downloaded from FM Access server. Missing fonts will result in diferent text appearance on the client and on the server side generated PDF.

Bugs fixed and other improvements for this version

    • [HDC-2439] - HDC produces very big pdf files
    • [HDC-2496] - HOPA call - double loading of the drawing structure
    • [HDC-2497] - Handling of float data type
    • [HDC-2566] - Batch print is using ambiguous ContentID
    • [HDC-2482] - FI2 import from CAD including several buildings/floors only imports vectors for one building/floor

API Changes

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

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

    Old Webservice: 


    New Webservice:


  • Done under JIRA Issue  [HDC-1847] - Links to spots should be shown in "Show links" dialog

    New Webservice:
    Get list of spots linked to selected object

    GET /api/object/linkedspots/{srcClassId}/{srcObjectId}

    Removes hyper link between source object and destination object

    DELETE /api/object/hyperlink/{srcObjectId}/{dstClassId}/{dstObjectId}

    Set default hyper link to spot for object

    PUT /object/defaulthyperlink/{classId}/{objectId}/{entityId}

  • General refactoring
    Changed Webservice:
    Change of method used:

    From GET to PUT /api/session_info/json/setversion/{versionId}

    From GET to PUT api/session_info/json/setlanguage/{langId}

    URL stays the same for both services will now use PUT method. This was needed as response of GET method returned many redundand data.

    New HDCAgent is needed to support this change.

  • Done under JIRA Issue [HDC-2256] - Batch print is using ambiguous ContentID 

    Batch print operated now on pairs of IDs: contentID(as before) and typeID (1- attachment; 2-composite drawing)

    Changed Webservice: 

    GET /api/drawing/print/batch?contentIds=8747,10118,10209,10252,10575,10576


    GET /api/drawing/print/batch?contentIds=8747,1;10118,2;10209;2

  • No labels