Jump to content

Alisha

Hornbill Users
  • Posts

    858
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Alisha

  1. Hello, Rather than having a few different static radioset fields, would it be possible to have radioset options show based on the previous question? We have many instances where we need to hide just one option, which means that we have to create a separate static radioset field without that option. Many thanks, Alisha
  2. @Steven Boardman That's excellent, thank you so much!
  3. Hi @Steven Boardman, Do you have an update on this please? Many thanks, Alisha
  4. Hi @Miro, Do you have an update on this please? Many thanks, Alisha
  5. Hi @Victor, I have tried this and unfortunately it doesn't work with wiki markup. Please could this feature be added? Just to give you an example, I would like to have a static radioset list with the following options: Extension mobility Phone line Voicemail Then, next to the extension mobility option, I would like to have a link that the customers can click on, which will take them to a page that explains what extension mobility is. Many thanks, Alisha
  6. @Victor, is it possible to add a hyperlink within a static radioset option? This could be a way around it if we can use hyperlinks.
  7. @Victor For example, if we're asking the analyst something like this: "Have you checked [info here] with <customer name>?" It would be nice to have the option of customising the user experience as well, if it's possible.
  8. Hi @Victor, In one of your progressive capture examples (VPN Access v2) on the demo site, the very first field on the custom form uses the variable {{user.fName}}. I was wondering if there are any other variables that can be used, such as the customer name, so that it's visible on the live instance to any analysts logging the request. Many thanks, Alisha
  9. Hi @James Ainsworth, Is there an update on having a User Picker please? Many thanks, Alisha
  10. Hello, Is there a list of variables that we can use in progressive captures? For example, {{user.fName}}. Is there one for customer name? (When calls are logged via the live instance rather than the service portal. Many thanks, Alisha
  11. Hi @Victor, If I remove the text from 'Default Value', but keep the original text in the Label field, nothing shows on the progressive capture. Many thanks, Alisha
  12. I found a way around this by adding some span code to white out the text in the Label field, but is there a cleaner way to do this please?
  13. Hello, I have added a label in a progressive capture, but once the request is logged, it duplicates the text. Is there a way to not have the text show twice (other than using different text for the first line, as it's just intended for information only)? Many thanks, Alisha
  14. Super! That would be really helpful, thanks @James Ainsworth!
  15. Hello, Our applications are going to be loaded in as Assets. It would be really handy to have an Assets option in the Group Picker, so we can filter out the different asset types. For example, we would like customers to pick the relevant application that they require access to in a Progressive Capture. Instead of picking from 'All Assets', which would also show assets such as hardware and third party, we would like just the applications to show. This would be much easier than creating a simple list, since we have so many applications. Would this be possible to implement please? Many thanks, Alisha
  16. Hello, We are using official terms for a number of categories and customers might not know what they mean. Would it be possible to implement a 'tooltip' feature please? For example, if we had a category called 'Softphone', it would be handy to show a definition for it when the customer hovers over the word. This would also be useful within progressive captures as well. Many thanks, Alisha
  17. Thanks for the update @conorh, much appreciated. :)
  18. Hello, Apart from using the Data Query option to Get All Sites, is there anything else that we can use it for in Progressive Captures? Just wondering if we can create our own data sets that customers can select from, for example, a list of departments. (Other than creating Simple Lists.) I just don't fully understand what the Data Query option is and how we can utilise it (apart from using it to get a drop down list of site names). Many thanks, Alisha
  19. Thank you, @conorh :) I've uploaded it and it will work well if we don't have too many additional people requiring access. Just thinking about some other requests that we need to create. Sometimes we have 20+ new recruits start at the same time. Is there a way to streamline this so we don't have the same questions appear multiple times on the logged request?
  20. @conorh, Is there a way to make the question, "Do you want to submit this request for another person?" invisible once the request is logged? So we don't see it several times on the same request?
  21. Thank you @conorh! We really like that idea, and I'll try that on an existing capture. :)
  22. Hi @conorh, Thanks for your reply. Here's a scenario that might better explain what we're after. We have a group of people who all need access to one folder. Instead of everyone logging requests individually, a nominated person from the group logs the call and enters all their colleagues' details onto the capture as well. This is where a table format would come in handy, so that they can enter details like this onto a capture: Full name - Read only access Full name - Read only access Full name - Write access Full name - Write access And so on. I understand that we could use a multi line text field, but if the customer logging the request could just tick whether they require read only/write access, it would make it more user friendly. Many thanks, Alisha
  23. Hello, When customers request access to folders, we need to know their details and which level of access they require. Would it be possible to include a table option in progressive captures so customers can enter their name, and then choose if they need read only or write access? It would be really useful as one person (the authoriser) could then add multiple people onto the one request, and not everyone requires the same level of access. Many thanks, Alisha
×
×
  • Create New...