Jump to content

Search the Community

Showing results for tags 'google'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
    • GRC Manager
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start








Website URL





Found 4 results

  1. Hi We have multiple email domains which means we have multiple IDP setups that log into Hornbill using SSO, however, when a specific idp is selected, we are correctly directed to log in via Google and provide MFA etc, however, instead of logging in, users are met with: The certificates do not expire until 2024, and the ACS URL and Entity ID in Google match our other idp settings that are working... One thing to note, which could be related. When we go into SSO Profiles within Hornbill, there is the following message: Your SSO SAML Metadata Configuration needs to be updated, this can be done from the SSO Profiles page. Please see here for more details However, when we try to follow the instructions as advised by above and upload the METADATA via XML, Hornbill "hangs" at "Importing Data..." and never finishes? I'm aware we have had SSO since it was a PHP setup and our other "working" domains are still pointing at the php setup, unsure if this is related or not. One other thing is when you download the XML from the SSO profiles page you'll notice this has "BETA" in the URL? entityID="https://sso.hornbill.com/(ourinstance)/beta https://mdh-p01-api.hornbill.com/(ourinstance)/xmlmc/sso/saml2/authorize/user/beta Tried setting up from scratch, still no luck. Any help would be appriciated. Thanks Adam
  2. Please can I request a Google Docs integration call to be added to the list of Hornbill Integrations. We would like the ability to create documents from requests passing fields inc custom fields, I am more than happy to discuss further if required.
  3. We have a business process that we pass information into a google sheet, this fails every time with the error below/attached, when we use the restart BPM icon in the request this then works and passes the information properly. We have the keysafe credentials added but we are becoming unsure of how to resolve this issue.
  4. Hi guys, I have been asked a really difficult question by my boss today: "Is it possible to translate manually on the fly content in Hornbill?"... Let me give you a bit more context. We have plants and offices all across EMEA, including IT Support staff. Unfortunately our users and not really bothered with high-tech, web sites, quality of data, etc... When they contact us, it's because something is broken and they need it fixed ASAP, or they have a question which needs an immediate answer (pretty much like all users I guess ! ). As a consequence, they do not setup their profiles properly... Here is the distribution of languages: And countries: As you can see, this is not great... Pretty much every single user has its profile setup with English when they are not in an English speaking country. Now this is getting problematic when for example John from Greece logs a request in Greek, but his profile is in "English". In this scenario, we do not get the "translate" button available: (Sorry for the poor quality, screen grab from youtube!) Another example (this time with a German guy): Thomas logged a request via the portal (great!) but because his profile language is set to "English" here is what we see in the request details: It is the same on all the timeline... Having given some context, I hope you will understand where my boss comes from with his question: how can we get the "translate" button available here? This is to date one of the main "negative" feedback we get from our analysts all across EMEA and we cannot really blame them. The way I see it, I can only think of 2 options: - Change the language of all users properly => not really long term solution especially as all our users are automatically synchronized with our Active Directory (using the LDAP User Import utility) and therefore I cannot really do much (given that the AD does not have a language field) - Change Hornbill to give us this possibility to translate on the fly (a bit like Google translate)? I am of course opened to any suggestions! PS: Don't shoot the messenger!!
  • Create New...