Fixes
TS002381649 — Cannot disable users
Fixed: Previously, there was no option to disable users from a model without deleting them from the model. Now, a user can be disabled and unable to log in, but are still associated with a model.
See: Locking users
TS002381649 — A user with no permission can still view Activities
Fixed: a user with no permission granted can still view some modules.
TS002193263 — Inconsistency in data grid template fonts
Fixed: When comparing data grid templates in Admin and Presenter, there is an inconsistency in the number of fonts available. Now, on-premise shows all system fonts when managing data grid templates and Cloud shows the default fonts when managing data grid templates.
Reproduction Steps
1. Log in to the admin client.
2. Go to Admin > Manage > Data Grid Templates.
3. Click 'Create a New Template' and follow the steps in the wizard.
a. Under the font menu, the number of available fonts is close to 90.
4. In Presenter, edit the data grid template.
Result: the number of available fonts is 12 when the number of fonts available should match the Admin menu. On-premise, the number of fonts is the same as the number of system fonts. On Cloud, the number of fonts is 12.
TS001701843 — Scheduler emails say task failed when the task generated only warnings
Fixed: email notifications from Scheduler state the task failed even if it generated only warnings. Now, the email notification states whether a task failed or completed with warnings.
61573 — No entry in audit log when a web form is edited
Fixed: when a web form is edited, there is no entry in the audit log.
Reproduction Steps
1. Log in to the admin client.
2. Add a web form and make some edits.
3. Go to the Audit Log.
Result: there is no entry for the web form edit.
62820 — Filtering the audit log with the web browser language set to French does not work
Fixed: cannot filter the audit log using French language.
Reproduction Steps
1. With the web browser language set to French - France, log in to the admin client.
2. Run a model optimize.
3. Go to the audit log.
4. Filter for "Optimiser le modèle."
Result: filter does not return any results for the French name of the action. Searching in English (Optimize Model) works correctly.
TS002834296 — Incorrect rounding on a calculation
Fixed: Calculation results are rounded even if the calculation formula uses IF statements and SUM(0).
Note: If an affected calculation uses a locked calendar, you must unlock the calendar and recalculate to apply this fix.
Reproduction Steps
1. Log in to the admin client.
2. In Composer, select a calculation that uses IF statements and SUM(0) in the formula, but does not use ROUND > View Current Values.
Result: The results are rounded.
TS002584125 — Calculation does not complete
Fixed: calculation does not complete.
TS002648006 — Sort Data rank value changes to "Standard" after it's created.
Fixed: after adding a sort calculation, the data rank value changes from sequential to standard.
Reproduction Steps
1. Add a sort calculation.
2. On Sort Data tab, from the Rank drop-down list, select Sequential.
3. Edit the calculation and go to the Sort Data tab.
Result: the Rank list value is now Standard when it should remain as Sequential.
TS002795584 — Calculation engine and calculation wizard issues related to browser language
Fixed: Restrictions in calculations do not work correctly for some languages (for example, Spanish - Argentina causes the issue, while Spanish - es does not).
For calculations already experiencing this issue, if those calculations used commas as the decimal separator for restrictions, you should re-save the restrictions in the calculation.
Reproduction Steps
Calculation Wizard:
1. Using a web browser with the language set to English-US, log in to the admin client.
2. Add a table.
a. From the Table type drop-down list, select Custom.
b. Type a name for the primary key field and select Text as the column type from the Type drop-down list.
c. Click Add a column to add a numeric field to the table.
3. Add table data and add a numeric value with a decimal to the table (for example, 0.02).
4. Add a user-defined calculation.
a. On the Data Sources tab, select the table created in step 2 as the data source.
b. On the Restrictions tab, add a restriction to the value you added in step 3.
c. On the Display Columns tab, select all the columns from the table as partitions.
5. Using a web browser with the language set to Spanish-AR, log in to the admin client.
6. Select the calculation added in step 4 > edit and look at the restriction.
Result: the restriction now shows as a whole number when it should remain as a decimal (for example, 2 instead of 0.02).
7. Try changing the restriction value to use a comma as the decimal separator (for example, 0,02).
8. Using a web browser with the language set to English-US, select the calculation added in step 4 > edit and look at the restriction.
Result: the restriction now shows as a whole number when it should remain as a decimal (for example, 2 instead of 0,02).
Calculation Engine:
9. Using a web browser with the language set to Spanish-AR, select the calculation added in step 4 > edit and look at the restriction.
Result: the restriction shows values in decimals (for example, 0,02).
10. Run the calculation and confirm the results.
11. Using a web browser with the language set to English-US, run the calculation.
Result: there are no results for the calculation.
Row Viewer:
12. Using a web browser with the language set to Spanish-AR, select the table > View Data.
13. Try to apply a filter using a period as the decimal separator.
Result: no values are filtered when the results should also filter on values using a comma as the decimal separator.
TS002914199 — Unable to save Presenter report due to error
Fixed: improved error message when attempting to save a Presenter report that has trailing space at the end.
Reproduction Steps
1. Log in to the admin client.
2. Add a Presenter report.
a. Type a name for the report that has trailing space at the end (for example, "Report test ").
3. Save the report.
Result: error occurs and report cannot be saved.
TS002692225, TS002780991 — Table pick list filter unable to add data sources
Fixed: unable to add pick list filter to a data source.
Reproduction Steps
1. Log in to the admin client.
2. In Composer, select a table > Edit.
3. Expand the menu under the first column, select the Filter checkbox, and then click "Add filter."
4. Try to drag a data source into the window.
Result: the data source cannot be dragged and dropped.
TS002872321 — 502 Proxy error
Fixed: load error occurs when trying to add a column to a table.
Reproduction Steps
1. Log in to the admin client.
2. In Composer, edit a table and add a column.
3. Go to Composer or the Audit Log.
Result: error occurs.
60678 — Data store preview does not indicate the total number of rows
Fixed: when previewing a data store, if the number of total rows is over 100, the message states, "showing 100/100 rows" instead of indicating the total number of rows.
Reproduction Steps
1. Log in to the admin client.
2. Add a data store.
a. Define a data source that has more than 100 rows.
3. Click Preview.
Result: the preview shows "100/100 rows" when it should show "100 of (total rows)".
TS002571247 — Unclear error message when deleting a display column in a data store
Fixed: When deleting a display column in a data store, users receive an error with the message, "The given key was not present in the dictionary" if one of the columns is used in a Presenter report. Now, the error message informs the user which report the column is being used by.
TS002444143 — Process list with Delete Rows task that was migrated errors out
Fixed: an error occurs when clicking a 'Delete Rows' task in a process list that was migrated from another model. The error message is, "Required parameter 'id' was null."
Reproduction Steps
You will need two models: a source model and a target model.
1. Log in to the admin client in the source model.
2. Add a table.
3. Define the table as global.
4. Add a process list.
5. Add two tasks to the list: View table and delete rows.
6. Log in to the admin client in the target model.
7. Perform a migration.
a. Select the table created in step 2 and the process list created in step 4 as the objects to migrate.
8. Log in to the admin client in the source model.
9. Add a task to the process list created in step 4: publish.
10. Log in to the admin client in the target model.
11. Perform a migration.
a. Select the process list created in step 4 as the object to migrate.
b. Select the Replace Conflicts checkbox.
12. View the process list and click the 'Delete Rows' task.
Result: error occurs.
62307 — Cascade delete does not work when deleting database imports
Fixed: if the record of an import is deleted, the record in the import database table is not deleted.
TS002738567 — Mapping of "Create Fields" when creating a saved import is not preserved
Fixed: when adding a new column to a saved import by using "Create Field", the column mapping is not saved when viewed from the Admin page.
Reproduction Steps
1. Log n to the admin client.
2. Import data from a database file.
a. Select 'Save this import as'.
b. When mapping columns, map at least one column using the "Create Field" option.
c. Select the Merge Field tab and create a merged field.
d. Click 'Add'. Note that the new field is correctly mapped in the column mapping window.
3. Go to Admin > Managed > Saved Imports.
4. Hover over the saved import created in step 2, click the ellipses > Edit.
5. Proceed through the wizard until you get to the column mapping tab.
Result: The data field for the column that used the "Create Field" option shows placeholder text (Match a column) when it should show the new field as it does in step 2d.
TS002725775 — Migration status window appeared stuck
Fixed: Fixed an issue where the migration status window appeared stuck when it fact the migration has already completed
TS002987799 — Cannot perform a migration
Fixed: when migrating Composer objects, the migration does not complete with an error. The error message is, "Object reference not set to an instance of an object."
Reproduction Steps
You will need access to 2 models for these steps: a source model and a target model.
1. In the source model, add a category calculation.
a. On the Data Sources tab, define the Payee table as the data source for your calculation.
2. In the target model, perform a migration.
a. Select objects from Composer as the objects to migrate.
b. Select the Replace Conflicts checkbox.
3. In the source model, add a user-defined calculation.
a. On the Data Sources tab, select the Payee table as the data source for your calculation.
b. On the Display Columns tab, select "PayeeID" and "Date_Of_Hire".
4. Edit the category calculation created in step 1 and replace the original source with the user-defined calculation created in step 3.
5. Lock the first month of the calendar you used when creating the user-defined calculation in step 3.
6. In the target model, perform a migration.
a. Select objects from Composer as the objects to migrate.
b. Select the Replace Conflicts checkbox.
Result: migration wizard closes but the migration did not complete. The activity page shows an error.
62471 — DatabaseVersion set incorrectly after upgrade
Fixed: after running the Model Upgrader, the DatabaseVersion is set incorrectly. The key DatabaseVersion is no longer in the Config table and is now stored in the DatabaseVersion table.
TS002759527 — Logging out of Payee Web with SSO enabled requires clearing browser cache
Fixed: logging out Payee Web with SSO enabled requires clearing cache.
Reproduction Steps
1. Log in to Payee Web (must have SSO enabled).
2. Log out.
Result: cannot log out.
3. Log back in.
4. Clear cache.
5. Log out.
Result: log out is successful, but it should be successful even if the browser cache is not cleared.
62722 — Maintenance banner reappears after refresh
Fixed: upcoming maintenance banner returns when the page is refreshed, even after it is closed by the user.
Reproduction Steps
1. Log in to Payee Web when the maintenance banner is active.
2. Dismiss the banner.
3. Refresh the page.
Result: the banner reappears. The banner also comes back when navigating through reports.
60257 — "Missing view permissions for current workflow" error occurs when submitting anything in a report with a pick list.
Fixed: error occurs when going from a web tab accessed via a workflow to any other web tab. Error message is, "Missing view permissions for current workflow."
Reproduction Steps
1. Log in to the admin client.
2. Start a workflow.
3. Log in to Payee Web as a user who has a pending workflow as a result of step 2.
4. Open the pending workflow.
5. Go to any other report that contains a pick list.
Result: user receives an error with the message, "Missing view permissions for current workflow."
TS002759527 — Payee Web log out from native redirects to SSO login
Fixed: after logging out of Payee Web with native login, the page redirects to the SSO login.
Reproduction Steps
1. Log in to Payee Web (native login).
2. Log out of Payee Web.
Result: page redirects to SSO login.
TS001870638, TS002874808 — Download action tool-tips are not displayed
Fixed: in Payee Web, hovering over the download buttons does not bring up a tool-tip.
Reproduction Steps
1. Log in to Payee Web.
2. Go to any report with inquiries or downloads enabled.
3. Hover over the download (or inquiry) icon.
Result: no tool-tip is displayed when hovering over the icon.
TS002759527 — Cannot log out of Payee Web with SSO
Fixed: cannot log out of Payee Web with SSO enabled.
Reproduction Steps
1. Log in to Payee Web with SSO enabled.
2. Log out.
Result: page redirects to Payee Web and the user is still logged in.
TS002193435 — Presenter report fails to load if the values of one pick list are dependent on another pick list
Fixed: Presenter report fails to load in Payee Web if the values of a pick list are dependent on another pick list.
Reproduction Steps
1. Log in to Payee Web.
2. Go to a report that uses a pick list filter in an editable source.
Result: the report does not load.
TS002151550 — Column values align differently in Payee Web
Fixed: when comparing reports from Payee Web Classic to Payee Web, values in data grid columns align differently.
Reproduction Steps
1. Log in to Payee Web.
2. Go to a report that has a data grid.
Result: value alignment in columns is different than they appear in Payee Web Classic.
TS002498079 — Secondary navigation menu missing scroll bar in Internet Explorer 11
Fixed: when viewing Payee Web with many web tabs in a group, if using Internet Explorer 11, the scroll bar is missing, making some web tabs inaccessible.
Reproduction Steps
1. Log in to Payee Web.
2. Go to a web tab that has a lot of sub-tabs in a group.
Result: the page cannot scroll left or right, making some tabs inaccessible.
TS002745370 — Maintenance banner in Payee Web returns upon refresh after being dismissed
Fixed: upcoming maintenance banner returns when the page is refreshed, even after it is closed by the user.
Reproduction Steps
1. Log in to Payee Web when the maintenance banner is active.
2. Dismiss the banner.
3. Refresh the page.
Result: the banner reappears. The banner also comes back when navigating through reports.
TS002757638 — Error occurs when submitting a value from an editable column
Fixed: If a data source name contains a special character (for example, "ż"), when submitting data from an editable column, an error occurs. The error message is, "Specified cast is not valid."
Reproduction Steps
1. Log in to the admin client.
2. Add a table.
a. From the Table type drop-down list, select Custom.
b. Type a name that includes a special character (for example, "ż").
3. Add table data.
4. Add a Presenter report.
5. Add the table from step 2 as a data source to the report.
6. Drag the source into the layout to add a data grid.
7. Add an editable column to the data grid.
8. Add a submit button.
9. In Portal Access, assign access to the report.
10. Log in to Payee Web and go to the report.
11. Enter a value in the editable field and submit.
Result: error occurs. The error message is, "Specified cast is not valid."
TS002498109 — Franc symbol missing from PDF file download of Presenter report
Fixed: the Franc symbol (₣) is missing if a Presenter report is downloaded as a PDF file.
Reproduction Steps
1. Log in to the admin client.
2. Add a Presenter report.
3. Add text to the report and include the Franc symbol (₣).
a. Change the font to Arial.
4. In Portal Access, assign access to the report.
5. Log in to Payee Web.
6. Download the report as a PDF file.
Result: the Franc symbol (₣) is not there when viewing the PDF file of the report.
TS002342778 — Function always appended to the end when using "Add a function" in Presenter
Fixed: when adding a function to a Presenter report computed column, the function is appended to the end of the formula box regardless of where the cursor is placed.
Reproduction Steps
1. Log in to the admin client,
2. Add a Presenter report.
3. Add a data source.
4. Add a computed column.
a. Add a source to the formula field.
b. Place your cursor at the beginning of the first source.
c. Select a function from the Add a function menu.
Result: the function is appended to the end of the formula when it should appear where the cursor is placed.
TS002329385 — Presenter report parameters preview and View Current Values
Fixed: When viewing current values in a Presenter report data source wizard, users cannot preview the values based on a set parameter.
Reproduction Steps
1. Log in to the admin client.
2. Add a Presenter report.
3. Edit the Presenter report.
4. Add a parameter.
5. Add a data source.
a. On the Data sources tab, select a table as the main source and the parameter created in step 4 as an additional source.
b. On the Restrictions tab, define the restrictions to be the value of the parameter.
6. Add a data grid by dragging the source into the layout.
7. Click Preview > Set Parameter.
8. Fill in the parameter and click Save.
The result is the data grid in the preview is restricted based on the parameter.
10. Edit the source > View Current Values.
Result: the values in the preview are not restricted based on the parameter.
TS002716507 — Error preventing numeric columns to be toggled as editable in Presenter reports
Fixed: When the Toggle Editable option is selected, an error occurs with the incorrect message, "Numeric formatting style cannot be set while the column is toggled editable" and the report cannot be saved.
Now, the error message says, "At least one submit button is required on reports with input controls. Please add a submit button to this report."
Reproduction Steps
1. Log in to the admin client.
2. Add a Presenter report.
3. Add a data grid to the report.
4. Add an editable column to the data grid.
Result: an error occurs and the report cannot be saved.
63025 — Improved security of error messages that included model information.
Fixed: Improved security of error messages that previously included unnecessary model information.
TS002795227 — Cannot access downloads > publications
Fixed: Downloads > publications tab does not load.
Reproduction Steps
1. Log in to the admin client.
2. Go to Downloads > Publisher.
Result: tab does not load.
TS002514080 — Provided JSON web token is invalid, font request is failing
Fixed: on the login screen for on-premise installations, an error occurs with the message, "provided JSON web token is invalid".
TS002173297 — Current Row not available as a source when adding a restriction to a pick list filter
Fixed: Current Row is not available as a source when adding a restriction to a pick list filter.
Reproduction Steps
1. Log in to the admin client.
2. Edit a table.
a. Add a column and select Pick List as the type.
b. Select a table to populate the pick list.
c. Select the "Filter" checkbox.
d. Click "Add filter."
Result: (Current Row) is not available as a data source.
TS002726100 — Scheduled process folder does not run
Fixed: scheduled process folder does not run.
TS003013877 — Cannot create purge history task
Fixed: cannot create a purge history task in Scheduler.
Reproduction Steps
1. Log in to the admin client.
2. Add a task to Scheduler.
a. From the Type drop-down menu, select Purge History.
b. Type the name of a table.
Result: no results appear when you should be able to select a table and create the task.
TS002623971 — Addition of warning message before scheduling a folder of tasks
Fixed: New confirmation message when users try to schedule a task that may conflict with another task. The new message is, "Another item may conflict with this schedule time. There may be a potential unsuccessful run in the future. Do you wish to proceed?"
TS002277849 — Individual Scheduler tasks do not send emails upon success or failure
Fixed: Scheduler email notifications are sent only for processes (folders) and not for individual tasks.
Reproduction Steps
1. Log in to the admin client.
2. In Scheduler, add a process folder.
3. Add a task to the folder.
4. Set the global Scheduler properties.
a. Select the On error, send email to these addresses checkbox and type the users' email addresses in the field.
b. Select the On success, send email to these addresses checkbox, and type the users' email addresses in the field.
5. Run the process folder.
Result: no email notification is sent for the task.
TS002735338 — View tables available on Index Rebuild list
Fixed: when adding an Index Rebuild task in Scheduler, view tables are available from the object list even though they cannot be rebuilt.
Reproduction Steps
1. Log in to the admin client.
2. Add a table.
a. From the Table type drop-down list, select 'View.'
3. Add a task to Scheduler.
a. From the Type drop-down menu, select Index Rebuild.
b. From the object menu, select the table added in step 2.
Result: the task fails because view tables cannot be rebuilt.
63221 — Cannot access Scheduler
Fixed: unable to access Scheduler.
Reproduction Steps
1. Log in to the admin client.
2. Go to Scheduler.
Result: the page does not load.
TS002048313 — User role change is not reflected
Fixed: when changing user roles via model options, the change is not reflected when clicking "Finish" and only shows up after refreshing the page.
Reproduction Steps
1. Log in to the admin client.
2. Go to Admin > Users & Permissions > Manage Roles.
3. Go to Model Options > select a model.
4. In the user list, select a user and click the "Edit" icon.
5. Under "User Role", select a new role and click Finish.
Result: the user role on the page does not update unless you refresh the page.
61761 — Payee Web redirects to native login page upon timeout on Salesforce web tab
Fixed: Resolved an issue where, when Payee Web is accessed via a salesforce tab, if a user clicks on the page after 15 minutes of inactivity, they are redirected to the native login screen when they should be redirected to a blank page instead.
Reproduction Steps
1. Log in to Salesforce and go to the Payee Web tab.
2. Wait 15 minutes for the session to expire and then click anywhere.
The result is the page redirects to the native Payee Web login page when it should redirect to a blank page.
TS002680095 — Payee Web redirects to a blank page upon timeout on a Salesforce web tab
Fixed: when accessing Payee Web is via Salesforce, after timeout, the user is redirected to a blank page when there should be information specifying the user was logged out due to inactivity.
Reproduction Steps
1. Log in to Payee Web using a Salesforce web tab.
2. Wait 15 minutes for the session to expire.
Result: user is redirected to a blank page.
TS001689568 — Error occurs in web forms when a column is added to a table
Fixed: if a column is added to a source table for a web form, when the web form is viewed in Payee Web Classic, it does not load.
Reproduction Steps
1. Log in to Payee Web Classic.
2. Go to a web form. Note how it loads.
3. Log in to the admin client.
4. Add a new column to a table used in the web form from step 2.
5. Log back in to Payee Web Classic and go to the same web form.
Result: an error occurs.
TS002754703 — Maintenance window notification time unclear
Fixed: Notification banner for upcoming maintenance is unclear.
Now, the time format spells out the month to improve clarity (for example, November 25, 2019 10:45 AM). The time zone is the user's local time.
TS003026530 — Payee Web API 500 error
Fixed: when updating multiple tables at the same time from Payee Web (usually done by using TS-API endpoints on web forms), there is a concurrency error that results in a generic 500 error.
Reproduction Steps
1. Log in to the admin client.
2. Add a table.
a. From the Table type drop-down list, select 'Custom' and click Next.
3. Import a lot of data into the table (at least 10k rows).
4. Repeat step 2 and step 3 to add a second table.
5. Using the TS-API, or by having two separate sessions of the admin client, update the tables 50 rows at a time.
Result: eventually, a deadlock occurs.