> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/04-11-26-release-notes-core.md). # 04/11/26 Release Notes (core) TBC > **Release date:** 4th November 2026 *** ## New Features #### **New Shape: Cross Reference** Process flows can now read and write [cross-reference lookups](https://doc.wearepatchworks.com/product-documentation/process-flows/cross-reference-lookups) directly, using a new Cross Reference shape. Previously, cross-reference lookups could only be used within [mapping transformations](https://doc.wearepatchworks.com/product-documentation/process-flows/cross-reference-lookups/using-a-cross-reference-lookup-in-field-transformations), and keeping them up to date meant editing values by hand or building cache-based workarounds. The new shape lets a flow maintain a lookup as data passes through - for example, after creating a product in NetSuite, write the returned internal ID against the SKU, ready for any other flow to use. Records in a cross-reference lookup do not expire and are available to every flow. * **Upsert** - match on a key field and insert the record if it's absent, or update it if it's present. The payload passes through unchanged, and the run log summarises what happened (e.g. `4 inserted, 0 updated, 0 unchanged, 3 skipped`). * **Lookup** - match on a key field and write the matched value to a target field in the payload. Choose the lookup direction (left to right or right to left), a match type (exact, starts with, contains) and an output type (string or integer). Keys with no match use the lookup's default value, if one is set. * **JSON & XML support** - target fields with wildcard paths for arrays (`products.*.sku`) in JSON, or XPath (including namespaces and attribute targets) in XML. Flow variables can be used in paths. * **Safe to manage** - a lookup can't be deleted while a flow references it, and renaming a lookup won't break the flows using it. The shape is fully supported in flow duplication, export/import and blueprints, with lookups included as blueprint dependencies. *** #### **New Shape: Data Transformation** A new [Data Transformation](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/data-transform-shape.md) shape handles common payload transformations without writing or deploying a custom script. Pick from a library of predefined transformations and stack as many as you need in a single shape. Transformations run in order (drag to re-sequence), each one shows what it accepts and produces, and you can test the whole sequence against a sample payload before saving. Transformations are maintained centrally by Patchworks and versioned: when a newer version is released, flows already using the previous version keep running unchanged - older versions simply emit a warning in the run log and can no longer be selected for new use. Bespoke transformations can also be added privately for a specific company - contact support if there's a script you reuse often enough that it should be on the list. *** #### **Review Patchworks - In-App Reviews** You can now rate Patchworks from inside the dashboard. A new **Review Patchworks** option in the sidebar (and an occasional prompt, with *remind me later* and *don't ask again* options) asks one question: how likely are you to recommend Patchworks to a colleague? *** ## Improvements #### **Mapping: handle null & empty values before transforms** Map V2 can now remove or skip null and empty values earlier in the mapping flow, so transforms like Date Format are less likely to fail when source data is missing or blank. * **Remove if null / Remove if empty** (source fields) - drop a mapping row entirely before any transforms run. For example, a `cancelled_date` field that's sometimes null can be excluded from the output instead of breaking a date transform. * **Skip if null / Skip if empty** (transforms) - bypass the transform and pass the value through unchanged. Existing maps are unchanged until these options are turned on. The new behaviour applies to Map V2 JSON mapping; XML and legacy mapping are not affected. One thing to note: skipping a transform in the middle of a transform chain may behave unexpectedly if a later transform depends on its output. Labels for the new toggles are English-only for now, with other languages to follow. *** #### **AI Studio agent updates** * **Assistant suggestions** - the Assistant now steers you to the right agent for the job. Ask it to document or explain a flow and it offers the Documentation Agent; tell it you're migrating from another platform and it offers the Migration Agent - alongside the existing Implementation Agent suggestions. * **Migration Agent map building** - when auditing an export from another platform, the Migration Agent now builds the field mappings it finds into Map shapes on the proposed flow, rather than leaving mapping as a manual follow-up. * **Health Monitor payload access** - when diagnosing a failed run, the Health Monitor can now retrieve the payloads saved against that run. It summarises what's there and asks before opening payload contents - so a large run with many payloads won't be dumped into the conversation. Payloads remain subject to the standard retention period. *** #### **Versions page: "used in" for non-deployed versions** The *used in* indicator on the flow versions page now appears for non-deployed versions too, not just the deployed one. *** ## Bug Fixes **Try Catch retries no longer repeat successful requests** - when one payload in a batch failed inside a Try Catch, the retry re-sent every payload from the beginning, including those that had already succeeded - which could create duplicate records (e.g. duplicate orders) in the destination system. Retries now re-send only the failed payload; anything already sent successfully is sent once. **Database endpoints: "Open endpoint" link** - choosing *Open endpoint in new tab* on a connector step using a database connector now opens the correct query page instead of an invalid endpoint URL. Other connector types are unaffected. *** *For questions about this release, please contact the Patchworks support team or refer to the* [*product documentation*](https://doc.wearepatchworks.com/product-documentation)*.*