[en] Varicent Incentive Compensation Management Documentation

[en] Fixed: when the "Disable Payee Enablement Emails In Task Manager" option is selected, running a "Web enable and send users their password" task via Task Manager does not work - payees are not enabled. The Audit Log also contains incorrect information that the user was enabled and a password email was sent.

[en] Fixed: there is now an option to delete all administrator messages generated through workflow alert nodes on a per-model basis. If you want to delete these administrator messages, please contact Support.

[en] Fixed: error message intermittently appears after logging in to Varicent ICM using SSO even though the user can still log in normally and doesn't prevent the user from doing anything in Varicent ICM. The error message is, "No Relay State Found in redis." With this fix, this incorrect error message should not appear.

[en] Fixed: Audit Log does not include the folder name when creating or moving folders.

[en] Fixed: if you have filters applied in the Audit Log, after viewing the history of a record, going back to the Audit Log causes the filters to reset. With this fix, the filters remain applied even when navigating through the record history.

[en] Fixed: previously, when scheduling or manually running Calculation and Lock tasks, if web users submitted data changes between the calculation and the lock, the lock would fail. Now, there is a new task type, which combines the Calculation and Lock process, which prevents data submission from interrupting the process.

[en] Fixed: inconsistent behavior with calendars. Locked calendars should not be editable.

[en] Fixed: An error appears where the user is unable to preview in calculation wizard.

[en] Fixed: when running Scheduler process folders using the Command Line Interface (CLI) tool, sometimes an error code of -1 is returned with the message, "Object reference not set to an instance of an object" despite the job continuing after the error and completing successfully. This error can occur occasionally if the status polling request times out. With this fix, if a request times out, it will retry up to 3 times. Setting the timeout value to a short duration (like 30 seconds) can also help prevent the process from getting stuck.

[en] Fixed: an error message appears when making an outbound connection.

[en] Fixed: in Composer, when the arrange button is set to 'Auto', objects are not automatically arranged.

[en] Fixed: with the Uses, Used By display turned on, the relationships do not remain highlighted as you navigate between components.

[en] Fixed: when creating a calculation with the same name as an outbound connection, and having at least two connected objects, the connection lines are initially incorrect. Refreshing the browser window fixes the visual error.

[en] Fixed: "Data could not be saved..." error message appears when arranging Composer.

[en] Fixed: when searching for Composer objects on the Home page, calculation links went to the performance page instead of the calculation itself.

[en] Fixed: Presenter Structured report Parameters appear under the Values section. This issue occurred when folders in both sections shared a name. With this fix, you'll be unable to add duplicate folder names.

[en] Fixed: when replacing a calculation in a connection, an error occurs. This error occurred when a metric in the calculation shared a column name with a system column (like Value). There is now a Localization icon on metrics with names that could cause errors and you can disable localization to prevent these types of errors.

[en] Fixed: a red line appears under the User column when looking at the history for a table. This issue occurred if the table was updated with a script. Now, instead of red line, "Unknown" displays under the user column.

[en] Fixed: Data Discovery Dashboard error appears when trying to create a table based on a data source with a blank value in a row.

[en] Fixed: missing columns on a report when comparing Payee Web and Payee Web Classic.

[en] Fixed: default data grids not appearing in Payee Web (they appeared in Payee Web Classic) - instead, the user has to click a Submit button to see the data grid. Now, a default data grid should always appear, matching the behavior in Classic.

[en] Fixed: a red line appears under the User column when looking at the history for a table. This issue occurred if the table was updated with a script. Now, instead of red line, "Unknown" displays under the user column.

[en] Fixed: one-time import permissions are not consistent for Excel file imports. If permission is granted for a one-time import, a user is able to import a text file, but not an Excel file. With this fix, permissions should be consistent across all file types.

[en] Fixed: "Caledars" typo appears on an error message in the migration wizard.

[en] Fixed: when a Presenter Structured report with "Next styles" enabled is migrated, the style preference is not enabled in the target model. This only occurs when migrating an existing report.

[en] Fixed: migration fails when trying to migrate Symon calculations as part of the migration process. The error message is, "Table [Symon object source] is missing a column [column from Symon object]."

[en] Fixed: when performing a migration during a global action, the migration page shows the migration as running and completing successfully (no error message appears). But the migration does not actually run - there is no entry in the audit log, and if you check the target model, no objects were migrated. Now, the migration wizard does not show when there are global actions running, since it doesn't function when global actions are running.

[en] Fixed: when migrating a Presenter Structured report, if pagination is the only difference between the source and target report, the report is not updated in the target model.

[en] Fixed: migration error occurs with the message, "An error occurred when an attempt to access the database was made. Invalid column name 'Value_'." This error occurred when a calculation in the model shares a metric name with a default column (like Value). Now, the error message is clearer about this issue. We also added a Localization icon to metrics with default names and you can turn off localization for these names to prevent these errors.

