Release Notes - Quantrix Modeler

To view these release notes with live links, see Modeler help online, and/or to see prior versions of Release Notes, view them at the Quantrix web site. 

 

Quantrix Modeler 23.2.1

Improvements in Modeler Version 23.2.1

(None)

Significant Fixes in Modeler Version 23.2.1

Performance is no longer an issue when working with sorted matrices without word wrap applied: Please see Known issue with performance for sorted matrices with word wrap applied (QM-25427)

Entering HTML in a cell using a formula or by directly editing it renders correctly (QM-25426)

Known Issues in Modeler Version 23.2.1

Sorting matrices that have Word Wrap applied can be noticeably slow while you are actively working on the matrix: consider turning off Word Wrap while working on the matrix, and turn Word Wrap on to view the matrix (QM-25427)

 

Quantrix Modeler 23.2.0

Improvements in Modeler Version 23.2.0

In prior Quantrix Modeler versions, cell text that exceeds a user-set column width would automatically wrap, but only if the row height allowed multiple lines to be visible. A new Word Wrap feature, when applied to items or groups on a row or column, will automatically adjust the height of the impacted rows and wrap the text so that all text in the cell is always visible (QM-24763). Once set, Word Wrap will continuously adjust (grow or shrink) row heights as cells are edited or formatted. Note that Word Wrap only applies to input, imported or calculated cells that contain text or hyperlinks and does not apply to item names or descriptors and cannot be applied to individual cells or partial item ranges.

Access Word Wrap from the item right-click context menu or the Format Toolbar button.

Word Wrap will continue to wrap text and automatically adjust row heights when models are published to Qloud, and text will remain visible when matrices are exported to PDF reports. However, Qloud users cannot apply or remove Word Wrap.

In order to make all characters visible Word Wrap may force breaks in the middle of long words or hyperlinks. The only time Word Wrap causes breaks in long words or hyperlinks is when the word is too long to fit on its own line.

Removing Word Wrap removes row height adjustments that may have been previously set by Word Wrap.

If you use non-standard fonts, it is possible the content may wrap with incorrect line spacing and padding when viewed on Qloud.

Word Wrap disables Auto-size width for the entire view if you have enabled it (Options/Preferences in Modeler > Matrix).

Word Wrap respects any user-set row heights as the minimum below which it should not shrink.

When Word Wrap calculates the required row height, it considers the values in filtered, hidden, and collapsed items. Therefore, row heights may appear larger than required to accommodate currently visible values.

Changes to row height, column width, text value, or text format cause Word Wrap to recalculate, as can moving a category, pasting data, and performing data operations. Therefore, excessive use of Word Wrap for large matrices may render more slowly.

The image below shows the new Format Toolbar Word Wrap button:

Please see details and examples in the Word Wrap section of the Entering Data in Cells help topic.

The animated example below illustrates how Word Wrap adjusts row height to accommodate the maximum needed, even if the currently visible values do not require that height:

 
 

New cell and item default row heights are now taller by two pixels, and the default minimum row height is 18 px (QM-25316). The new minimum row height affects Word Wrap, when manually setting a height with double-click, and right click > Row Height > Auto-Resize. When removing Word Wrap, the new minimum cell height is respected and will not be reduced below that manually set cell height. When Word Wrap is applied to existing text cells they adjust to the new minimum cell height. 

In the prior Quantrix release, we added the capability to synchronize edits of data imported from a Salesforce table. To use this feature, it is required that the import be configured to contain the primary key for that table. In this release we made this feature easier to use.

Data Import is improved with the addition of Primary Key icons for Salesforce data sources and SQL data sources (QM-25360). When Quantrix recognizes a Primary Key field in either type of source, the primary key icon displays in both the Data Source and tree. This makes it easier for users to ensure the key is present in a matrix to facilitate Salesforce synchronization.

The Salesforce primary key is a long character string that, when included as a matrix item, may detract from model usability. In this release it is now possible to use a different imported field as a display label to be shown in place of that long string (QM-25303). It might be useful, for example, to display the Salesforce Opportunity Name instead of the Opportunity key field. Further, the label itself need not be unique but might instead, for example, be the lowest level of a grouped hierarchy, where the grouped items together are unique.  See also Using Import Data.

