pCon.planner (OBX)

The WebKatalog exchanges configured articles with pCon.planner through .obx files — in both directions. A customer can configure in the WebKatalog and continue planning in their pCon installation, or show a configuration from pCon in the WebKatalog.

Enabling

https://web.3doffice.de/webkatalog2_5/planning
  ?token={TOKEN}
  &manufacturer=mau
  &program=ar
  &basearticlenumber=AT165MDF
  &obxexport=true

In the information area, the section "OBX exchange" appears under Download, with "Export OBX" and "Import OBX".

Export: WebKatalog → pCon.planner

1. Configure the article in the WebKatalog.
2. Download → Export OBX.
3. Load it in pCon.planner via File → Import.

The article appears in pCon as a real OFML article with all OCD properties in the WebKatalog's configuration.

Requirement in pCon.planner

The manufacturer's OFML data must be installed in pCon.planner. If it is missing, pCon shows no error message, only a gray placeholder box with the article number. The Download tab points this out with the manufacturer's name.

Not transferred are meta properties (e.g. table series or top dimensions as editable planning properties in pCon; the geometry is still correct) and — without a price profile — prices.

Import: pCon.planner → WebKatalog

1. In pCon.planner: File → Export → Articles → "OBX exchange format (*.obx)".
2. In the WebKatalog: Download → Import OBX — or simply drag the file onto the WebKatalog.
3. If the file contains several articles, you pick one.
4. The article is configured in the background. A card with a progress bar shows the status: about 2 seconds per differing OCD property; meta properties are faster (a conference table with twelve reconfigured chairs takes about a minute).
5. The article is then shown; a message confirms the result. Catalog and breadcrumb bar jump to the article's manufacturer (not to its exact catalog folder).

Requirements for the import

• The login (token) must be enabled for the manufacturer.
• The article must exist in the WebKatalog's current manufacturer data. The file should therefore be created in pCon with current manufacturer data.

What is applied

Applied	Not applied
Article (manufacturer, series, article number)	Sub-articles with no counterpart here (e.g. Assmann's KN12M) — the message states how many
all OCD properties the article has in the current data	Quantity, prices, discounts, texts
Meta properties and the sub-articles that depend on them (e.g. the chairs of a conference table), as far as the WebKatalog has a meta level

Articles without a meta level (e.g. Assmann) are configured through the OCD properties only, as before.

Values that do not exist (any more) in the current data are listed in the message after the import ("… 2 properties not applied: Frame color (wanted 9006), …").

Files that do not work

File	Message
older pCon exports whose articles no longer exist in the current data	"Article … is not available in this catalog."
manufacturers the login is not enabled for	"Article … is not available in this catalog."
other pCon formats (.obk, .pbox, .pec, …)	"That file is not an .obx file."
empty exports ("0 OBX articles were exported" in pCon)	"The OBX file contains no article."

In all these cases, the article shown before stays unchanged.

---

pCon is a trademark of EasternGraphics GmbH; the WebKatalog is an independent competing product.