SCSM Runbook Automation Activity - Number of Parameter Mappings

Question

Dear Supporters,
Can you please help me with the following problem:
I am automating the creation of new users over the SCSM Self Service Portal with the help of an Orchestrator runbook. I am configuring the Runbook Automation Activity in Service Manager and I must map all the parameters defined in the Runbook, so that they
can appear later on the Portal.
My problem ist that Service Manager has a limited number of parameters, that I can map – 10 Text, 5 Long Text, 5 Integer and so on. When I am creating the user I want to be able to enter more parameters (for example more that 10 Text fields or more than
5 Integer fields) and so the default parameter mappings in SCSM are not suffcient.
Is there a possibility to have more parameter mappings for Runbook Automation Activities in SCSM? Is there another way to solve or to workaround this limitation?
Many help in advance for all of your efforts!
Regards,
Stoyan


Answer 1

It's a little hard without actually seeing an example, but I will try to mentally visualize your approach.
My first thought would be, go back to basics, and start simple. Create the Runbook with all the Parameters needed to accomplish the automation (i.e. create the user account). I'm not sure why you are using a PowerShell script to create a new user, when there
are Activities in the Active Directory Integration Pack which will accomplish the same thing (unless you're a big PowerShell fan, and will state that it's "more" efficient; but that's besides the point). 
For some of the New User fields, is there an option to assume some of them (i.e. if you are only in Canada, then don't get the user to fill out Country, and just hard-code the value of "Canada"). That will save one field/prompt in the Portal, but
still ensure the value it set. 
For the summary email to the Manager, what information are you trying to send? Account details? You can extract those from the AD Integration Pack "Get User" activity, and reference the various field properties. The Runbook can even send the email
itself (I've done this myself), with a templated email using Activity variables that produce dynamic values. 
For the Runbook, if you have a variable in the Initiate Runbook list, then those fields must be mapped to something. From the Service Request side of things, you don't have to map everything into the Runbook. 
For the Security Group, what is the criteria to determine which group the new user should be a member of? In the example that I did for a client, I used the Title and Department. I wrote a PowerShell script (used within the Runbook), and evaluated each of
those values. I used a Switch statement to make it easier to add more in the future. Based on these values, I assigned a value to a new variable (i.e. "SecurityGroup"), and used that variable in another Activity (i.e. Update User) to add them to
the AD Security Group. 
Please remember to click “Mark as Answer” on the post that helps you. AdinE MCSE, MCSA, MCITP, MCTS; (Specializing in System Center and Private Cloud) LinkedIn: http://ca.linkedin.com/in/adinermie Website: http://AdinErmie.Wordpress.com