For improved usability, the Copy View right-click menu option from the Model Browser has been removed and the right-click menu option Copy now copies a view if a single view is selected, or copies multiple components if more than one is selected (QM-24681). Note that what is pasted may depend on where you paste it, such as to the model browser vs. an external application.  The top-level model toolbar option, Edit, still offers both Copy and Copy View.

The Boolean constraints UI is improved when you've selected "Show a box only on hover", and shows check boxes on hover only for cells that are editable (QM-24892)

Significant Fixes in Modeler 23.2.0

In the below list, if you see an identifier that begins with “F0…” this designates that the issue is from our Customer Support system and therefore an issue reported by you, our customer. We pay special attention to customer reported issues and thank you for using our support system to report them!

Copy and paste once again works correctly for sorted selections (QM-25275, F0137637)

The permission to open script views is now controlled entirely by the Permission for Edit Structure > Edit/View/Manage Scripts (QM-25364, F0138871). Non-script view permissions are still controlled by Permissions > Open Components.

Using a MERGE INTO clause in Post-push SQL no longer issues an error, and the Post-push SQL completes successfully (QM-25202, F0136537)

Changing a filter tray selection and deleting an item no longer changes another filter selection, and synchronized views behave correctly whether the views are open or closed (QM-25288, F0138063)

Advanced Find & Replace in the Script editor now correctly refreshes the results of the replace (QM-25293, F0138136)

Modeler's file drop-down menu showing recently opened files, and descriptors as shown in the context menu, now display the first 50 characters of a file or descriptor name: hovering over the name shows the rest of the file name if it includes more than 50 characters (QM-24642)  

An exception should no longer occur related to filter trays, adding/removing categories, modifying filters, and updating Data Import (QM-25119)

Due to a Java bug, some Windows users have experienced exceptions when attempting to browse file folders containing two copies of the same shell folder. To prevent this exception, it is no longer possible to navigate to such folders using Quantrix Modeler (QM-25362)

When selecting a range of cells and copying, all relevant formats including line formats are copied and pasted, whether pasting to a model or to external locations such as Word (QM-25281)

In Data Import, canceling out of a JDBC connection or changing the custom SQL while not connected no longer causes an exception in certain scenarios (QM-25309)

When using the LAST keyword on the left side of a formula, the previously calculated values will now be cleared if new items are added at the end of the category or group (QM-25282)

When you ignore cell filter in a chart data table, it now correctly ignores the filter in the chart and its associated chart-table view (QM-21833) 

An exception no longer occurs involving charts and deleting categories followed by using undo (QM-23172)

Exceptions should no longer sometimes occur on canvases with line points on various components such as charts, with delete and undo actions (QM-24006)

An exception no longer sometimes occurs related to category replace, link and unlink operations (QM-21672)

When a matrix containing a stored image is copied to another model the image displays and no longer appears broken (QM-23978)

An exception no longer occurs when multiple trailing slashes are entered in URL/URI fields (in Options/Preferences, for example): Quantrix now checks for URL/URI's containing trailing multiple slashes, and removes them (QM-25335)

An exception no longer occurs related to copying script libraries to another model and renaming actions (QM-25069)

An exception related to the mouse hovering over data that is being deleted no longer occurs in various areas of Modeler (QM-24860)

Hyperlinks in cells that are created by manually entering the hyperlinks in cells, and/or by populating the hyperlinks from formulas, must contain only html and anchor tags in order to be valid (QWC-5415).  Note that when you use the insert hyperlink dialog to insert hyperlinks they are automatically entered correctly.

Known Issues in Modeler 23.2.0

On macOS, certain file choosers, such as the one used to pick the location of an Excel export, will not show if the Grammarly application is being used in the background. To resolve this, unload Grammarly by using System Settings > Security and Privacy > Accessibility and temporarily remove Grammarly from the list shown in the Accessibility section (QM-25260, F0137334)

 

Quantrix Modeler 23.1.0

Improvements in Modeler Version 23.1.0

