Attributes | IMI Life Science

Attributes

Purpose: Custom fields for products.

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.

List Display Styles

For a simple List attribute, choose how each value appears on the storefront:

  • Bullet: Show a bullet before every item. This is the default.
  • Numbered: Show items as an ordered numbered list.
  • Checklist: Show a check icon before every item.
  • None: Show each item on its own line without a marker.

Structured object lists use their configured schema renderer instead of this setting.

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

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

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.