|
| 1 | +--- |
| 2 | +'@objectstack/plugin-approvals': patch |
| 3 | +'@objectstack/plugin-security': patch |
| 4 | +'@objectstack/service-automation': patch |
| 5 | +'@objectstack/plugin-sharing': patch |
| 6 | +--- |
| 7 | + |
| 8 | +Clause-②: no |
| 9 | + |
| 10 | +The approval, security, automation and sharing objects describe their records in plain admin |
| 11 | +sentences. Approval Delegations now reads "While someone is away, approvals assigned to them |
| 12 | +personally go to their delegate.", Record Shares "Records shared beyond their owner, one row per |
| 13 | +grant.", User Positions "Which positions each user holds, one row per assignment.", Audience |
| 14 | +Binding Suggestions "A package's suggestion to give one of its permission sets to everyone who |
| 15 | +signs in, and the decision taken on it." and Automation Runs "Paused automation runs waiting to |
| 16 | +resume, and the recent history of finished runs." Field help on Approval Requests, Approval |
| 17 | +Delegations, User Positions, User Permission Sets and Audience Binding Suggestions, the |
| 18 | +descriptions of the `organization_admin_no_bypass`, `mcp_agent_data_read` and |
| 19 | +`mcp_agent_data_write` permission sets, the flow-dispatch ledger's description and the |
| 20 | +reserved-position refusal no longer carry design-record numbers or runtime vocabulary; those |
| 21 | +references stay in the code comments. The zh-CN, ja-JP and es-ES translations follow. Wording |
| 22 | +only: no field, permission or behaviour changes. |
0 commit comments