Release notes – version 4.2.6

In this release This version includes significant delete operations improvements and a couple of PATCH operation improvements. New functionality Hard delete Simple delete means that the twin is archived in the database. Hard delete means complete database removal of the twin without leaving any fallback copy (except snapshot history). Read more

By |2025-02-11T14:55:03+02:002022-07-14|Release Notes|

Release notes – version 4.2.5

In this release Even more collection improvements are introduced, and a new collection subclass: Region. New functionality Region Region - collection sub-class that allows grouping twins of classes RealEstate and Building. New endpoints to manage Regions are introduced: Include twins into region - PUT /json/region/{id}/include Exclude twins from region Read more

By |2024-02-23T16:07:01+02:002022-06-23|Release Notes|

Release notes – version 4.2.4

In this release New Collection sub-classes are introduced: Apartment, TenantUnit, SpaceCollection. User sign up functionality is added. New functionality Apartment Apartment - collection sub-class that allows grouping twins of types Building and BuildingComponent. New endpoints to manage Apartments are introduced: Include twins into apartment - PUT /json/apartment/{id}/include Exclude twins Read more

By |2025-02-11T14:54:08+02:002022-06-16|Release Notes|

Release notes – version 4.2.3

In this release New twin sorting functionality is introduced. New functionality Sorting Since this release it is possible to retrieve sorted paged data. By default all paged data is provided as an unsorted collection. In order to obtain paged and sorted data, a new query parameter ‘sort’ is introduced. Read more

By |2025-02-11T14:53:12+02:002022-05-26|Release Notes|

Release notes – version 4.2.2

In this release New functionality Twin status All twin types are upgraded with new property ‘status’ which describes if the twin is valid or not. Possible status values are: ‘Valid’, ‘Incomplete’, ‘Incorrect’, ‘SuspectedInvalid’. When a twin is onboarded and no status value is provided, ‘Valid’ status will be set Read more

By |2024-02-23T16:02:50+02:002022-04-28|Release Notes|

Release notes – version 4.2.1

In this release   New functionality Device Coordinates Devices (and subclasses Actuator and Sensor) have a new property ‘hasGeoReferenceOrigo’ to store its coordinates. In case of large devices, the coordinate should mark the south western corner of the device. The property accepts three coordinates (latitude, longitude, altitude above sea Read more

By |2025-02-11T14:52:37+02:002022-04-14|Release Notes|

Release notes – version 4.2.0

In this release Several new features for multiple areas of ProptechOS come with this release. One of the most significant improvements is the new opportunity to observe the twin lifecycle, with an audit trail. There is now a general view of all twins for quick high level info. Additionally Read more

By |2025-02-11T14:38:08+02:002022-03-31|Release Notes|

Release notes – version 4.1.0

In this release ProptechOS is migrated to the new Active Directory. This release will provide an opportunity to invite new users directly to the ProptechOS. Also in this release a new type of Collection - System, will be introduced. Apart from this, support of rec messages version 3.3 is Read more

By |2025-02-11T14:37:16+02:002022-02-28|Release Notes|

Release notes – version 3.3.12

In this release Alias based actuation messages. New functionality Alias based actuation messages With this feature, ProptechOS can send RealEstateCore cloud to device  messages with actuator alias id instead of ProptechOS actuator ID in Actuation Command. That means the edge system does not need to keep a map of Read more

By |2025-02-11T14:07:20+02:002021-11-11|Release Notes|

Release notes – version 3.3.11

In this release In order to simplify Service Object functionality implementation of internal feature ‘user impersonation’ is introduced. General actuation functionality improvements. New functionality User impersonation The intention of the feature is to allow admin user to execute requests on behalf of other non-admin users. Breaking changes None. Fixes Read more

By |2025-02-11T14:05:31+02:002021-11-01|Release Notes|
Go to Top