Jump to content

Jim

Hornbill Users
  • Posts

    395
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Jim

  1. hmm, hard to say unless there's anything missing ref the defaults, here's how our incidents looked for our side, obviously your ID's, service and statement are going to differ

    {
         "Description":"This object configures the importing of Incidents",
         "Import":true,
         "CallClass": "Incident",
         "SupportworksCallClass":"Incident",
         "DefaultTeam":"Service Desk",
         "DefaultPriority":"P4",
         "DefaultService":"IT Support",
         "SQLStatement":"SELECT opencall.callref,  logdatex, closedatex, cust_id, cust_name, itsm_title, owner, suppgroup, status, updatedb.updatetxt, priority, itsm_impact_level, itsm_urgency_level, withinfix, withinresp, bpm_workflow_id, probcode, fixcode, site FROM opencall, updatedb WHERE updatedb.callref = opencall.callref AND updatedb.udindex = 0 AND callclass = 'Incident' AND status < 15 AND status != 6 AND opencall.callref IN (0789852,0779402,0788229,0793492)",
         "CoreFieldMapping": {"h_catalog_id" = "111",
           "h_datelogged":"[logdatex]",
           "h_dateclosed":"[closedatex]",
           "h_summary":"[oldCallRef] - [itsm_title]",
           "h_description":"[updatetxt]",
           "h_external_ref_number":"[oldCallRef]",
           "h_fk_user_id":"[cust_id]",
           "h_status":"[status]",
           "h_request_language":"en-GB",
           "h_impact":"[itsm_impact_level]",
           "h_urgency":"[itsm_urgency_level]",
           "h_customer_type":"0",
           "h_container_id":"",
           "h_fk_serviceid":"",
           "h_resolution":"",
           "h_category_id":"[probcode]",
           "h_closure_category_id":"[fixcode]",
           "h_ownerid":"[owner]",
           "h_fk_team_id":"[suppgroup]",
           "h_fk_priorityid":"",
           "h_site":"[site]",
           "h_company_id":"",
           "h_company_name":"",
           "h_withinfix":"[withinfix]",
           "h_withinresponse":"[withinresp]",
           "h_custom_a":"",
           "h_custom_b":"",
           "h_custom_c":"",
           "h_custom_d":"",
           "h_custom_e":"",
           "h_custom_f":"",
           "h_custom_g":"",
           "h_custom_h":"",
           "h_custom_i":"",
           "h_custom_j":"",
           "h_custom_k":"",
           "h_custom_l":"",
           "h_custom_m":"",
           "h_custom_n":"",
           "h_custom_o":"",
           "h_custom_p":"",
           "h_custom_q":""
         },
         "AdditionalFieldMapping":{
           "h_firsttimefix":"",
           "h_custom_a":"Custom Data",
           "h_custom_b":"[itsm_title]",
           "h_custom_c":"[updatetxt]",
           "h_custom_d":"",
           "h_custom_e":"",
           "h_custom_f":"",
           "h_custom_g":"",
           "h_custom_h":"",
           "h_custom_i":"",
           "h_custom_j":"",
           "h_custom_k":"",
           "h_custom_l":"",
           "h_custom_m":"",
           "h_custom_n":"",
           "h_custom_o":"",
           "h_custom_p":"",
           "h_custom_q":"",
           "h_flgproblemfix":"",
           "h_fk_problemfixid":"",
           "h_flgfixisworkaround":"",
           "h_flg_fixisresolution":""
         }
       },

     

  2. I would also check the log file to see if it complains of any access issues if its permissions related, although I don't think that should matter considering its gotten as far as actually logging the request, I would assume the catalog item is actually published?

  3. Ahhhh great minds :D I can't think why a process would not execute once a catalog item is provided, I have seen this issue before though I can't think what it was at the time.  I think it was an error when scheduled requests were added as a feature, so wouldn't relate to your issue, Ironically I think not setting a customer may cause some issues to do with subscriptions etc, maybe try adding a default value of a dummy account that lives in Hornbill

  4. This made sense in my head, the layout doesn't help :D but essentially store the email address in the custom fields, use that custom field to search for the user and retrieve the hornbill user id, update the customer, all as part of the hornbill workflow 

  5. Okay I see the issue, does the email address look right? and is that available in Supportworks? 

     

    My not so clean but may work solution would be as follows - don't import customers but store the email in a custom field, in the process do the following -> Get Request details - > get user by email in

    the screenshot

     image.png.a727df4884db26ca8f942a3f8af9473e.png

    --> update customer with the retrieved user id image.png.7d08f59e5dc2fc993f3491d16a00cf3c.png

    image.png

  6. 6 minutes ago, Steve Giller said:

    callref has never included the F, nor any preceding zeros - it's an Integer field. Including them will not effectively match.
    I believe that some versions have an additional field, which I cannot remember the name of off the top of my head, that holds the full reference to make reporting a little simpler.

    Well that explains our lack of F's in our query, I'm guessing the next part is aimed at @billster, From what I can gather its to help resolve h_fk_user_id to a [cust_id] as he has no matching data between the same users on the 2 systems, I think this ought to match the userID to the userid within hornbill though so rather than stripping the domain name, it actually needs to concatenated to the user id they have in support works ??  

  7. 4 hours ago, billster said:

    I tried to use an IN() operator, but, the import tool failed. I tried this... does it look right to you? I also tried AND opencall.callref = "F10245915"

     

    I'm not sure if this is relevant, but ours doesn't include the F's, 

     

    "SQLStatement":"SELECT opencall.callref, logdatex, closedatex, cust_id, cust_name, itsm_title, owner, suppgroup, status, updatedb.updatetxt, priority, itsm_impact_level, itsm_urgency_level, withinfix, withinresp, bpm_workflow_id, probcode, fixcode, site FROM opencall, updatedb WHERE updatedb.callref = opencall.callref AND updatedb.udindex = 0 AND callclass = 'Incident' AND status < 15 AND status != 6 AND opencall.callref IN (0789852,0779402,0788229,0793492)",
  8. If you need any help let me know I've done a fair bit with the new powershell api module 

     

    I didn't get much hands on the support works config but I believe we stripped a lot of it for testing and used 5 incidents in this section 'SQL Statement'

    We used the references in an 'IN()' operator hopefully this helps

    image.thumb.png.b376cd1ab6bbc2a32663e4a2773c1fd9.png

  9. Ahh I see your problem, no matching data to tie them together anymore, 

    Have you considered doing this in the user import script? not sure if this allows anything that way 

     

    What I would end up doing in your circumstance is using PowerShell to do this via the API's linked below :)

    GitHub - hornbill/powershellHornbillAPIModule: Powershell module for making XMLMC calls against the Hornbill platform

    / admin / userProfileSet (hornbill.com) 

  10. Which import are you using, is this for requests?

     

    Slightly unrelated answer but in some scripts this applies: 

    UPN does not have to be the matching criteria in the json config it can be any of the belowimage.thumb.png.ab3e0a8bc814b3dd005f059f7efa63cf.png

  11. Hi David, it's pretty simple to implement there are nodes under request timers for start response time - usually as soon as a request is logged, and then a node for stop response time (Usually when a request has been responded to manually) It is up to you though where you want that time to be marked, I think the correct way is to mark when a customer has been responded to, but we class the service desk assigning it to another team as a 'Response' also so we have it after the assignment node

     

     

  12. @TrevorHarris Thank you for feeding back, that's a shame as I have boards that are process driven and I don't want viewers to be able to move them, however sorting them themselves or new cards added following the same sort by would be much better, as an admin this is more overheads that are unnecessary 

×
×
  • Create New...