Follow

EvOps for Azure Stack - Request Templates

Gridpro AB

Rev: 1.0.7820

Published: December 2017

 

What is a Request template?

Request template is an object in an EvOps account that contains marketplace metadata, wizard input definition and workflow that can be published in the Azure Stack Marketplace.

When a user clicks on a published request template-based Azure Stack Marketplace offering, it is presented with the wizard experience defined in the template and once submitted it creates a request object that contains a workflow that can be tracked in My requests node. Instead of just deploying a resource, a workflow is initiated and can contain multiple activities such as approvals, webhooks, manual tasks etc. plus of course ARM deployments.

 

Overview

Marketplace

Marketplace section of the request template contains all information that is visible in the Azure Stack Marketplace:

Name

Description

Display name

Name shown in Azure Stack Marketplace

Name

Unique name that is generated or can be set manually

Publisher

Name of publisher

Summary

Brief description of offering

Category

Select an existing or create a new category that the offering should belong to

Template type

Type of template, Incident or Service Request

Long summary

Description of offering

Icons

Upload icons in png format for offering in sizes:
Small (40x40); Medium (90x90), Large (115x115) and Wide (255x115)

Screenshots

Upload screenshot in png format for offering in size 533x324

Useful links

One or multiple weblinks e.g. Product Page, Support etc.

Description

Detailed description of offering in HTML format

When creating a request template, you only set a subset of the options, you need to edit the request template after creation to set all options.

 

Wizard

In this section you design the wizard experience for the offering. You can design your own lists and SKUs and set fields as required and with conditions.

There are two wizard modes available:

Simple Mode: Prompts are listed on one blade

Wizard Mode: Prompts can be grouped in steps

The wizard journey is then design by adding prompts of diverse types, please see below table for available prompt types:

Name

Description

Textbox

Single line text input

Multiline Textbox

Multiline text input

Checkbox

True/False input

Date

Date input

Time

Time input

Datetime

Date and time input

List

List selection input

Numeric

Numeric input

Options

Multiple options input

Resource picker

Select ARM resource that can be filtered on type

Slider

Drag slider input

Resource group

Select resource group

Subscription

Select subscription

Location

Select location

SKU

Lets you create your own SKUs for selection

Password

Masked prompt for passwords

 

Visibility

Visibility can be configured per prompt, based on a condition on value in another prompt.

Validators

Depending on prompt type, validation can be applied. Example validation could be required.

Workflow

Here you design the optional workflow that will be initiated once the request is created. A workflow consists of a sequence of activities that will be processed.

See below table for available activities:

Name

Description

Review

Configure an approval/reviewer to continue the workflow

Manual

Set a manual step that is required in the workflow

Deployment

ARM deployment template in the workflow

Runbook

Execute Service Management Automation (SMA) runbook

Webhook  

Initiate outbound Webhook from the workflow

Delay

Inject a timer for x number of seconds/hours/days

 

Mappings

When wizard and workflow have been defined, the input needs to be mapped to the request and activities. To assist, there are three different binding types:

Name

Description

Default

Accept any default value already set

Static

Set a fixed value

Simple binding

Map a value direct

Advanced binding

Map a value and modify it

 

Publishing

To make the request template available in the Azure Stack Marketplace, you need to publish the template:

  1. Open targeted Request template
  2. Click Publish
  3. Refresh browser
  4. Done

 

Create a Request template

Please follow the steps below to create a request template:

  1. Open your EvOps account
  2. Click Request template tile
  3. Click New
  4. Provide a Display name for your template
  5. Accept or modify the generated unique Name
  6. Provide a Publisher
  7. Provide a brief description in Summary
  8. Select Create new or Use existing category
  9. Select Template type
  10. Click OK to create template
  11. Click newly created template in list
  12. Click Wizard and design your wizard experience
  13. Click Workflow to author your workflow
  14. Click Mappings to set all values
  15. When done, click Publish to make the request template available in Marketplace

 

Export/Import Request templates

Request templates can easily be exported and imported. Please follow the below instructions to export/import request templates.

Export

  1. Open your EvOps account
  2. Click Request template tile
  3. Click the Request template you want to export
  4. Click Export
  5. Done

Import

  1. Open your EvOps account
  2. Click Request template tile
  3. Click Import
  4. Browse and select an evpkg file for import
  5. Edit Display name and Name if required
  6. Click OK to import
  7. Done

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments