[en] Varicent Incentive Compensation Management Documentation

[en] Fixed: scrolling through the Activity log is not smooth and appears to jump around the page. Now, it should be smooth and responsive when scrolling up and down.

[en] Fixed: a visual bug on some calculations (generally those with a lot of sources) where if you add a source, a previously-added source appears duplicated. But when you proceed in the wizard and then go back, the duplicate source is gone.

[en] Fixed: when editing a calculation, when adding restrictions, if one restriction is deleted, the restrictions below it show incorrect values in the drop-down menu.

[en] Fixed: when performing a migration between environments, the migration completes successfully, but an error message appears. This was reported as fixed in a previous release.

[en] Fixed: users with view-only access to a component can still turn the "web viewable" option for a table on and off.

[en] Fixed: when creating a new inbound connection by dragging the source to the component in Composer, an error occurs. The error doesn't occur when clicking “Create new inbound connection”.

[en] Fixed: error message displays placeholder text in Data Discovery Dashboards when the web browser language is set to French.

[en] Fixed: if there is a full calculation running in a model, a Data Discovery Dashboard in Payee Web does not show any values until the calculation is complete.

[en] Fixed: more options menu doesn't work in Data Discovery Dashboards if the source is in use.

[en] Fixed: when editing a Presenter Structured report, clicking on a data grid in the layout causes an error. The error message is, “An error occurred when loading this page”. This error occurs when the data stores used in the data grid have restrictions where the columns are different types. Now, there is an additional check which prevents users from changing the display column types in a data store if that column is in use by any report.

[en] Fixed: in an effective-dated table, when you click the View All button to put the current date in the date box and makes the Add and Import buttons visible, the date box and the Add and Import buttons become inactive if you scroll up and down through the records.

[en] Fixed: user cannot log in to the education portal through the Help sidebar even though they can log in successfully when using the direct education link. This occurred for users whose username did not follow a text@domain.com format.

[en] Fixed: when clicking on the 'History' button on a row in a table, an error occurs. The error message is, "Object reference not set to an instance of an object."

[en] Fixed: disabling the inquiry for an individual report does not disable the inquiry buttons at the individual table level in Payee Web. This issue does not occur in Payee Web Classic.

[en] Fixed: when performing a migration, the list of objects in Composer are not listed in alphabetical order.

[en] Fixed: migration fails with an internal error.

[en] Fixed: when performing a migration, the list of objects in Composer are not listed in alphabetical order.

[en] Fixed: when the layout type is set to Nested, the logo appears smaller when compared to the Stacked layout.

[en] Fixed: when scrolling down, header row cell lines are not aligned with the other data grid cell lines in Payee Web. This does not occur in Payee Web Classic and only occurs if using Firefox as the web browser.

[en] Fixed: when trying to access Payee Web when no tabs are set to viewable on web and the Message Center is disabled, an error occurs and the user is directed to a generic error page. Now, in this scenario, the user will get this error message: "You have no available web tabs. Please contact your administrator."

[en] Fixed: when trying to export a data grid from a report in Payee Web, nothing happens. If you look in the Network tab, there is a pending 'export' request which eventually times out with a '400 Bad Request'. Now, users will get a visible error message when the export fails due to going over the size limit.

[en] Fixed: while a Scheduler fold is running trying to enter data through Payee Web causes an error. The error message is, "Input string was not in the correct format." This issue does not occur in Payee Web Classic.

[en] Fixed: when adding an external URL as a web tab on, you cannot add it if the length exceeds 100 characters. Now, the character limit is 1,000.

[en] Fixed: when previewing a Presenter report that was migrated from a V8 model, an error occurs. The error message is, "Required parameter missing."

[en] Fixed: a Presenter report that uses borders on text boxes to create grey frames around images looks different depending on the web browser you view the report in. If you have experienced this issue, you must open the report as if to edit it, and then save the report for the fix to take affect.

[en] Fixed: a data grid with pagination enabled and a toggle editable date column causes an issue where any row modification in the date column only changes the first row entry.

[en] Fixed: previously, when trying to delete a data source that was no longer being used in a data grid in a Presenter report, an error would occur. Now, these unused data sources can be deleted.

