Table of Contents

What is new in Pimics PIM 13.0

Master Data

PIM History Card for Categories

Business Value

Maintain a complete audit trail for your category structure with version history that captures all features, descriptions, and item allocations at each point in time. When investigating data changes for compliance requirements or troubleshooting, the history card provides the full context you need—what changed, when, and which items were affected—without requiring access to external audit logs or backups.

Technical Changes
  • New PIMX History FactBox displays complete version history for category records
  • Allocations Subpage added to history card showing linked items per version
  • Affected pages include Item Group, Product Group, Chapter, and Catalog Group list pages
  • Version-specific display ensures historical accuracy and traceability

History Card for Categories - Add Links

Business Value

Quickly trace which items were linked to a category at specific points in time without navigating between multiple screens. The allocations subpage displays version-specific item relationships directly from the history card, reducing the effort required when investigating data relationships or validating historical allocations for publications.

Technical Changes
  • Allocations Subpage added to history card displaying allocations same way as features
  • Version-specific filtering shows only allocations relevant to that particular version
  • Implementation completed with 2 programming commits

Configuration Template for Catalog Items

Business Value

Extend template standardization to non-stock and catalog items so data entry teams can create items more efficiently using pre-configured features and descriptions. This reduces manual data entry work and helps ensure consistency across similar item types, particularly valuable when onboarding items that share common attributes.

Technical Changes
  • Templates now support features and descriptions for non-stock and catalog items
  • Related items section now visible for catalog item template assignments
  • Validation ensures template assignment respects entity-specific business rules

Pimics FastTabs on Catalog Item Card

Business Value

Manage catalog item content more efficiently with FastTab interface that consolidates features, translations, keywords, pictures, and documents on a single card. This reduces navigation between pages and delivers the same streamlined experience available for regular PIM items, helping ensure complete and consistent item maintenance.

Technical Changes
  • New FastTab interface on Catalog Item Card with Features, Keywords, Translations tabs
  • Picture Gallery and Document Gallery tabs for multimedia management
  • Direct editing without navigation to separate pages

Mass Edit System Status

Business Value

Update system status for multiple items simultaneously rather than editing each item individually. This is particularly useful when moving batches of products through lifecycle stages—updating status for dozens of items in a single operation instead of individual edits.

Technical Changes
  • System Status field added to Mass Edit Card for items
  • Bulk update logic applies selected system status to all filtered items
  • Validation ensures system status transitions comply with business rules and workflow configurations
  • System Status field displayed alongside other mass-editable item fields

Classification & Features

Bulk Edit Features for Categories and Digital Assets

Business Value

Apply feature changes across multiple categories, item groups, product groups, chapters, catalog groups, digital assets, and classification classes in a single operation. Rather than opening individual records, bulk edit enables you to update shared attributes across many related entities at once—reducing effort when implementing category-wide policy changes or ensuring consistent attributes across your product hierarchy.

Technical Changes
  • Bulk Edit extended to six new entity types: Item Group, Product Group, Chapter, Catalog Group, Digital Asset, and Class
  • Bulk operations access available from respective entity list pages
  • Full support for bulk updating custom and system fields specific to each entity type

Feature Matrix - Load Next / Previous Features

Business Value

Work with large feature sets more effectively when managing products with 40+ specifications. The navigation controls let you load feature groups in manageable 20-column sets rather than horizontal scrolling through hundreds of columns, making data entry for complex product hierarchies like ETIM standards more practical and less error-prone.

Technical Changes
  • Navigation controls for loading next/previous feature columns on Feature Matrix
  • 20-column display maximum maintained for optimal viewing
  • Alternative "Features by Items" view available for complementary navigation pattern

Publication & Export

Source Record in Excel/CSV Export

Business Value

Export different versions of your multilingual product data in a single operation by specifying the source—Master Record, Publication, or Specific Translation. This reduces the number of export operations required when preparing product data for partners or sharing information across departments, particularly when dealing with publication-specific content or language variants.

Technical Changes
  • Source Record field in export mappings extended with Publication and Translation options
  • Export logic handles publication-based data extraction including language-specific content
  • Validation ensures appropriate language and structure configurations for multi-language exports

Features and Keywords for Documents in Publication and API

Business Value

Control which documents appear in publications and API responses by assigning features and keywords. This enables targeted content delivery to different customer segments without maintaining separate files—high-end customers see premium documentation while basic customers see core information, all sourced from a single document through automated publication filtering.

Technical Changes
  • Extended the Publication Document structure to include feature and keyword fields.
  • Updated the publication build process to capture and include document features and keywords.
  • Added feature and keyword fields to the /documents API endpoint, ensuring external systems can access this metadata.
  • Implemented UI changes to allow users to define features and keywords for documents within publication configurations.

