Jump to content

HHH

Hornbill Users
  • Posts

    813
  • Joined

  • Last visited

  • Days Won

    23

Posts posted by HHH

  1. I just want some advice and recommendations on how we can handle our customers who have a three layer structure so to say.

    Structure is Company -> Branches -> Contact where the contacts can either belong to the different branches or to the overall company itself.

    They may have branch staff that creates requests and should only be able to see their branch's requests and also company staff that should be able to see requests from the whole company.

    Any ideas?

     

  2. We are experimenting with a single form progressive capture for our customers which looks like this.

    Form.jpg.f8fb4360b4560a79f7b79155b36c7ba2.jpg

     

    I have managed to take the summary field in the form and inject it into the  &[global["flowcode"]["summary"]] but is there a way to do the same with  &[global["flowcode"]["description"]].

    When I try to do it in the Business process description only takes manual text field input (see screenshot).

    BP.thumb.jpg.42003fcf125cfbfb4c42620ce01e8015.jpg

  3. We handle both external and internal customers in our Service Manager instance.

    Is there a way to differentiate service catalogue items per portal so that some are only seen on customer.hornbill.com/instance and others only on service.hornbill.com/instance?

    I have looked but seem to only be able to differentiate on service level by setting subscriber.

  4. I have the same problem but use (SR|sr)[0-9]{8} or (IN|in)[0-9]{8} for reference and Rule expression depending on type of call.

    I have tried using both REGEX_MATCH(subject, .*(IN|in)[0-9]{8}.*) and REGEX_MATCH(subject, '.*(IN|in)[0-9]{8}.*')

    That's with and withoute single quote

  5. @ArmandoDM

    Some more info. We have another manager attached to that ticket as a member and she can see the ticket as intended.

    She is a member of the team that currently has the ticket, other than that they are the same.

    A third manager that is not affiliated to any teams is also a member and can view her I'm a member tickets.

    All can view the ticket if they go directly to the ticket by editing the URL.

  6. Hi, I need some help figuring this out.

    We have a request that one of our organisation managers wanted to see despite not being part of the assigned or supporting teams.

    So I added him as member to the request.

    When he logs in he can see that there is a request but he cannot open or view it. See attached screenshot.

    Is this a bug or is there some setting I have missed. 

    He has the Incident Management User and Collaboration roles and the request is an incident. The request in question is resolved.

    Clipboard01.jpg

  7. Is it possible to automatically assign each user to a team when importing them through CSV upload for example by adding an organzation ID column?

    The wiki https://wiki.hornbill.com/index.php/Users doesn't say anything but if this is possible what should the name of the column to be imported be and how should the format be for the organization?

    Organization ID in organizations is in the format company/department/team, could this be used here as well?

  8. I have our internal users set up with the following structure:

    • The Company
      • Division 1
        • Team A
        • Team B
        • Team C
      • Division 2
        • Team A
        • Team B

    etc..

    I want all of Company to be able to subscribe to a service through the Service portal, how do I do that?

    I tried just adding "The Company" to subscribers but  my user who is in Division 1 > Team A cannot see the service in the service portal in order to log requests to it. What am I missing?

  9. On 2017-08-11 at 7:39 AM, James Ainsworth said:

    This operation can also be used as a great way to manage a re-opened request.  Once a request has been resolved you can use the Suspend and Wait for Status Change to identify when the request has moved from resolved to being open again, or to closed.  In each case a decision node can be used to manage both situations.  An Expiry can be used where after a period of time where the status hasn't changed, you can set it to close automatically.  This will solve the above issue where re-opened requests were still automatically be closed.

    @James Ainsworth

     

    Can you show a BP example of how this can be set up. I like the idea but cannot really follow your description.

     

  10. A question about making a CSV import of organisations into a live system where there already customers implemented.

    If we already have a number of customers for example CustomerA and CustomerB.

    Each have a number of request tickets already.

    If I then make a CSV import of CustomerA, CustomerB, CustomerC and CustomerD with CustomerA and CustomerB's information being identical to what's already in the system, will their old request tickets still be connected to them.

    That is, is a visible field used as a foreign key in the database.or is there a hidden key that's used so when setting up CustomerA it gets a key of for example 1 and if I add it again from CSV import it gets an ID of for example 3.

    I hope I'm somewhat clear. What I'm trying to achieve is to be able to import customers from our sister companies one at a time by appending the new customers to an existing CSV and then re-importing.

×
×
  • Create New...