Loginom 6.3.3 release Notes

Mechanism of collapsing and expansion of supernodes was revised in this version. As a result, several issues were resolved.


  1. Integrator: if a set of input fields of earlier published node was changed as a result of automatic synchronization of fields, the following error occurred, when calling such node: “Invalid column count in the matrix of values” (#5601).   
  2. Quick view, Cluster profiles: when using Internet Explorer, the cells containing real numbers with values exceeding 1e20 or less than 1e-6, were not drawn in Quick view, and when opening the “Cluster profiles” visualizer, the following error occurred: “The object does not support the property or "log10"” method (#7661, #7689).      
  3. Web application: when changing the scale on the login page, an error could occur, and the login and password field was locked. In some cases, error message was not displayed, but login and password fields were also locked (#7644).
  4. Import from Deductor Warehouse: when importing fields with the Date/time type and set filter condition “the first” or “not the first” and value 18/30/42... months from the current date, the following error occurred: “Error executing query to Data Warehouse” (#7676).
  5. XML import: when the imported XML file has a particular structure, the input data set will contain extra rows that contain the only value or that consist fully of <'null'> (#7601, #7641).
  6. Configure variables values, Row filter: it is allowed to enter infinity in the real number field. It can be done using two methods: you can enter the number exceeding 1.79e+308 or less than -1.79e+308; you can insert Infinity or –Infinity from the clipboard. The following error occurred previously while attempting to enter the number more or less than the allowable one: “Value of this field cannot exceed 1.79e+308 [less than -1.79e+308]” (#5254).     
  7. Connection to REST service: it is not possible to create a new connection if there was at least one certificate with the blank “Issuing Authority” field in the certificate store (#7663). 
  8. Cluster profiles: if a blank cluster was received as a result of clustering, when pointing the mouse cursor to histogram in the main table, or histogram of the blank cluster in the comparison table, the following error occurred: “Cannot read property 'toString' of undefined” (#7672).   
  9. Cluster profiles: the following error occurred  in Internet Explorer, when pointing the mouse cursor to histogram: “Failed to receive the "parentElement" property of a link the value of which was not defined or is NULL” (#7673).   
  10. Expand/collapse supernode: if we expand the Supernode containing a random Node and one more Supernode with the Derived Node that has a set “Protected” visibility level, in the case of reverse collapsing the visibility area of the Derived Node was increased up to the “Internal” level that was not required (#5932).   
  11. Expand/collapse supernode: if two nodes (or more) with the “Open” or “Published” access modifier with no links to them in none of the opened packages were collapsed into the Supernode, the access modifier of the final Supernode became “Closed”. As a result, if there were links to the final nodes in other packages that were not opened when collapsing, these links became invalid (#5985).  
  12. Expand/collapse supernode: if it is required to collapse into the Supernode any node and other Supernode containing the 
  13. Reference Node configured for the collapsed node, while attempting to run the Reference Node, the following errors occurred: “Socket not configured” and “No reference to node specified” (#6182). 
  14. Expand/collapse supernode: when collapsing or expanding, the Supernode with complex dependences (containing several nested Supernodes, Derived Components and Loops tuned to run the Supernodes) can cause inconclusive errors (#6407, #6892).  
  15. Expand/collapse supernode: when collapsing the Derived Node of connection to the Supernode, the access modifier of connection was “Closed”, as a result, the connection was not visible in the Supernode (#6408). 
  16. Expand/collapse supernode: when collapsing into the Supernode, settings of the visibility components located in the nested Supernodes were not correctly installed. As a result, the external Derived Node stopped to react to the base node changes, and in the case of repeated package opening, such node was denoted as invalid (was marked in red color), as it was not possible to find the base component for it (#6974).  
  17. Expand/collapse supernode: if the Group Processing Loop was collapsed into the Supernode, in some case settings of the input fields were reset, as a result, the Loop was run with an error (#7560).
  18. Expand/collapse supernode: when collapsing into the supernode, the node access modifier that is the base one for the Derived Component (Component #1) was not changed. If before collapsing into the supernode, one more Derived Component (Component #2) was created from such Derived Component, and the Derived Node used for creation was deleted, then after collapsing of the base node into the supernode, while attempting to create the node based on Component #2, the following error occurred: “The local component doesn’t exist in {...-..-..-..-...} identifier list” (#7651).  
  19. Expand/collapse supernode: when expanding the supernode containing connections, the expanded nodes were biased to the right and downwards (#7706).

Usability improvements

  1. Expand/collapse supernode: logic of generation of input and output ports when collapsing to the supernode was changed. Previously, the number of input and output nodes was defined by the number of connections, now it is defined by the number of source ports. There is the following principle of captions generation for input nodes: if the input port of the resulting Supernode is connected with one internal port, then it will receive the same caption as the internal port. Otherwise, the captions of “Table 1” and “Table 2” type are generated (#6232, #7680).
#release notes#6.3#6.3.3#loginom

See also

Building customers' loyalty
What is customer loyalty? Is it repeated purchases? Or an emotional connection that is manifested, for example, in the fact that the client recommends your company to their friends?
The credit pipeline. The case of the MigCredit microfinance organization
How to migrate to a modern analytical platform and replace the database without stopping the work of the credit pipeline. A practical case from the leader of the microfinance market in Russia,...
Missing data imputation
In practice, missing data are very common in real data processing. The reasons may comprise data entry errors, information hiding, or fraud. In this article, we will discuss in which cases...