Entity Actions, v16 & v17 #7681
Conversation
bszyman
force-pushed
the
entity-actions
branch
from
2233d8f to
623bd06
Compare
…and verified code samples. Formatting improvements. Additional clarity around entity action permissions.
bszyman
force-pushed
the
entity-actions
branch
from
623bd06 to
0bb891b
Compare
Removed reference to "xgrid" (unsure what that meant here)
I thought it best to flesh out the example
since the current backoffice is now v17. Removed "Umb.DocumentRecycleBin.Restore" entry, as doesn't exist.
for consistency throughout the article.
as the flow felt confusing to display the default UI after mentioning it can be replaced.
Remove the `config` part as it does not exist in the codebase.
leekelleher
left a comment
leekelleher
left a comment
There was a problem hiding this comment.
Reviewed the technical contents. I have made changes to the code snippets, (for consistency and TypeScript support).
@sofietoft I have left a comment about the extra anchor tags.
From a technical perspective, I am happy with these changes.
Thank you @bszyman for the herculean effort you've put into this! 💪 #h5yr
| <img src="../../../.gitbook/assets/entity-action-sidebar-context.svg" alt="graphic representation of the sidebar context menu"> | ||
|
|
||
| ### Workspace Entity Menu <a href="#workspace-entity-action-menu" id="workspace-entity-action-menu"></a> |
There was a problem hiding this comment.
@sofietoft Am I correct in thinking that we don't need this explicit anchor tags? As in Gitbook will auto-generate the anchor IDs for each heading?
| | I | Umb.Document.CultureAndHostnames | | ||
| | P | Umb.Document.PublicAccess | | ||
| | K | Umb.Document.Rollback | | ||
| | V | Umb.DocumentRecycleBin.Restore | |
There was a problem hiding this comment.
I've removed the Umb.DocumentRecycleBin.Restore entry, as it does not exist. The user permission for recycle-bin restore is actually checked against Umb.Document.Move.
|
|
||
| | Current Backoffice Letter | Verb | | ||
| | ------------------------- | -------------------------------- | | ||
| | Current Backoffice letter | Verb | |
There was a problem hiding this comment.
I've renamed to "Legacy" (since the "current" backoffice is now v17).
Although I'm unsure if we need this section going forwards. It may be useful for package developers who need to migrate user-permissions from v13 to v17, but for newcomers it is not relevant.
|
|
||
| In the following example, the `conditions:alias` property of an `entityAction` extension matches the `alias` property of the `entityUserPermission` extension definition. | ||
|
|
||
| Similarly, the `conditions:config:allOf` array must contain the one of the values from the `meta:verbs` array of the `entityUserPermission` extension definition. |
There was a problem hiding this comment.
The config part is incorrect, I have updated the code example.
3 participants
📋 Description
Update Entity Actions article to support Umbraco v16, v17. Refreshed and verified code samples. Formatting improvements. Additional clarity around entity action permissions.
📎 Related Issues (if applicable)
#7318
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
v16, v17
Deadline (if relevant)
N/A
📚 Helpful Resources