47 results found
-
To allow updating Visiting Location & Requestor through Visitor API
Currently not all fields are available for update. Please allow updating Visiting Location & Requestor through Visitor API
1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had only one vote.
-
Need to have a field to specify requestor when creating visitor using Visitor API
Currently there is no way to specify requestor when creating visitor using the API.
After visitor is being created, a random user is assigned as the requestor, which does not make sense.1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had only one vote.
-
Condeco to segregate Delivery Point Groups from the other Groups in interface API
At present, there is a need to presync delivery groups even though the delivery groups don’t come from Planon. With this request, the APIs will not touch delivery groups when they make any edits in the room hierarchy thus eliminating the need for presyncing delivery groups.
1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had only one vote.
-
Retry or Queuing logic to handle events when the notification URL is unavailable
There are times where the application hosting the notificationURL for a listener event goes down. Today the event logic fires a message to the notificationURL and does not check that the system received the message. To avoid missing events, it would be great if there was a failsafe mechanism that takes advantage of retrying and/or queuing the events in the event that the notificationURL does not respond to events sent to it.
1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had less than 5 votes. If you still feel your idea is important and should be rereviewed please feel free to create a new UserVoice submission.
-
Additional Security on Listener Event Messages
The ability to specify a token value to be placed in an authorization header on event messages being sent to the notification URL will enhance the security of the receiving application.
1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had less than 5 votes. If you still feel your idea is important and should be rereviewed please feel free to create a new UserVoice submission.
-
Corsham - Meeting notification 15 mins prior
Currently the system provides a meeting notification 5 minutes before the meeting. There is a requirement that this be extend to 15 minutes prior to meeting start. Given the size of the building this will allow the host to make their way to the meeting room.
1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had only one vote.
-
More than 50 characters for the username field
It would be great, if more than 50 letters could be entered in the username field in the user profile. Some users have a longer first name or surname or double names. Consequently, these users could also enter their full name after raising the maximum number of characters.
1 voteDue to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had only one vote.
- Don't see your idea?