Modeler's Constrain Input Boolean is improved so that you can now set a default value, initialized to true or false, or the corresponding display type equivalent (QM-25019). Cells with empty values to which the constraint is applied will be initialized with the default value and old cells will retain the values they had (QM-25037).  The default values will also be applied to newly created cells in the constrained range. See the related Known Issue for exceptions (new cells created by adding a category via linking).

Another Constrain Input Boolean improvement is that for non-checkbox Booleans (True/False, 1/0, Yes/No, or Custom), you can now toggle cell values more quickly, while still
being able to easily select them (QM-24902). Hover over the right side of the cell, and a check box appears. Click the check box to toggle the value (which will not select the cell) or click the cell contents to select the cell.

The Smart button feature is improved with the addition of the Open Perspective button. Use this new Smart button to place Open Perspective buttons on canvases and associate each button with a perspective to open (QM-25024). As with the open canvas smart button, the open perspective button won’t lose the association to the perspective with which you associate it even if the perspective is renamed. Unlike canvas navigation, perspective navigation does not yet have a concept of “previous” or “next” and you may experience unexpected behavior when canvas and perspective navigation are used together. Please see the Using Smart Buttons & Scripted Buttons help topic for more.

Another Smart button improvement is the ability to filter in the Edit Button dialog for Open Canvas, Open Perspective, and Custom Script lists to easily find what you need (QM-25021): 

 

Modelers can now put all canvases in a model in Interaction or Layout mode with one click (QM-25026). Once you've built a canvas, choose Interaction mode and all canvases in the model will be in Interaction mode unless or until you change the mode.  Likewise, if you choose Layout mode, all canvases in the model will be placed in Layout mode provided permissions are adequate. This behavior will be true both for newly created models and existing models that you open in this version. Note that canvases in existing models are set to Interaction mode if any canvas in the model is in Interaction mode at the time of the last save. 

Another canvas improvement is the addition of the Alignment and Distribution right-click options to the right-click context menu when you have multiple canvas items selected (QM-25025):

 

To support improvements to canvas scripting and the scripting api, two new objects, selectedCanvasObject and matrixChartOrTableView, allow you access to a single-object canvas selection or a matrix-like selection (this latter is designed to allow the creation of a modified selection in the matrix, chart or table view the user is working in, whether on a canvas or not) (QM-24950).
Per the autocomplete help,

matrixChartOrTableView -  The current view if it is a matrix, chart, or table view, or if the current view is a presentation canvas, the current selection on that canvas if it is a chart or table view.

selectedCanvasObject -  The current selection if it is a single canvas object. 

Please see related known issue.

An ease of use improvement to scripting is Ctrl-/ on Windows, and Cmd-/ on macOS to comment out a line or lines in the script editor. To remove a previously commented line or lines, use the comment command again and the comment (//) character(s) is removed (QM-24954) 

In Scripting, the Ask() method now takes an optional argument(s) allowing you to set default values for input fields (QM-24949). Per the autocomplete help, "this is an alternate version of ask that allows for both a preceding message and initial selections for the query arguments". In the example below, "Track" and "2" will be used as the defaults for Sport, and Number of Seasons respectively. Note also that the default value implemented by DOB:new Date() will default to the current date because new Date() returns the current date.  

ask("Sports Survey: Please complete",[DOB:Date.class, 'Sport':['Hockey', 'Football', 'Track'], 'Number of Seasons':Integer.class],['Sport': 'Track', DOB:new Date(), 'Number of Seasons':2])

The scripting function called exportPDF() is now supported in Modeler as well as in Qloud. It can be used to export all or a specific list of views to a local PDF file (QM-24501). Please see the Scripting Examples help topic for details.

A new Rename option in the Script Manager lets you easily rename libraries and scripts (QM-24975). The Rename option is located at the top of the right click menus accessed from the Script Manager's Libraries and script actions. 

To be more consistent with MacOS shortcuts MacOS now uses Cmd (Cmd + / and Cmd + Shift + / ) rather than Ctrl for the three formula autocomment operations, specifically: comment out whole formulas, comment out formula lines during edit, and comment out selection during edit (QM-25059). To turn off the help menu shortcut on MacOS so you can use block commenting, use: Keyboard > Shortcuts > App Shortcuts > All Applications > Show Help menu.

A new structural function, @itemCount() lets you easily return the number of items in a category (QM-24983). You can apply it to multiple categories, for example:

@itemcount(Matrix1::A):itemcount(Matrix1::B))

