Product Editor | IMI Life Science

Link a Node to Its ERP Article

  • Node header: Enter the verified ID_ARTICLE in ERP article index (ID_ARTICLE) in the sticky node editor header, then save. The value is internal and never appears in the storefront.
  • One article, one node: Use a positive integer from the configured ERP environment. Duplicate links are rejected. Clearing the field unlinks the node; new and duplicated nodes are not automatically matched by code.
  • Stock and pricing: Generate a fresh preview after changing a link. Synchronization uses the saved article index, not an article-number, order-code or FAS-reference guess. Missing, inactive or protected articles block processing.
  • Order export: The connector captures the saved IDs on every order line before ERP creation. Captured order IDs cannot be changed by editing the node. Failed capture prevents export; conflicting identities or unknown ERP outcomes require integration-owner reconciliation.
  • Existing orders: Enter missing node links and re-queue only eligible paused failures after resolving their cause. An ERP acknowledgment remains distinct from shipment or invoicing.

Product Editor

Purpose: Edit product details.

Actions

  • Update: Price, Stock, Attributes.
  • Media: Upload images.

Concurrent Editing

  • Automatic Locking: A lock is acquired when you start editing.
  • Read-Only Mode: If another user is editing, the page becomes read-only, and you will see their name in a banner.
  • Lock Expiry: Locks expire after 1 hour of inactivity.
  • Force Release: Administrators can unlock a page if needed.

Attribute Display

Current node result: Start with At a glance to review the rule source, child behavior, visible placements, filters, and layout bindings. Expand surface details for resolved values and outcomes, or Change inheritance when children need different defaults. Configure attributes contains the full matrix; it starts open, can be collapsed, and its surface menu focuses on one destination. Priority 0 appears first; visible priorities are unique, and choosing an occupied priority moves that attribute while shifting its peers. Without the edit lock, summaries and disclosures remain available while mutation controls are read-only. Clearing a direct policy asks for confirmation before inheritance is restored.

  • Keep values separate: Edit specification values in General. Use Attribute display only for storefront visibility and order.
  • Choose each surface: Configure Quick specifications, Attribute details, Comparison, Product card, Catalog filters, and explicit Layout bindings independently.
  • Set priority: Priority 0 appears first. Visible priorities are unique per surface; choosing an occupied priority moves that attribute and shifts the other visible rows automatically. Layout block position controls explicit binding order.
  • Empty values: Use Hide when empty per attribute. The matrix marks a current-node value as Auto-hidden now when no value resolves; child values are evaluated per child.
  • Current node and children: Use Same for both for one shared definition, or Configure separately when child nodes need another default.
  • Inheritance: The closest node definition wins. Clear current or child defaults to reveal the nearest inherited definition.
  • Immediate effect: Saving invalidates storefront product caches; refresh an open storefront page if the live event connection is unavailable.

Attribute Display Safeguards

Purpose: Review and change storefront attribute placement without losing child-specific work or hiding meaningful values.

  • Current-node preview: At a glance always evaluates the current node and includes pending current-node edits before you save.
  • Integer priorities: Enter whole numbers within the visible range. Priority 0 appears first, and moving an attribute shifts its visible peers independently on that surface.
  • Protect child defaults: When current-node and child definitions differ, switching to Same for both asks for confirmation. Confirming replaces the child default with the current-node definition; cancelling preserves both definitions.
  • Hide when empty: Enable Hide when empty to suppress nullish values, blank or nullish text, empty arrays, visually empty rich text, and equivalent legacy wrapped values. Zero, false, structured values, and media remain visible.
  • Legacy fallback: When no effective display policy exists, the storefront continues to use legacy visibility, featured, comparison, filter, configured-card, and attribute empty-value rules.

SI Unit Style

Purpose: Review displayed quantities against common NIST SI conventions before saving content for IMI Life Science.

  • Review warnings: The SI unit style panel identifies the field, highlights the affected text and cites the NIST section. Warnings remain visible while a supported issue exists, including in collapsed block content.
  • Apply a correction: Use Fix field or Apply safe fixes to correct deterministic spacing, range, dimension and uncertainty notation in the current draft. Save normally afterwards; applying fixes does not save or publish.
  • Check spacing: Leave a space between the number and unit, including percent and degree Celsius. Plane-angle symbols stay next to the number. Repeat units for dimensions and range endpoints.
  • Review ambiguous values: Parts-per notation, mixed units, quantity qualifiers, ambiguous hyphens and some shared-unit expressions need manual review. The helper does not convert magnitudes, guess prefixes or certify full SI compliance.
  • Respect ownership: Read-only values keep warnings without correction controls. Change unit metadata in the attribute definition. Source and translated drafts save separately; links, identifiers, numeric values and technical configuration are retained.

NIST SI guide, Chapter 7

Last Updated: 2026-09-14

