Product Updates - v3.73

This release spans platform capabilities (a new external-integration framework and an advanced Work search API), a reporting/dashboard reliability pass, and a set of bug fixes.

🪄 Feature Updates & Enhancements

External Integration Framework

A new Rise-X integration framework lets customer-specific external API integrations be configured (in MongoDB, via the API) rather than hard-coded — each integration defines endpoints, authentication (Basic / OAuth / client-credentials / webhook / anonymous) and request/response mappings, usable from Asset Search (pull) and Automation activities (get/post/patch/store data and post attachments). (#611)

Advanced Filtering API for Work Search (Platform / V3→V4)

A new v4 Work search endpoint supports dynamic filtering, sorting and projection on work data (data.* paths), not just the fixed field set — including per-flow schema resolution, date and numeric handling, wildcards on string fields, and a schema-discovery endpoint so callers know which fields are filterable. This underpins richer, data-driven views and tables. (#880)

Permission Sync to Linked Items

View/edit permissions on a parent work item now propagate automatically to its linked child items. Previously the related-work-table could appear empty for users who had access to the parent item but no explicit permission on the child items. (#707)

Cleaner Rich-Text Display in Table View (Improvement)

Rich-text fields that contained pasted content from Word/Outlook/Excel (with embedded CSS/style blocks) were leaking that CSS as visible text in work-list table cells. Style content is now stripped so table cells show clean plain text. Related to the production filter issue #1171 below. (#1185)

🐞 Bug Fixes

Status label showed a stale name in the work view and PDF report (#1165)

After a status was renamed , Kanban and table views showed the new name but the work view and PDF report still showed the old one — because the label was cached onto the work at transition time and not re-derived. Clients saw two different names for the same status. The affected surfaces now resolve the current status label.

Action created after a rejection/rollback did not inherit shared access (#1136)

An Action created after a plan was rejected and rolled back did not receive the general-access group in its share panel, even though the invite-to-related-works activity fired — so it behaved differently from Actions created on the first pass. Access is now granted consistently on repeat submissions.

Duplicate step and task names created in no-code (#1210)

Adding a new step in the no-code builder produced duplicate step/task names — two "add step" clicks both produced "Step 2 / Task 2" instead of incrementing to the next step/task. Step and task numbering now increments correctly.

Problem Definition filter showed raw HTML characters (#1171)

The filter against a text area component presented HTML/style characters in its options list. Fixed across text-area fields available for filtering.

Status filter not showing all statuses (#1190)

Not all statuses visible on the Kanban were available in the status filter dropdown; they should all be selectable. Fixed so the filter presents the full status set. Related to the status-label work in #1165.

Dashboard month/year charts dropped a time bucket (#1245)

Aggregated dashboard charts grouped by month (or year) could omit a bucket — often the current month — due to an off-by-one in the bucket calculation, so a period chart and a KPI tile over the same data disagreed. Bucket counting now uses calendar boundaries.

Period charts dropped the latest period when records had empty dates (#1283)

Period-by-month/year charts silently dropped the most recent bucket whenever the dataset contained records with an empty/missing grouped date, because invalid dates corrupted the min/max calculation. Unparseable dates are now filtered before computing the range.

Reports showed false "Data path not found" errors on coalesced fields (#1247)

When a report field lists multiple data paths (first-found coalesce), a miss on an earlier path was reported as an error even though a later path resolved and the value was correct — filling the response's error map with misleading noise. Per-path misses are now only surfaced when no path in the field resolves.

Endpoint-backed lookups now honour configured parameters (#1295)

A search-things / data-grid thing lookup could not be filtered by a work-data value because the component didn't forward its configured parameters to the entity-search endpoint, so a parameter-driven lookup returned no data. The component now forwards its parameters.

Work owner could not delete their own work item (#1180)

A user who was both flow owner and owner of a work item could not delete it — only the work's original creator could. Delete authority now correctly recognises the work owner.

Workflow Owner permissions not updating after removal (rise-x-api #1607)

After a user was removed from the Workflow Owner list, they could still open "Manage Workflow" and enter the Builder — the permission remained "sticky" after being granted and later removed. Removal of Workflow Owner access now takes effect correctly.