[en] Varicent Incentive Compensation Management Documentation

[en] Fixes

[en] 00191308 — UserIDs are missing in exported Microsoft Excel file

[en] Fixed: when exporting the list of users from User and Permissions > Change Roles, the Excel file does not list all of the UserIDs.

[en] TS003126982 — String was not recognized as a valid Datetime

[en] Fixed: when using a Windows system with Chrome as the web browser, when clicking on a Process List, some of the lists with filters will cause an error. The error message is, "String was not recognized as a valid Date time."

[en] TS003198728 — Tenant logs now show whether a user was able to successfully log in

[en] Previously, the tenant log only showed that there was a login event, regardless of whether the user was successful. Now, the tenant log has a "Success" column that shows TRUE if the user successfully was able to log in, and FALSE if they could not. The new error column also shows why the user was unable to log in.

[en] 00192059 — Export from Change Roles has inconsistent information for users

[en] Fixed: when exporting the User Permission Report from change roles, the email address shows for users that were imported from V 9 whereas the username shows for users manually added. Now, the exported file always shows user IDs.

[en] 00190524 — If the name of a permission on the Admin page > Change roles contains a comma, it breaks the line in the exported Microsoft Excel file

[en] Fixed: when exporting the list of users and permissions on the Admin page > User and Permissions > Change Roles has a comma in the title, the text is split into two cells instead of one, causing inconsistent formatting in the Microsoft Excel file.

[en] 00189097 — Computation log does not show alternate calculation method names

[en] Fixed: the computation log now indicates whether a calculation used an alternate method (used for troubleshooting calculation issues).

[en] 00188545 — Single calculation takes more time than the total report calculation time

[en] Fixed: in the computation logs, sometimes a single calculation would appear to take more time to run than the total report calculation time. A previous improvement allowed some calculation events to run simultaneously. But the total calculation time was still based on the sum of all events, causing this error. Now, the computation log correctly uses the start and end time instead of the sum.

[en] 00188899 — Calculation auto-cancelled

[en] Fixed: made improvements to the monitoring application to reduce likelihood of a rare issue that caused a calculation to cancel with no errors.

[en] 00191004 — Calculation error not recorded on Audit Log, performance graph shows invalid runtimes

[en] Fixed: calculation still appears to be "in progress" in the performance log, with the duration value continuing to accumulate, despite a successful calculation.

[en] TS003371991 — Orphaned calculation still reporting "started" status

[en] Fixed: calculation still appears to be "in progress" in the performance log, with the duration value continuing to accumulate, despite a successful or cancelled calculation.

[en] TS001994099, TS002010892, TS001184154 — 'Include Empty Partitions' option for calculations can cause non-responsive queries

[en] Fixed: added a warning message when choosing the Include Empty Partitions option in the Display Columns tab when adding or editing a calculation.

[en] TS003204696 — Category calculation period tab missing calendar name

[en] Fixed: the Period Tab does not display the calendar name when setting up a Category Calculation, and displays only the ID of the calendar.

[en] 1. Log in to the admin client.

[en] 2. In Composer, add a calculation.

[en]   a. Select Category as the calculation type.

[en]   b. On the Data Sources tab, add a calculation that has a calendar partition as the data source.

[en]   c. Go to the Period tab to define the start and end dates.

[en] Result: only the calendar ID is displayed when it should also show the calendar name.

[en] TS003096394 — After naming a View table, the window title stays as "Add View" when it should show the view name

[en] Fixed: when adding a view table, the placeholder text "Add View" remains even after saving a name for the table.

[en] 1. In Composer, add a View table.

[en] 2. Save a name for the table.

[en] Result: the table name shows as 'Add View' when it should show the saved name.

[en] TS003031631 — Error occurs when trying to delete payees from the Payee table

[en] Fixed: unable to delete payees from the Payee table due to foreign key constraints with other tables.

[en] 64969 — Data Store restrictions fail with "Object reference not set to an instance of an object" error

[en] Fixed: after editing restrictions on a data store and trying to save, an error occurs. The error message is, "Object reference not set to an instance of an object."

[en] TS002952177 — Error when trying to add a transposed column to a Presenter Report source

[en] Fixed: added a clearer error message when trying to add a transposed column that has too many rows. The error message is, "A data source used in the report is over the limit."

[en] TS002196403 — Composer auto arrange does not work or behaves differently when compared to V9

