September 22nd - Sprint 211 Release Notes

Happy Sprint Release Day! 🚀

We’ve packed this sprint with enhancements designed to give your teams more control, visibility, and flexibility across their workflows. This release adds smarter workflow controls for conditional positions and generative workflows, data-readiness gates for Copywriting, Outfit Readiness filtering for production planning, richer production context through MCP and more.

We're always eager to hear your thoughts, so don't hesitate to share your feedback.

You can now manually enable or disable photography positions governed by conditional rules without changing product data to work around an edge case. The override follows the familiar production-type pattern, clearly shows whether the current state is rule-controlled or manually overridden, and can be reverted when the position should return to conditional-rule control.

Conditional position override can be applied in bulk across multiple Product Requests.

This feature is available across Gamma, Kelvin & Chroma.

Learn More: How to Override Conditional Rules

We've introduced a "Stop at Trigger Step" setting in position settings, giving you a direct way to mark a position as input for an Generative production rather than something you deliver. Once a trigger passes the shot to the AI production, the asset completes that step and stops there, so post-production and delivery steps don’t receive the unnecessary work.

Learn More: Generative Style Guide Settings

You can now choose to have Copywriting tasks wait for the product data a writer needs before they move to To Do status. The Data Readiness gate prevents tasks from opening against empty or incomplete fields which reduces blocked work, AI Pre-Writing done with incomplete data, and the need for writers to chase missing information outside Creative Force.

To enable Data Readiness, go to Style Guides > Copywriting tasks and select the options relevant for the task.

Learn More: Copywriting: Style Guides

A new connection method is now available for the Azure Blob connector: Client Credentials. This provides an identity-based path for Blob connectivity and expands the connector’s supported authentication choices. Once Blob is added as a Data Source in Studio settings it will be available for use in your workflows.

Learn More: Azure Blob connector

You can now display selected product properties directly in Hue and the Hue Photoshop panel. Properties such as colour appear on the Hue’s review screen and in a new dedicated section of the Photoshop panel, so retouchers can check the details they need without leaving their workflow.

Studio settings control which properties are shown - this reuses the existing display and alert settings in the properties section. Hue’s settings control the visibility and placement of the property section in the Photoshop panel.

Learn More: Hue panel features

You can now filter productions by Outfit Readiness in the Production view and when assigning productions to sessions in Planning. Choose Ready, Fallback, or Not Ready to narrow the list to the work you care about, so productions whose outfit samples aren't available yet don't get scheduled by mistake.

A new Outfit Readiness column is also available in both places. It shows the readiness status of the outfits created for each production, and hovering over the label reveals the full breakdown. The column can be saved as part of a Saved View.

Learn More: Outfits overview

Users can retrieve the working Display Image for pre-capture items for samples and also query sent/expected/returned External Post counts for Ecom productions. This enhances the details available with MCP, enabling you to see sample images and properly detect risk on deadlines and production completeness.

Learn More: MCP Server

In Dreem, we released a better way to handle Creative Force QC rejections, so sending a replacement back no longer depends on hitting an exact drop target. We also added content templates to the Studio start screen.

When a shot is rejected in Creative Force, you can now name the target position, or the rejected asset itself, and drop the replacement there. If several assets in the same position were rejected, Dreem asks which one you mean. A drop that cannot be accepted now tells you why instead of doing nothing. We also fixed a bug where Submit to Creative Force could send an asset from a different session, so the wrong image reached QC.

The Studio start screen now opens on a wall of content templates, so you can start from a shot that already works instead of a blank page. On the mobile app, you can start from a photo in your camera roll, and you get a push notification the moment a generation finishes. You can also delete your own uploaded images and add several sessions to a project at once.

Learn More

We’re always striving to create the best product for you and your team! Feel free to drop us a line via email/chat, or submit your ideas and feedback directly to our product team via product@creativeforce.io.