Table of Contents

Pimics PIM 13.0 - User Guide for New Features

This guide helps you understand and implement the new features introduced in Pimics PIM 13.0. For complete documentation on existing features, visit docs.pimics.com.

Table of Contents

Master Data Management

PIM History for Categories (User Story #37209)

What's New:
Historical tracking is now available for category entities, matching the functionality already available for items.

Supported Categories:

  • Item Groups
  • Product Groups
  • Chapters
  • Catalog Groups

How to Use:

  1. View History from Category Card

    • Open any category card (e.g., Item Group Card)
    • In the Related tab, find the "PIM History" action
    • Click to view all historical versions

  2. Review Historical Changes

    • The PIM History list shows all archived versions with:
      • Version number
      • Timestamp of the change
      • User who made the change
    • Click on any version to view it as a category card

  3. Compare Versions

    • Open the history card to see the exact state of the category at that point in time
    • Review changes to:
      • Descriptions and Texts
      • Features and Classifications
      • Custom Fields
      • Relationships and Inheritance
      • Structure and Hierarchy

  4. History FactBox

    • The PIM History FactBox is now visible on all category cards
    • It shows recent versions without leaving the current page

Benefits:

  • Traceability: Complete audit trail of all category changes
  • Compliance: Meet regulatory requirements for data governance
  • Recovery: Restore previous category states if needed
  • Analysis: Understand how category structures evolved over time

Configuration:

  • History tracking is configured in Catalog Setup > History
  • Settings for "Keep Category Version" work the same as item versioning

Related Documentation:

History Card for Categories - Add Links (User Story #38118)

What's New:
The PIM History card now includes an Allocations Subpage that displays version-specific item relationships, allowing you to quickly trace which items were linked to a category at specific points in time.

How to Use:

  1. Open Category History

    • Navigate to any category card (Item Group, Product Group, Chapter, Catalog Group)
    • Click the "PIM History" action in the Related tab
    • Select a historical version to open the history card

  2. View Item Allocations by Version

    • On the history card, find the "Allocations" subpage
    • This shows only the items that were linked to the category in that specific version
    • The list displays the same information as the current allocations

  3. Compare Allocations Across Versions

    • Open different historical versions to see how item allocations changed over time
    • Identify when items were added or removed from categories

Benefits:

  • Complete Audit Trail: See exactly which items were related to a category at any point in history
  • Validation: Verify historical item-category relationships for compliance and audits
  • Change Analysis: Understand the impact of category modifications on items
  • Troubleshooting: Investigate issues by reviewing historical relationships

Use Cases:

  • Validating that the correct items were in a category when a publication was created
  • Investigating why an item relationship changed at a specific date
  • Preparing compliance reports showing historical category-item relationships
  • Recovering historical states when needed

Related Documentation:

Configuration Template for Catalog Items (User Story #35862)

What's New:
Configuration templates now support non-stock items and catalog items, allowing you to standardize data entry for all item types.

What You Can Standardize:

  • Features and Feature Values
  • Descriptions and Texts
  • Related Items
  • Custom Fields

How to Set Up:

  1. Create Configuration Template

    • Go to Master Data > Configuration Templates
    • Create a new template or open existing one

  2. Select Item Type

    • In the template header, set "Table" to:
      • Item - for standard inventory items
      • Nonstock Item - for non-stock/service items
      • Catalog Item - for catalog items
    • This determines which fields are available in the template

  3. Configure Template for Catalog Items

    • Set Features with standard values used for catalog items
    • Set Descriptions in all required languages
    • Configure Related Items section (now visible for catalog items)
    • Add any custom field defaults

  4. Assign Template

    • When creating a new item of the selected type, select this template
    • All configured fields and relationships will be populated automatically

  5. Apply Template to Existing Items (optional)

    • Select items to which you want to apply the template
    • Use Bulk Operations to apply the template
    • Validation ensures template assignment respects item-specific rules

Use Cases:

  • Creating consistent catalog items for vendor catalogs
  • Standardizing non-stock service items
  • Reducing data entry time and errors
  • Ensuring compliance with data governance standards

Related Documentation:

Pimics FastTabs on Catalog Item Card (User Story #35820)

What's New:
Catalog Item Card now includes the same FastTab interface as standard PIM items, consolidating all content management on a single card.

Available FastTabs:

  • Features - manage product features and specifications
  • Translations - manage multilingual descriptions and texts
  • Keywords - add searchable keywords for the catalog item
  • Picture Gallery - upload and manage product pictures
  • Document Gallery - upload and manage product documents

How to Use:

  1. Open Catalog Item Card

    • Go to Inventory > Catalog Items
    • Open any catalog item

  2. Navigate FastTabs

    • Click each FastTab to view and edit that type of content
    • All editing happens directly on the card without navigation

  3. Add Features

    • Click Features tab
    • Click New to add a feature
    • Select feature code and enter value
    • Features auto-save to the item

  4. Add Translations

    • Click Translations tab
    • Shows descriptions in all configured languages
    • Edit descriptions directly
    • Works the same as standard items

  5. Add Keywords

    • Click Keywords tab
    • Enter searchable keywords separated by commas
    • Used for searching and filtering in publications

  6. Upload Pictures and Documents

    • Click Picture Gallery or Document Gallery tabs
    • Use drag-and-drop or file selection to upload
    • Organize media directly from the card
    • Add captions and metadata

Benefits:

  • Efficiency: Manage all catalog item content without leaving the card
  • Consistency: Same interface as standard items improves adoption
  • Organization: All media and metadata in one place
  • Speed: Direct editing without separate page navigation

Related Documentation:

Classification & Features

Feature Matrix - Load Next / Previous Features (User Story #30361)

What's New:
The Feature Matrix now includes navigation controls to view features in manageable batches instead of horizontal scrolling.

How to Use:

  1. Open Feature Matrix

    • Go to Master Data > Items or category list
    • Find the item or category with many features
    • Click Feature Matrix action

  2. Navigate Feature Columns

    • The matrix displays up to 20 features per view (maximum column width)
    • Use navigation buttons:
      • First Features - jump to the beginning (feature 1-20)
      • Previous Features - move back one feature at a time
      • Current Position - shows which features are displayed
      • Next Features - move forward one feature at a time
      • Last Features - jump to the end

  3. Edit Feature Values

    • Edit values in the visible feature columns
    • Changes are saved as you move between features
    • No horizontal scrolling required

  4. Use Alternative View

    • If you prefer a different layout, click Features by Items action
    • Shows the same data in a table format with all features listed vertically

Use Cases:

  • Managing items with 40+ features (e.g., ETIM-based products)
  • Entering specifications for complex products
  • Reviewing large feature sets without scrolling
  • Comparing features across multiple items

Performance Tips:

  • The matrix loads features dynamically for better performance
  • Navigation is instant even with hundreds of features
  • Consider using filters to show only relevant features if possible

Related Documentation:

Quality Management

IF Conditions in Checklists (User Story #29602)

What's New:
Checklists can now include conditional logic to show only relevant quality checks based on item data.

How to Use:

  1. Open Checklist Configuration

    • Go to Quality Management > Checklists
    • Open an existing checklist or create a new one

  2. Add Condition to Checklist Line

    • On the Checklist Lines subpage, select a line
    • Click the "Condition" action
    • The Condition Indicator shows if conditions are configured

  3. Define Conditions

    • Select the field to evaluate (e.g., Posting Group, Item Type, etc.)
    • Set the condition operator (equals, contains, is greater than, etc.)
    • Enter the value to match
    • Multiple conditions can be set (all must be true for rule to show)

  4. How Conditions During Checklist Execution

    • When running a checklist on an item, only matching rules are displayed
    • Rules with conditions are only shown when conditions are met
    • Users see only validation checks relevant to their data

Example Scenarios:

Hazardous Materials Checklist:

  • Rule: "Confirm hazardous material handling documentation"
  • Condition: Posting Group = "Hazardous"
  • Result: Only shown for hazardous items

Perishable Items Checklist:

  • Rule: "Verify expiration date handling"
  • Condition: Product Category = "Food"
  • Result: Only shown for food items

Export Compliance Checklist:

  • Rule: "Verify export licenses"
  • Condition: Item Status = "New"
  • Result: Only shown for newly added items

Benefits:

  • Focused Validation: Users only see applicable rules
  • Reduced Errors: Less chance of missing required validations
  • Efficiency: Shorter checklists mean faster quality reviews
  • Compliance: Ensures industry-specific rules are applied automatically

Related Documentation:

Rules & Workflows

Rules - Move Up / Down (User Story #37141)

What's New:
Rule execution order can now be changed directly from the user interface using Move Up/Move Down actions.

How to Use:

  1. Open Rule Configuration

    • Go to Quality Management > Rules
    • Open a rule to view its actions

  2. View Rule Actions

    • Scroll to the "Rule Action" section
    • This shows the sequence of actions executed
    • Line numbers determine execution order

  3. Change Action Order

    • Select an action you want to move
    • Click "Move Up" to execute earlier (lower line number)
    • Click "Move Down" to execute later (higher line number)
    • Line numbers update automatically

  4. Why Order Matters

    • Validation rules should run before transformation rules
    • Prerequisites should run before dependent actions
    • Data quality checks should run before exports

Use Cases:

  • Running validation before data transformation
  • Executing prerequisite actions first
  • Controlling the sequence of multiple rule actions
  • Optimizing rule performance

Related Documentation:

Remove Protection Level of SetSourceRecParameter (User Story #37064)

What's New:
The SetSourceRecParameter procedure in the PIMX Rule Process CodeUnit is now public, enabling partner extensions to invoke rule execution.

How to Use (for Developers/Partners):

  1. Add Reference in Your Extension

    • In your AL project, reference the Pimics app
    • Add using Allium.PIM; (or relevant namespace)

  2. Access Rule Processing

    • Call the public SetSourceRecParameter procedure
    • Pass the source record (item, category, etc.)
    • Execute rules against this record

  3. Example Usage (Pseudo-code):

    RuleProcess: Codeunit "PIMX Rule Process";
MyRecord: Record MyTable;
RuleProcess.SetSourceRecParameter(MyRecord);
RuleProcess.Run();

  4. Integration Scenarios

    • Trigger Pimics rules from external workflow systems
    • Invoke data quality checks from custom processes
    • Integrate rule execution in partner solutions
    • Validate data before export to external systems

For Implementation Partners:

  • This enables deeper integration with Pimics rule engine
  • Rules can now be executed as part of external workflows
  • Reduces need for duplicate validation logic in custom solutions

Related Documentation:

Interface PIMX Rule Condition Type c1 (User Story #37714)

What's New:
The new Rule Condition Type c1 interface provides developers with complete data context for implementing advanced conditional logic in rules.

How to Use (for Developers):

  1. Understand the Interface

    • The c1 interface passes the Data CodeUnit as a parameter
    • This gives access to the complete record context
    • Enables evaluating conditions based on item properties, feature values, category types, etc.

  2. Create Custom Condition Implementation

    • Implement the "PIMX Rule Condition Type c1" interface
    • Receive the data context in the IsValid method
    • Access properties and fields from the source record
    • Return true/false based on your logic

  3. Advanced Condition Examples

    • Check if item has specific features with certain values
    • Validate cross-references based on item category
    • Evaluate publication status and content
    • Complex nested conditions based on item relationships

  4. Enable in Feature Management

    • The RuleConditionC1 feature flag is automatically enabled in v13.0
    • Old interface is deprecated
    • Fallback available if you need legacy behavior during upgrade

Benefits for Developers:

  • Rich Context: Access complete item/category data for smart conditions
  • Advanced Logic: Implement complex business rules
  • Integration: Create custom validation specific to business needs
  • Flexibility: Adapt rules based on real-time data evaluation

Related Documentation:

Publications

Publication and Translation as Source Records in Excel/CSV Export (User Story #32916)

What's New:
You can now export data directly from publications and translations, enabling scenarios where you need both the main language and translations in the same export file.

Available Source Types:

  • Master Record (existing) - Item, Item Group, etc.
  • Publication (new) - Data from Publication Lines
  • Translation (new) - Translated content from publications

How to Set Up:

  1. Create or Edit Export Mapping

    • Go to Excel/CSV Export > Export Mappings
    • Create a new mapping or open an existing one

  2. Select Source Record Type

    • Find the "Source Record" field in the mapping header
    • Select one of:
      • Master Record - for item-based exports
      • Publication - to export from publication data
      • Translation - to include translation lines

  3. Configure Publication Source When using Publication as source:

    • The field list will show Publication Line fields
    • You can access publication-specific data like System Status, Element, etc.
    • Map fields to your Excel columns as usual

  4. Configure Translation Source When using Translation as source:

    • The field list shows Publication Subline ML fields
    • Additional fields available:
      • Line Type
      • Number (Nummer)
      • Description (Bezeichnung)
      • Description 2 (Bezeichnung 2)
    • Map translated fields to include multiple languages in one export

  5. Multi-Language Export Example To export main language + translation:

    • Create one mapping with Publication source for main language data
    • Create another mapping with Translation source for translated fields
    • Or use different columns in the same file with different source filters

When to Use Each Source Type:

Source Type Use When Best For
Master Record Exporting item/category master data Internal ERP feeds, price lists, basic exports
Publication Exporting publication-specific data Channel-specific content, publication status tracking
Translation Exporting multilingual content Multi-market catalogs, localized product information

Best Practices:

  • Use Publication source when you need publication status, element, or channel-specific data
  • Use Translation source when multiple languages are required in the same export
  • Combine sources in different columns for comprehensive multilingual exports

Use Cases:

  • Exporting product catalogs with multiple languages
  • Preparing data for external systems that require translations
  • Comparing main language content with translations

Related Documentation:

Mass Edit System Status (User Story #36289)

What's New:
The Mass Edit Card for publication lines now includes the System Status field, allowing you to update the status of multiple publication lines simultaneously.

How to Use:

  1. Open Publication

    • Navigate to Publications > Publication List
    • Open the publication you want to edit

  2. Filter Publication Lines

    • On the publication lines, use filters to select the lines you want to update
    • Example: filter by Template Code, Category Type, or any other criteria

  3. Open Mass Edit Card

    • Click the "Mass Edit Card" action
    • This opens a card showing fields that can be bulk edited

  4. Update System Status

    • Find the "System Status" field in the Mass Edit Card
    • Select the new status (e.g., Draft, Approved, Published)
    • Click OK to apply

  5. Validation

    • The system validates that status transitions comply with:
      • Business rules
      • Publication workflow configurations
    • Invalid transitions will be prevented with an error message

Workflow Integration:

  • System status changes trigger the same validations as individual line updates
  • Use this in conjunction with the new Pipeline system for automated workflows

Workflow Examples:

Moving Products Through Workflow in Bulk:

  1. Filter publication lines by current status (e.g., "Draft")
  2. Select all lines ready for review
  3. Use Mass Edit to change status to "Approved"
  4. System validates all lines meet approval criteria
  5. Approved lines are now ready for publication

Bulk Publishing to Channel:

  1. Filter lines with status "Approved"
  2. Select lines for a specific channel
  3. Use Mass Edit to set status to "Published"
  4. Lines are exported to the channel

Rolling Back Changes:

  1. Filter recently changed lines using date filters
  2. Use Mass Edit to revert status (e.g., "Published" → "Draft")
  3. Review and correct issues before re-publishing

Related Documentation:

Cross-Reference Types with Descriptions and Translations (User Story #37378)

What's New:
Cross-references now support type codes, descriptions, and multilingual translations, providing better context and clarity.

New Fields:

  • Cross Reference Type Code - categorize the relationship
  • Description - describe the cross-reference type
  • Translation Support - localized descriptions for each type

How to Set Up:

  1. Define Cross-Reference Types

    • Go to Master Data > Cross-Reference Types
    • Create types such as:
      • "Related Product"
      • "Accessory"
      • "Replacement Part"
      • "Alternative"
    • Enter a code and description for each type

  2. Enable Translation

    • On the Cross-Reference Type card, enable the "Translate" field
    • Click "Translations" action
    • Add descriptions in each required language

  3. Assign Types to Cross-References

    • When creating cross-references on items or categories:
      • Select the appropriate Cross Reference Type Code
      • The description is automatically populated
    • This categorizes the relationship

  4. Use in Publications and API

    • Cross-reference type information is included in:
      • Publication outputs (Excel, BMECat, API feeds)
      • API responses (/documents endpoint)
    • External systems can display the type to end users

Integration Examples:

E-commerce Platform Integration:

  • Cross-reference type "Accessory" → Display as "Recommended Accessories"
  • Cross-reference type "Related Product" → Display as "Customers Also Viewed"
  • Cross-reference type "Replacement Part" → Display as "Replacement Parts"

Sana Commerce Example:

Product: Laptop Model XYZ
Cross-References:
  - Type: "Accessory" → Laptop Bag, Mouse, Keyboard
  - Type: "Related Product" → Desktop Monitor, Docking Station
  - Type: "Replacement Part" → Power Adapter, Battery

API Response Format:

{
  "crossReferences": [
    {
      "typeCode": "ACCESSORY",
      "description": "Accessory",
      "translations": {
        "de-DE": "Zubehör",
        "fr-FR": "Accessoire"
      },
      "items": ["ITEM001", "ITEM002"]
    }
  ]
}

Upgrade Considerations:

  • An upgrade procedure automatically sets "Translate" to true on all existing Cross-Reference Type records
  • Translation lines are generated for all configured Pimics languages

Related Documentation:

Publication Rule - Processing Order (User Story #27830)

What's New:
Publication rules are now applied during the pre-publication stage, validating data before publication lines are created rather than after.

How to Use:

  1. Understand the New Processing Order

    • Before (v12): Items → Publication Lines → Validate → Remove Invalid
    • After (v13): Items → Validate → Publication Lines (only valid items)
    • Invalid items are filtered out before entering the publication

  2. Configure Publication Rules

    • Go to Publication > Publication Groups
    • Add rules to filter which items should be included
    • Rules are checked during publication build

  3. Rule Execution Timing

    • Rules execute before allocation-to-publication conversion
    • Invalid items are excluded early
    • Reduces publication bloat with unwanted items
    • Improves publication quality

  4. Benefits

    • Quality: Only valid items appear in publications
    • Performance: No need to clean up invalid lines later
    • Efficiency: Smaller, cleaner publications
    • Compliance: Rules enforce data standards before export

Use Cases:

  • Excluding items that don't meet minimum data requirements
  • Filtering items by category or product type
  • Applying compliance rules before publication
  • Ensuring only approved items are published

Related Documentation:

Data Management & Performance

Retention Policy - Complex Primary Key Support (User Story #38115)

What's New:
Pimics now implements custom retention policy handling for tables with complex primary keys, enabling automatic purging of audit logs while maintaining compliance and database performance.

How to Use:

  1. Understand Retention Policies

    • Retention policies automatically delete old records
    • Configured in System Administration > Retention Policies
    • Tables affected in Pimics:
      • PIMX Activity Log (1 week retention)
      • Master Data Change Log (1 week retention)
      • Publication Line Change Log (1 week retention)

  2. Configure Retention Policy

    • Go to System Administration > Retention Policies > Retention Policies
    • Find Pimics tables in the list
    • Set retention period (default: 1 week)
    • Enable the policy

  3. Apply Retention Policy

    • Automatic: Enable job queue to run nightly (8pm-8am window)
    • Manual: Navigate to Applied Retention Policies and click Apply Manually
    • System processes records in batches of 10,000

  4. Monitoring

    • Check Activity Log to see deletion results
    • System handles complex primary keys automatically
    • No manual cleanup required

Why This Matters:

  • Performance: Large audit logs slow down the system
  • Storage: Reduces database size and backup time
  • Compliance: Maintains recent logs while archiving old data
  • Automation: No manual record deletion needed

Configuration Options:

  • Record retention periods by table type
  • Automatic or manual execution
  • Custom retention schedules via job queue

Use Cases:

  • Managing large environments with extensive audit logging
  • Maintaining regulatory compliance with data retention rules
  • Preventing database bloat from activity logs
  • Improving system performance

Related Documentation:

Workflow and Process Management

New Pipeline System (User Story #37457)

What's New:
Pimics 13.0 introduces a comprehensive Workflow/Pipeline system for defining and automating multi-stage processes for product data management.

Key Concepts:

Processes

  • A process is a complete workflow (e.g., "New Product Introduction")
  • Each process consists of multiple steps

Steps

  • Steps represent stages in the workflow (e.g., "Manufacturing", "Sales", "Marketing")
  • Each step has a defined order

Actions

  • Actions are tasks executed before entering (input actions) or after leaving (output actions) a step
  • Examples:
    • Apply configuration template
    • Run checklist
    • Add prices
    • Certify channels
    • Generate marketing text

How to Set Up:

  1. Define a Process

    • Go to Workflow > Processes
    • Create a new process
    • Enter:
      • Code - unique identifier
      • Name - descriptive name
      • Description - purpose of the process

  2. Add Process Steps

    • Open the process card
    • Add steps in the order they should execute:
      • Step Code
      • Step Order (determines sequence)
      • Step Name
      • Step Description

  3. Configure Step Actions

    • For each step, define actions:
      • Input Actions - executed before entering the step
      • Output Actions - executed when leaving the step
    • Select from the action library or create custom actions

  4. Assign Process to Items

    • On the Item card, set the "Process ID" field
    • Or define a default process in Catalog Setup
    • Processes can also be assigned via configuration templates

  5. Run the Pipeline

    • On the item card, click "Run Pipeline"
    • The system:
      • Executes input actions for the first step
      • Moves the item to that step
      • Logs all activities

  6. Monitor Progress

    • View the Process Log to see:
      • Current step
      • History of transitions
      • Actions taken
      • Timestamp and user for each change

  7. Navigate Between Steps

    • Actions available:
      • Move to Next Step - proceed to next stage
      • Move to Previous Step - go back if needed
      • Re-run Pipeline - restart the entire process
      • Re-run Action - retry a specific action if it failed

Example Workflow:

Process: New Product Launch

Step 1: Manufacturing (State: Complete)
  - Input Action: Apply "Manufacturing" configuration template
  - Output Action: Run "Manufacturing Completeness" checklist

Step 2: Sales (State: Active)
  - Input Action: Add sales prices from price list
  - Output Action: Run "Sales Ready" checklist

Step 3: Marketing (State: New)
  - Input Action: Add to marketing channels, generate marketing text
  - Output Action: Certify all channels

Advanced Features:

  • State Tracking - Each step has an associated state for the item
  • Logging - Complete audit trail of all pipeline executions
  • Validation - Actions can include validation logic
  • Error Handling - Failed actions are logged; re-run capabilities

Configuration:

  • Default Process - Set in Catalog Setup to auto-assign to new items
  • Templates - Include process assignment in configuration templates

Related Documentation:

Localization

Multi-Language Support

What's New:
Pimics PIM 13.0 now provides complete native-language interfaces for international teams in four additional languages.

Supported Languages:

  • Czech (CZ) - čeština
  • German (DE) - Deutsch
  • French (FR) - Français
  • Spanish (ES) - Español

In addition to existing English and other supported languages.

How to Set Up:

  1. Change User Language

    • Open your User Setup in Business Central
    • Set Language to your preferred language
    • All Pimics UI elements update immediately

  2. Available Translations Include:

    • All menu items and navigation
    • Page captions and field labels
    • Action descriptions
    • Report titles and column headers
    • Error messages and notifications
    • Help text and tooltips

  3. Language-Specific Formatting

    • Dates display in local format
    • Numbers use local decimal separator
    • Currency symbols follow locale
    • Text alignment adjusts for RTL languages (if applicable)

  4. Multilingual Content Management

    • Item descriptions translated to each language
    • Category names in local language
    • Publication content follows publication language rules
    • All new v13.0 features fully localized

Benefits:

  • Accessibility: Users work in their native language
  • Efficiency: Reduced learning curve for new features
  • Global Teams: Support distributed teams across regions
  • Compliance: Meet regional language requirements
  • User Adoption: Better acceptance of new features

Translated Elements in v13.0:

  • All new user interface components
  • Feature and classification captions
  • Rule and condition descriptions
  • Pipeline and process names
  • Document and asset metadata
  • Report and export templates

Use Cases:

  • Czech team members use dedicated interface
  • German and French departments have localized training materials
  • Spanish-speaking users see native-language validation messages
  • International organizations provide consistent user experience

Important Notes:

  • Change language at user level, not installation level
  • Each user can choose their preferred language independently
  • Existing translations from previous versions continue to work
  • Custom translations can be added via standard XLF files

Related Documentation:

Important Changes

The following changes may require adjustments to your existing workflows or customizations:

API Extensions

Documents API

  • The /documents endpoint now includes features and keywords fields
  • Update any integrations that consume document data to handle the new fields
  • Existing integrations will continue to work (backward compatible)

Cross-Reference API

  • Cross-reference responses now include:
    • Cross Reference Type Code
    • Description (with translations)
  • Update integrations that parse cross-reference data

Publication Changes

Source Record in Exports

  • The Source Record field in export mappings now supports Publication and Translation types
  • Review custom export logic to ensure compatibility

Cross-Reference Expansion

  • Publications support the new Expanding Type field
  • Custom publication build extensions should handle expanded cross-references correctly

Master Data

Bulk Edit

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

History Tracking

  • Category history is now tracked automatically
  • New history archive tables have been created
  • Custom history-related code should be tested for compatibility

Customization Notes

Preprocessor Symbols

  • Several preprocessor symbols related to Catalog Features have been removed in version 13.0
  • The PRODUCTFEATURE feature must be enabled during installation
  • Custom code referencing removed preprocessor symbols must be updated

Publication Line Fields

  • The field Zeilenart has been replaced by Line Type (enum)
  • API pages now use the new field
  • Update any custom code or API consumers that reference the old field

Event Subscribers

  • Custom event subscribers related to:
    • Publication versioning
    • Document handling
    • Cross-reference management
  • Should be tested to ensure compatibility with enhanced data structures

Getting Help

For detailed information on any Pimics feature, visit:

Summary of New Capabilities

Feature Area New Capability User Story Primary Benefit
Master Data Bulk Edit for Categories & Digital Assets #30912 Efficient mass updates across entity types
Master Data PIM History for Categories #37209 Complete change tracking and traceability
Master Data History Card with Item Linking #38118 Track category version changes with item references
Master Data Configuration Templates for Items #35862 Standardize catalog item setup configurations
Master Data FastTabs on Catalog Item Card #35820 Direct editing of features, translations, keywords, media
Classification Feature Matrix Navigation #30361 Load next/previous features efficiently
Quality Management IF Conditions in Checklists #29602 Conditional rule evaluation based on item properties
Rules Move Up / Down Rules #37141 Reorder publication rules dynamically
Rules SetSourceRecParameter Protection #37064 Control source record parameter access levels
Rules PIMX Rule Condition Type c1 #37714 Advanced rule conditions for complex logic
Publications Publication/Translation Export Sources #32916 Export items from multiple source contexts
Publications Mass Edit System Status #36289 Bulk update publication line statuses
Publications Expand Cross-References to Items #37374 Convert category references to item lists
Publications Cross-Reference Types & Translations #37378 Categorize and localize cross-references
Publications Document Features & Keywords #37598 Enrich document metadata in exports
Publications Publication Rule Processing Order #27830 Validate items before creating publication lines
Data Management Retention Policy with Complex Keys #38115 Manage audit log lifecycle automatically
Workflow Pipeline System #37457 Automated multi-stage product processes
Localization Multi-Language Support — Czech, German, French, Spanish native interfaces

This guide is based on Pimics PIM version 13.0. For the most up-to-date information, always refer to docs.pimics.com.