[en] Fixed: when selecting auto-arrange in Composer, it does not auto-arrange automatically and instead you have to select 'Arrange' every time.

[en] 1. Log in to the admin client.

[en] 2. In Composer, navigate to a component.

[en] 3. In the toolbar, select the Auto option beside the auto-arrange icon.

[en] Result: objects are arranged.

[en] 4. Leave the component and then come back.

[en] Result: objects are not arranged when they should be because Arrange is set to auto.

[en] 00191564 — Error trying to remove payees from the Payee table

[en] Fixed: when trying to remove payees from the Payee table, an error occurs. The error message is, "Data could not be saved because it is no longer valid."

[en] TS003404504 — Deleting payee table entries causes error

[en] Fixed: when trying to delete users in the Payee table, an error occurs. The error message is, "Data could not be saved because it is no longer valid."

[en] TS003417044 — Unexpected behavior while publishing a table to your local machine

[en] Fixed: if you publish a table in Excel to your local computer, but there is already a file with the same name in Imports, that file will be downloaded instead of the published table data.

[en] 1. Pick a table in your model that has at least one row of data.

[en] 2. On your local computer, create a Microsoft Excel file and add one row of data. When you save it, give it the same name as the table you identified in step 1.

[en] 3. On the Admin page, go to Downloads and import the Microsoft Excel file.

[en] 4. In Composer, select the table > Show More > Publish.

[en]   a. Select One Time Publication.

[en]   b. Select Microsoft Excel as the destination for the published table.

[en]   c. In the Name field, do not change the title.

[en] 5. When the download completes, check the file.

[en] Result: the downloaded file is the file created in step 2 when it should be the data from the table identified in step 1.

[en] 00174750 — Disabling tracking on source table returns 502 proxy error

[en] Fixed: when attempting to disable history tracking on a large table, Composer eventually shows a 502 Proxy Error. The audit log shows the disabling tracking action has started, but the failure is not recorded.

[en] 1. Log in to the admin client.

[en] 2. Select a table > Data > clear the Track History option.

[en] Result: after waiting for some time, a 502 proxy error occurs.

[en] TS003330277 — Effective date filter does not work on tables

[en] Fixed: when publishing a table with effective date filters, the data in the published file is not restricted by those filters. Additionally, the effective data filter is reset whenever a new restriction is added.

[en] 1. Log in to the admin client.

[en] 2. In Composer, select a table that has effective dates and view the values in the table.

[en] 3. Apply a filter to the table, ensuring some data is hidden.

[en] 4. Publish the table.

[en] Result: the data in the table is not restricted based on the filter.

[en] 5. Apply another restriction to the table.

[en] Result: all values are visible again.

[en] 00192765 — Calculation comments no longer display in Composer

[en] Fixed: when hovering over calculations in Composer, only the name displays when both the name and comments should display.

[en] TS003017554 — Increase the limit in Data Discovery Dashboards to greater than 100,000

[en] Previously, the limit on Data Discovery Dashboard sources was 100,000 rows. Trying to add a data source larger than this would cause an error. This limit has now been removed. Note that visualizations will still limit the data you can see all at once, but you can use filters to see data that isn't visible initially.

[en] TS002996593 — Data Discovery Dashboard large data set error 400 on canvas

[en] Fixed: Previously, the limit on Data Discovery Dashboard sources was 100,000 rows. Trying to add a data source larger than this would cause an error. This limit has now been removed.

[en] 00190775 — Roboto font not appearing in Payee Web

[en] Fixed: when selecting Roboto as the font in a Presenter Report, the font does not render in Payee Web or when previewing from the admin client. It works correctly in Payee Web Classic.

[en] 00188635 — Error when trying to import files larger than 2GB

[en] Fixed: unable to import a file into a table after uploading it through SFTP. The error message indicated imports larger than 2GB were not supported, but the issue was unrelated to file size. Users can now upload files larger than 2GB without seeing this error.

[en] TS002740577 — Unable to perform migration due to error with inquiries.

[en] Fixed: cannot migrate portal access trees that have inquiries, even when those inquiries are closed. The error message is, "The workflow tree is being used in an ongoing inquiry."

[en] 00190525 — Cannot migrate Portal Access trees

