Jobs Queues & Retention Policy: Overview and Recommendations
Retention Policy
Pimics collects certain data that should be periodically cleaned up. Below is a table with suggested configurations. To define it please follow these steps: Set up a retention policy.
Complex Primary Key Support in Retention Policy
Retention policy handling supports tables with complex primary keys. This enables automatic purging of audit logs and other data while maintaining compliance and database performance, even for tables that do not use simple keys.
How to use:
- When configuring retention policies, select the relevant table and follow the prompts for complex key handling.
- Review compliance requirements and retention periods for each table.
This ensures your system remains performant and compliant with data retention standards.
| Table | Table No. | Suggested Clean-up Period | Description | Suggested Parameters |
|---|---|---|---|---|
| Master Data Change Log | 70113732 | Weekly | Master Data Change Log contains all the information about data changes in Pimics. It is used for background processes. it is not necessary to keep it for long periods. | - |
| Activity Log | 70113724 | Monthly | Potential issues and errors are saved to this log | - |
| Publication Queue | 70113734 | Weekly | For integration to Shopify or when Pimics send request to API. Pimics sends requests through this table. When there is no error, it doesn't make sense to keep it. | Only when State is Done |
| Publication Line Change Log | 70114174 | Weekly | Information for 3rd party integrations about the changes in Publications. Usually, they read this info at least hourly | - |
TODO
History | There is locked predefined filters Publication Line Archive | No possibility to keep latest Publication Price Archive | No possibility to keep latest
Job Queues
Pimics contains lots of codeunits and reports to run certain actions in the backgound as a Job Queue.
| Object | Description | Parameter String | Additional Links |
|---|---|---|---|
| codeunit 70113790 "PIMX Job Full Upd Publication" | On select publications (parameter -CODEFILTER) run selected actions. We recommend to use at least -REORGANIZE or -UPDATE. | -CODEFILTER publicationcode -LOCK -RELEASE -REORGANIZE -UPDATE -PUBLISH | Refreshing the publication data |
| codeunit 70113798 "PIMX Job Send Publ. Queue" | It takes records in Publication Queue and send them to APIs | nothing | - |
| codeunit 70113818 "PIMX License Job" OBSOLETE | It periodacaly call our license service to get the newest pimics license | nothing | - |
| codeunit 70113878 "PIMX Rule Job" | Process Rules on Features that have been changes since the previous success run. This codeunit should be defined only once. | nothing | Rules |
| codeunit 70113888 "PIMX Job Upd. Publ.By Log v10" | It goes through Master Data Change Log and reorganize selected publications (parameter -CODEFILTER). It updates only lines that has been modfied in master data (see fields Publication State and Publications in the log). Parameter -FIRSTRUN will not reorganize any lines, but sets internal states that all changes have been processed. This codeunit should be defined only once. | -CODEFILTER publicationcode -DEBUG -BATCHSIZE -FIRSTRUN | Refreshing the publication data |
| codeunit 70113898 "PIMX Job Publ. Lines Cleanup" OBSOLETE | |||
| report 70113723 "PIMX File Sync SharePoint" | Synchronize 1 SharePoint library with Pimics. It reads the whole library to create or update documents. | Use Reqest Page | SharePoint configuration |
| report 70113736 "PIMX Refresh DA Metadata" | On existing files it calls the repository and update the metadata of the file. The same action as on pages Refresh Metadata | Use Reqest Page | - |
| report 70113740 "PIMX SharePoint Delta Sync" | Retrieves changes from a SharePoint library by using the timestamp of the last successful synchronization | Use Reqest Page | - |
TODO
Change Log
Configuration Templates
Workflow and Pipeline System
The Workflow/Pipeline system allows you to define and automate multi-stage processes for product data management.
Key features:
- Define process templates with multiple steps and actions
- Automate product data management workflows
- Monitor progress and review process history
How to use:
- Access the Workflow/Pipeline configuration from the Pimics setup menu
- Create or edit process templates, define steps, and assign actions
- Use the monitoring tools to track workflow execution and troubleshoot issues
This system helps standardize and automate complex business processes in Pimics.