Fixes
00191926 — Checking process list items too fast does not register
Fixed: when items on a process list are checked off too quickly, some of the check marks do not register. The green check marks appear briefly and then immediately disappear. If these items are checked slowly, it works as expected.
TS002976227 — All sources are visible from Data Discovery Dashboards even when Component access is restricted
Fixed: you can view all sources when adding a source in Data Discovery Dashboards even when the Component access is restricted.
00193134 — Audit Change Details button missing for data saved entries in Dutch
Fixed: when the web browser language is set to Dutch, in the Audit tab, the Change Details button is missing for saved entries.
00192587 — Error when providing an end date for time shift calculations
Fixed: user cannot add an end date to some pre-existing time shift calculations using columns that involve a locked time period. When adding an end date and clicking "finish", an error message appears. This error is provided despite the start date checkbox not being checked.
1. Create a monthly calendar starting January 2020.
2. Create a custom table with effective dates. You can use any columns ("id" and "text").
3. Enter a new row with a start date of June 1, 2020. Enter another row for the same ID with a start date of July 1, 2020.
4. Create a user-defined calculation:
-Data source: custom table from steps 2-3
-Restrictions: None
-Display Columns: the "id' column and the "Effective_Start" (using the test calendar, monthly calculation and accumulation levels, and no start or end date)
-Formula: SUM(TestTableName.value)
5. Create a time shift calculation:
-Data source: the calculation from Step 4
-Shift: 1 period
-No start date or end date
6. Lock the calendar until the end of June, 2020.
7. Edit the time shift calculation. Check off "End Date" and add an end date after the lock date of June 30, 2020.
8. Upon clicking "Finish", you will see an error reading "Start date must be later than 2016-10-29T00:00:00Z. Earlier dates are locked."
00191891 — Dragging value into formula box deselects the cursor
Fixed: when dragging and dropping values into the formula box, the cursor disappears and you need to click inside the formula box before you can start typing again.
1. Create a new calculation.
2. When you get to the formula step, write 'SUM(' and then drag a value from the sources into the formula box.
Result: the value is inputted, but the formula box is de-selected.
TS002616488 — Can't change the source of a period partition for a locked calendar
Fixed: the source of the period partition for a locked calendar in a calculation cannot be changed.
1. In Composer, add a calculation with a period partition.
2. Lock at least one of the periods used by that calculation.
3. Edit the calculation you made in step 1.
4. Try to change the source for the period partition.
Result: error occurs. The error message is, "The calculation is locked, the requested action may not be completed."
00192908 — CLI calcall results in "the operation has timed out" error
Fixed: when running a full calculation via CLI, an error occurs in the CLI tool, but the full calculation does run in the model. The error message is, "The operation has timed out."
00194293 — Unable to edit or save a view
Fixed: when editing a view in Composer in Internet Explorer, the window crashes and closes.
00192840 — Path for nested components disappears when it is too long
Fixed: previously, when creating nested components in V10 and the path name became too long or there were many nested components, the components' path at the top of the Composer map started to accumulate on top of each other. Now, you can see a longer breadcrumb path in Composer, making it easier to navigate when there are components with long names and nested components.
00193172 — Unchecking a child component leaves the parent component checked
Fixed: previously, during a migration, unchecking a child component would leave the parent component checked. Now, there is a partial check for parent components if only some child components are checked.
1. In Composer, create a component with at least two child components. If you already have this set up, skip this step.
2. Navigate to a different model, go to Migration, and connect to the model where you created the components.
3. Select the parent component.
4. Clear one of the child components.
Result: the parent component remains checked.
00191249 — UI issues when selecting multiple rows in row viewer
Fixed: when highlighting multiple rows in row viewer in Internet Explorer, additional rows that are not selected are also highlighted.
00189992 — Pick list data isn't filtered based on effective date
Fixed: in row viewer, pick list controls are not filtered based on the effective date when the pick-listed table is also effective-dated.
1. In Composer, add a structural table. Make it effective-dated.
2. In Composer, add a custom table.
a. When creating columns, make one of the columns a pick list to the structural table added in step 1.
3. Add data to the structural table. Make sure at least one row has an effective end date before the default end date. For example, set the effective end date to 02/28/2014.
4. Add data to the custom table. Set the effective date to after the row you added in step 3 (the example being 02/28/2014).
5. Click the Add button to add a row.
6. Click the drop-down menu for the pick-listed column (the one you added in step 2a).
Result: you can select data from the structural table even though, based on the effective end date selected for the custom table, it isn't valid. When you try to submit the row, an error occurs, but invalid data shouldn't appear in the pick list.
00193041 — ODBC imports cause an error: "The headers in the import source do not match those in the column mapping."
Fixed: when running ODBC imports, column mapping don't register the first time and results in an error. The error message is, "The headers in the import source do not match those in the column mapping."
00193326 — Completing a migration does not refresh the home page
Fixed: completing a migration does not refresh the home page. Once a migration has completed, the model does not return to original functionality. In some cases, there are missing icons on the screen. In other cases, the migration percentage would still display "0%", but in a new Varicent SPM tab, it says the task completed successfully.
1. Migrate a component.
2. Open a new browser tab (make sure you open at the home page).
3. In the new tab, wait until the migration completes.
Result: The new browser tab shows missing icons and activities in the Varicent SPM home page.
00192021 — Report parameters appear in Payee Web Classic reports, but not in Payee Web
Fixed: in V10, entering parameters into certain Presenter reports reveals a data grid in Payee Web Classic. This data grid does not appear in Payee Web with the same parameters.
00190250 — Error when clicking on pie charts in Payee Web
Fixed: when clicking on pie charts in certain Presenter reports in Payee Web, an error message appears. This error does not occur in Payee Web Classic.
00188894 — On Payee Web, a scroll bar appears on the top menu when the page is zoomed in, but does not disappear when zoomed out
Fixed: when using Payee Web in Internet Explorer 11, when the page is zoomed in, a scroll bar appears on the right side of the screen. When the page is zoomed out, the scroll bar remains.
TS002498194 — Reports in Payee Web cannot be zoomed out to view the full report at once in Safari on an iPad
Fixed: when using Safari on an iPad, you cannot zoom out to view full reports in Payee Web. The display is zoomed in, so only parts of the report can be viewed at once.
00192330 — Headers in Payee Web not maintaining format when scrolling down the page
Fixed: when scrolling down a data grid with Freeze Header Row enabled, the cell size in some header rows change. This issue does not occur in Payee Web Classic.
1. Find a Presenter Report with a source that has quite a few columns.
2. Ensure that the source has at least a couple of hundred rows to scroll down the page.
3. Check Freeze Header Row.
4. Attach Presenter to a web tab.
5. On Payee Web Classic, go to the Presenter Report and scroll down.
Result: The header row does not maintain cell height consistency.
00192299 — An error occurs when opening some reports in Payee Web
Fixed: when accessing some reports in Payee Web, this error message appears: "An internal error has occurred. Contact System administrator for assistance."
00191591 — Number scaling option not working correctly for charts in V10 Payee Web and Payee Web Classic
Fixed: number scaling not working properly for charts in V10 Payee Web and Payee Web Classic. When hovering over a bar in the chart, the whole number should be displayed. Instead, only the scaled number shows. This issue does not occur in V9.
TS002235920 — Report is blank after logging back in to Payee Web after session expires
Fixed: when the session times out in Payee Web with SSO enabled, if the user previously had a report loaded with parameters, when they go back to the report, it's completely blank.
65479 — REST API console appears blank on successful startup
Fixed: Previously, the REST API console showed log details upon startup. A change was made to avoid exposing the full logs, but this made the console appear blank, which could be confusing, as it looked like an error. Now, some start up messaging appears in the console. The rest of the logs do not appear, but you can still view the logs if needed from the log file location specified in restapi.appsettings.config.
63370 — Unable to edit records in some tables that contain Boolean values
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."
TS002711267 — Payee Web on mobile page exceeds screen length on Safari on an iPhone
Fixed: when viewing certain web reports on Payee Web on mobile using Safari on an iPhone, the page does not take up the full screen. Instead, you have to scroll to the right to view the full report. This also happens with maintenance announcements.
00192256 — Error displaying webform on Payee Web when editing format of multiple cells
Fixed: webforms with multiple formatted cells do not display properly on Payee Web. Also, when a formatted data source is deleted from a webform, a new data source cannot be created in the same cell since there are leftover objects from the first data source occupying the same cell.
00194203 — "Index was out of range" errors in workflows nodes
Fixed: Workflows Alert nodes result in a Service node error: "Index was out of range. Must be non-negative and less than the size of the collection". Although the error occurs for Alert nodes, it is logged as Service node error.