Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Sv translation
languageen


Excerpt

New features, improvements and bug fixes done for version 3.6.0

Table of Contents

Table of Contents
stylesquare


New user parameter Attachment fit mode

Issue [HDC-3235] - Attachment view - control page fit

New parameter Attachment fit mode can be changed by users to control default PDF viewer zoom mode.


In User Profile, go to document tab to change this option. Default value is Page Fit.

Note

Same parameter has been also added to System Settings in Administrator panel. This will decide of default value for PDF viewer zoom level for all users (unless user selects it in User Profile).



ObjectData import type allows adding new objects

Issue [HDC-3189] - Import objects via excel

ObjectData import type have been modified to allow adding new objects given in XLS spreadsheet.

Import dialog for ObjectData import have additional options.

  • Context Object - set root for import, all new objects will be linked to selected context object.
  • Add unmatched objects - if checked, objects from spreadsheet that are not matched via TOBIS field will be added as new, linked to selected context object.
    If not checked, not matched object will not be added. Only update operation will be done.
    If not checked but Context Object is chosen then updated objects will be additionally linked to context object.

 


Filters that only handles objects linked to selected object in tree

Issue [HDC-2663] - Filter that only handles objects linked to selected object in tree.

New option "Only for selected object" is added to Presentation panel that will narrow filter results to objects linked to selected Tree object (ex. Floor).


This can be useful for databases where same document is linked to multiply objects (for instance Floors).
If we have simple presentation "Room Area" that colors all rooms on drawing and presents their area we would get list of all rooms from all floors where our drawing is linked to and not currently selected floor.
If we use new option "Only for selected object" on Presentation panel, then the presented list will be narrowed to rooms connected only to currently selected Floor object in Tree navigation.



Possibility to run "Text compounder" and "Math basic operation" plugins for subtree

Issue [HDC-3003] - Text compounder run for subtree

Custom fields plugins Text Compounder and Math Basic Operation can now be run from Tree context menu in subtree mode.


Right click on desired Tree objects - for instance Building, and choose Smart Fields/Math Basic operation/Subtree to run plugin on building and all sub-objects of building.

Subtree operations can be time consuming as they may run for hundreds or thousands of objects. 
Because of that, those operation are run in background. Push notification will be visible when plugin is finished.

Administrators can see status of those operations in Admin Panel/System/Running processes. Please check for Task ModifySubTree.

Possibility to run "Update areas" for subtree

Issue [HDC-3006] - Update Areas for subtree

Update area functionality can be run in subtree mode in same way as Text Compounder and Math Basic Operation plugins, described above.

Manual start of Autolink function in application

Issue [HDC-3013] - Manual start of Autolink function in application

Auto-Linking can now be run outside imports. 

It can be run:

  • from Admin Panel/Data Processing/Auto-Linking using Auto Link Now button to process all objects in database according to all auto-linking definitions.



  • form Tree context menu Links/Auto Link/Selected or Subtree - to process currently selected object or it's sub-tree. 


After auto-linking process is finished, report will pop-up with list of created links:


Note

Proper rights to linked objects (View&Edit) is required of course to perform auto-linking.


New built in system group: "System Users"

Issue [HDC-2376] - I can use built in system group: "System Users"


New system group is now added to all databases in HDC.cloud called System Users.
This is group of system internal type that will always have all users in the system as it's members.

Traits:

  • It will always return all active users when asked for members.
  • Cannot be deleted but name can be changed.



Example of usage:

System group can be assigned HyperDoc User role and new users will automatically have this role assigned through that group.


New permission "Redline"

Issue [HDC-3023] - System role for users that are not allowed to Redline

New permission Perform redline is now added for each Security Scheme
This permission will decide if user can perform redline operation or not for objects to which Security Scheme is assigned. 

Note

Still seeing shared redline layer is possible without this permission.
Perform redline permission applies only to editing operations (add redline drawing, layer, draw redline, delete redline).

Security Scheme dialog:

In this case no users can perform redline operations on drawings to which "General Scheme" applies.
But if we create "Arkitekt" scheme that applies to all Arkitekt objects and assign users/groups to Perform redline permission then those users will be able to redline on Arkitekt drawings.


Note

When upgrading databases to version 3.6.0, new group "System Users" is automatically assigned to Redline permission for all Security Schemes.
This will prevent users from loosing possibility to redline. After that system group can be un-assigned and desired permissions set.

New HOPA paramter "fitmode"

Issue [HDC-2928] - HOPA: Fitmode in HopaGetView4Object

New HOPA parameter is added: fitmode FitMode (FM) with 0, 1, 2 possible values.

  • 0 – fit to specified width and height – this is the default value. Uses default width and height values if not provided.
  • 1 – fix width: generated picture has width equal to specified and height results from aspect ratio;
  • 2 – fix height: generated picture has height equal to specified and width results from aspect ratio;

    Note

    When ScaleMode (SM)  for viewport is set to Scale View/Drawing with given specific scale value,  fitmodeWhen output is wrapped in print template, FitMode parameter has no effect as templates have dimensions of their own (this always applied for Widht and Height).


Print refactoring

Issue [HDC-3115] - General Print Refactoring

Major print refactoring has been done for this version. Printing process should now be more stable, faster and correct in terms of expected printout result.
Performance improvements are best seen on multi-page printouts. Still in future versions we plan to improve print speed a bit more.

Within this task, many print and hopa bugs were fixed as well.

Select multiple values from filter list

