ES/S Identity Prefix
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.
Benefits
The benefits of using a prefixed identity scheme are obviously achieving direct adressability both electronically and manually. A lone datasets provides the exact usage type of following identity suffixes and can be addressed without further information on any process, no matter if on paper or transmitted digitally.
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, that have been paid for while before or while ordering |
| 59 | Order (ESSB.PostfactureOrder) | A Postfactured Order, for example a bill for services or delivered goods, that have sent out before payments have occured |
| 72 | Project (ESSB.Project) | A Project, for example a collection of tasks or roadmaps to achieve orders |
Customizability
Most distributions allow for extension or forking of data types. This mechanisms include addressing of unallocated prefixes. The prefix length is not limited, however included identities are generally 2-digits.
