locked
Assign User directly from self portal RRS feed

  • Question

  • Hello,

    I would like to create a request Offering where I could let the user to define the assigned user directly from the fields of supply. The problem is what type of field should I choose and how to map the fields Assigned To ?

    Thursday, July 4, 2013 3:28 PM

Answers

  • Hey

    You can use Queries to present User CIs for selection in the offering. However, the selected user CI(s) must be "linked" to the created Service Request. For that you only have 2 relationships available. If you want to use another relationship, you need to do some XML hacking. Check out Patricks blog which explains how to do it and use any kind of relationship --> http://blogs.litware.se/?p=1300

    Cheers
    Marcel


    Marcel Zehner // Blog --> http://marcelzehner.ch // Twitter --> @marcelzehner // Business --> http://www.itnetx.ch


    Thursday, July 4, 2013 3:47 PM
  • Hey

    Sorry, maybe that was a bit confusing :) If you use queries, the user can select 1 or multiple CIs from a selection list. These objects will be related/linked to the Service Request. When you configure the query in the Request Offering you must choose which relationship you want to use:

    - Service Request --> Affected CI
    - Service Request --> Related CI

    This relationship will be used to relate the selected CI (User CI in your case) with the Service Request. If you want to use another relationship, you must select 1 of the 2 relationships in the above list, then export the MP and edit the XML file. Then you can choose the relationship to anything else.

    Read Patrick's post I mentioned. It's very well explained there ...

    Cheers
    Marcel


    Marcel Zehner // Blog --> http://marcelzehner.ch // Twitter --> @marcelzehner // Business --> http://www.itnetx.ch

    Thursday, July 4, 2013 4:18 PM

All replies

  • Hey

    You can use Queries to present User CIs for selection in the offering. However, the selected user CI(s) must be "linked" to the created Service Request. For that you only have 2 relationships available. If you want to use another relationship, you need to do some XML hacking. Check out Patricks blog which explains how to do it and use any kind of relationship --> http://blogs.litware.se/?p=1300

    Cheers
    Marcel


    Marcel Zehner // Blog --> http://marcelzehner.ch // Twitter --> @marcelzehner // Business --> http://www.itnetx.ch


    Thursday, July 4, 2013 3:47 PM
  • Hi,

    You can use Orchestrator 2012 to do this because you can not directly map the field "assign to"

    For the type you must use Query Result  to the Active directory user class for example (you can use filter to reduce the scope). You can chose the Dsiplay Name for display columns . For the options, check "Add user-selected object to Template as related items".

    Create an Orchestrator Runbook who monitor all new service request (that corresponds)
    When a new SR was detected, select the related item
    Active directory user and update the SR with putting the user to "Assigned to".

    Enjoy !


    Best Regards Remy BOVI

    • Proposed as answer by BOVI Rémy Thursday, July 4, 2013 3:49 PM
    Thursday, July 4, 2013 3:49 PM
  • Hey,

    Sorry marcel but I don't understand very well, what do you mean by :" However, the selected user CI(s) must be "linked" to the created Service Request"? 

    Thursday, July 4, 2013 4:13 PM
  • Hey

    Sorry, maybe that was a bit confusing :) If you use queries, the user can select 1 or multiple CIs from a selection list. These objects will be related/linked to the Service Request. When you configure the query in the Request Offering you must choose which relationship you want to use:

    - Service Request --> Affected CI
    - Service Request --> Related CI

    This relationship will be used to relate the selected CI (User CI in your case) with the Service Request. If you want to use another relationship, you must select 1 of the 2 relationships in the above list, then export the MP and edit the XML file. Then you can choose the relationship to anything else.

    Read Patrick's post I mentioned. It's very well explained there ...

    Cheers
    Marcel


    Marcel Zehner // Blog --> http://marcelzehner.ch // Twitter --> @marcelzehner // Business --> http://www.itnetx.ch

    Thursday, July 4, 2013 4:18 PM