In Data Import, if you select  “Allow editing of imported cells” in the Configure Import Options panel, a new option below it, "Mark Changed Cell Values"  allows you to track any cell changes to imported editable (non-calculated) cells (QM-25136). Edited cells visually indicate that their values have changed so you can easily identify them. Please see the related improvement below that allows you to show only the rows or columns whose values have changed. Please also see the Configure Update Options help for details.

Related to tracking cell changes to imported data is the addition of a new right-click context menu that shows under certain conditions. Provided you have filter permissions and have selected Allow editing of imported cells in Configure Import Options, a right-click option for Changed Cells is available from cells or items (QM-25137). 
 
Under the Changed Cells menu, there are two menu items: Show Changed Rows, and Show Changed Columns.  When you choose Show Changed, unchanged rows/columns are hidden so you see only the changed rows/columns. This right-click context menu option is useful to consolidate your view to show only changed cell values for rows/columns. To return to the view of all rows/all columns, open the right-click menu option and remove the show changed selection(s).You can select both, and you can toggle the selection(s) off by right-clicking and then clicking the selection.

The Changed Cells menu has a third option for Salesforce imports only: Mark as Changed (or, if mark as changed is in force, mark as not changed) (QM-25276). Mark as Changed allows you to mark a cell or cells as changed, so that Salesforce will update with that value when you Synchronize to Salesforce.

Mark as Not Changed only works if the cell values have not been changed. If cell values have been changed and you try to apply Mark as Not Changed, a message displays explaining that the changed mark could not be removed for one or more cells whose value(s) were actually changed.

A major enhancement to our Salesforce connection allows data in Modeler that was imported from Salesforce to be modified and returned to Salesforce. A new feature called Synchronize will push any valid changes you made to the imported Salesforce data back to Salesforce and then refresh the data import (QM-25138). A new Synchronize button in the lower right corner of the Salesforce data matrix is available to perform this function . Specifically for Salesforce import matrices, there is also a new button to show changed recordsin addition to the right click menu option Changed Cells, that has a similar function.

Changes you push to Salesforce cannot be undone. To qualify for the Synchronize, the selected matrix view must be a Data Import matrix with a Salesforce Data source using a custom URL and must be based on a single table. See Synchronize Changes with Salesforce for additional rules and details.

The Data menus and some dialog wording are rearranged to support the data operation changes (QM-25249). DataPush has been changed to Push Data or simply Push; where it made sense the menu option order is changed. Convert to Data Import is now in the DataLink submenu.

In support of Salesforce, you can use new methods in a script to Synchronize changes with Salesforce (QM-25139). Scripts using these methods are supported on Qloud. The scripts that check for valid changes from a data matrix and to push them and then synchronize are:

canSynchronizeSalesforceData() - returns true if conditions are satisfied.
synchronizeSalesforceData() - pushes the data, and then synchronizes any changed data from Salesforce, or reports errors if needed.

Significant performance improvements have been made to Data Import from Salesforce when using the Configure Salesforce Import "Custom" connection, from a custom URL. OAuth authentication is used if supported (QM-25105)

To support data integrity, connection options for an existing Salesforce connection may not display (QM-24957)

The SQL used to create or update the table schema now uses a preferred data type for data and date-time columns if the database supports it (QM-25151)

Calculation performance is improved regarding import actions, such as Data Imports and in scripts, and will only trigger calculations when data has been updated that directly affects the calculation (QM-25205)

To enhance security and be consistent with Qloud, Modeler dialogs related to logging in to Qloud now use email addresses to identify users and not usernames (QM-25036)

The Qloud menu's Check Out dialog now includes a filter so you can filter the list of models by name or tag (QM-25080):

For improved usability Excel export no longer automatically adds protection to the exported Excel spreadsheet (QM-25225). You can protect the sheet from within Excel if desired.

Significant Fixes in Modeler 23.1.0

A Data Import Update error no longer occurs when importing data from Redshift database columns containing boolean datatypes (QM-24822, F0132207). Please see related Known Issue. 

