Skip to content

2025_JUL_01

Release

ProcessFactorial.Platform

  • Version API: New endpoint to fetch the current platform version.
  • .NET 8 Upgrade: Core services migrated to .NET 8 for improved performance.
  • Flow Import/Export: APIs added to import/export specific versions of flows, forms and integrations.
  • Validation: Application form now properly rejects non-image uploads.
  • Dependency & Auth Fixes: Resolved BlobContainerClient.CreateIfNotExists errors and “Need a non-empty authority” issue.
  • Execution Runtime: Corrected negative runtime calculation for completed flows.
  • Security & Logging: Applied Snyk vulnerability patches and enhanced pipeline logging.

NPO API Management

  • Swagger Spec: Updated APIMSwagger.json for consistent endpoint definitions.

NPO Portal

  • Tiles & Login Control:
    • Option-set fields can now render as interactive tiles.
    • New customizable login control added.
  • Event & Relationship Editing:
    • Flow-definition events now fully editable.
    • Linked-record relationship UI enhanced.
  • UX Improvements:
    • Added “About” button on the Portal.
    • Confirmation dialogs revised for clarity.
    • Removed stray console logs.
  • Accessibility: Header and tool-ribbon components updated.
  • Terminology: All “Process” labels renamed to “Flow.”
  • Documentation: Journey guides updated; artifact import/export fixes applied.

NPO Customer Portal Backend

  • Condition Builder: Fixed UI issue when using “Different Business Object” in rules.
  • Security Upgrades: Express bumped to 4.21.2 and jsonwebtoken to 9.0.0 to address vulnerabilities.

Bug Fixes

Several defects addressed, including: - Multi-object field compare and action-creation errors in business-object scenarios.
- Single-action-in-step bug when creating multiple records.
- Tiles visibility logic and portal UI inconsistencies.
- “Jump to process step” configuration and runtime anomaly fixes.
- Miscellaneous spelling, layout and accessibility corrections across modules.

Deployment Steps

Note that this deployment has additional manual deployment steps, found here