72 results found

1. Include Department Info on Data Analytics Dump

   Currently User Department is not part of Data Analytics Data, this makes it impossible to report on usage by Department. Request is to capture and include in Data Analytics Dump.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. HR Feed - enable to start browsing from a deeper OU

   Currently you can only specify a single OU which shall be in the root tree.
   In an internationa company it is most likely the relevant accounts are on a deeper level of the tree.
   HR feed should be able to handle an OU string like: "OU=devisonx,OU=regionx,OU=userx,OU=alluser" to start searching from there.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. 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.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Consideration  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Identifiable context in Equipment Mailbox configuration

   As requested in Ticket 447155 please find Feature Request.

   Our Exchange admins would like to see some specific identifier in headers, API, subject or similar that they could use to create Exchange rules to identify bookings from Condeco platform.

   e.g. allow a customisable template to be used for meetings booked through Outlook/App in which we could add "CB" (Condeco Booking) to the meeting subject.
   This way we could block all other requests and thus only accept those made through Condeco

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. MS365 Calendar Integration - Visitor tick Box

   For internal attendees - can the visitor tick box not be populated or removed against internal attendees.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. User Story for the case#383418 - under desk booking-API

   Dear CONDECO,

   Below are the requirements:-

   1. 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.
   2. 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.
   3. Required:- We need to refresh the Condeco table data as faster. Current:- Its taking at least 7-8 Hours to refresh the data.
   4. Required:- We need quick and continuous support for user queries. Current:- Difficult to communicate and not getting better resolutions as expected by chat.
   5. Required:- Desks Booked should be restricted as 1 user can book 1 desk at a time and should not be duplicate at same time,
   6. Current:- User can book multiple desks at same date and same time.

   Thanks
   Tharani. T

   Dear CONDECO,

   Below are the requirements:-

   1. 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.
   2. 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.
   3. Required:- We need to refresh the Condeco table data as faster. Current:- Its taking at least 7-8 Hours to refresh the data.
   4. Required:-… more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 'Check In time' required in historical booking API.

   Check In time is required to filter the different tables and data in historical bookings API.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Fully manage Condeco Connect screens via an API

   It would be amazing if we could do the following via an API for Condeco Connect:
   - Get all devices in a given regions and on a given floor
   - Set device settings for a given device
   - Manage admin accounts: Get, Add and Remove
   - Restart a device

   Essentially mimic what you have in the Condeco connect management portal.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Desk Cancelation API Endpoint

    This will allow an external system to use the API to see which desks are canceled at a given date/time. In our scenario it will help to manage parking space (via desk booking) and have proper billing via thirs party application.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. We need to add the host racfid field to the Azure table data so that data lake condeco data and source applications data can be compared

    We need to add the host racfid field to the Azure table data so that data lake condeco data and source applications data can be compared

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Allow PurposeOfVisit in Visitor_CreateVisitor_V1 API to allow other values

    The purposeOfVisit API has been designed to only support UnKnown = 0, InternalVisitor = 1, ExternalVisitor = 2. Does not allow other values to pass through which is quite cumbersome.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. API: Visitor Listener - Multiple Visitors in one notification and Multiple Ids for Visitors over multiple days

    Due to the way visitors are created in Condeco there is a visitor id / record created for everyday a visitor is visiting. This means any action will send multiple Ids in a single notification. Equally if a meeting is created and multiple visitors are created in that meeting, a notification is sent for multiple visitor ids for multiple visitors.

    In most use cases of the visitor listener I would imagine the applications they are posting to are doing some sort of deduplication of this data as they will only need one Id per visitor to retrieve their information. As there is no way from the visitor notification to determine if the ids are for multiple days of one visitor or many visitors of one meeting a workaround need to be put in place. This is to loop through the IDs getting the visitors name by the getVisitorsbyID endpoint and then checking if the current name is the same as the previous name. As names can be nonunique this is not a perfect solution. This solution also massively increases the API calls required

    This could be solved in a few ways:

    Firstly the listener could only post one notification per visitor. This would keep the idea of multiple ids for one visitor over multiple days however it would create a notification per each visitor created via the create meeting form

    If the above is not a potential solution a id could be added for each visitor so that they can be deduplicated based on this e.g:

    Multiple Visitors -
    [{'VisitorId': 1460985, 'Action': 1, 'VisitorNotifId': 0}, {'VisitorId': 1460986, 'Action': 1, 'VisitorNotifId': 1}, {'VisitorId': 1460987, 'Action': 1, 'VisitorNotifId': 2}]

    One Visitor over Multiple Days -
    [{'VisitorId': 1460985, 'Action': 1, 'VisitorNotifId': 0}, {'VisitorId': 1460986, 'Action': 1, 'VisitorNotifId': 0}, {'VisitorId': 1460987, 'Action': 1, 'VisitorNotifId': 0}]

    Due to the way visitors are created in Condeco there is a visitor id / record created for everyday a visitor is visiting. This means any action will send multiple Ids in a single notification. Equally if a meeting is created and multiple visitors are created in that meeting, a notification is sent for multiple visitor ids for multiple visitors.

    In most use cases of the visitor listener I would imagine the applications they are posting to are doing some sort of deduplication of this data as they will only need one Id per visitor to retrieve their information. As… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Provide location filter capability for all notifications, specifically visitor

    The API notification service allows for filters related to resource IDs, please provide the ability to filter for location ID too. Specifically for the visitor event (type 8), although seems like a great idea to do the same for other event types too.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Transfer QR code string via API HierarchyMapping endpoint

    We generate the QR string in our main data source. We would like to add the ability the transfer the QR code string from our main data source via the API into Condeco. This can then be used for desk/room check-in/check-out.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Accepted  ·  0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Provide 'hot desking for phones' integration with Zoom

    Please see the link below from Zoom's product roadmap from April 2022. Zoom is coming out with features where folks can use their phone to temporarily connect to an office phone (someone else's with their permission, or a communal phone). Part of it is to show a location on a floor map. I checked Condeco's configuration guide and product roadmap and did not find anything on this topic.

    Please consider this integration for the future, see link below for more details.

    https://support.zoom.us/hc/en-us/articles/360043841032-Using-hot-desking-for-phones

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. OAuth Client Credentials - Westpac

    Condeco currently have API that requires authentication with OAuth 2 password grant type. Unfortunately, it is not aligned with Westpac Digital Platform (WDP) standards, as “PASSWORD” is not a supported grant type, and it is not secure (basic authorization which is passed in HTTP header). The requirement for Westpac is for Condeco to accept “Client Credentials” as the Grant Type.

    Due to this legacy grant type, Westpac have been advised by our Security architecture to get Condeco to uplift the grant type to accept “Client credentials”. This issue impacts the following API functions.

    1. Condeco Visitor API
    2. SCIM API
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. deactivate user visibility as default after user is created or imported in Condeco System

    Condeco is not using any automated process to provision users. Users either take the path of self-registration with SSO or a bulk CSV upload is done for this client to onboard new users. Condeco did an automation with Clops which does this update however due to caching issues this is not a successful solution to us. In order to mitigate this, Condeco was looking to explore the options available on our Admin API(APIM) endpoint for users however the attribute is not present on current build of admin API.
    Available today –
    {"users": [{"email": "string","userName": "string","title": "string","firstName": "string","lastName": "string","initial": "string","telephone": "string","mobile": "string","extension": "string","fax": "string","userRole": 0,"costCode": "string","deskSlotsPerWeek": 0,"userPin": "string","thirdPartyId": 0,"externalId": "string","externalSystem": "string"}]}
    We want to request to extend the attribute as its available in Users table update value of parameter 'hidedeskandworkstatus' to '1' in tbluser within the user’s endpoint.

    Condeco is not using any automated process to provision users. Users either take the path of self-registration with SSO or a bulk CSV upload is done for this client to onboard new users. Condeco did an automation with Clops which does this update however due to caching issues this is not a successful solution to us. In order to mitigate this, Condeco was looking to explore the options available on our Admin API(APIM) endpoint for users however the attribute is not present on current build of admin API.
    Available today –
    {"users": [{"email": "string","userName": "string","title": "string","firstName": "string","lastName": "string","initial": "string","telephone": "string","mobile":… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Ability to extract booking source for Personal Space via Condeco's API

    Right now, it is not possible to get datapoint around where the Personal Space has been booked from (Mobile, Web, Outlook Add-In, or Physical Hardware). Looking at adding this into the data source so that it is made available for extraction via API call.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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 etc.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close