Expand Cross-References to Items in Publication

Business Value

Automatically expand category-level cross-references to individual items for channels that require item-level relationships. Rather than manually configuring each expansion or maintaining parallel mappings, the expanding type controls whether cross-references remain at category level, reference only other items, or expand to show all related items—giving each channel the granularity it requires.

Technical Changes
  • New Expanding Type field on Publication objects controls reference expansion behavior
  • Options include: Default (use header setting), Referencing (no expansion), Resolution (expand structure)
  • Publication Group control logic handles same/different scenarios for complex hierarchies
  • Bug fixes for "Same" option logic and publication group selection alignment

Cross Reference Type and Translation

Business Value

Support multilingual publications where cross-reference type descriptions appear in your customer's native language. Instead of showing source language labels in an otherwise localized publication, cross-reference types automatically translate to match the publication language, improving clarity for international users.

Technical Changes
  • Catalog Translation table extended with new "Cross Reference" translation type option
  • New Translate field on Cross-Reference Type enables multi-language support
  • Publication ML Subline table extended for Cross Reference Type Description
  • Upgrade procedure automatically generates translation lines for existing types
  • API cross-reference endpoint now includes type code, type description, and translations

Rules & Workflows

IF Conditions in Checklists

Business Value

Show only relevant quality checks by using conditions in checklists. Instead of displaying all validation rules to every user, checklists can adapt to the data being entered—for example, showing hazardous material compliance checks only when the posting group indicates hazardous materials. This focuses users on the validations that actually matter for their specific data context.

Technical Changes
  • Checklist Line table enhanced with Condition boolean flowfield
  • UI component added for condition configuration and management
  • Support for context-aware rule execution based on data attributes

Rules - Move Up / Down

Business Value

Reorder rule execution sequences through the interface without manual line number management. When execution order matters—such as running validation rules before transformation rules—administrators can adjust sequences directly from the rule configuration page.

Technical Changes
  • Move Up/Move Down actions added to Rule Action sections
  • Automatic Line No. field management maintains sequential integrity
  • Straightforward implementation with clean separation of concerns

Interface "PIMX Rule Condition Type" c1

Business Value

Support advanced rule implementations where business logic needs access to complete data context. The c1 rule condition interface provides partners and custom developers with parameters and context information needed to create intelligent conditions that adapt based on item properties, category types, publication status, and other business factors.

Technical Changes
  • PIMX Rule Condition Type c1 interface includes Data CodeUnit parameter for condition context
  • RuleConditionC1 feature flag in Allium Feature Management (automatically enabled in v13)
  • Old interface deprecated and removed in v13.0
  • Fallback mechanism available when feature flag disabled during upgrade

Remove Protection Level of SetSourceRecParameter

Business Value

Enable partner extensions to invoke rule execution from external systems by providing public access to rule execution capabilities. This supports integration scenarios where partner workflow systems need to trigger Pimics rules or third-party validation engines need to invoke built-in data quality checks.

Technical Changes
  • SetSourceRecParameter procedure in PIMX Rule Process CodeUnit protection level reduced to public
  • Enables business partner extensions to integrate rule execution workflows
  • Supports custom integration scenarios without requiring core product modifications

Workflow

Workflow and Pipeline System

Business Value

Define standardized multi-stage workflows to guide products through your data lifecycle. Configure pipelines with specific actions at each stage—data validation, mandatory field checks, approval gates, integration triggers—and track product progress through the workflow. Automated notifications alert users when actions are needed, improving team coordination and helping ensure consistent data quality across departments.

Technical Changes
  • Introduced a new Pipeline module with support for defining workflows, processes, stages, and actions.
  • Implemented a Process Engine that executes pipeline stages sequentially and applies configured actions to data entities.
  • Added UI components for managing pipelines, including pipeline designers, stage configuration pages, and action libraries.
  • Created an extensible action framework that allows custom actions to be developed and integrated into pipelines.
  • Integrated pipeline status tracking with PIM entities, enabling items, publications, and other records to be associated with pipeline stages.
  • Added event triggers and scheduling capabilities to automate pipeline execution based on data changes or time-based conditions.

Data Management & Performance

Retention Policy - Complex Primary Key Support

Business Value

Manage database performance and storage costs by automatically purging audit logs according to retention policy. High-volume environments generate extensive activity logs that can impact performance over time. Retention policies allow you to keep recent audit data for troubleshooting while removing older records, maintaining compliance without manual cleanup.

Technical Changes
  • Custom Reten. Pol. Deleting Enum Extension implements complex key handling
  • Affected tables: PIMX Activity Log, Master Data Change Log, Publication Line Change Log (1 week retention)
  • Solution bypasses BC standard retention filtering limitation with composite primary keys
  • Installation note: Tables require removal and re-add during upgrade (no in-place update available)
  • Uses OnApplyRetentionPolicyRecordLimitExceeded event with 8pm-8am processing window

