The Web.Wizard controls the process that the user sees to enter the data to submit a Request. It is a combination of built-in pages and custom forms.  

A typical Web.Wizard might look something like this.

Each page is shown, and when the user clicks next, the following happens:

The user clicks on a button to start a new Request.

A new Job is created in memory on the server for the specified Task.

The user enters the data and then clicks Next

Form data is sent to the server to process. 

These controls then update the Job Arguments in Memory on the server

The next page is generated and shown to the user as HTML

Repeat the process above until the user clicks 'Submit' on GenericConfirm

The Job in memory is saved to the database where the Job Service picks it up and starts the Workflow.

The Job is stored in session memory on the server

This means it is possible to lose the job if the session times out

The UI and Job can get out of sync if the user uses the Back button.

The process is quite different in mechanism.

The user clicks on a button to start a new request.

The server generates a JobViewModel for the first page

This contains a JSON model of the Job and the first form to display.

The Job is NOT stored on the server and only exists in the Model

The Job in the model contains the arguments and a securityToken. This securityToken is a SHA256 Hash of the data in the Job.

The Job data cannot be changed by the client and is sent back to the server to update.

View Model - information required to display the form

The model contains the data that can be updated by the form.

The bindings contain the mapping between the Form Controls -> Model -> ActivateBind

The bindings controls the validation and the mapping between the Model and the Job ActivateBind statements.

This also protected by a SHA256 hash and cannot be changed on the client.

The client renders the Form Controls and displays the data from the model for each control.

The user changes the Model by interacting with the controls.

The Job, Model and Bindings are sent the server

The Server validates the Model data for each binding and updates the Job with the new data.

The server then returns the updated Job with the new View model for the next page.

The GenericConfirm page will update and validate the Job and then submit the Job to Activate Orchestrator for processing.

The Job is never stored on the Web Server and only exists in the model and is stored in the history for each Page.

If the user hits the back button the Job will be restored to the correct version for that page.

Any changes made in 'future' pages are lost and the job is restored to a consistent state.

V8 Form Migration

V8 Job Submit and Form Changes

Microsoft’s cloud platform providing infrastructure, networking, storage, and application services. In Activate, it’s used as the hosting environment or for integration with Microsoft 365 and Entra ID services.

Azure

DotNetVersion

Microsoft Entra Connect (formerly Azure AD Connect) is a tool that syncs on-premises Active Directory identities with Microsoft Entra ID, enabling hybrid identity and seamless access to cloud resources.

Microsoft_Entra_Connect

Active Directory (AD) is Microsoft’s directory service that stores and manages user accounts, devices, and permissions, enabling secure authentication and centralized access control within a Windows network.

Active_Directory

ActivateJobService

ActivateAdministrator

SupportedPowerShellVersions

SupportedOSVersions

SupportedSQLVersions

Name that identifies the instance of Activate.  This is only used by Administrators and isn't displayed to end users.

instance_name

An installation type of Activate where there is no local domain connection, all authentication, authorisation and identity management is handled by Entra ID.

Cloud_Only

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud-based identity and access management service, providing secure authentication, user lifecycle management, and access control for Microsoft 365 and other apps.

Microsoft_Entra_ID

A software switch that enables or disables functionality at runtime without redeploying code. In Activate, they are configured under //Resources/Configuration/FeatureFlags.

feature_flag

Microsoft module for managing Exchange Online, using modern authentication and REST API–based cmdlets for faster, more reliable automation of mailboxes, compliance, and organisation settings.

EXO_V3_PowerShell_Module

An Organizational Unit (OU) is a container in Active Directory used to organise users, groups, computers, and other objects within a domain. OUs help structure resources logically and apply group policies for easier management and administration.

A User Type is a template in Activate that defines rules, attributes, and behaviours for a category of users (e.g., Employee, Contractor), ensuring consistent user account setup and configuration.

User_Type

A resource object in Activate representing a physical or virtual Exchange Server

Exchange_Server_Resource

Defines the object type that the resource will emulate or operate as.

Class_parameter

Clonesthe selected inherited parameter to make a local copy to override the value

Override

Runs the Activate Provisioning Server and performs actions across target systems.

Orchestrator_Account

A complete, immutable log of identity-related events, including provisioning actions, access approvals, and policy evaluations.

Audit_Trail

An integration module that enables Activate to read/write data from external systems (e.g., provisioning accounts in Azure AD).

Connector

A periodic process where managers or data owners validate that users still require their existing access — critical for compliance.

Access_Certification_and_Review

A user-initiated process to gain access to new systems or roles, often requiring manager or system owner approval.

Access_Request

Any downstream application or service where identities need access (e.g., Active Directory, Okta, Salesforce).

Target_System

The authoritative system from which identity data is imported (e.g., HRIS like Workday or SAP SuccessFactors).

Identity_Source

An access control model that uses user, resource, or environment attributes (e.g., department = "HR", location = "US") to make access decisions dynamically.

ABAC_Attribute-Based_Access_Control

An access control model where users receive permissions based on assigned roles. This model helps enforce least privilege.

RBAC_Role-Based_Access_Control

A collection of entitlements assigned based on a user’s job function or department. Roles simplify access management and are often tied to policies (e.g., "Finance Analyst Role").

Role

A specific access right or permission within a system (e.g., "Read-only access to Salesforce Reports"). Entitlements can be grouped into roles.

Entitlement

The removal or disabling of user accounts and access when they are no longer required — for example, when an employee leaves the organization.

Deprovisioning

The automated process of creating accounts and granting access to systems or applications based on a user’s role or attributes.

Provisioning

A digital representation of a user (employee, contractor, service account, etc.) within an organization. Each identity is typically linked to a unique identifier, such as an email address or employee ID.

Identity

This is the process of bringing on a new user

Onboarding

Hierarchical Role-Based Provisioning automates user access by assigning roles based on organisational structure, ensuring users inherit the correct permissions and resources aligned to their position or function.

Hierarchical_Role-Based_Provisioning

A group email address that automatically forwards messages to all its members, allowing you to send emails to multiple recipients at once.

Distribution_List

An expression is a conditional statement using Activate expression syntax.