Difference between revisions of "ES/S Identity Prefix"
(→List of common prefixes) |
(→Extensible Services / Server for Business) |
||
| Line 13: | Line 13: | ||
! Description | ! Description | ||
|- | |- | ||
| − | | | + | | 57 |
| − | | | + | | Customer (ESS.B.DefaultCustomer) |
| − | | A | + | | A Customer Data set, commonly used to identify a companies customers |
|- | |- | ||
| − | | | + | | 58 |
| − | | | + | | Order (ESS.B.PrefactureOrder) |
| − | | A | + | | A Prefactured Order, for example a online shop order |
|- | |- | ||
| − | | | + | | 72 |
| − | | | + | | Project (ESS.B.Project) |
| − | + | | A Project, for example a collection of tasks or roadmaps to achieve orders | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | A | ||
|} | |} | ||
Revision as of 03:42, 28 April 2023
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 for Business
| Prefix | Type | Description |
|---|---|---|
| 57 | Customer (ESS.B.DefaultCustomer) | A Customer Data set, commonly used to identify a companies customers |
| 58 | Order (ESS.B.PrefactureOrder) | A Prefactured Order, for example a online shop order |
| 72 | Project (ESS.B.Project) | A Project, for example a collection of tasks or roadmaps to achieve orders |
