46 results found
-
Integration with Webex room devices
Meeting room devices have various sensors built into them including presence (physical people in the room), temperature, air quality and more. A native integration would bring loads of opportunity to Condeco users that have Webex units in rooms
4 votes -
Allow PurposeOfVisit in Visitor_CreateVisitor_V1 API to allow other values
The Visitor API has been designed to support UnKnown = 0, InternalVisitor = 1, ExternalVisitor = 2 and no other values. Suggest to enhance this feature as it does not make sense to have only 2 values accepted.
4 votes -
Require Meeting Subject Validation in Outlook Engage Add-in Before Reservation Submission
Prevent users from completing room reservations through the Outlook Calendar + Eptura Engage Add-in workflow when no meeting subject has been provided.
Problem Statement
When users book meeting rooms through the Eptura Engage Add-in within Outlook Calendar, reservations can be submitted without a meeting subject.
Where a meeting subject is required by organizational policy, the reservation may subsequently fail, creating a disconnect between the user's action and the final outcome.
From the end-user perspective, this often appears as:
- A room booking issue
- A synchronization problem
- An Eptura application issue
rather than a missing meeting subject.This results…
3 votes -
Allow check-in from a Cisco Webex or MTR room console if the customer does not have an Eptura branded room booking panel.
Allow check-in from a Cisco Webex or MTR room console provided that a videoconferencing bridge has scheduled in for customers who do not have a room booking panel from Eptura.
3 votes -
Send booking OR cancellation emails when made via API
Configure Engage for sending emails for bookings or cancellations made via API.
The engineering team has confirmed that currently the booking confirmation emails are not triggered when the booking is created through the admin API.
2 votes -
Add the HR system Employee ID to the SCIM integration as an optional attribute.
Companies have shifted from using employee IDs for identity and user management in systems to using email IDs. This causes challenges with integrated reporting, as name changes can lead to email ID changes, thus losing the ability to track history in operational reports. Additionally, textual data linking can face challenges in the case of special characters. Adding employee ID to the SCIM integration as an optional attribute will ease integrated reporting.
2 votes -
Populate user profile with user data from Single Sign On dialogue
As part of the single sign-on dialogue the first name, last name and email of the user is sent to Condeco. Currently Condeco does not use the information to populate a new user's profile. Auto-populating the profile would improve data integrity by reducing the chance that the user mistakenly or purposely enters the wrong data.
2 votes -
Floor plan improvement
When viewing the floor plan, automatically show workstations that have been booked and display the photo...if available of the individuals that's booked it instead of having to search and then click on the workstation to see this data.
2 votes -
User Story for the case#383418 - under desk booking-API
Dear CONDECO,
Below are the requirements:-
- Required:- We need Desks Booked and Desks Available from one table/API Itself as unable to join the different tables as lack of unique ID/Column, Current:- We have 2 different tables for each without any Unique ID/Column to join the both tables.
- Required:- We need to apply the filters before extracting the data from condeco especially date and country filters. Current:- We need to extract full data then will apply the filters.
- Required:- We need to refresh the Condeco table data as faster. Current:- Its taking at least 7-8 Hours to refresh the data.
- Required:-…
2 votes -
Allow admin to booking outside the booking window in Outlook/Exchange
If the booking window is set to 4 months then admin (eg PAs) can book outside this for say the following year to book board meetings etc. This is possible in the App so need Outlook to understand the admin rights.
2 votes -
Need the ability to have all meeting attendees to be sent to Visitor
Currently, attendees are only sent to Visitor when they are marked as External in the meeting invitation. However, there are scenarios where an employee who is not regularly on-site should still be registered in Visitor for check-in and site access purposes.
While marking the attendee as External will allow them to be sent to Visitor, this can be confusing for end users because they recognize the individual as an internal employee rather than an external visitor.
The feature request is to provide an option to default attendees to External for Visitor integration purposes, or otherwise allow internal attendees to be…
1 vote -
Guest Type Should be sent from Engage to Visitor
Currently, when a meeting is booked in Engage that includes external visitors, the visitor information is successfully sent to Visitor. However, the integration does not provide a way to specify the visitor type, such as Guest, Contractor, Vendor, or other categories.
As a result, organizations cannot leverage visitor-type-specific workflows and communications within Visitor, such as tailored notifications, instructions, or check-in processes. Instead, all visitors must follow the same communication workflow regardless of their classification.
The feature request is to enhance the Engage-to-Visitor integration to pass the visitor type during the booking process, allowing Visitor to apply the appropriate communication templates…
1 vote -
Multi-Day Meeting Support Between Engage and Visitor
Currently, when a non-recurring booking in Engage spans multiple days, the booking is not sent to Visitor, even when the Engage-to-Visitor integration is enabled. Single-day bookings are successfully passed to Visitor, but multi-day bookings are excluded.
The feature request is to have multi-day bookings processed through the integration in the same manner as single-day bookings, ensuring they are automatically created in Visitor whenever the Engage-to-Visitor integration is configured.
1 vote -
API Access to Key Worker Roles
Organizations require a consolidated view of Key Worker role assignments across their entire workplace portfolio.
Currently, locating Key Workers requires navigating individual floorplans, making it difficult to quickly identify responsible personnel across multiple buildings and floors.
Requested Enhancement
Provide an API endpoint that exposes Key Worker role assignments from Eptura Engage, enabling integration with internal workplace and facilities management tools.Desired Data Elements
- User Name
- Email Address
- Key Worker Role Type
- Building
- Floor
- Workspace / Location
- Presence/Availability Status (where available)Business Value
- Single view of all Key Workers across buildings and floors.…1 vote -
Enable setup and clear down to sync with M365
Setup and clear down buffers are essentially system bookings either side of a user booking. Can the system not create and sync these buffers under a system account? This would then keep both platforms looking the same.
1 vote -
Enable closure booking to sync with M365
When closing a room in Engage, there is no corresponding block created in the M365 Room Account. While Microsoft Exchange does not support the concept of 'closing' a room, in principle, the closure is just a booking made by the system rather than an end user.
When enabling a room closures, can the system not create a booking in M365 using a system account? This would then mirror the closure scenario in both platforms.
1 vote -
Support a service account ownership model that supports room as organizer bookings
When a new booking is created in a scenario with an active Exchange integration and mailbox mapping for a room, Engage does currently not provide the option for Cisco Room Navigator devices to properly handle the check-in from the Cisco panels (via Exchange mailbox). Bookings that are not synchronized to ones personal calendar (add to my calendar checkbox) will result in a room as the only attendee for a meeting, where the check-in trigger via Exchange fails due to missing organizer of the meeting. The request is to support a service account ownership model where bookings are managed on behalf…
1 voteOur Product team is currently reviewing your idea. We may contact you if we need additional information or clarification. While not every idea will be added to our product roadmap, we carefully evaluate each submission and yours will receive full consideration.
-
SSO Passthrough
Allow Engage to accept SSO Passthrough Authentication. The client has a single mobile app for all employees to use and various other SaaS applications are housed within it. Currently, that single mobile app authenticates the user via SSO. However, Engage currently does not accept that SSO Passthrough so prompts the user to log in again.
1 vote -
calendar
Support for Outlook integration without requiring access to end user calendars.
1 vote -
API - Change of unique employee identifier
Current API allows the fetching of Eptura Profile ID based on passthrough of Email Address Attribute. We would like to pass across our unique employee identifier code (BRID) in place of Email Address to fetch the Eptura Profile ID for a variety of reasons where Email Address may not be matching, such as change of business entity, users changing their last name or rejoining the business etc. whereby email changes have API returning two different user records — one active and one historical and consequently cannot match the user returning in with error.
1 vote
- Don't see your idea?