Software Development Lifecycle (SDLC)
The Software Development Lifecycle (SDLC) capability provides a governed, modular approach to promoting analytic workflows across environments in Alteryx One. Environments are modeled as Workspaces, allowing workflows to move through development, testing, and production in a structured and auditable manner.
SDLC makes sure every step is done consistently and in compliance. The concept of packages and promotion request in SDLC includes built-in approval steps, tools to adjust workflow dependencies between environments, and a clear record of all approvals and runs. It also provides protection to prevent key assets from being changed after approval of the promotion request.
For more details on packages, promotion requests, and other key concepts, go to SDLC Key Concepts.
Package Creation and Promotion
A creator bundles a workflow into an immutable, versioned package and submits a promotion request to an upstream workspace. A Workspace Admin reviews the request, remaps workflow dependencies for the target environment (datasets for cloud workflows or connection mapping for desktop workflows and Workspace Execution), performs a test run if needed, and approves or rejects the request.
Approved packages become immutable release artifacts that provide a consistent, traceable record of workflow promotion. They can also be labelled and certified using Data Labels, consumed by Plans and Schedules with version pinning, and support additional governance capabilities as they become available.
Role-Based Capabilities
Different users can perform different actions within the SDLC process based on their assigned capabilities within relevant roles. This ensures that promotion, approval, and execution activities are governed through appropriate access controls.
The following table outlines the available role-based capabilities within the SDLC process in Alteryx One:
Capability | Assigned To | Allowed Actions |
|---|---|---|
SDLC Promotion Request | Creator Roles (for example, Designer Cloud Creator) | Create or raise promotion requests. |
SDLC Promotion Approval | Workspace Admins (and custom roles) | Review, test-run, approve/reject promotion requests; grants Workspace Execution |
Custom Roles
Alteryx One allows administrators to create custom roles. Each role can be designed to support your SDLC process. For example, you can define roles such as Promoter or Reviewer and assign specific permissions to each one.
Packages and package specifications follow the same permission rules used across Alteryx One.
Personas
Creator | Approver | Workspace Admin | |
|---|---|---|---|
Role | Designer Cloud Creator | Workspace Admin | Workspace Admin |
Actions | Build workflows, request promotion. | Review, test, map datasets, override dependency mappings at the package level, and approve/reject promotions. | Manage workspace-level connection mappings. |
Capability | SDLC Promotion Request | SDLC Promotion Approval | SDLC Promotion Request |
Dependencies Mapping
When approving an incoming promotion request, you must map all dependencies required for the ability to run a package to equivalent dependencies in the target workspace. The type of dependency mapping required depends on the workflow type:
Designer Cloud workflows require Dataset Mapping.
Desktop workflows require Connection Mapping.
If a required dataset has no equivalent, the promotion request cannot proceed until it is resolved.
Note
Ensure that Connections and Datasets have the appropriate permissions before mapping. The system does not automatically create these objects, instead it uses only existing ones.
Only one mapping model (Dataset Mapping or Connection Mapping) can be applied to a workflow at a time. The two models cannot be used together.
For more details, go to Asset Dependencies Mapping.
Package Execution and Job History
Both in-review promotion requests and approved packages can be run:
During review: To validate workflows before approval.
After approval: To execute workflows in the target workspace.
Each job is linked to the package as a whole and not to a single workflow.
Note
The ability to run a promotion request or package depends on the user’s role and permissions in Alteryx One. Users must have the appropriate role and access to all required dependencies to run a promotion request or package.