Check Attribute Values at a Glance

  • Category counts: Each Attributes category header shows how many visible attributes have a defined displayed value, even while collapsed. General uses the same count.
  • Included values: Local and inherited values count once per attribute. Zero and No count as defined; blank text and empty lists or objects do not. A populated list counts as one attribute, not one per item.
  • Live updates: Counts update as you edit, clear, or revert values. Open a category to inspect its fields and inheritance indicators.

Restore a Deleted Attribute

Attribute codes remain reserved after deletion. Creating an attribute with a deleted code offers to restore the original attribute.

  • Restore existing attribute: Confirm to restore the original record and use its saved settings. New values entered in the creation form are not applied. A selected node is assigned the restored attribute.
  • Keep editing: Decline restoration without changing data. Your draft remains available so you can choose another code.
  • Active duplicates: Use Add Attribute to select an existing active attribute instead of creating another one.
  • Recover from a failure: The dialog stays open with recovery details. If restoration succeeded but loading or assignment failed, Finish restoring retries the remaining work without restoring again. Save any remaining node assignment changes normally.
  • Permissions: Checking and restoring deleted attributes requires the corresponding PIM Trash permissions. Ask an administrator when access is denied.

Last Updated: 2026-09-21

Hide, Inherit, or Show an Attribute

In Attribute display, each surface has three visibility choices.

  • Hidden: Save an explicit hidden override for this surface. Its priority is inactive.
  • Inherited / Default: Remove the visibility override and follow the ancestor policy, or the attribute defaults when no ancestor policy applies. Later upstream visibility changes continue to apply after saving.
  • Visible: Save an explicit visible override. Empty-value handling and the resolved attribute value still determine whether content renders.
  • Effective result: The status below the selector shows the resulting visibility. Priority remains editable whenever the effective choice is visible.
  • Scope: Use Same for both or Configure separately for the current node and children. Save display persists both scopes; Clear current or Clear children removes the entire selected definition.
  • Product-card fallback: When no attributes are selected on the product-card surface, enabled cards retain their configured or automatic attribute selection. Disable card attributes in the card layout to suppress that fallback.

Reliable Node Media Editing

  • Attach: Choose a usage type, then select an existing asset or upload a file. A single upload is selected automatically using its saved filename, file type and visibility. The same asset can have different usage types, but the same asset and usage type cannot be attached twice.
  • Main image: The main image is shared across the whole product, not one per usage type. Only a storefront-visible image can be selected. Hidden images and documents remain attachable without the main-image option.
  • Order: Drag attachment handles to save the complete order together. On compact screens, scroll the attachment list horizontally to reach all controls.
  • Chips: Open the tag control to add or remove chips. If saving fails, the changed chips remain available with Retry saving chips.
  • Remove: Confirm removal of the selected attachment. A failed removal keeps the confirmation open for retry; Cancel performs no write. Removing an attachment does not delete the asset.
  • Saving: Wait for the Saving indicator to clear before making another change. If a change was saved but refreshing failed, reload the node before retrying to avoid repeating a successful write.

Restore A Previous Layout

  • Open history: Select History in the layout editor, or Version history on a layout-library row. History is available after a layout has been saved.
  • Choose a snapshot: Review its timestamp, author and comment. Latest snapshot is the saved state before the most recent update, not the current layout, and can also be restored.
  • Confirm restore: Select Restore and confirm Restore version. The current saved layout is preserved as a new snapshot before the selected name, sidebar setting, blocks and translations are restored. Unsaved editor changes are replaced; Cancel makes no changes.
  • Check the result: The editor and storefront caches refresh after restoration. Layout assignments are unchanged, so shared-layout changes affect every node using that layout.
  • Audit: Restore operations appear in the Audit Trail under PIM.NodeLayouts, with the selected version and recovery snapshot identifiers. To undo a restore, restore the recovery snapshot from History.

Node Media Asset Classification

  • Asset Type: In the node Media tab, choose the classification in each attached file's Asset Type column. The choices come from the Asset Types manager and follow its configured order.
  • Shared classification: Saving changes the asset wherever it is used. It does not change the attachment role, main image, chips or attachment order.
  • Attachment Role: Choose the saved role used for the storefront download group. Changing it affects this node attachment, not the shared library classification.
  • Downloads: The storefront groups by saved Attachment Role even when Asset Type is Unclassified. Groups follow first-attachment order; files retain their order within each role.
  • Recovery: Retry loading asset types if the list fails. A failed classification save keeps the previous value; select the desired type again after resolving the error. If saving succeeded but refresh failed, reload the node before another edit.
  • Choose content: Select related products, siblings, children or the parent. Filter explicit relations and limit the number of items. Set the section title, callout and optional section action.
  • Choose visible text: Toggle the section title, callout, product name, SKU, relation badge, price, stock and compare action independently. Add a SKU prefix or replace the relation badge label.
  • Set dimensions: Set title, callout, name and SKU sizes. Zero inherits managed typography; positive sizes are bounded to 10-72 pixels. Set the product name line count to zero for unlimited lines.
  • Arrange cards: Choose grid or carousel, 1-6 desktop columns, 1-2 mobile columns, spacing, padding, border, shadow and corners. Choose image visibility, aspect ratio and contain or cover fitting.
  • Choose navigation: Select any combination of image, name, SKU and product button links, or select the whole card. Whole-card navigation replaces inner links to avoid nested links; compare remains independent. Selecting no zones disables product-page navigation. Hidden content has no corresponding link.
  • Style product actions: Set the product button label and solid, outline or link style. Product links can open safely in a new tab. The section action is configured separately.
  • Check the storefront: Preview uses the same card renderer and saved configuration as the storefront. Global commerce visibility rules still override local price and compare settings. Layouts without the new presentation fields retain their legacy rendering.