[en] Fixed: when trying to start a workflow from Payee Web, an error occurs despite the workflow running successfully in Payee Web Classic.

[en] Fixed: when comparing two reports in Payee Web and Payee Web Classic, the report in Classic loads after defining parameters from the parameter menu. In Payee Web, defining those parameters causes an error.

[en] Fixed: auto-fill suggestions in web reports do not work correctly if source name has been changed in the associated Presenter Structured report.

[en] Fixed: in Payee Web, when a required field is not entered for a workflow, you're unable to start the workflow if the "Submit when selected" option is selected for the action node. If you correct the fields, and try starting it again, you are still unable to start the workflow. With this fix, you should be able to start a workflow after initially receiving an error if you correct the missing fields.

[en] Fixed: when updating computed columns in Payee Web, the value is not updated until you submit it. In Classic, the value does update dynamically, but there is an intermediate step where the value is converted to milliseconds. With this fix, the value updates dynamically in both versions without the conversion step.

[en] Fixed: after setting up SSO for Payee Web, the link for URLs ending in /payeemobile redirect to Payee Web's SSO login page. With this fix, these URLs will redirect to the native Payee Web log in page, as /payeemobile is not supported.

[en] Fixed: an error occurs if a Presenter Structured report that has a pick list is opened in Payee Web after opening the same report from the Message Center > Workflows. The error message is, "Missing view permissions for current workflow."

[en] Fixed: when automatically logged out of Payee Web due to inactivity, users are redirected to the native login page even when SSO is enabled. With this fix, users will be redirected to their SSO login page.

[en] Fixed: calculation returns an error message despite calculation running successfully. With this fix, error handling is improved to avoid incorrect error messages.

[en] Fixed: in a previous release, we added the option to disable the optimization process that normally occurs after a calculation. At release, this option was not available for PPO models. With this release, the option is available for PPO models, too. To find it, select the calculation in Composer > Show More > Choose Calculation Method and then select the Disable post-calculation optimization checkbox.

[en] Fixed: Presenter report with an editable source that has the “Display only input row“ option selected doesn't load in Payee Web despite the report loading in Payee Web Classic. The error message is, "A data source used in the report is over the limit. Contact the system administrator for assistance."

[en] Fixed: text objects cannot be blank. In a previous release, users could leave text objects blank to a Presenter Adaptive report and still save the report. Recently, this was changed to not support blank objects. With this release, this has been reverted back so text objects can be left blank and users can still save the reports.

[en] Fixed: when managing data grid templates, the preview for even row style properties does not work.

[en] Fixed: formatting options header appears for computed columns. Since you can't apply formatting to computed columns, this heading should not be visible.

[en] Fixed: an error page appears when a link is added to the USA map. With this fix, the USA map can be added without an error.

[en] Fixed: a new parameter added to API calls was made required when it should have been optional, causing calls to fail. Now, these parameters are optional and should not affect existing scripts that make these calls.

[en] Fixed: in Scenarios, a blank page appears after generating a report (clicking Show report options displays the report). Now, the graph and chart appears without having to click Show report options.

[en] Fixed: there is now an option to change the behavior of external tools and publish tasks in Scheduler to not run as global actions, matching the behavior in V9. To enable this behavior change, you must contact Varicent Support. Note that by changing publishes and external tools to run as non-global actions, those tasks can fail when another global action is running.

[en] Fixed: when copying a folder in the Scheduler to another folder, the original folder's Next Run Time moves ahead 11 hours after the page is refreshed.

[en] Fixed: using commas to separate multiple recipients for scheduler notifications causes an error.

[en] Fixed: when the Disable Emails In Scheduler/Task Manager option is selected, running Task Manager to enable access for a group does not work. With this fix, you can enable access through Task Manager without having to enable emails.

[en] Fixed: the Ask Varicent "Use Custom Name" option does not translate properly in non-English browsers (defaults back to Ask Watson).

[en] Fixed: when comparing a Presenter report in the Sales Portal, in Classic it loads immediately after adding a row, but in Payee Web, it takes up to 10 minutes to load after adding a row. With this fix, both versions of Payee Web should load with consistent times.

[en] Fixed: when web is disabled, the error message was the same whether web was disabled for all Payee Web users or just specific users. Now, there are different error messages for these 2 scenarios.

[en] Fixed: when automatically logged out of Payee Web due to inactivity, users are redirected to the native login page even when SSO is enabled. With this fix, users will be redirected to their SSO login page.

[en] Fixed: a workflow no longer passes on a pick list parameter and fails with the error "cannot take action because workflow item has no assignee."

[en] Removed inline scripts.