Navigation
Lead / Send Request Scenario
General
Design
APIs
Sidebar
advanced:postmessage:errorhandling
Error Handling
pCon.ui sends postMessages to the parent window in case of errors (e.g. article not found). The receiving website, the website where pCon.ui is implemented, is free to handle this event as needed (e.g. show error message to the user, write log or email notification to administrator).
The HTML postMessage sends a json object with the following information:
{ "action": "error", "data": { "type":" ", "subtype":" " } }
The following types and subtypes are currently supported:
| Parameter | Value | Description |
|---|---|---|
| type | article | |
| subtype | not-found | The article does not exist in the product data. |
| subtype | insert-failed | The article could not be inserted. Usually due to an error in the OFML data. |
| subtype | needs-migration | The article insert with obx file could not be created validly with (current) newer ofml data and need migration. |
| subtype | migrated | The article insert with obx file was migrated automatically (if this option is activated in your instance) to (current) newer ofml data. |
| type | catalog | |
| subtype | not-found | The catalog node does not exist in the product data. |
| type | configuration | The insertion of a configuration by the provided OBX failed. |
| type | unlicensed | The gatekeeper-ID is not allowed to be opened in pCon.ui (generally or with the used parent URL). |
| type | priceservice | |
| subtype | not-available | The price-service is not available. |
| subtype | empty-response | The answer does not contain price data. |
| type | articledata | A property change could not be done. |
| subtype | manufacturer article-Number message | Details about the article and the occurred error. |
advanced/postmessage/errorhandling.txt · Last modified: by Karolin Merten