Gridpro AB

Rev: 1.2008.2074 (Azure Stack 2008)

Published: November 2020

What is a Request template?

The 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. Once submitted, it creates a request object that contains a workflow that can be tracked in the My requests node. Instead of just deploying a resource, a workflow is initiated containing multiple activities such as approvals, webhooks, manual tasks, ARM deployments, etc.

Overview

Security

By default, published request templates in Marketplace can be accessed by any user in the same tenant directory as the EvOps account, or tenants that have been selected as whitelisted in the EvOps account. In the Security section, you can override this behavior and configure that only specific users or groups can access the request template in the Marketplace. Request templates will still be visible for all users, but when trying to access the request template they will receive a message that they do not have access to it.

Marketplace

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

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:

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 can 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:

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. 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