Jump to content

ArmandoDM

Hornbill Developer
  • Content Count

    255
  • Joined

  • Last visited

  • Days Won

    6

ArmandoDM last won the day on June 18

ArmandoDM had the most liked content!

Community Reputation

26 Excellent

About ArmandoDM

  • Rank
    Hornbill Developer

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,062 profile views
  1. Thank you @Alberto M I raised a ticket internally in order to fix this issue and to prevent adding duplicates. Armando
  2. Hi @Alberto M I investigated on this and actually you should have only 1 record for each multiOption , as the user is obliged to select only 1 answer. I run a few tests and I was unable to replicate. Is this an issue currently happening ? Armando
  3. @Alberto M let me double check for you
  4. @Alberto M yes. This is done in the Service page. Here is a screenshot of the popup where you can create a feedback question. As you can see, you may add question of different type, including 'Checkbox group'
  5. Hi @Alberto M because h_field_type is a multiOptions (list of checkboxes) , then the same question may have multiple answers. So, for h_feedback_question_id = 68, for example, the customer checked 2 options: the number 1 and the number 5. It doesn't seem they are duplicates. Regards Armando
  6. Hi @dwalby this should be possible through the import configuration https://wiki.hornbill.com/index.php/Database_Asset_Import Under Configuration Examples you may find an example. Hope that helps. Regards Armando
  7. Hi @TomW, the query was working for me so I suggested it. Good work anyway, glad to hear that you got it working.
  8. @TomW can you try this one ? SELECT ( (SELECT COUNT(h_sm_relationship_entities.h_entity_id) FROM h_itsm_requests,h_sm_relationship_entities WHERE (h_itsm_requests.h_pk_reference = h_sm_relationship_entities.h_linked_entity_id) AND (h_sm_relationship_entities.h_linked_entity_id LIKE 'IN%') AND (h_sm_relationship_entities.h_entity_id LIKE 'CH%')) / (SELECT COUNT(h_itsm_requests.h_pk_reference) FROM h_itsm_requests WHERE h_itsm_requests.h_pk_reference LIKE 'CH%') ) * 100 Regards Armando
  9. @Jeremy the scheduled tasks against assets appear on the right hand side of the asset page. They can be created if you click the icon next to Activities. In order to create and view tasks, the asset must be In Policy. To put an asset In Policy, you need to have Configuration Manager installed. With Configuration Manager installed, you will see an icon on top right of the asset page (see screenshot). If you click on it, it will open the Explorer for that asset, where you you can put it In Policy . Hope this helps Armando
  10. @Jeremy I will report this issue for fix. If you can, as a temporary fix, you can either remove the Vendor or add Product and Version too.
  11. Hi @Jeremy do you populate the Vendor when creating the asset ? I can see an issue when the Vendor is populated but Product and Version are not
  12. Hi @chrisnutt this feature already exists. In order to define new type of relationships, you need to access the admin tool and add new elements as you need. See screenshot. Here is the documentation for more detailed info: https://wiki.hornbill.com/index.php/Service_Manager_Relationships Hope this helps Regards Armando
  13. Hi @Jeremy could you show which properties are set to visible and which one are not ? General properties and Additional properties. I would like to create an asset type with the same configuration as yours, and see if I can replicate the issue. Thanks Armando
  14. Hi @Jeremy can you please double check that 'company' and 'site' are both set to ''visible'' or ''not visible'' on the asset type ? Regards Armando
  15. Hi @Joshua T M the params are all in string format. Only 'queryName' and 'resultType' are required, and their possible values are as per documentation. About the other params: queryString: deprecated userId: ID of request's owner customerId: ID of the request's customer (as James mentioned, this can be numeric or alphanumeric depending on the customer type - contact or user) statusFilter: the request status, as specified in the documentation requestType: additional request type, on top of Incidents and Service Requests For example: <queryName>getCustomersRequests</queryName> <resultType>allData</resultType> <userId>joshuatm</userId> <customerId>armandodm</customerId> <rowstart>0</rowstart> <limit>10</limit> <statusFilter>status.open</statusFilter> <statusFilter>status.new</statusFilter> <requestType>Change Request</requestType> will return the first 10 requests (rowstart=0, limit=10) where: joshuatm is the owner, AND armandodm is the customer AND the status of the request is open OR new AND the request type is Incident OR Service Request OR Change Request The list of requests are returned in JSON format as shown in the image I hope that helps Regards Armando
×
×
  • Create New...