Dashboard changelog

February 21, 2024 #

Added:

  • Functionality to temporarily block Situm Dashboard access to users in case of too many failed login attempts. If the failures continue the time will increase until the first successful login.

February 15, 2024 #

Added:

  • Now it is possible to limit access to Situm Dashboard to certain IPs. Please contact support@situm.com to enable it.

February 5, 2024 #

Fixed:

  • Fixed a bug related to the handling of images in the information fields of cartographic elements.

February 2, 2024 #

Fixed:

  • Previously, alarms did not sound if the user didn’t interact at all with the page before the alarm went on.

January 17, 2024 #

Added:

  • Now you’ll be able to upload cartographic files (GeoJSON, IMDF, Raster tiles) from the building editing form. For more information, you can consult the document here.
  • You’ll now be able to see the identifier of the following elements from their editing forms: Building, Floor, POI, Geofence, and POI Categories. Additionally, a quick access option has been introduced to conveniently view their data in JSON format (REST API call)

December 11, 2023 #

Added:

  • We have activated the update notice of our Master Subscription Agreement to reflect the use of Sentry in the mapviewer. For more information you can consult the document here.

Fixed:

  • We have restored the polish language

November 8, 2023 #

Fixed:

  • Resolved an issue that could cause the modification of POIs to fail when their position was changed with a “drag & drop” action.

October 30, 2023 #

Fixed:

  • Fixed problems with duplicate websockets messages

Agust 24, 2023 #

Fixed:

  • Fixed an issue that could cause users to experience issues when updating certain POI categories

Agust 17, 2023 #

Added:

  • Now it will be possible to upload personalized images for each of the points of interest. These images will correspond to the selected and unselected icon. These icons will be used in the following versions of the different viewers and apps

Agust 02, 2023 #

Improved:

  • Now you can use the api key without including the user’s email address. Before with the api key you had to include in a header the user’s email associated to the api key. From now on this will not be necessary. Consult the documentation here for more information

July 27, 2023 #

Fixed:

  • Fixed an issue with the visualization of tooltips for alarms when the alarm generated was of type ‘assistance request’.

July 13, 2023 #

Added:

  • The maximum image size for the POI category icons has been limited to 128 x 128 pixels.

July 6, 2023 #

Added:

  • The possibility of configuring a parent category has been added to the creation and editing forms of POI categories. This allows the creation of hierarchical relationships between POI categories.

June 20, 2023 #

Fixed

  • Fixed error when reseting your password. In the login page, if you clicked on “Forget your password?”, you’d receive an email with a link to reset it. However, the password reset operation could not be completed properly before this fix.

June 15, 2023 #

Fixed

  • Fixed the assignment of building and groups to devices when the group or building was assigned to more than one device.

June 06, 2023 #

Fixed

  • The description of alarms of type “Breach” (“Round Breach” as shown in the Dashboard) was not being shown correctly: the POI or area associated with the breach was displayed as “unknown” every time. This happened, for example, in the Alarms report. Now, it displays the POI/area name correctly.

June 05, 2023 #

Fixed

  • Fixed a bug that caused the custom fields of POI categories to not be saved correctly when editing a POI category.

May 31, 2023 #

Improved

  • Improvements in the documentation of the api/v1/reports endpoints. For further information see the API docs.
  • Internal updates to improve system stability.

May 12, 2023 #

Improved

  • Added support to associate several categories to a POI. We have updated the POI creation and editing form to allow adding multiple categories to a POI. For further information see the API docs.
  • Internal updates to improve system stability.

May 10, 2023 #

Added

  • Allows the subcategories of POIs through open api. For further information see the API docs.

May 04, 2023 #

Improved

  • Added support to add custom fields in poi categories.

April 24, 2023 #

Improved

  • Custom fields have been added to POI categories. This allows saving any type of extra information related to them. The creation of these custom fields can be done both from the dashboard and through our API. For further information see the API docs.

March 22, 2023 #

Fixed

  • Fixed a problem not showing all the devices with available data in the analytics filter form.

March 16, 2023 #

