How to set AssignedToUser equal to the CreatedByUser automatically

We want to setup a quick create and auto-solve for incidents and servicerequests that reached us by phone and got a quick fix. In our template we only expect our helpdesk dispatcher to fill up the AffectedUser and Title for an incident or servicerequest. We then have a workflow that auto-solves a quick-workitem.
The creation using template and the auto-solve workflow is working fine. The only thing we want to do nicer is setting the AssignedToUser to the CreatedByUser. We didn't see a solution using workflows and we tried this with the Cireson Powershell Activity extension. But the powershell activity app works only for servicerequests and changes, not for incidents.
How can we achieve our goal and through what customisation? 

Answers

  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭
    Do you have SCORCH or SMA running?
    Or can always create a powershell script that runs from SCORCH or SMA or as a windows scheduled task. Script it to run once a day to run thru all the incidents matching the template ID to then perform the Assigned to user relationship
  • Jeff_LangJeff_Lang Customer Advanced IT Monkey ✭✭✭
    if logging the incident/service request via the portal, something like the below should work for incidents and be easily modified for service requests as well, needs to go in the custom.js
    app.custom.formTasks.add('Incident', null, function (formObj, viewModel) {


  • john_doylejohn_doyle Cireson Support Ninja IT Monkey ✭✭✭✭
    Hi @Frederik_Vandendries 

    A different solution would be to create a new page in the Portal. Here's an example:
    Create a file in the CustomSpace\views folder called quick-incident.js and enter this code in that file:
    {

    Next create a file called QuickIncident.js in the CustomSpace\views\viewpanels folder.
    Paste this code into that file. Replace the guid 'a77bb0c9-e201-dd93-230c-799a66d9e8fa' with the guid of your incident template.
    {

    The final step is to create a new link under Navigation settings.


    Now you will have a new form which will enable you to create incidents where the assigned user is the created by user. You could easily extend the code so that the analyst can choose whether to create an incident or a service request. The only thing that would change in the code is the template id. You could put radio buttons on the form for Incidents or Service Requests and then call the CreateProjectionByTemplate API with the appropriate template Id.
  • john_doylejohn_doyle Cireson Support Ninja IT Monkey ✭✭✭✭
    Hi @Frederik_Vandendries 

    I modified the QuickIncident.js code
    {

    Here's what it looks like in the portal.



  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭
    edited December 2017
    @john_doyle or @Jeff_Lang
    I have spent a good amount of time training my analysts to use the service catalog as it performs the proper data mapping that we then use for reporting. 
    Was attempting to use the powershell activity to set the assigned to user but it doesn't work on IR's. 
    Is it possible to have a trigger on specific SO's to make the relationship?

    And side note diffidently going to work on adding the quick create for my desk that takes first line phone calls.
  • john_doylejohn_doyle Cireson Support Ninja IT Monkey ✭✭✭✭
    Hi @Brian_Wiest 

    With the ARO, you can add a direct link to a Request Offering, so you could still redirect them to a form like this through the service catalog.
  • john_doylejohn_doyle Cireson Support Ninja IT Monkey ✭✭✭✭
    @Brian_Wiest 
    That said, I don't think the system would associate the resulting ticket with the RO, so it would have to be done by the form itself when creating the ticket.
Sign In or Register to comment.