[en] Fixed: when attempting to migrate Portal Access trees, an "invalid column name" error occurs. This issue occurred when the 'Enable payees in group for web and notify them of their passwords' Task Manager rule was set for that Portal Access tree. This has now been fixed.

[en] TS003294883 — Tenant logs do not show which user made a password change

[en] Previously, the tenant log only showed the user whose password was changed, not who initiated the password change. Now, the tenant log clearly states which user initiated the change and for which account.

[en] 00191119, 00191889, 00191603, 00192607 — When trying to add an existing user to model, the list is missing users

[en] Fixed: when adding users from existing users to a model, the list is missing users.

[en] TS002985860 — Payeeweb V2 Error shows Parameter Name instead of Value

[en] Fixed: when hovering over an inquiry field with validation rules, a tool-tip appears with the parameter name in Payee Web. In Payee Web Classic, the tool-tip showed the validation rule instead of the name. The tool-tip now shows the validation rule to match the behavior in Payee Web Classic and be more helpful to the end user.

[en] TS002361637 — Payee Web object alignment issues in Safari

[en] Fixed: vertical alignment issues when comparing reports in Payee Web on Safari versus Firefox web browsers.

[en] TS002875020 — Linked reports in Payee Web display incorrect web tab

[en] Fixed: when adding links from one Presenter report to another, if a web tab was not selected in the Add a Link wizard, the linked report always opens in the first web tab that has that report mapped. This can be confusing if you link to the same report in different web tabs. With this fix, if you do not specify a web tab when adding a link to a Presenter report, the linked report appears as a stand-alone report with no web tab in the header. This issue does not occur in Payee Web Classic.

[en] TS002498168 — Save comment button is not properly visible in PayeeWebv2

[en] Fixed: when adding data to an editable field in Payee Web, the Submit button is not fully visible when there is more than one line of text. This issue does not occur in Payee Web Classic.

[en] TS002427032 — When a column is unhidden, the last column is not resized properly

[en] Fixed: when a column is made visible, the column that was previously hidden is not resized equal to the other columns. This issue did not occur in Payee Web Classic.

[en] 00190246 — Font in the downloaded Microsoft Excel file is different from what is specified in Presenter report

[en] Fixed: when downloading a report to Microsoft Excel, sometimes the font in the downloaded file is different than what it specified in the report.

[en] 00188930 — Batch export to PDF is blank in Payee Web

[en] Fixed: when doing a batch export to a PDF file, the files are blank in Payee Web. This issue does not occur in Payee Web Classic.

[en] TS003252052 — Varicent ICM Performance Log counts ongoing calculation times even when nothing is running

[en] Fixed: calculation still appears to be "in progress" in the performance log, with the duration value continuing to accumulate, despite a successful calculation.

[en] 00189139 — Payee Web pyramid chart legend shows inverted values

[en] Fixed: when using a pyramid chart in a Presenter report, viewing it in Payee Web shows inverted values. This issue does not occur in Payee Web Classic.

[en] 1. Log in to the admin client.

[en] 2. In Composer, add a Presenter report.

[en] 3. Add a data source to the report.

[en] 4. Add a pyramid chart to the report.

[en]   a. Click Legend and complete the following steps:

[en]   b. Select the Show Legend checkbox to display a legend on the chart.

[en] 5. In Portal Access, assign access to the report.

[en] 6. Log in to Payee Web and go to the report.

[en] Result: legend shows incorrect information.

[en] TS003156018 — Changes to an editable field in a Presenter Report does not update records correctly.

[en] Fixed: an issue where, when submitting data through an input row form, a new row is added but the wrong data is sent. This occurs when a column has the same prefix as another (for example, a column named COL when other columns are named COL2, COL3, and so on).

[en] 1. Log in to the admin client.

[en] 2. In Composer, add a table.

[en]   a. Name the columns with the same prefix (for example, COL, COL2, COL3).

[en] 3. Add a Presenter report and then edit it.

[en] 4. Add a data grid to the report, using the table created in step 2 as the source.

[en] 5. Add editable columns to the data grid.

[en] 6. In Portal Access, assign access to the report.

[en] 7. Go to the report and add data to each of the editable columns.

[en] Result: upon submission, the data is not entered correctly (one column might be empty, and two submissions might appear in another).

[en] 00190619 — Clicking out of the data grid sort window closes the wizard

[en] Fixed: clicking outside of the data grid sort wizard in Presenter Reports immediately closes the wizard.