Publication Rule - Processing Order

Business Value

Improve publication quality by validating data before publication lines are created. Moving rule execution to the pre-publication stage allows invalid items to be filtered out early, rather than cleaning up bad data after it enters publications. This helps ensure reliable, high-quality data in customer-facing publication feeds.

Technical Changes
  • Paradigm shift from post-validation to pre-validation filtering
  • SetSourceRecord and OnValidateData interface calls in proper execution order
  • Rule execution happens before allocation-to-publication conversion
  • More reliable publication logic with reduced invalid data in exports

Localization

Multi-Language Support

Business Value

Provide native-language interfaces for international teams in Czech, German, French, and Spanish. Users see menus, forms, reports, and messages in their native language, supporting distributed teams across multiple regions and improving accessibility for global organizations.

Technical Changes
  • Translation support added for Czech (CZ), German (DE), French (FR), and Spanish (ES)
  • All UI elements, reports, and messages included in translation packages
  • Language-specific formatting applied per local standards
  • New v13.0 features fully supported in all languages

Important Changes

The following changes in Pimics 13.0 may require adjustments to existing customizations or API integrations:

API Changes

  • Documents API Extension: The /documents API endpoint now includes additional fields for features and keywords. API consumers must update their data models to handle these new fields. Existing integrations will continue to work, but responses will include the additional metadata.

  • Cross-Reference API Extension: Cross-reference responses now include Cross Reference Type Code and Description fields (with translations). Integrations that parse cross-reference data should be updated to handle these new fields.

Database Schema Changes

  • Publication Document Structure: The Publication Document table structure has been extended with feature and keyword fields. Custom reports or queries directly accessing these tables may need adjustment.

  • Cross-Reference Tables: New fields for cross-reference type code, description, and translations have been added. Direct SQL queries or custom procedures accessing cross-reference tables should be reviewed.

  • Category History Tables: New history archive tables have been created for Item Groups, Product Groups, Chapters, and Catalog Groups. Custom history-related extensions should verify compatibility.

  • Process and Pipeline Tables: New tables introduced for Processes, Process Steps, Step Actions, and Process Log. Custom integrations referencing workflow data should review new table structures.

  • Item Table: New Process ID field added on Item table for pipeline assignment. Custom code reading or writing to Item table should account for this field.

  • Configuration Template Tables: Template structures extended to support features, descriptions, and related items for non-stock and catalog items. Direct table access should verify compatibility with new template types.

Functional Changes

  • Export Mappings: The Source Record field now includes Publication and Translation as valid types. Custom export logic or extensions that validate source types must be updated to recognize these new options.

  • Cross-Reference Expansion: Publications now support expanding cross-referenced categories to items using the Expanding Type field. Custom publication build extensions should ensure they handle expanded cross-references correctly.

  • Pipeline Integration: The new Workflow/Pipeline system introduces pipeline status tracking on PIM entities. Custom code that modifies item or publication status may need to consider pipeline state transitions and validations.

  • Rule Execution Order: Publication rule processing now uses pre-validation filtering paradigm. Custom publication rule extensions should verify SetSourceRecord and OnValidateData interface call order aligns with new execution model.

  • Feature Flag Management: RuleConditionC1 feature flag behavior changes in v13.0. Custom code relying on rule condition implementations should test both c1 and legacy interface behavior during upgrade transition period.

  • SetSourceRecParameter Visibility: Protection level changed to public, enabling partner extensions. Custom extensions integrating rule execution should validate access paths and security contexts.

Customization Considerations

  • Bulk Edit Extensions: If you have custom bulk edit implementations for categories or digital assets, review them for potential conflicts with the new built-in bulk edit functionality.

  • Bulk Edit Validation: Custom validation rules for bulk operations should be tested across all new entity types (Item Group, Product Group, Chapter, Catalog Group, Digital Asset, Class) to ensure business rules are enforced.

  • Mass Edit Card: Custom fields added to publication lines should be tested with the new System Status field in the Mass Edit Card to ensure proper behavior during bulk updates.

  • Template Extensions: Custom templates or template-related extensions should verify compatibility with new catalog item and non-stock item template support. Visibility rules for "Related" section may be affected.

  • Pipeline Extensions: Custom extensions integrating with the new pipeline system should implement process event handlers and action frameworks. Partner solutions calling SetSourceRecParameter require public access validation.

  • History Extensions: Custom code accessing category history data should account for new allocated items tracking and version-specific filtering in allocation subpage.

  • Event Subscribers: Custom event subscribers related to publication versioning, document handling, cross-reference management, or item template assignment should be tested to ensure compatibility with the enhanced data structures and new functional flows.