47 results found
-
Filter Room Availability results to only bookable rooms
Currently, the GetRoomAvailability API has a UserID filter which can display rooms that only the user has visibility to. However, we have many rooms which the user can view but will not be able to book, as they are in restricted groups.
Using this API, the full set of rooms are returned, even though many rooms are not bookable by the user, which leads to the user trying to book the room but unable to do so.
The GetRoomAvailability API should have a filter like "onlyBookableRooms: true" which will only return rooms where the user has permissions to book the…
2 votesDue 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.
-
API- Error message
When extending a room due to set up/clear down times we see 400error with a generic text. Can this message be updated to be more specific as observed in this scenario rather than a generic message,
2 votesDue 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.
-
Allow GetUsers / GetAllUsers to filter by ResourceName / Username
Currently the API for UsersGetAllUsersV1 only allows for obtaining CondecoID for user based on email address. Since a Condeco user's email address is editable via their profile page, it is not a suitable field to be used to map to Condeco ID. Existing we are using SCIM to sync new user accounts from ActiveDirectory to Condeco. It would be better to obtain CondecoID via ResourceName / Condeco Username using this API.
Hence, can there be a /api/V1/users?resourceName=<user's condeco username>, so we can retrieve the user's Condeco UserID which is used for all other subsequent API calls like CreateMeeting…
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.
-
Check-in time parameter
‘Allow check-in time’ parameter from screen profile in the API to manage the check-in into meeting space bookings from this parameter. For e.g. if we provide value of this flag as 10 mins, user should be able to start the meeting 10 mins before the actual start time of the booking. The API endpoint which is being used for the check-in is ‘BookingsUpdateMeetingV1’.
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.
-
API that will retrieve all the booking created for specific data time range
Currently there are no endpoint to fetch all booking created in past “X” time period.
Currently the process would be
1) Get all desks
2) Get booking for each of the deskAbove process would be very time consuming as we may have to traverse thousands of desks.
3 votesDue 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.
-
The Reduced Capacity Checkbox shouldn't impact the previous setup styles and capacity when posting via Spaces API
- Imagine there is a meeting room which has ‘Reduced Capacity’ checked as a Seating Style in the Resource Admin page and as a result of this, other/previous seating styles and capacity with setup and clean down times are greyed out
- When the Admin posts a new default room setup style and default capacity from Spaces Master Source application via Spaces API to Condeco, the previous setup styles and capacity with setup and clean down times (if any) will be completely erased and this results in a bad Admin experience
Suggestion : It would be good if the previous setup styles…
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.
-
Prevent on-line changes to hierarchy data that is mastered in a different system.
Our master system for space data is Planon. Changes to the space data are made in this system and posted to Condeco. Unfortunately it is still possible to create space information in Condeco without it being created in Planon and this has resulted in duplicate data (see ENSD-52156 : DeskAzureProd || API Creating Duplicate groups). This results in a very poor user experience because the users can make duplicate desk or room bookings.
It is requested that Condeco consider:
• Preventing hierarchy information from being created in Condeco if it is mastered elsewhere OR
• Warning the user creating or…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.
-
API access to self certification status
API access to self-certification status would allow us to disable badges and control access if screening is not passed
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 structured field in Getbookings
Replace th eunique name attribute by two separates attributes: firstname and lastname and check if the mail is still known as the mail of an existaing user of Condeco to avoid the external / internal attribute which relies on mail domain management, that is not efficient in certain context.
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.
-
To have Visiting Location and Expected departure date & time in the result of Get Visitor
In the result of Get Visitor, not all fields are available. Please allow the following data extraction:
Visiting Location (no way to get this for visitor without room booking)
Expected departure date & time
2 votesDue 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.
-
Token Provider API - Automation
Please provide the swagger document for the token generation API. We would like to automate the deskbooking API but we are having issues because the token needs to be manually generated
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.
-
Un-mapping a selection of Exchange Rooms at once
As a Condeco Global Admin - I would like to un-map a selection of Exchange rooms in Condeco. This however seems not possible. All I can do is to click on the "Unmap" button line-by-line.
When mapping rooms I can highlight more entries at once and click on 'Map selected' button. Something like that is needed for un-mapping rooms.
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.
-
Additional API for catering management approval
We need an API for catering rejection of certain orders based on room booking details.
For example, Catering will be allowed only for room bookings of 4 hours and more, in case the booking was shorter and catering was ordered we can fetch the same by API and reject the catering order separately. The requestor shall get an email notification about the decline of his catering request.
2 votesDue 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.
-
Location API Endpoint - Group Membership
The current API endpoint available to update a location gives you an option to map all groups that belong to the location using the groups external ID’s. If you do not do this the existing mapped groups are removed.
This causes an issue as some IWMS systems do not manage all the types of groups that Condeco can manage for example Delivery Point groups, so these groups will need to be added and maintained directly in Condeco. As such they will have no external ID and would not be part of any presync.
For customers that require regular location updates…
2 votesDue 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.
-
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.
-
API endpoints for data analytics
Current API endpoints are not useful for data analytics purposes. For example /api/v1/deskBookings requires either deskId or userId
So to get all desk bookings per day in order to analyse who is booking desks where, you have to write a process to get all deskids and then loop through them one by one, appending the results.
It would be better to have endpoint which provides all desk bookings, with optional parameters as filters.
This feedback would apply to pretty much every GET endpoint in the API
3 votesDue 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.
-
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.
-
This is a request to increase the number of rooms returned by Bookings_RoomAvailability_v1.
This is a request to increase the number of rooms returned by BookingsRoomAvailabilityv1. Currently a maximum of 20 rooms and while I realise is for performance reasons, just a few more would cover the number of rooms we have on most but not all of our floors.
2 votesDue 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.
- Don't see your idea?