Embotics® vCommander® includes a service request form designer which is used to create the forms that appear in your service portal. There are two types of forms, for new service requests and change requests. vCommander 5.5.1 introduces the blueprint model, where the forms for individual components are created in the Service Catalog, but administrators who have upgraded will continue to see legacy component forms until they complete the transition to the blue print model. Legacy component forms will be fully deprecated in a future version of vCommander.

A few default service request forms are available right away:

  • Default Service
  • Decommissioning Request
  • Resource Change Request


These three forms are global, which means they are used whenever a user or group does not have another form of the same type specifically assigned to them. When a form is specifically assigned, either directly or via group membership, that form will always be used.

There can only be one global new service request form available at any time. All others must be assigned to specific groups or users. You can have any number of change requests, including those that are global. An image of a globe beside the the form indicates it’s globally available, and a group icon indicates that it’s available only for specified users or groups.

You can configure your approval workflows so that the form used to submit the request determines who the receives the approval email. The most common use for this configuration is to provide forms for departments who already have groups created in Active Directory, and have requests generated from those forms go to the correct department head.

Configuring Conditional Approval

When designing the approval workflow to choose an approver based on which form was used to generate the request, you will add a conditional step for each form. These steps will send an approval email to a recipient you define, for example a department head, only if the form specified as the condition was used.

  1. Login to Embotics vCommander® and choose Service Request Configuration under Configuration.
  2. Switch to the Approval Workflow tab and click Add.
  3. On the Name & Type page, enter a meaningful name for the approval workflow. Choose to apply this workflow when a new request is created.

  4. On the Assignment page, choose to make the workflow global or add specific users or groups for whom it will be used. Click Next.
  5. On the Steps page, click Add and choose Send Approval Email.
  6. Edit the Step Name to something meaningful, such as Check Dept: Development.
  7. Choose Execute when conditions are met for Step Execution.
  8. Click Edit and enter the Condition #{request.form.menuText} -eq “Developers New Service Requests”. Click OK.

  9. Add recipients to the Address List. When a request originated on the named form, one of these people will have to approve it in order for it to continue.
  10. Edit the Email Subject and Email Body as suitable for your needs.
  11. Repeat steps 8 – 10 for each form you want to be handled by the workflow, then click Next.
  12. On the Automation Options page, choose whether or not requests are automatically deployed. Check Set primary owner as administrator to add the requester to the local Administrators group on deployed Windows VMs. Click Next.
  13. Review your configuration on the Summary page and click Finish when complete.

See Also