In Data Import, when a filter uses an expression that refers to a range of values where some of the referenced cells are empty, an erroneous warning message no longer occurs (QM-25169)

In Data Import, when you use a filter qualifier, large integers in the Value field no longer show decimal places in the qualifier pane or qualifier pick list (QM-24992, F0134118)

Stored credentials are no longer cleared after exiting a model that performed a DataPush via a performWithAuthentication script (QM-25012)

When updating a DataLink on Qloud that was configured to import a text file and skip rows and/or columns, all data that should be imported on Qloud is imported (QM-25088, F0135196)

An exception no longer occurs in Data Import when you bring data into a data matrix using a filter qualifier with a pick list (QM-24344)

An exception no longer sometimes occurs when changing the data source (such as from a URL to a csv file) (QM-24055)

An exception should no longer sometimes occur related to loading (adding or importing) the same or different versions of database drivers (QM-25261)

User feedback when running scripts, regarding script messages and script progress (percent complete) is improved and is more accurate in most script operations (QM-25016, F0134596)

The Constrain Input Boolean checkbox behavior in matrices is now consistent with canvas check boxes regarding empty cells and non-numeric cells and whether the check boxes appear selected (QM-24854)

When a cell can't display all the data in it, and Auto-size on cell, item and format changes is not enabled (via Tools > Options/Preferences > Matrix settings), right-clicking in the related item and choosing Row Height > Auto-Resize now resizes correctly (QM-25173). Undo and Redo are available for these actions.

remove(), removeAll(), or clear() no longer show in the autocomplete for formula selections (for example, |Matrix1::Formula::| and |Matrix1::Formula::1-3|) (QM-25098,F0135725)
Formula and FormulaSelection (like |Matrix1::Formula::| and |Matrix1::Formula::1-3|: allow both delete() and deleteWithoutClearing()), to clear formulas via scripting
Single formulas (e.g. |Matrix1::Formula::1|): allow remove() and clear() actions (but not delete with or without clearing)
A formula list from a matrix (|Matrix1|.formulae) and a groovy list version (|Matrix1|.formulae.asList()): allow remove() and clear() actions (but not delete with or without clearing)
Better error messages display when clear() and remove() on lists is not supported

A canvas layout permission error no longer occurs involving legends laid out with a 1-pixel width (QM-25114,F0135802) 

Filtered canvases no longer sometimes render incorrectly when you change the filter criteria (QM-25172, F0136377)

Next / Previous navigation no longer sometimes opens the wrong canvas when used in conjunction with opening a perspective (QM-25132)

Multiple login pages no longer appear when you open a local Qloud model when logged out (QM-24774)

Reconfiguring timelines in a model containing formulas in other matrices that use non-overlapping timelines no longer throws an error (QM-25189, F0136508)

Errors that sometimes occur when saving models show a meaningful message explaining that there was a problem saving the file and suggesting you try saving again or try saving to a different file (QM-25167)

An exception no longer sometimes occurs related to copy and pasting canvases with line end points that point to cells, items, categories or charts (QM-22330)

An exception no longer occurs when resizing items in certain scenarios involving hide empty rows and columns (QM-24885)

An exception related to logging in to the Qloud in certain scenarios involving saved basic credentials for the Qloud and the Qloud being set to use OAuth, should no longer occur (QM-25038)

Exceptions should no longer occur in certain situations involving using undo in the permissions panel followed by deleting or renaming the permission-relevant objects (QM-25109)

An exception no longer occurs when a formula is deleted in the Problems pane and the matrix containing the formula has been deleted: a Delete Formula error displays (QM-25107)

Known Issues in Modeler 23.1.0

Update Data Import will sometimes fail when trying to aggregate the boolean type because the aggregation operators sum, average, min and max are not supported in many databases for booleans. Aggregation of boolean data types is supported only by Count. If booleans are needed, consider using an all rows query (QM-24822)

New cells created by adding a category or by linking will not get the default values you have set for the boolean constraint. 

Salesforce Push Data: You can't push fields that are relations to other tables in Salesforce. For example, the owner.name field in an Account object is a relation to a User table and cannot be pushed.

Currently the canvas scripting selection object matrixChartOrTableView does not work for a selected chart's data view on the canvas.