Application history and the audit log agree on related records - Product News

Four fixes from the sweep of the API's own test suites, two of them visible to Administrators.

Fixed

• Application History lists related records by the audit log's rules. An entry about a refund, a repayment, a Fund, a generated milestone schedule, a referee request or a duplicate check that names an Application now appears under the reach of its own record type (payments, milestones, applications), exactly as the Audit log decides it. A record type your Data Access Rules do not reach stays hidden, as does a record no rule covers.
• Thirteen newer record types have audit-log visibility rows. Accounting bill syncs, AI draft suggestions, milestone AI comparisons and referee requests are decided as their record type is; SMS templates, broadcasts, report-summary AI drafts and the reporting objects (reports, folders, data tables, combined sources, schedules, meetings, dashboard widgets) are configuration and follow the round gate. Before this, none of them had a row of its own.
• Rounds data exports name their files by the platform's file-name rule. A name a file system refuses has its forbidden characters dropped rather than replaced with underscores, and a long name is cut to 150 characters keeping its extension.
• Behind the scenes: the local database bootstrap grants the migrator the right to act as the runtime role, so the schema integration specs prove the runtime's grants again.