SafetyTest Mapping
This page describes which OMD data elements are shared with SafetyTest.
Mapping Elements
Customer-level mapping
| OMD data element | SafetyTest data element | Purpose |
|---|---|---|
| Account ID | Customer ID | Stable technical customer identity. |
| Account number | Customer external/reference ID | Business-facing customer reference. |
| Customer name (fallback: task name) | Customer name | Human-readable customer identity. |
| Street | Customer address | Customer location details. |
| Postal code | Customer postal code | Customer location details. |
| City | Customer city | Customer location details. |
| Country | Customer country | Customer location details. |
Site/installation mapping
| OMD data element | SafetyTest data element | Purpose |
|---|---|---|
| City | Location header name | Groups related location nodes. |
| Account ID | Location header customer link | Connects location grouping to customer. |
| Account/debtor reference | Node group name | Groups related entities for the customer. |
| Street | Node group address field | Site details. |
| Postal code | Node group postal code field | Site details. |
| City | Node group city field | Site details. |
| Customer name (fallback: task name) | Node group free text field | Additional label/context. |
| City | Location node name | Property/location identification. |
Resource access mapping
| OMD data element | SafetyTest data element | Purpose |
|---|---|---|
| Scheduled resource external ID | SafetyTest username match | Finds the user to grant access to. |
| Customer and node-group identities | User access permission entries | Grants resource visibility to relevant customer/site data. |
Mapping-Specific Normalization
- Input strings are trimmed before processing.
- Names used in portal entities are normalized with truncation (maximum 50 characters).
Data Dependency
SafetyTest synchronization depends on linked data being available in sequence:
- Customer identity and address data.
- Location grouping data.
- Node group/site data.
- Resource identity match (
scheduled resource external IDmust match a SafetyTest username).
If a dependency is missing, downstream sharing (especially user access grants) may be incomplete.
Idempotency
The SafetyTest connector is designed for idempotent operation.
- Re-running upload checks whether entities already exist before creating new ones.
- Existing records are reused and corrected where needed (for example, naming corrections).
- Repeated runs can therefore be used safely for retries and consistency recovery.