Jump to content

Alisha

Hornbill Users
  • Posts

    856
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Alisha

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

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

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

    Hornbill.jpg

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

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

    Hornbill.jpg

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

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