Skip to main content

v1.67 — Rapid Platform

· 3 min read
Danny Rattu
Danny Rattu
Documents

We're excited to announce new features live on Rapid Platform Monday, September 28th

Features​

Permission inheritance​

Items can now inherit their permissions from a parent record. In Designer, the Permission Inheritance section of a table's Security & Permissions tab lets you choose the parent using a lookup or universal link column. System lists can inherit too, and a record can inherit from another record in the same table, such as a quote inheriting from its parent quote. New items take on their parent's permissions when they're created, and any change to the parent's permissions flows down through every level of child items. You can also choose whether a table's items share its default permissions or have their own, and restore a record to its table's base inheritance.

Permissions admin page​

A new Permissions admin page under Maintenance in Designer shows which items have permissions that differ from their table's defaults. From here you can reset items to their defaults, bulk apply permissions to items matching a filter, or bulk set items to inherit from their parent. Every bulk change is previewed before it's applied. You can also see exactly who can access an item and where that access comes from, or pick a user or group to see everything they can access.

SharePoint permission sync in the background​

SharePoint permissions now sync in the background whenever an item is created or updated, so saving is no longer slowed down by the sync. Folder permissions follow the same inheritance as their items, and drift is detected and repaired automatically. Admins can track queued, completed and failed syncs in the new Permission Sync Events list.

Stronger Designer and Workflow permissions​

The Designer and Workflow permissions are now enforced across the API, not just in the UI. Users without the Designer permission can no longer change a site's structure, such as its tables, fields, views, menus and pages, and workflow administration requires the Workflow permission. Tables that extend another table are now protected by their own permissions, so a user with access to a base table can't read the extra fields on a table they haven't been granted.

Improvements​

  • You'll now see a confirmation, showing where an item's permissions come from, before breaking its permission inheritance
  • Permission errors from Designer and Workflow are now shown instead of failing silently
  • Searching in the principal picker is no longer case-sensitive
  • Full principal names are now shown in the permission picker and table
  • You can no longer save an empty set of permissions
  • Installing a bundle now checks its tables first and names any invalid table, instead of installing it partially
  • Site repair now carries on when a SharePoint folder can't be created for a table, and tries again on the next repair

Bug Fixes​

  • Fixed an issue where notes created from the Activity Feed didn't inherit permissions from the record they were linked to
  • Fixed an issue where a Tab Strip crashed when none of its tabs were visible to the user
  • Fixed an issue where removing a table that extends another table failed with a SQL error
  • Fixed an issue where opening a process run could crash while colouring its diagram
  • Fixed an issue where public forms failed to load on sites containing a table installed from a bundle without settings
  • Fixed an issue where pages returned a 404 when their search state contained a dot, such as an email address
  • Fixed an issue where the Creating document notification in Adaptive Designer never cleared