[en] Fixed: when submitting a new row in a Presenter report, if the column type is set to percentage, a percentage symbol is automatically added to the value, but when you try to submit the new row, an error occurs. Editable sources should be numeric instead of percent. Now, if a column is coming from an editable source, the option to make the column type percentage is disabled.

[en] Fixed: when using the conditional formatting background color option with Presenter Next styles, the background color in a cell appears to "spill over" outside the borders of the cell.

[en] Fixed: the header row on Presenter report data grids doesn't show a border on the right side if Presenter "Next" styles are enabled.

[en] Fixed: if a user is assigned to more than one group in Portal Access, and both of those groups are in a tree, if a Presenter Adaptive report is assigned to that access tree, the report will not load on Payee Web for that user.

[en] Fixed: when using the publishextract REST API call, an error occurs if the view column are renamed with web view restrictions and users cannot modify (edit or delete) columns if they are used by restrictions.

[en] Fixed: when using an API key generated through user options, the key does not work for migration calls despite working for other calls.

[en] Fixed: unable to sort columns in Scenario reports. With this fix, users can now sort report columns. We've also fixed an issue with the report not displaying until a new action is received and the Payee list not showing up in report options.

[en] Fixed: when deleting unused data sources from a Presenter Structured report, an error occurs. The error message is, "Source name is missing from the Presenter Report."

[en] Fixed: a calculation fails in Varicent ICM for Symon objects, but the Symon run completes successfully. The error message is, "Object reference not set to an instance of an object." This failure occurred when a column name contained invalid characters (like "/"). Varicent ICM now better handles these situations.

[en] Fixed: if you enter the wrong username or password when logging in to Payee Web with the web browser language set to French, the error message is different between the two versions of Payee Web and is not translated in Classic. Now, the error message is consistent across both and is correctly translated.

[en] Fixed: tables in Payee Web that allow data submission (not effective-dated tables) displays some values as if they were effective-dated. There are also some other text-wrapping and font-weight issues with some columns.

[en] Fixed: when both versions of Payee Web are enabled on a model, workflow alert emails would default to Payee Web (V2) links, causing an error if the base URL was set to Payee Web Classic. To fix this issue, there is a new option on the Admin page under More Options > Web beside the Base URL field to set the Web Version type. This option determines what type of Payee Web link is generated in workflow alert emails. Default creates Payee Web links and Legacy creates Payee Web Classic links. Generally, you’ll use this option only if you are doing parallel testing with both versions of Payee Web and need workflow alerts to go to Payee Web Classic links. If you have only one version of Payee Web enabled, the default setting will work.

[en] Fixed: error occurs when initiating a workflow. This error occurred when there are duplicate email addresses between multiple payees in the system.

[en] Fixed: error occurs when initiating a workflow. This error occurred when there are duplicate email addresses between multiple payees in the system.

[en] Fixed: there is no way to scroll through a table when viewing a Scenario report.

[en] Fixed: a visual bug where an internal error message appears when performing a migration with the web browser's language set to Japanese. This is a visual bug only since the migration still completes successfully.

[en] Fixed: calculation runs for longer than expected or gets stuck at 99%.

[en] Fixed: in Presenter Adaptive, the Sort menu in the pick list configuration allows users to select any text column. In Presenter Structured, the only options for sorting are ID and Description which correspond to other columns selected by the user. Presenter Adaptive should have the same behavior with ID and Display.

[en] Fixed: pick list options in Presenter Adaptive don't seem to work. The Hide ID column option is always applied, even when the checkbox is cleared. The Hide value for export options also does not seem to work (the pick list still shows up on the pick list, but only shows the default option rather than the selected value).

[en] The Value required option is also reported as not working. This option has been temporarily disabled and will be fixed in a future release.

[en] Fixed: process nodes in workflows are not kicking off Scheduler process. All other nodes in Workflow Manager are working. This fix may not be applied automatically. To ensure it is applied, stop all currently running workflows and then start them again. If you experienced this issue and it is not resolved by this fix, please contact our Support team.