Attachment Role Download Groups

  • Grouping source: Use the single Media Type selector in the node Media tab. Managed types and compatible legacy roles share one catalog; existing file classifications remain a fallback for missing roles.
  • Ordering: Managed catalog order controls resolved groups. Unmatched legacy groups retain attachment order, and files retain their order within each effective type.
  • CHIPREG: Both manuals share User Manual. Case-study PDFs and the demo ZIP share Tech Note. The model uses 3D Model. The brochure uses Technical Datasheet because that is its saved role.
  • Shared files: A file attached under different roles can appear in each role group. Changing an Asset Type does not change those attachments.

Unified Media Types

  • One selector: The node Media tab uses one Media Type control instead of separate Attachment Role and Asset Type controls.
  • Compatibility: Existing known attachment roles retain their meaning. Exact codes and unambiguous historical aliases use the managed type's name, translations and order. Missing or orphaned roles fall back to a saved file classification.
  • Legacy definitions: Missing legacy definitions are added to the Asset Types manager without changing existing IDs, names, translations, priorities or attachment assignments. Ambiguous definitions are not guessed or merged by display name.
  • Saving: A node selection changes only that attachment. Compatible legacy identity creation and attachment changes save atomically; the shared file default is not overwritten.
  • Missing data: Empty GUID placeholders are never displayed as type labels. A file with no meaningful assignment stays Unclassified until an editor selects its type.

Deleted SKU Recovery

  • SKU found in trash: Your current input is kept. Choose another SKU or select Restore with current input for the matching deleted product.
  • Confirm the identity: If several deleted products share the SKU, select the correct product. Confirmation replaces its editable details with your current input while keeping attached media, prices, relations, translations, and history. Keep editing cancels without making changes.
  • Retry a partial save: If the product was restored but its details could not be saved, correct the reported issue and select Retry saving. This updates the same product without creating or restoring it again.
  • Unavailable recovery: Refresh a failed lookup or a product that has disappeared from the trash. Restore and update permissions are required; ask an administrator when those actions are unavailable. Resolve active SKU or ERP article index conflicts before restoring.

Attribute Display Defaults

  • In Attribute Manager, create or edit an attribute and set Attribute display defaults for Quick specifications, Attribute details, Comparison, Product card, Catalog filters, or Layout bindings.
  • Default retains the existing behavior. Hidden or Visible sets the fallback for that surface only. Save Attribute persists the choices; select Default again to clear a choice.
  • Explicit current-node and inherited child policies remain authoritative, including omitted attributes. A node surface set to Inherited or Default follows its ancestor policy before using the attribute default. Priorities, hide-empty rules, assignments, values, and layouts remain separate.
  • Existing explicitly selected card and detail-block attribute codes retain their fallback precedence. Layout bindings use the attribute default when no node policy applies. Core fields such as product name and SKU are unaffected.
  • A product-card policy with no visible rows retains the existing configured or automatic fallback. Disable card attributes in the card layout to suppress that fallback entirely.
  • JSON export/import and version restore retain display defaults. CSV exports include metadata for reference; the import wizard accepts JSON. Older updates or imports that omit display defaults preserve saved choices. System and locked attributes remain read-only.

Edit Rich Text as HTML

  • Edit HTML: Use the code icon in an editable rich-text toolbar to open its current HTML. Visual editing remains the default, including compact fields and labels.
  • Apply: Return supported HTML to the visual editor, then use the parent record's normal Save or Publish action. Applying source alone does not save the record.
  • Supported markup: Source uses the same rich-text format as the field. Unsupported tags or attributes may be removed or normalized. Scripts, unsafe links, and event handlers are removed; existing server validation and design rules still apply.
  • Cancel: Cancel, close, or press Escape to discard the source draft. Opening source or applying unchanged source does not change the record. If content changes elsewhere while the dialog is open, cancel and reopen it before editing.
  • Mail variables: Keep placeholders such as {{firstName}} and {{accountUrl}} intact, including placeholders in link addresses. The source dialog does not expose internal variable-chip markup.
  • Read-only content: HTML editing is unavailable when the field is read-only. Plain-text fields and structured block settings are not HTML editors. A failed Apply retains the source draft for correction.