Enterprise-Grade

Deployment Server

A fully integrated, enterprise-grade control plane for managing your entire deployment lifecycle end-to-end.

Project Management

Organize with Organizations

Environment Management

Dev, QA & Production

Deployment & Testing

Automated Workflows

Account Management

Roles & Permissions

Core Capabilities

One centralized place to manage everything end-to-end

Project Management (PMIS)

Associate every entity with User Stories for end-to-end tracking. Fully integrates with external systems like Jira, ADO, and more.

Environment Management

Connect Dev, QA, and Production environments via secure keys with special tags for environment identification.

Observability

Track commits, builds, deployments, and user stories with full visibility across all environments.

Secure Connection

Environments connect to Deployment Server via secure keys with environment-specific tagging.

Environment Types

Three environment types supported - Dev is limited to a single instance, while QA and Prod support multiple instances

All environments connect to Deployment Server via secure keys with environment-specific tags for identification

DEV

Development

Single instance development environment with PMIS integration

PMIS System

User Story Tracking

Sprint Management

Code Check-in

Single instance only

Quality Assurance

Testing environment with flexible deployment options

Unit Testing

UAT Configuration

Flexible Deploy Schedule

Build Validation

Multiple instances supported

PROD

Production

Live production environment

Final Deployment

Package Promotion

Version Increment

Release Management

Multiple instances supported

Dev Server

Integrated PMIS System

The Dev Server features a new Project Management Information System (PMIS) that centralizes all development workflow management, eliminating the need to continuously rely on external systems.

External PMIS Integration

Fully integrates with Jira, ADO, and other external project management systems

User Story Import

Import user stories to continue workflow within Decisions - everything in one place

Sprint Management

Sprints wrap user stories, providing organized development cycles

Team Assignment

User stories can be assigned to developers who then start working on them

Active Work Indicator

US-1234 Active

When a developer starts working on a user story, a visual indicator appears in the portal header showing the active story. All new changes automatically get tagged with that user story.

UnassignedIn DevIn ReviewCompleted

User Story Workflow

Complete development lifecycle from assignment to completion

Assign User Story

User story is assigned to a developer

Unassigned → Assigned

Start Development

Dev starts working, status changes to 'In Dev'

In Dev

Commit Changes

Check in changes to Deployment Server

Committed

Code Review

Automatically sent for review

In Review

Approval Decision

Reviewer approves or requests changes

Approved / Request Change

Assign User Story

User story is assigned to a developer

Unassigned → Assigned

Start Development

Dev starts working, status changes to 'In Dev'

In Dev

Commit Changes

Check in changes to Deployment Server

Committed

Code Review

Automatically sent for review

In Review

Approval Decision

Reviewer approves or requests changes

Approved / Request Change

Request Changes Loop

If changes are requested, the story returns to "In Dev" status

Deployment Server

Unified Repository Experience

The old Repository is now the new Deployment Server with enhanced organization capabilities

Organization Hierarchy

Users create

Organizations

Organization

Projects

Deployments

Environments

Organizations

New grouping concept

Organizations allow you to group projects together for meaningful deployment. Perfect for customers with different lines of business, separate auditing requirements, or data segregation needs.

Organization A

Project 1

Project 2

Organization B

Project 3

Deployment Packages

Build management

Active PackageIn Progress

Commit #45 - US-1234

Commit #44 - US-1233

Build 1.2.3

Every check-in appears as a commit with entity data. User stories can be added to the deployment package, creating builds automatically.

Two Ways to Create Builds

Method 1

Manual Addition

Develop features on the Dev environment

Commit changes to Deployment Server

Manually add user stories to the package

Each user story creates its own build

Best for: Selective deployments

Method 2

Auto-Configuration

Configure user story from Dev Server

Set to auto-add to deployment package

Every commit auto-creates a build

Builds added inside active package

Best for: Continuous integration

Commit

User Story

Build

Deploy

Package Versioning

Clear versioning format: [Major].[Package].[Build]

Major

Manually set release line

Package

Increments per package

Build

Increments per build

Version Progression

1.0.0

New Package

Package created, build number starts at 0

1.0.1

Build Created

First build added to the package

1.0.6

More Builds

Sixth build in the current package

1.1.0

After Release

New package created, build resets to 0

Major Version

Manually set, represents major release line (default: 1)

Package Increment

Increments when new package is created after release

Build Reset

Resets to 0 when promoted to production

Pre-Deployment Validation

Conflict Detection & Resolution

Identify and resolve conflicts before deployment with centralized conflict reporting

Central Conflict Report

View all conflicts before attempting deployment

Your

Package

Compare

Target

Environment

What the Server Checks

Entity Changes

Detects modifications on target environment

Package Version

Shows entity version from your package

Target Version

Shows current version on target environment

Example Conflict Report

Entity	Package Ver.	Target Ver.	Status	Resolution
UserForm.flow	v2.3	v2.1	Conflict	Override
PaymentRule.rule	v1.5	v1.8	Conflict	Ignore
Dashboard.page	v3.0	v2.9	OK	—

Resolution Options

Ignore

Skip deployment of entity

The conflicting entity will not be deployed to the target environment. The existing version on the target remains unchanged.

Entity skipped during deployment

Override

Replace entity on target

The entity from your package will overwrite the version currently on the target environment, replacing it with your changes.

Package version deployed to target

Unified Resolution Across Environments

When you set a resolution for a conflicting entity, that resolution applies to all target environments. You cannot set different resolutions for different environments — ensuring consistent deployment behavior across your entire infrastructure.

Prod

Same resolution applies

Deployment Options

Flexible deployment strategies for QA and Production environments

Automated

Auto Deploy

Automatically deploys builds when a new build is created

