Skip to content

Commit 2ecb814

Browse files
Apply suggestions from code review
Co-authored-by: Niels Lyngsø <[email protected]>
1 parent 9d6f977 commit 2ecb814

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

16/umbraco-cms/customizing/back-office-signs.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,14 @@ description: Describes how to use sign information provided in management API re
44

55
# BackOffice Signs
66

7-
When trees, collections and items are presented in the backoffice, additional information can be displayed in the form of signs. Which signs to present will be determined by the management API response, that will be populated with a collection of `signs`.
7+
When trees, collections and items are presented in the backoffice, additional information can be displayed in the form of Signs. Which Signs to present will be determined by the Sign Manifest.
88

9-
For example, a document scheduled for future publishing will have the following as part of the trees, collections and item response:
9+
A Sign can utilize conditions in the same way as other Extensions or it can be bound to a Flag coming from the Management API.
10+
11+
For example, a Document scheduled for future publishing will have a Flag defined as part of trees, collections and item response:
1012

1113
```json
12-
"signs": [
14+
"flags": [
1315
{
1416
"alias": "Umb.ScheduledForPublish"
1517
}

0 commit comments

Comments
 (0)