[en] 00190619 — Clicking out of the Add calculation window closes the wizard

[en] Fixed: clicking outside of the Add calculation wizard in Presenter Reports immediately closes the wizard.

[en] 00190676 — Clicking out of the text display link window closes the wizard

[en] Fixed: clicking outside of the Add a link wizard in Presenter Reports immediately closes the wizard.

[en] 00186121, 00190381, 00191157, 00190630 — Some actions do not extend the Payee Web session timeout

[en] Fixed: some actions in Payee Web do not extend the user session (like scrolling through a report or clicking a checkbox), forcing the user to log in again too soon. This issue occurred in Payee Web and Payee Web Classic and it has been fixed in both.

[en] TS002446919 — Unable to modify Presenter report link on slow internet connections

[en] Fixed: if the user has a slow internet connection, you cannot edit the link target between two reports without modifying the parameter configurations.

[en] 00190251 — Padding and border disappear after editing Presenter report charts

[en] Fixed: When editing a chart in a Presenter report, if there is any padding around the chart, it resets to 0 padding after clicking Create in the chart wizard.

[en] 00190371 — CurrentDate table column name displayed with a space when used as a source

[en] Fixed: a table with the column name "CurrentDate" was used as a source in a calculation but when displayed in the wizard, the column name includes a space, "Current Date".

[en] 00191779 — Cannot edit saved publication path

[en] Fixed: in some saved publications, editing the publication path returns an error. The error message is, "Publication name has already been used". This occurs even when the name is unique.

[en] 63370 — Unable to edit records in some tables that contain Boolean values

[en] Fixed: unable to edit records in some tables. The error message is, "Data could not be saved because it was modified somewhere else. Please refresh the page to get the latest version."

[en] TS002925535 — Index rebuild timing out

[en] Fixed: running an index rebuild times out before the operation completes.

[en] 1. Log in to the admin client.

[en] 2. Schedule an index rebuild.

[en] Result: operation times out before it can complete.

[en] 00189718 — Unable to apply text formatting to IBM Plex when used in a report

[en] Fixed: unable to apply text formatting (bold, italic, and so on) to IBM Plex in Presenter reports.

[en] 1. Log in to the admin client.

[en] 2. In Composer, edit or add a new Presenter report.

[en] 3. Add a text field to the report.

[en] 4. Set the font to IBM Plex.

[en] 5. Apply text formatting like bold, italic, or underline.

[en] 6. Preview the report.

[en] Result: text formatting is not applied. Text formatting also does not appear when viewed in Payee Web or Payee Web Classic.

[en] 00181858 — Users can still use Payee Web after web is disabled

[en] Fixed: when a logged in web user is disabled for web access, they can still use Payee Web until they log out. Now, access is restricted immediately when the change is made in the admin client.

[en] 00191590 — Different message displayed in SFDC when web is disabled when comparing Payee Web and Payee Web Classic

[en] Fixed: when web is disabled in SFDC, Payee Web Classic shows this message: “An internal error has occurred. Contact the administrator for assistance”. The correct message in Payee Web is “Payee Web is temporarily unavailable. Please try again later”. The message is now the same in both versions.

[en] TS003198728 — Locking and unlocking users is not recorded in the audit log

[en] Fixed: the audit log now shows when a user account is locked or unlocked.

[en] 65169 — Workflow Error: "String or binary data would be truncated"

[en] Fixed: email messages are now trimmed if they exceed 1,000 characters to prevent this error.

[en] 63785 — Workflow value not passed to parameter

[en] Fixed: workflow does not initiate if there are parameters in a swimlane that should be required, but are currently not set as required. Now, you will get an error when trying to edit the workflow which parameters are missing from the workflow.

[en] TS003237294 — Swimlane restrictions are not updated at first attempt

[en] Fixed: when editing swimlane restrictions, they are not updated the first time and you have to go back and edit a second time before it updates.

[en] 1. Log in to the admin client.

[en] 2. In Workflow Manager, edit a swimlane in a workflow.

[en] 3. On the Restrictions tab, edit a restriction.

[en] 4. Click Create.

[en] 5. Edit the swimlane again and go to the Restrictions tab.

[en] Result: the edits made in step 3 were not saved.

[en] 6. Try editing and saving the restriction again.

[en] Result: edits are now saved.