← Back to Roadmap

Content Lifecycle

11 features

📋 Description

Workflow enables teams to define, manage, and track the progression of content through various stages, ensuring that each piece of content is reviewed, approved, and published according to established processes. Users can visualize the status of content items and identify bottlenecks or pending actions, supporting efficient and transparent content operations.

💎 Business Value

Improves operational transparency and throughput by clarifying ownership, highlighting blockers, and standardizing review and approval, leading to faster, more reliable publication.

🗺️ Roadmap Features (4)

Configurable statuses per workspace

Allow each workspace to define custom statuses (e.g., "Legal Review", "Tech QA") and map them to a status type. This supports local process naming while maintaining standardized reporting.

Status rules and allowed actions

Enable granular rules for each status, specifying which users or roles can perform actions such as edit, comment, request changes, approve, schedule release, or publish. Rules can enforce required checks (e.g., approvals, validations) and control status transitions (e.g., Review → Approved requires two approvals).

Status types

Define core status types: Draft, Review, Approved, Released. These represent the standard lifecycle stages for content progression.

Visibility and auditing

Display the current status, required actions, blockers, and provide a complete audit trail of status transitions, approvals, and rule evaluations.

✓ Merged to main
🕐 Development time: 12d-08h-51m⏱ Time to deployment: 0d-00h-04m

📋 Development Summary

Summary: This epic delivered a comprehensive content lifecycle management capability, including lifecycle data models, APIs, transition handling, custom status management, and audit support. The work also expanded operational tooling through configuration seeding, local HTTP setup, build/documentation updates, and safer search index management with schema drift detection. Final cleanup removed an outdated frontend delivery specification after the feature was merged to main. Key Changes: - Implemented core content lifecycle management data models and APIs, including support for additional status types such as Review and Released. - Added custom workspace status CRUD endpoints, mapper logic, optional visualization settings, and default-per-type status behavior. - Delivered lifecycle transition capabilities, including bulk transition services/endpoints, dependency validation, and transition rule retrieval/validation. - Integrated audit logging and event emission through lifecycle audit services and repository implementations for status and lifecycle operations. - Enhanced platform configuration and operations with lifecycle configuration seeding, local development HTTP configuration, API/build documentation updates, and search index schema drift detection with conditional index recreation/deletion. Impact: These changes establish a robust, auditable lifecycle framework for managing content states and transitions, improving governance and workflow automation. They also reduce operational risk by strengthening configuration management and search index handling, supporting more reliable deployments and maintainability.

🔧 API Changes (13 files)

  • M src/Aleido.Platform.API/Models/Preview/RecipePreviewResponse.cs
  • M src/Aleido.Platform.API/README.md
  • M src/Aleido.Platform.API/Services/Hierarchy/HierarchyService.Subversion.cs
  • M src/Aleido.Platform.API/Services/Hierarchy/HierarchyService.Version.cs
  • M src/Aleido.Platform.API/Services/Lifecycle/ILifecycleService.cs
  • M src/Aleido.Platform.API/Services/Lifecycle/ITransitionRuleService.cs
  • A src/Aleido.Platform.API/Services/Lifecycle/LifecycleService.BlockedAudit.cs
  • M src/Aleido.Platform.API/Services/Lifecycle/LifecycleService.DerivedStatus.cs
  • A src/Aleido.Platform.API/Services/Lifecycle/LifecycleService.ReleasePath.cs
  • M src/Aleido.Platform.API/Services/Lifecycle/LifecycleService.cs
  • M src/Aleido.Platform.API/Services/Lifecycle/TransitionRuleService.cs
  • M src/Aleido.Platform.API/Services/ObjectService.cs
  • M src/Aleido.Platform.API/Services/Translation/TranslationService.Jobs.cs

📝 Commit Log

47c193ff5 Refactor XML docs for clarity and conciseness 62e6aa6ce feat(lifecycle): converge on updated 024-content-lifecycle rules (Phase 12) c8036f361 Merge branch 'main' into 024-content-lifecycle 4d3d929d3 docs(024): update lifecycle API documentation to clarify known issue with ETag usage and enhance schema definitions d0126c405 docs(024): enhance lifecycle API documentation with concurrency model and schema details 847aec632 refactor(024): reconcile lifecycle API paths and enhance approval endpoints in lifecycle-api.yaml 0c6e52339 docs(024): update lifecycle API documentation and quickstart with correct endpoint paths 0894ef469 fix(024): correct DeriveObjectStatus to return latest version's status f02bbce7d refactor(024): update lifecycle configuration storage and enhance tests documentation 0b3764faf spec(024): align lifecycle artifacts with PO updates and convergence work c46ffb223 Merge remote-tracking branch 'origin/main' into 024-content-lifecycle 6b39042df Merge branch 'main' into 024-content-lifecycle 9800eaeaa spec(024): allow translation submission from Approved or Released status f9e4decec spec(024): remove mandatory review, make Approved the release gate, block Released→Draft for all users afeddb088 024-content-lifecycle: moved spec from archive to active

💻 Development Features (7)

Lifecycle Status Queries and Transitions

No description available

Approvals Workflow

No description available

Audit Logging

No description available

Dependencies Validation

No description available

Lifecycle Configuration Management

No description available

Final Validation and Documentation

No description available

Bulk Transitions

No description available

📋 Backend Requirements (3)

Related requirement tasks from other projects

✓ 2.12 - System supports the capability of a collaborative web review process

To Do

Description Platform Status: will be supported PPT Status: Roadmap MVP: Yes Must Have: Priority 1 (A) Notes Delve into review requirements and investigate Have functional requirements of web review tool

View in Azure DevOps →

✓ 2.22 - System shall allow assigning multiple reviewers in parallel order.

To Do

Description: Allows multiple reviewers with configurable approval order. Platform Status: supported PPT Status: Roadmap MVP: Yes Must Have: Priority 1 (A) Notes already Assign users for specific roles Check if it's all or one of the reviewers needs to be able to approve. Discussion thread between reviewers Not just comment on the object, but the specific parts Get very clear configs (business rules) from AGCO Based on product line When sending it out for review is it when: You configure the review workflow Is it pre-configured Pick one config to demo. Notes: Assign users for roles; check all or one approval conditions; discussion threads; comment on specific parts; business rules from AGCO; product-line-based configuration; config demos.

View in Azure DevOps →

✓ 2.13 - System allows multi-level workflows

To Do

Description Supports multi-level workflows for translation/review tied to Windchill. Platform Status: will be supported PPT Status: Roadmap MVP: Yes Must Have: Priority 1 (A) Use Case not started, in work/draft, in review, review complete,in translation, translation complete, ready to publish, published…) Current Challenges Current toolset is limited to the workflows that are approved program-wide. Tech info wa more specific workflow needs. Notes In place when translation and review are implemented Has to do with Windchill need more tech writer, information architect focused. Notes: In place when translation/review implemented; requires tech writer/info architect focus.

View in Azure DevOps →