You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 16/umbraco-cms/customizing/back-office-signs.md
+84-2Lines changed: 84 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ For example, a Document scheduled for future publishing will have a Flag defined
23
23
A Flag can be the determinant for a Sign by declaring the `forEntityFlags` as part of its Manifest.
24
24
25
25
Example:
26
+
26
27
```json
27
28
...
28
29
forEntityFlags: "Umb.ScheduledForPublish",
@@ -33,7 +34,88 @@ Using this binding lets the server determine which signs are present in the resp
33
34
34
35
## Displaying a Sign
35
36
37
+
To display a Sign in the backoffice, register an `entitySign` extension.
38
+
39
+
Typically, you’ll bind it to one or more flags returned in the server response using the `forEntityFlags` property. However, you can also provide your own logic to determine when a Sign should appear.
40
+
41
+
If you're using an icon variant, set `kind` to `icon` and provide both `meta.iconName` and `meta.label`. This ensures the user interface has the necessary visual and accessible information to render the Sign correctly.
42
+
43
+
### Example: Rendering an Entity Sign from a Server Flag
0 commit comments