Release Notes - Smart Spaces - R2023.02

Written By Natalia Povrozniak (Administrator)

Updated at March 25th, 2024

Table of Contents

What's changed

  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/approve?callId={callId}
  • Connector Configuration
  • PUT {application-url}/api/v1/{connectorId}/visits/{extVisitId}?callId={callId}
  • DELETE {application-url}/api/v1/{connectorId}/visits/{extVisitId}?callId={callId}
  • PATCH {application-url}/api/v1/{connectorId}/visits/{extVisitId}?callId={callId}
  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/checkin?callId={callId}
  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/checkin?callId={callId}
  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/checkout?callId={callId}
  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/cancel?callId={callId}
  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/approve?callId={callId}
  • POST {application-url}/api/v1/{connectorId}/visits/{extVisitId}/deny?callId={callId}
  • Connector Configuration - accessLevelId
  • POST/PUT {application-url}/api/v1/{connectorId}/visits/{extVisitId}/checkin?callId={callId} - accessLevelId support
  • Add POST {application-url}/api/v1/config
  • Add PATCH {application-url}/api/v1/config/{connectorId}

What's fixed

  • Visits Created in DST (UTC+1) are displayed with the Incorrect Times in SmartSpaces GUI.
  • Once a booking is cancelled that has visitor assigned to it, the visit record doesn't get cancel in SmartSpaces V1.
  • Once a booking is cancelled that has visitor assigned to it, the visit record doesn't get cancel in SmartSpaces (via the microservice V2).
  • Reload config error messages - missing values in config.
  • Passing x-function-key in URL.
  • Passing Invalid DateTimes to POST /v1/{connectorId}/visits Call results in incorrect error message.
  • Connector configuration - use local time.
  • DELETE /v1/{connectorId}/visits/{extVisitId}/cancel returns incorrect result if the {extVisitId} does not exist.
  • DELETE /v1/{connectorId}/visits/{extVisitId}/cancel returns incorrect result if the {connectorId} does not exist.
  • Reload Config Error Messages - Wrong Connector Type.
  • POST /v1/{connectorId}/visits Call with Connector Id that does not exist results in Code 400.
  • POST /v1/{connectorId}/visits/{extVisitId}/checkin Call Connector Id does not exist results in Code 400.
  • POST Checkout Visit Call Connector Id does not exist results in Code 400.
  • POST Checkout Visit Call Visit Id does not exist results in Code 400.
  • POST Checkin Visit Call Visit Id does not exist results in Code 400.
  • Passing Blank Email Feild to POST /v1/{connectorId}/visits & PUT /v1/{connectorId}/visits/{extVisitId} Calls results in Code 200.
  • POST Create Visit Call Host Email Field is not mandatory.
  • Passing Invalid Times to POST /v1/{connectorId}/visits & PUT /v1/{connectorId}/visits/{extVisitId} Calls results in incorrect Error Message.
  • Passing Invalid FirstName to POST /v1/{connectorId}/visits Call results in incorrect Error Message.
  • Passing Invalid LastName to POST /v1/{connectorId}/visits Call results in incorrect Error Message.
  • Swagger Document - Opening one Endpoint opens all endpoints under current Controller.
  • Reload Config Error Messages - Invalid Json Config.
  • Reload Config Error Messages - ConnectorId Cannot Be Found.
  • DELETE /v1/{connectorId}/visits/{extVisitId}/cancel returns incorrect result if the {connectorId} does not exist.
  • Passing Invalid LastName to POST /v1/{connectorId}/visits & PUT /v1/{connectorId}/visits/{extVisitId} Calls results in incorrect Source of Error Message.
  • Passing Invalid FirstName to POST /v1/{connectorId}/visits & PUT /v1/{connectorId}/visits/{extVisitId} Calls results in incorrect Error Message.
  • Reload Config Error Messages - ConnectorId Cannot Be Found.
  • Reload Config Error Messages - Invalid Json Config.
  • Passing Invalid DateTimes to POST /v1/{connectorId}/visits & PUT /v1/{connectorId}/visits/{extVisitId} Calls results in incorrect Error Message.
  • Reload Config Error Messages - Wrong Connector Type.
  • POST /v1/{connectorId}/visits Call with Connector Id that does not exist results in Code 400.
  • POST Checkin Visit Call Visit Id does not exist results in Code 400.
  • POST Checkout Visit Call Visit Id does not exist results in Code 400.
  • POST Checkout Visit Call Connector Id does not exist results in Code 400.
  • POST /v1/{connectorId}/visits/{extVisitId}/checkin Call Connector Id does not exist results in Code 400.
  • Reload Config Error Messages - Missing Values in Config.
  • MicroService Code 401 Error Messages Missing.
  • SmartSpaces System Code 401 Error Message.
  • Error Message for when External VisitId is not Passed to the microservice.
  • DELETE Call not passing Visit Id Error Message.
  • Passing Invalid DateTimes to POST /v1/{connectorId}/visits & PUT /v1/{connectorId}/visits/{extVisitId} Calls results in incorrect Error Message.
  • If no Start or End Date is Supplied in Payload incorrect message is displayed.