Jump to content

Victor

Administrators
  • Posts

    5,696
  • Joined

  • Last visited

  • Days Won

    169

Posts posted by Victor

  1. I know the product is not very helpful here as it seems to have the same naming for internal and external groups, so let's call external groups "Organisations" and internal groups "Companies".  So what you are looking for is roles/rights to allow a user (one of your analysts) to manage (other) user membership for Companies, right? If so there is no dedicated system role for this but I think a custom role can be created with the following rights:

     image.png

    I think the "User" and "Group" rights are required, at least "Manage" ones... Create/Delete can be added if the user should also be allowed to perform these actions on users and groups/companies.

  2. 1 hour ago, Berto2002 said:

    should the action of changing someone from User to Basic not remove them from the association with a Team?

    @Berto2002 not necessarily. The system is designed so such actions can be reversed. What the system needs to ensure is that this association for archived users is not taken into account in current functionality, which is not the case for admin::userGetGroupList

  3. @Berto2002 there is no anomaly in the database here... the discrepancy comes from what data is retrieved from the database in the two scenarios:

    a) user record -> organisations for that user

    The API that retrieves the list of users (admin::userGetGroupList) will display all organisations that the user is associated with regardless of the user status (active, suspended, archived)

    b) organisation record -> users assigned to that organisation

    The API the retrieves the list of users (admin::groupGetUserList) will display all users that are not archived. Users that are archives are excluded from the list.

    When a user is archived the organisation association record is not removed but the system will ignore this association going forward. The argument here is that admin::userGetGroupList should, potentially, not be run or ignore the association (so no data is returned, no organisations are displayed for the user) if the user is an archived user.

  4. @Berto2002 not a very helpful message there... these are direct outbound emails, there is no practical way to make use of the message ID anywhere in the UI to locate this message and review the delivery logs... something we would need to look into.

    Meanwhile, if needed, the delivery logs for this type of emails are stored in h_msg_direct_delivery_log table. If you filter on message ID (which in this occasion is 19530) you would get details of the delivery and if it failed, why it failed. 

  5. @Berto2002 you can make use of {{Customer Coworker.H_home_organization}} but that means a) user needs to have a Home Organisation set (which I would assume it does) and b) this actually gives you the org ID, not the name so it might not be what you are after in an email...

    If we need the name in the email this becomes a bit more convoluted, won't be that straight forward...

    1.  Get User Details (we need the Home Org from this one)

    image.png

     

    2. Get Organisation Details (we need the Name from this one)

    image.png

     

    3. Store the "Name" value somewhere on the request, most likely a custom field

    4. Use the custom field variable in the email template to output the company name

  6. 42 minutes ago, Berto2002 said:

    the H_company_name is not pulling-through the Company despite that being known in the workflow for the expression to use immediately prior

    @Berto2002 ok so, basically this statement is incorrect. {{.H_company_name}} is an email template variable and only used in email templates. In workflows you have workflow variables which are different than email template variables.

    The value for {{.H_company_name}} variable in an email template is retrieved from h_itsm_requests.h_company_name. If this has no value in the database for the respective record, the email will display {{.H_company_name}} (this is the default behaviour which can be changed by formatting the variable in email template configuration).

    "Get Request Information -> Customer Details" node will set the value for the "Company" parameter from h_sys_groups.h_name based on h_sys_account_groups.h_group_id for the respective user.

    As you can probably imagine, "h_itsm_requests.h_company_name" and "h_sys_groups.h_name based on h_sys_account_groups.h_group_id for the respective user" will not always be the same. I believe in your test h_itsm_requests.h_company_name is empty (no value) which means the request is associated with a customer but not a company while "h_sys_groups.h_name based on h_sys_account_groups.h_group_id for the respective user" does have a value given the user is associated with one (or more) organisations.

     

  7. @Chloe Carson the error you see there is because https://api.hornbill.com/admin/?op=contactSetAuthentication API fails to execute for the reason mentioned in the error, which is the value for <authCredential> param did not meet the required input pattern constraints. This is a "passwordType" param and it needs to comply with the patterns documented here: https://api.hornbill.com/_types/passwordType. Whatever value ends up in the <authCredential> param, it does not comply with this.

  8. @will.good @samwoo although this seems like an obvious option and something that should be there, unfortunately this is not very straight forward. I won't bother you with the technicalities (they are quite a bit of these in this area even if this is not apparent). We were looking for some time to enable this option on the webform however we do not have a solution that we are happy with at this time.

    • Thanks 3
  9. @John C do you want to prevent requests raised from portal or user app too? If just portal then you can disable portal visibility for the service(s) or you can set the catalog items service desk only. Disabling user log in via SSO achieves the same but it is a bit extreme... it will prevent users from log in Hornbill altogether...

  10. @QEHNick 

    12 minutes ago, QEHNick said:

    the ability to prompt for time spent in a Task is not reflected in a timesheet?

    Because time spent in task is a task functionality which is a Core item. Timesheets are Timesheet Manager app items and they only exist when the TM app is installed in an instance. Tasks (and their time spent functionality) will exist with or without TM app. Time spent in task existed long before TM app was created.

    14 minutes ago, QEHNick said:

    can we somehow integrate this?

    You don't integrate them, with TM App installed you would use the TM time spent functionality. Without TM app you use task time spent.

×
×
  • Create New...