Improved

  • Improvements have been made in the management of POIS and POIS Categories to prevent POIS from being assigned to a non-existent category which has been deleted by another user in concurrence with POI creation. In addition, before deleting a POI category, all the POIs belonging to it will be reassigned to the default category “No category”.

March 06, 2023 #

Fixed

  • The value of the “code” field, in responses to geofences GET requests, will be set to an empty string (“”) in cases where it is null to prevent the IOS SDK from exhibiting an unexpected behavior when this field is accessed. The affected endpoints are:
    • GET /api/v1/geofences/search
    • GET /api/v1/geofences/{id}

February 16, 2023 #

Added

  • Now it is possible to generate a positioning model without WiFi or BLE calibrations, using only GPS positioning geofences for outdoor locations.
  • New warning modal to alert user when training a model with positioning gps geofences only.
  • New warning modal to show info about model generation and to alert the user that previous models are going to be removed

Fixed

  • Fix error when saving calibrations without calibrations selected.

Improved

  • Improved search geofences feature.

February 14, 2023 #

Added

  • Add the new typology GEOFENCE MAX_STAY_TIME for the creation of alarms. For further information see Alarms API documentation.

January 31, 2023 #

Fixed

  • Fixed a bug related to the deletion of API keys. https://developers.situm.com/pages/rest/openapi/#tag/Alarms

Improved

  • Internal updates to improve system stability.

January 26, 2023 #

Fixed

  • On users tab: navigation icons colors are now always gray colored and not black or white.

December 13, 2022 #

Fixed

  • Trajectories report page now loads correctly all devices in selection combo when organization has many devices.
  • Solved error when fetching all staff users.
  • Solved error when navigating to Real Time with a Staff Manager.
  • Device Assignment page now loads correctly all devices in selection combo when assigning a device to a user.

December 11, 2022 #

Added

  • /api/v1/reports/geofencing_stay_time_historical and /api/v1/reports/geofencing_sessions_matches_historical endpoints that operate with a historical perspective of the data. For further information see the REST API changelog.

November 16, 2022 #

Fixed

  • In building’s infrastructure view: fixed bug that displayed beacons queried previously for another building.
  • User’s delete modal translation fixed.

Improvements:

  • Users management:
    • After create/update user now redirects to users list.
    • Role admin option now available in creation form.
    • New message displayed when current user is showed in users list.
    • Keeping users list applied filters after creating, updating and going back to list without doing changes.

November 15, 2022 #

Fixed

  • Now users list and users selectors used in some reports are consistent working with staff.

November 08, 2022 #

Added

  • Allow to select a group of geofences in batch by selecting their building in the selection combo. This is a complementation to the previous geofences single selection mode
  • Also the selected items include the building name to know in which building the geofence selected is at
  • Now the geofences column in the reports table, also includes the building name where the geofence is at
  • In the same way, the CSV file also contains the building name in the geofences column

Fixed:

  • Prevents showing non existing or deleted buildings in the geofence select combo
  • Alarms without lat and lng not rendering correctly

November 3, 2022 #

Added

  • Add public endpoint Get /api/v1/progaizations/current_organization that allow retrieve information about the current user organization.

October 19, 2022 #

Fixed

  • Fixed error that occurred when launching an automatic training when new or deleted calibrations were detected after finishing a training process launched by the user.

Improved

  • Improvements in building training request processes.
  • Improvement in the management of exceptions in training processes.

October 6, 2022 #

Fixed

  • Fix API rest error message and fields when updating the user email and an error occurs. The endpoint fixed
  • Allow the user manager consult users in the api rest by user id when both share access to at least one building. The endpoint fixed

Jun 1, 2022 #

Added

Improved

  • Security audit fixes
    • Hardened password requirements
    • Force session cookie to be SSL secured
    • More fixes in API security
    • Analytics API: only return error identifiers if error occurs

Fixed

  • Fix problems with device assignation for some particular cases
  • Fix flash messages not being properly closed
  • Avoid performance problems inalarms API when attending huge amount of alarms at once
  • Improve wifi filtering with better UX
  • Fix crash in trajectories report
  • Fix bug in rounds report
  • Fix RT crashing in small displays (phones)
  • Fixed errors on calibrations on not found exception and added new error handling on required request params.