Issue [HDC-3159] - Select multiple values from filter list

It is now possible to select more than one filter from activated presentation.

Selected filters will be visible on a drawing, print preview and on a printout.


Object's location path added to Excel reports

Issue [HDC-2523] - Excel Reports location path

Whenever we export excel report with list of objects, we now add new column "path" that will give a navigation path to this object. This is added to following reports:

  • advanced search Excel export report,
  • object set Export report,
  • grid XLS Export report,
  • batch downloading report,
  • batch printing.
Note




Hold tab button to remain on same object tab

Issue [HDC-3158] - Remain on same object tab when switching object in tree

When "Hold tab" button is turned on last user selected class is stored as preferred one.


When "Hold tab" button is active:

  • user preferred class is selected by default when switching object in Tree (even if there is default drawing set on different class),
  • if the user preferred class is not available, use first active tab (the fallback tab is not set as user preferred of course),
  • when the user selected class is available again on next Tree object switch, preferred class will be chosen.

When hold is off: tab containing default document will be selected over the last user selected class.

The hold stat is saved in browser local storage (it is persistent on this browser only).

Bugs fixed and other improvements for this version

  • [HDC-2954] - Multi-line text not printed on a specific drawing
  • [HDC-3108] - Micasa text macros - on initial load macro does not load properly
    [HDC-3178] - Need help with ifc import problem
  • [HDC-3182] - Draw function gets stuck on "isDrag" check
  • [HDC-3208] - Print Preview: Legend template windows is not following presentations filters selections
  • [HDC-3214] - Export finishes with NPE after exporting object from object set
  • [HDC-3225] - SAML logout request is not signed.
  • [HDC-2607] - Viewer performance has dropped below acceptable level
  • [HDC-3153] - Add information about "Forgot password" and link to login page in user invitation mail
  • [HDC-3244] - Improve handling of layers on IFC import


API Changes

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

General: 

Deprecated WSes removed:

  • POST ..api/drawing/link/{classId}/{objectId}/{entityId}
  • DELETE ..api/drawing/raster/{contentId}/{rasterFileId}
  • DELETE ..api/drawing/vector/{contentId}/{vectorFileId}
  • POST ..api/drawing/vector/json/{compositeId}
  • DELETE ..api/drawing/map/{contentId}/{mapDrawingId}
  • GET ..api/drawing/map/datasources/json
  • POST ..api/drawing/map/json/{compositeId}
  • PUT ..api/drawing/map/json/{mapDrawingId}
  • PUT ..api/drawing/upload/rasterparameters/{rasterFileId}
  • POST ..api/drawing/rasterparameters/json/{rasterFileId}
  • PUT ..api/drawing/rasterparameters/json/{rasterFileId}
  • GET ..api/drawing/rasterparameters/json/{rasterFileId}
  • DELETE ..api/drawing/vector/entity/{entityId}
  • POST ..api/drawing/vector/entity/{vectorId}
  • PUT ..api/drawing/vector/entity
  • GET api/drawing/print/{contentId}/{templateId} - has been merged in to ..api/drawing/printmulti/{templateId}

Issue [HDC-3115] - General Print Refactoring


Removed Webservices: 

Unused WSes removed:

  • GET ..api/drawing/{contentId}
  • GET ..api/drawing/printview/{contentId}/{templateId}
  • GET ..api/drawing/view/{contentId}


New Webservices:



  • Issue [HDC-3023] - System role for users that are not allowed to Redline

    All api/redlineentity/* web-services were modified to work only when user have Perform redline permission.

    Up till now some web-services like add new layer where same both for redline and private layers. Since 3.6.0 new services where added only for redline scope.



  • Issue [HDC-2376] - I can use built in system group: "System Users"

    Minor API change: additional flag 'managed' returned with groups.
    Important change: getting users for group will return now only enabled (active) users!



  • Issue [HDC-3006] - Update Areas for subtree

    New Webservices:

    Calculate area for given object with its subtree connected to spots on specified layer

    POST /api/areacalc/subtree/json/{perspId}/{classId}/{objectId}/{layerId} 

    Calculate area for given object with its subtree

    POST /api/areacalc/subtree/json/{perspId}/{classId}/{objectId}


    Chenged Webservices: 
    GET ..api/areacalc/json/{drawingId} to

    POST /api/areacalc/drawing/{drawingId}


    GET ..api/areacalc/json/{drawingId}/{layerId}  to

    POST /api/areacalc/drawing/{drawingId}/{layerId}



  • Issue [HDC-3003] - "Text compounder" and "Math basic operation" run for subtree

    New Webservices:

    Run event plugin for subtree, it starts process and processes in background

    PUT /api/plugins/run/subtree/{pluginName}/{perspId}/{classId}/{objectId}


    Chenged Webservices: 
    GET ..api/plugins/run{pluginName}/{classId}/{objectId} to

    PUT /api/plugins/run{pluginName}/{classId}/{objectId}



  • Issue [HDC-3013] - Manual start of Autolink function in application

    New Webservices:

    Perform autoLinking for specified object - edit restriction for this object is required

    PUT /api/autolinking/json/{classId}/{objectId}


     Perform objects autoLinking for specified object with its subtree in given perspective (view and edit restrictons for autoLinked objects is required)

    PUT /api/autolinking/subtree/json/{perspId}/{classId}/{objectId}


    Perform objects autoLinking for all objects in database (view and edit restrictons for autoLinked objects is required)

    PUT /api/admin/autolinking/allobjects






...