Default

Manual Deploy

Every build has user action to deploy to target environment

Planned

Scheduled Deploy

Schedule date and time to deploy the package

QA Environment Flexibility

Unit Testing

Run unit tests on QA environment

UAT Configuration

Set environment as UAT for user acceptance testing

Flexible Configuration

Configure deployment schedule per environment

Package State: Each deployment package is initially in In Progress state. Builds contain user stories which have entities associated with them.

Project Observability

Unit Test Results on Deployment Server

Centralized visibility of unit test execution across development and QA environments, with results tracked at both build and package levels.

Unit Test Execution Flow

Developer Commits

Code changes pushed to repository

Development Server

Unit Tests Execute

Tests run automatically at project level

Development Server

Auto Deploy to QA

If configured, build deploys automatically

QA Server

QA Tests Execute

QA server runs configured unit tests

QA Server

Results to Deployment Server

Test results sent at build/package level

Deployment Server

Step 1Development Server

Developer Commits

Code changes pushed to repository

Step 2Development Server

Unit Tests Execute

Tests run automatically at project level

Step 3QA Server

Auto Deploy to QA

If configured, build deploys automatically

Step 4QA Server

QA Tests Execute

QA server runs configured unit tests

Step 5Deployment Server

Results to Deployment Server

Test results sent at build/package level

Observability Features

Build-Level Visibility

View test results associated with each specific build version

Package-Level Tracking

Track test outcomes at the package level for granular insights

Cross-Environment Results

Compare test results from Dev and QA environments in one place

Historical Analysis

Review test trends and patterns across multiple deployments

Centralized Test Intelligence

The Deployment Server acts as the central hub for all unit test results. Whether tests run on the Development Server during commit or on the QA Server after auto-deployment, all results are aggregated and made visible at both the build and package level for comprehensive project observability.

Automated test execution on commit

Auto-deploy triggers QA testing

Results tracked per build & package

Roles & Permission Management

Centralized account management with role-based access control. Manage team permissions directly from the Deployment Server.

Environment Access Matrix

Role	Dev	Test	Prod
Project Managers
Developers
QA
Reviewers
Users

Project Managers

Full oversight and control across all environments

Environment Access

DevTestProd

Permissions

View all builds
Deploy to any environment
Manage team access

Developers

Build and deploy code in development environment

Environment Access

Dev

Permissions

Create builds
Deploy to Dev
View Dev logs

QA

Test and validate builds in test environment

Environment Access

Test

Permissions

Run tests
Deploy to Test
Report issues

Reviewers

Code review and approval in development

Environment Access

Dev

Permissions

Review code
Approve builds
View Dev environment

Users

Access production applications

Environment Access

Prod

Permissions

Access Prod apps
View release notes
Submit feedback

Project-Specific Access Control

Access can be granted or revoked on a per-project basis directly from the Deployment Server. Administrators can override default role permissions for specific projects, allowing flexible team configurations while maintaining centralized control.

Complete Process Flowchart

End-to-end visualization of the Deployment Server workflow from development to production

PHASE 1: EXTERNAL INTEGRATION

External PMIS

Jira, Azure DevOps, etc.

Import User Stories

Sync work items

Dev Server PMIS

Centralized management

PHASE 2: SPRINT MANAGEMENT

Create Sprint

Group user stories

Assign Developer

Allocate work

Start Work

Status: In Dev

ACTIVE DEVELOPMENT

Portal Header Indicator

Changes Tagged to Story

Complete & Check-in

PHASE 3: CODE REVIEW

Auto Send for Review

On check-in

Reviewer Decision

Approved

Story Complete

Request Changes

Back to In Dev

PHASE 4: DEPLOYMENT SERVER

Commits Sync

All check-ins appear

Organization

Group projects

View PMIS Data

Stories & Sprints

Add to Package

Select user stories

DEPLOYMENT PACKAGE CREATION

Method 1: Manual Addition

1Develop on Dev Environment
2Commit to Deployment Server
3Manually add stories to package
4Each story creates a build

Method 2: Auto Configuration

1Configure story in Dev Server
2Set to auto-add to package
3Every commit auto-creates build
4Builds added to active package

Package Version Format

1.0.0

MajorPackageBuild

PHASE 5: ENVIRONMENT DEPLOYMENT

Auto Deploy

Deploys automatically on new build

Manual Deploy

User action required (Default)

Scheduled Deploy

Set date and time

DEVDevelopment

Deploy

QATesting & UAT

Unit TestsUAT

Promote

PRODProduction

Live

Package Completed

After production deployment, a new package is created automatically. Version increments from 1.0.6 to 1.1.0

Key Benefits

Deployment Server Advantages

The unified Deployment Server provides significant improvements over traditional repository management

Organization

Group projects by business unit

Logical separation for different teams or departments

Data segregation

Isolate sensitive data between organizations

Separate auditing

Independent audit trails per organization

Build Management

Automatic build creation

Builds generated from user story commits

Flexible packaging

Manual or auto-add to deployment packages

Version tracking

Clear versioning with commit history

Deployment Control

Multi-environment support

Dev, Test, Acceptance, Production workflows

Controlled releases

Stage deployments through environments

Rollback capability

Quick revert to previous builds

Collaboration

Team visibility

See all commits and changes in one place

User story tracking

Link commits to business requirements

Conflict resolution

Intelligent merge conflict handling

Testing & Quality

Unit test visibility

View test results from test and production environments

Cross-environment tracking

Compare test outcomes across Dev, Test, and Prod

Quality metrics dashboard

Centralized view of test pass/fail rates per build

Unlimited

Organizations

Scalable

Projects per Org

Automated

Build Tracking

Multi-tier

Environments

Visible

Test Results