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