workflow-authoring-schema-compatibility

Maintain JSON schema compatibility during C# workflow refactoring by implementing alias shims in your DTOs to accept both canonical property names and legacy aliases during deserialization. This prevents breaking changes for existing clients sending patch payloads.

Renaming workflow properties without breaking legacy JSON payloads is best achieved using dual-contract validation and alias mapping. This approach shims older naming conventions to cleaner canonical models while keeping persisted JSON shapes and runtime validation synchronized.

Dual-contract validation for evolving workflow definitions works by enforcing strict runtime validation requirements while simultaneously allowing the backend authoring system to accept historical data fixtures and older patch envelopes through property alias shimming.

Yes, you can use alias shims in your C# data transfer objects to support both new canonical property names and old legacy aliases in API patch requests. This dual-acceptance strategy ensures backward compatibility during your data model transition.

You need alias mapping for your workflow JSON schema when transitioning from legacy property naming conventions to cleaner canonical shapes. It is required to prevent breaking existing clients, historical data fixtures, and patch payloads during backend data model refactoring.