Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this section:

...

  • If you use the functionality of ResultMatrixStyledCell, entries, getEntries() etc., test it properly. For example, if the Groovy logic uses ResultMatrix in a way that is not compatible, there will be an error in the logic (e.g. dashboard will not display or quote calculation will fail).

  • If you have IMs reading ResultMatrix data, test the functionality.

  • In some cases, the issue can be fixed if you re-save faulty logics and – if needed – the libraries they depend on.

  • In other cases, you may have to modify the logics (e.g. correct type name).

Fix

  • There will be a patch to solve the backward compatibility for cases known so far.

  • This patch will be released with the regular monthly minor release 9.3, and possibly as part of 9.2.x as wellRelease 9.3 covers all currently known issues. For any customer still experiencing ResultMatrix related errors in 9.3 or later, support should run the /system$ReSaveFormulas/<partition_name> system command.
    Recommendations:

    • Do not try to run this command on pre 9.3 releases (it may cause issues in some Analytics logics).

    • On AWS, there is a high risk of running out of memory. As a rule of thumb, running it on a couple of partitions with a total of 200-300 logics (across all partitions and logic types, with libs, WFs) is safe. Otherwise contact Core or DevOps so we can raise the memory settings.

    • On bare metal, there are usually less memory constraints. So up to 5 partitions or a total of 1000 logics sounds safe. Pricefx employees and partners can ask in Core Teams channel if in doubt and also check memory usage in Grafana.

Note

The recommended way to create ResultMatrix is via api.newMatrix() (not by new ResultMatrix()).

...

Code Block
languagegroovy
export const quotesDetailOpen = async ({ quoteAPI, api: { notify } }) => {
  const clicOutputResult = await quoteAPI.getHeaderOutputResult('outputName');
  await notify.info(clicOutputResult);
}

Unification of User Roles

In Hurricane 9.3.0, in the Rebates module and Sales Compensations module 4 user roles have been modified, so that the behavior is consistent across the modules and is consistent between frontend and backend permissions.

Please review the changes and update your project setup accordingly.

Notation: Additions are marked green, deletions red.

Rebates

In this module, there have been changes in the two below listed user roles.

Role Name
(Its Code Name)

Description

Tab / Document

Actions

Add

Edit

Delete

Revoke (RA)

Duplicate

Attributes

Calculate

Administer Rebate Agreements

(RM_REBATEAGREEMENTS_ADMIN)

Provides access to Rebate Agreements where the user can perform the listed actions.

In addition, this user can revoke Rebate Agreements and delete attachments to Agreements in states other than Draft or Delete/Modify.

This user can also create/edit/delete folders for Rebate Agreements.

Rebate Agreements

+

+

+

+

+

-

+

Rebate Agreement Types

+

+

+

To have access to Rebate/Payout Records, you also need the role .

Rebates Records

+

+

+

+

Payout Records

+

+

+

Administer Rebates

(RM_REBATEMANAGER)

Provides access to Rebate CalculationsRebate Agreement Types and Rebate Condition Types and other components listed here where the user can perform the listed actions.

This user can also create/edit/delete folders for Rebate Agreements.

Rebate Agreement Types

+

+

+

+

+

Condition Types

+

+

+

+

+

Rebate Agreements

+

+

+

 

+

+

+

Calculations

+

+

+

+

+

Rebate Records

+

+

+

 

+

+

+

Payout Records

+

+

+

 

+

+

 

Sales Compensations

In this module, there have been changes in the two below listed user roles.

Role Name
(Its Code Name)

Description

Tab / Document

Actions

Add

Edit

Delete

Revoke

Duplicate

Attributes

Calculate

Administer Sales Compensations Module

(SC_ADMIN)

Provides access to the Sales Compensations module components where the user can perform the listed actions.

Does not provide access to Sales Compensations logics.

Compensation Plans

+

 

+

+

 

+

+

+

Compensation Records

+

+

+

+

+

+

Condition Types

+

+

+

 

+

+

Compensation Types

+

+

+

 

+

+

Calculations

+

+

+

 

 

 

 

Accrual Records

+

+

+

 

 

+

 

Administer Compensation Plans

(SC_COMPENSATIONSMANAGER)

Provides access to Compensation Plans where the user can perform the listed actions.

In addition, this user can revoke Compensation Plans and delete attachments to Compensation Plans in states other than Draft or Delete/Modify.

This user can also create/edit/delete folders for Compensation Plans.

Compensation Plans

+

+

+

+

-

+

Compensation Types

+

+

+

+

+

To have access to Compensation/Accrual Records, you also need the role Manage Compensation Records.

Compensation Records

+

+

 

 

 

 

+

Accrual Records

+

+

 

 

 

 

 

...