The sequences are stored as content properties with the parent page. This makes the generation process quick, even if there are more than a few hundred siblings. | Caution Box |
|---|
Please note that sequences are not incremented atomically. In case of a sequence clash, a single identifier is used twice. These clashes need to be resolved manually. |
If you need to adjust the value, please use the REST API for content properties. | Code Block |
|---|
| language | js |
|---|
| title | /rest/api/content/{id}/property/{key} |
|---|
| {
"value": "ID-10010-00010",
"version": {
"number": 2,
"minorEdit": false
}
} |
A sequence id is compared by splitting it into its parts. Parts are delimited by the dash ('-') character. Each part which represents an integer is compared as a number. Non-numbers are considered strings and are compared lexicographically. Shorter strings that are prefixes of other strings are considered smaller. Please note that the natural sort order of titles in Confluence is not changed. So although the Auto Increment service understands that REQ-COMP1-123 is larger than REQ-COMP1-23, the natural sort order of documents being displayed in a list, sorted by the title will still be REQ-COMP1-23, REQ-COMP1-123. To compensate this, you could add leading zeros: REQ-COMP1-00123, REQ-COMP1-00023. | 
