Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
User Inputs from Portal don't get passed to Runbook

Unanswered User Inputs from Portal don't get passed to Runbook

  • 04 Mei 2012 20:41
     
     
    Masuk untuk Memilih
    0

    In SCSM 2012, after publishing a request offering, the Request Offering passed the user input to Runbook Activity, but Runbook Activity doesn't seem to pass the user inputs to Orchestrator Runbook; though Runbook still run successfully with empty parameters...

    Did I miss anything? here are some of my screenshots:

    Service Request:

    Runbook Activity:

    Patrick Zhang

     

Semua Balasan

  • 04 Mei 2012 20:43
     
     
    Masuk untuk Memilih
    0

    Addition to that: the User Name and User Group's type is Query Results, and to query the class Active directory User and Active Directory Group in SCSM, Reason is just plain text field; but none of them got passed to Runbook.

    Thanks,

    Patrick Zhang

    Patrick Zhang

     
  • 05 Mei 2012 10:36
    Moderator
     
     
    Masuk untuk Memilih
    0

    Hi Patrick,

    We need to see your Request Offering mappings and the Runbook Activity mapping in order to help you.

    Regards
    //Anders

    Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se

     
  • 06 Mei 2012 10:31
     
     
    Masuk untuk Memilih
    0

    Hi Patrick,

    I have found that you cannot have a selected item from a query result as the input to a runbook parameter and will instead need to have the selected objects added as related items to the runbook activity or the service request. Then, within the runbook, obtain the runbook activity or service request object and then get the related items. The built in Orchestrator activities were insufficient to perform the relationship lookups I wanted so I resorted to powershell scripts and SMLETS.

    You can refer to Travis Wright's excellent video at Demo: Automating Service Request Fulfillment from the SCSM Service Catalog with Orchestrator. This will give you more information.

    Good luck

    Dean

     
  • 07 Mei 2012 16:25
     
     
    Masuk untuk Memilih
    0

    Patrick Zhang

     
  • 07 Mei 2012 16:26
     
     
    Masuk untuk Memilih
    0

    Patrick Zhang

     
  • 07 Mei 2012 16:26
     
     
    Masuk untuk Memilih
    0

    Patrick Zhang

     
  • 07 Mei 2012 16:26
     
     
    Masuk untuk Memilih
    0

    Patrick Zhang

     
  • 07 Mei 2012 16:27
     
     
    Masuk untuk Memilih
    0

    thanks Anders,

    I updated more screen shots for the Request Offering and Runbook Activity Template.

    Patick

    Patrick Zhang

     
  • 07 Mei 2012 18:31
    Moderator
     
     
    Masuk untuk Memilih
    0

    Hi Patrick,

    Let's take a look at your last screenshot - you are passing the Text1, Text2 and Text3 properties as the input parameters to the Orchestrator Runbook. These Text fields are nothing more then regular string properties of the Runbook Activity within Service Manager.

    Next, you have two Query Result qestions, and the answer to these questions cannot be mapped to a regular property - instead you have to relate the objects to the actual work item. According to your screenshots you are relating the answers of the query result questions as related objects to the Runbook Activity. However, these items are NOT passed to the Runbook (Text1, Text2 and Text 3 are though, but you haven't mapped any property to those fields.)

    I strongly suggest you take a look at the blogpost that Dean linked to, as well as this blogpost:
    http://blogs.technet.com/b/servicemanager/archive/2011/11/10/demo-automating-service-request-fulfillment-from-the-scsm-service-catalog-with-orchestrator-real-world-examples.aspx

    Regards
    //Anders

    Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se