Hi All ,
As you all know , user can request VM and can do the entitled actions for each Business Group but I need to create a ticketing workflow as well , I have tried to create the vCO workflow and publish it using advance service designer .
But still it is not up to the mark , If anybody has tried this . please share your inputs here.
Hi Echotome ,
Below is the requirement , i just giving the form here what I am looking and tried ;
Username : Auto populate by the current user login in VCAC from SSO /LDAP
Business Group : Multiple Fields , select appropriate
Ticket Type : New Ticket / Issue-/Outage
Ticket Category : Multiple Network | Linux | Windows | VM
Subject : What is went wrong.
Severity : critical | medium | high | low
Impact : description of the impact.
Issue description : -
I have tried to created the VCO and added above as inputs and presented to advance service designer and published as a service blue print in catalog items.
I have stuck in the Username part where it is not automatically populating based on the current login .
I don't know if is possible to autocomplete the request form, but you can remove that field and grab the username when the Workflow starts.
You can see it in this link:
Regarding form presentation: Design the entire thing in vRO. Current user is a passed in entry from ASD as already stated in this thread. Just assign that value without adding it to the form. Other form entries... play around with the Presentation Properties in vRO. Each "input" can have presentation properties from a list of defined items, constraints, and even OGNL calls over to "actions" (functions) that can reach out to data sources to gather information based on whatever criteria you specify. (even from other form inputs) You can also hide/show input fields based on data within the field. Once your workflow is created with all the right inputs... then create your ASD Resource Action or Service Blueprint. All the form design you put into vRO will work in vRA (VCAC). Exception: some of the OGNL date stuff doesn't work.
Regarding ticket lifecycle and actions: Each ticket that gets created can be stored as an inventory item via Custom Resources. First you would create a Dynamic Type that points to database row entries of your "Ticket" type. The database entries serve as a lifecycle representation of any "real" tickets that are generated in your downstream ticketing system. Your workflow that provides the "presentation" of the input properties RETURNS the DynamicType:Ticket object type. In doing so the Resource Action or Service Blueprint is set to "provision" that type and you can pick the return from the workflow as the item provisioned. Then you have the ability to create Resource Actions against each created ticket "resource item".
I deleted the dynamic types example I was playing around with... but the concept is similar with this return from the AD plugin. It just shows that a ADGroup-aaS Custom Resource object/item is returned with associative metadata and also actions can be leveraged against it. I only have one defined action... but you could have many more as necessary... like any action you would do against a ticket. Each action is a new workflow that uses the item (e.g. ticket) instance as the source (data) to run the action against.