Difference between revisions of "ES/S Identity Prefix"
(→Extensible Services / Server for Business) |
(→List of common prefixes) |
||
| Line 4: | Line 4: | ||
=== List of common prefixes === | === List of common prefixes === | ||
| + | |||
| + | ==== Extensible Services / Server ==== | ||
| + | |||
| + | {| class="wikitable" style="float:center; margin:0 0 0.5em 1em;" | ||
| + | |- | ||
| + | ! Prefix | ||
| + | ! Type | ||
| + | ! Description | ||
| + | |- | ||
| + | | 7 | ||
| + | | System Identity Approval Permission | ||
| + | | This identity is used pan-system wide exclusively to control programmed permissions | ||
| + | |} | ||
==== Extensible Services / Server for Business ==== | ==== Extensible Services / Server for Business ==== | ||
Revision as of 03:45, 28 April 2023
Contents
General
All ES/S Compatible Systems, but especially the ones used in complex enterprise applications make use of prefixed identities. This is used to clarify and allocate the identity space a company uses internally. The idea behind is to uniquely allocate prefixes to a specific dataset type or enumeration, that for example, can be a customer, a project or a task.
List of common prefixes
Extensible Services / Server
| Prefix | Type | Description |
|---|---|---|
| 7 | System Identity Approval Permission | This identity is used pan-system wide exclusively to control programmed permissions |
Extensible Services / Server for Business
| Prefix | Type | Description |
|---|---|---|
| 57 | Customer (ESSB.DefaultCustomer) | A Customer Data set, commonly used to identify a companies customers |
| 58 | Order (ESSB.PrefactureOrder) | A Prefactured Order, for example a online shop order |
| 72 | Project (ESSB.Project) | A Project, for example a collection of tasks or roadmaps to achieve orders |
