Varicent Sales Performance Management Documentation

Fixed: trying to edit a source in a Presenter report causes the page to crash.

Fixed: when calculating results via Composer for a specific payee, you don't get results when searching for payees past the first 100 results in the table.

Fixed: recent activity times displayed do not match with the values inside the audit log.

Fixed: when Data Tier Optimization is enabled, a calculation fails. The error message is, "Rounding with SQL Server should not be used, as it does not use Banker's rounding".

Fixed: previously, the ROUND and ROUNDDOWN function in calculations did not round values correctly if the second parameter is a negative value. With this fix, when a negative value is passed in the second parameter, the value is rounded up or down at the index to the nearest even integer. If you have encountered this issue, contact Support to enable this fix.

Fixed: when adding restrictions to a calculation that contains multiple data sources, the operator menu does not include the full list of operators.

Fixed: using the backspace or delete key to edit a date in a time shift calculation does not work as expected (for example, pressing backspace on the value '2020' changes the value to '0202' instead of '202').

Fixed: when the browser language is set to Polish, there is a mismatch between weekday and date in the text boxes with the calendar selection.

Fixed: when using the row viewer to edit values in a table with a filter applied, the UI does not reflect the changes made unless you refresh the page or remove the filter.

Fixed: when creating a new (not effective-dated) table in Composer, you can pick list an effective-dated table even though you should not be able to pick list an effective-dated table in a non-effective-dated table. This issue only occurs if you add the pick list at table creation, as an error occurs, as expected, when editing an existing table.

Fixed: when editing a data store that has a union with a mis-matched column, the changes can be saved. Now, you should be unable to save edits to data stores if the unioned columns are mis-matched.

Fixed: view tables not showing values.

Fixed: when attempting to end-date a calculation, an error occurs and the action is not completed. The error message is, "The proposed changes attempt to modify the locked calculation 'CALC NAME'. The requested action may not be completed."

Fixed: previously, when trying to locally publish large tables (over 10 million records), those downloads would either time out or only partly download. Now, there is a default limit on local table publishes of 1 million records, but you can request to increase the limit to up to 10 million by contacting Varicent Support.

Fixed: when searching for data sources to create data stores or View tables in Composer, the search only returns 50 results. With this fix, the search will now return 100 results.

Fixed: when editing an existing source in a Presenter report, the edit wizard appears but the loading spinner stays indefinitely so the source cannot be edited.

Fixed: previously, some object types were incorrectly reported as unused in the Health Dashboard. Now, tables used in saved imports and calculations used in view tables will no longer be considered unused objects.

Fixed: user-defined calculations that are included in a workflow appear in the “Unused Objects” metric when you run a Health Dashboard evaluation.

Fixed: view tables can have history tracking entries when they shouldn't. With this fix, history tracking will never be enabled on view tables.

Fixed: when using the Inquiry module to add inquiry logs to a web tab, it only shows the "My inquiries" tab and you cannot click on the inquiry row to open the inquiry. With this fix, the Inquiry module shows all tabs and you can click on any row to view that inquiry. This issue does not occur in Payee Web Classic.

Fixed: if you add an Inquiry module to a web tab, the module shows as blank until you visit the Message Center. With this fix, the Inquiry module shows inquiries the first time you visit the web tab.

Fixed: when downloading a data grid in a Presenter report to Microsoft Excel, it takes twice as long to download the file in Payee Web when compared to Payee Web Classic.

Fixed: when exporting a Presenter report to a PDF, an error occurs if the report contains a chart with 0 width and 0 height. This issue does not occur in Payee Web Classic.

Fixed: when adding a URL to a workflow action node, when that message is viewed in Payee Web, the URL does not appear as a hyperlink. This issue does not occur in Payee Web Classic.

Fixed: when viewing documents in the Payee Web Message Center, if you sort the list of documents by clicking the column header and then navigate away, when you come back to the documents page, the list is back to being unsorted despite the column header showing the 'sorted' icon. This issue does not occur in Payee Web Classic.

Fixed: when using conditional formatting to add a background color to cells in a Presenter report, when you export to Microsoft Excel, the conditional formatting is not retained in the Excel file.

Fixed: when viewing a Presenter report in Payee Web, the header row alignment always uses the default (aligned to top) even when the Align Headers to Bottom checkbox is selected. This issue does not occur in Payee Web Classic.

Fixed: when submitting data through a custom web form, after clicking the submit button, the navigation bar duplicates at the top of the page.

Fixed: when accessing Payee Web through Salesforce, clicking the "Inquiry copy" icon in a data grid does not work.

Fixed: when viewing a Presenter Structured report that has an editable field in Payee Web, a thick, black border appears around the cell. This only occurs in Safari and Chrome.

Fixed: (PPO only) when using QueryTool, some column data incorrectly shows as "Invalid date". This issue was caused by a UI bug which incorrectly interpreted some values as dates although there were no issues with the source data.

Fixed: when adding a transpose to a Presenter report, you cannot scroll down if there are more available rows than what can fit in the wizard window.

Fixed: trying to edit a source in a Presenter report causes the page to crash.

Fixed: when using sort selection to add a page break to an aggregate source in a Presenter report, on some models, the page redirects to an error page.

Fixed: when using the row viewer to edit values in a table with a filter applied, the UI does not reflect the changes made unless you refresh the page or remove the filter.

Fixed: when filtering column results, records that contain special characters cause an error. The error message is, "(value) could not be parsed".

Fixed: language-specific special characters are causing an error in filtering column results.

Fixed: when using the copy and paste function in Scheduler to create External Tool tasks that were created using type PYTHON3, the resulting "pasted" external tool reverts to PYTHON2, which causes errors when you try to run the task.

Fixed: clicking the Expand button does not do anything when changing Role Settings in Task Manager.

Fixed: an error occurs when clicking a cell in a web form to load parameters from a linked Presenter report.

Fixed: in a web form that populates a list of records, only the first row of records is returned when multiple rows should appear.

Fixed: an error occurs when clicking a cell in a web form to load parameters from a linked Presenter report.

Fixed: slow performance when opening and editing workflows. With this fix, users should see an improvement in performance.

Fixed: swimlane sources and restrictions are not displayed after being saved. This issue occurred because the Presenter report contained a parameter with the same name as a system table. Now, you cannot add parameters to Presenter reports or workflow swimlanes, which will prevent these errors.