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
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
Development
Single instance development environment with PMIS integration
Quality Assurance
Testing environment with flexible deployment options
Production
Live production environment
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
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.
User Story Workflow
Complete development lifecycle from assignment to completion
Assign User Story
User story is assigned to a developer
Unassigned → AssignedStart Development
Dev starts working, status changes to 'In Dev'
In DevCommit Changes
Check in changes to Deployment Server
CommittedCode Review
Automatically sent for review
In ReviewApproval Decision
Reviewer approves or requests changes
Approved / Request ChangeAssign User Story
User story is assigned to a developer
Unassigned → AssignedStart Development
Dev starts working, status changes to 'In Dev'
In DevCommit Changes
Check in changes to Deployment Server
CommittedCode Review
Automatically sent for review
In ReviewApproval Decision
Reviewer approves or requests changes
Approved / Request ChangeRequest Changes Loop
If changes are requested, the story returns to "In Dev" status
Unified Repository Experience
The old Repository is now the new Deployment Server with enhanced organization capabilities
Organization Hierarchy
Users create
Organizations
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.
Deployment Packages
Build management
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
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
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
Package Versioning
Clear versioning format: [Major].[Package].[Build]
Manually set release line
Increments per package
Increments per build
Version Progression
Package created, build number starts at 0
First build added to the package
Sixth build in the current package
New package created, build resets to 0
Manually set, represents major release line (default: 1)
Increments when new package is created after release
Resets to 0 when promoted to production
Conflict Detection & Resolution
Identify and resolve conflicts before deployment with centralized conflict reporting
Central Conflict Report
View all conflicts before attempting deployment
Your
Package
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.
Override
Replace entity on target
The entity from your package will overwrite the version currently on the target environment, replacing it with your changes.
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.
Deployment Options
Flexible deployment strategies for QA and Production environments
Auto Deploy
Automatically deploys builds when a new build is created
Manual Deploy
Every build has user action to deploy to target environment
Scheduled Deploy
Schedule date and time to deploy the package
QA Environment Flexibility
Run unit tests on QA environment
Set environment as UAT for user acceptance testing
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.
Complete Process Flowchart
End-to-end visualization of the Deployment Server workflow from development to production
External PMIS
Jira, Azure DevOps, etc.
Import User Stories
Sync work items
Dev Server PMIS
Centralized management
Create Sprint
Group user stories
Assign Developer
Allocate work
Start Work
Status: In Dev
ACTIVE DEVELOPMENT
Auto Send for Review
On check-in
Approved
Story Complete
Request Changes
Back to In Dev
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
Auto Deploy
Deploys automatically on new build
Manual Deploy
User action required (Default)
Scheduled Deploy
Set date and time
Package Completed
After production deployment, a new package is created automatically. Version increments from 1.0.6 to 1.1.0