Skip to main content

2020.2 to 2021.0

1. Changed configuration of the indexer​

What changed​

The configuration of the indexer has been moved from the instance configuration to its own alias. Instead of configuring the indexer directly within the instance configuration, you now define a new indexer alias under the alias node in the project tree.

Why it matters​

This change improves modularity and flexibility by separating the indexer configuration from the instance configuration, allowing independent deployment and management of the indexer alias.

  • Add a new indexer alias definition under the alias node in your project tree.
  • Deploy this new alias definition.
  • Configure and use the indexer alias within your systems.
  • In the instance configuration, under the modules node, select the new indexer alias.
  • Note that the properties of the indexer configuration remain unchanged.

2. System table upgrader​

What changed​

The system database upgrader has been extended and renamed to "system table upgrader." It is now accessible via the context menu of the system alias.

Why it matters​

This extension provides improved upgrade capabilities for the system database, facilitating smoother and more reliable upgrades.

  • Open your system.
  • Right-click on the system alias.
  • Select Upgrades from the context menu to access the system table upgrader.

3. Changes to the probability column of OFFER and SALESPROJECT​

What changed​

The probability column in the OFFER and SALESPROJECT tables has been changed to use numerical values instead of keywords.

Why it matters​

Using numerical values allows for more precise probability representation and easier processing in the system.

  • If you use Liquibase, update your database using the Update function to apply this change.
  • Otherwise, execute the new server process migrateProbabilities to migrate existing data from keyword-based to numerical values.

4. Changes to Keywords​

What changed​

The keyword system has been updated to enable different sorting options. This includes new database tables and columns, and changes to how keywords are stored and referenced.

Why it matters​

These changes improve keyword management and sorting capabilities, but require migration and adjustments to existing data and customizations.

  • Execute the new Liquibase scripts to update your database tables accordingly.
  • Use Liquibase to update the standard keywords included in xRM.
  • For custom keywords, run the server process Migrate all Keywords. More details can be found in the process's documentation property within the Designer.
    • This process can generate Liquibase scripts and output them to a file or the server log.
    • If Liquibase is not used, the process can apply all changes directly to your database.
  • Review and update project-specific customizations:
    • Replace all access to AB_KEYWORD_ENTRY.CONTAINER with AB_KEYWORD_ENTRY.AB_KEYWORD_CATEGORY_ID.
    • Note that AB_KEYWORD_ENTRY.AB_KEYWORD_CATEGORY_ID is a foreign key to AB_KEYWORD_CATEGORY, not just a name field like the old CONTAINER column.

Example usage​

// Old:
newWhere("AB_KEYWORD_ENTRY.CONTAINER", $KeywordRegistry.addressType());

// New:
newWhere("AB_KEYWORD_ENTRY.AB_KEYWORD_CATEGORY_ID", KeywordUtils.getCategoryIdByName($KeywordRegistry.addressType()));