April 3, 2022 #

Added

Improvements:

  • Performance improvements for the /api/v1/reports/has_data endpoint
  • Huge performance improvements in the RT data ingestion
  • Performance improvements in the dashboard screens that fetch users from the API
  • Reactive comunication in our platform about cartographic elements
  • Better user privilege handling when modifying cargographyc elements

Fixed

  • API: Fix user privileges access while retrieving calibration scans from the API
  • API: Allow positioning and readonly API keys to assign users to devices.
  • RealTime: Fix outdoor positions being saved with the wrong floor_id
  • Cartography: Fix rotate, move and size change of buildings being broken for some particular cases.

March 3, 2022 #

Added

  • New geofence report with two modes, stay times and visits, more granular control over filters.

Improvements:

  • Better handling of user permissions in the Realtime page

Fixed

  • Bug: fixed user positioning not being shown properly in RealTime page tooltips
  • Bug: Fix incorrrect positoning information shown in heatmap report

January 26, 2022 #

Added

  • 🇧🇷 Add  brazilian portuguese language to the dashboard

Improved

  • Perf: Improve performance in the global realtime page for organizations with hundreds of users positioning
  • UX: Persist filters in heatmap report form between page reloads
  • UX: Improve layout in the heatmap report form
  • UX: Improve detection of global vs building mode in the realtime page when zooming on large buildings

October 21, 2021 #

Improved

  • UI: Navigation to a realtime building can be done by clicking on the building marker in organization realtime view, selecting a building alarm or a user positioning on that building or query param, for example dashboard.situm.com/realtime?buildingId=5962.
  • UI: New buttons in the alarms element to see any alarm on a minimap from the global view.
  • UI: Informative improvement of the alarm title, using human language to recognize when the alarm occurred.
  • UI: Now the box to show and create tasks is always visible both in global mode and in local mode. It is necessary to select the building if you are not in local mode to create a task as it is a required field.
  • UI: New side panel and poopups UI styles improvements.
  • UI: Implemented a dark mode for the map.
  • UX: Faster by displaying data when changing floors in real time (alarms, positions, etc.).
  • UX: The default floor when entering a building´s real time becomes level 0 or the lowest floor.
  • UX: The sound banner can now be heard in global realtime. In addition, it tells us in which building it has occurred and allows us to quickly navigate to the alarm on the floor by clicking the Go to alarm link.
  • UX: Building markers show a small red marker at the bottom right if they have any alarms inside.

Fixed

  • Bug when trying to see some layers in realtime window.
  • Fixed several errors in the infrastructure panel related to information visualization.
  • Soved bug of black floors.
  • Solved bug of not rendering a floor when a selection in floor selector is made.

September 2, 2021 #

Improved

  • UI: New icons for reports, points of interest and licenses.

Fixed

  • Users: Error when creating a new user and not saving its assignment to a group.
  • Users: Error when removing an user from a group.
  • Fix deckgl error in infrastructure panel.
  • Reports: Fixes in trajectory report.
  • Cartography: Fixed screen not being properly centered in the building after reload.

August 21, 2021 #

Improved

Subscribe to our newsletter

BASIC INFORMATION ON DATA PROTECTION

Data controller: SITUM TECHNOLOGIES, S.L.
Contact: Data controller: situm@situm.es
Responsible for protection: dpo@situm.es
Purpose and legal basis: To manage the sending of SITUM newsletters only with consent.
Legitimation: Express consent of the interested party.
Recipients: The data will not be passed on to third parties with the exception of legal obligations.
Retention period: As long as the interested party remains subscribed to the newsletter (a link to unsubscribe will be available in each newsletter sent by Situm).
Rights: The interested party may at any time revoke their consent, as well as exercise their rights of opposition, access, conservation, rectification, limitation, deletion of data and not be subject to a decision based only on automated data processing, by writing to SITUM at the addresses indicated.
Additional Information: You can consult additional and detailed information on Data Protection in our privacy policy.

Please, download your copy here

Thank you for downloading our whitepaper. Please do not hesitate to contact us if you would like to know more about how our solutions can help your business. Download whitepaper


Close window