Skip to Content
Release NotesRelease Notes 3.8

Release Notes 3.8

New Features and Improvements

  • SnowflakeSource supports Key Pair Authentication with key encryption (3.8.2025-07-08)
  • MessageConsumerService does not add record to activity log about executing the handler scenario for each message by default. Parameter “Disable Activity Log” is added to MessageConsumerService: values are true and false (true by default) (3.8.2025-06-12)
  • executeJob REST API call now checks permissions according to the opeation name: more granular permissions supported for RunScenario and RunWorkflow operations (3.8.2025-06-09)
  • ‘run’ privilege is added for ‘specification’ subobjects of ‘app’ object (3.8.2025-06-09)
  • Support Target -> Format paramters -> Content format -> json now implemented (before it was available but not implemented) (3.8.2025-03-13)
  • Support for Identity Provider (IdP) initiated SSO (3.8.2025-02-05)
  • Javascript builin function ilQueryQL is addeded (3.8.2024-12-09)
  • REST API api/v1/getActivityLog.jsp “after” parameter is added (3.8.2024-11-20)
  • LoadXML: detecting duplicate elements for a table column and support for support Ignore duplicate elements matching the same column (3.8.2024-09-19)
  • LoadXML: support for ‘Parse only’ when the data is parsed but not inserted in the target source (3.8.2024-09-18)
  • LoadXML: the table schema is created from the column mapping if it is provided instead of deriving the schema from the first record (3.8.2024-09-09)
  • MatchOneSource -> consolidation optimized: max now processed differently from min because in max we can filter out nulls thus making the result table smaller (3.8.2024-08-21)
  • HTTPRequest operation now supports Options that allows specifying connectTimeout, readTimeout, writeTimeout for the HTTP request (3.8.2024-08-19)
  • Activity log functionality and corresponding Maintain operation options are extended (3.8.2024-07-17):
    • The activity log stores the id of the user who executed the job. User filter for activity log is now available in UI, Maintain operation -> trimActivityLog command and Maintain operation -> loadActivityLog command.
    • Maintain operation -> trimActivityLog command is extended with appId filter.
    • Maintain operation is extended with loadActivityLog command. It allows you to download activity log records from the metadata repository to a CSV file or a table stored in any data source. You can use all kinds of filters such as appId, userId, job status, start time, etc. Using these filters you can easily configure incremental activity log synchronization or other synchronization strategies.
  • OracleDatabaseSource supports Column profile in data viewer (3.8.2023-10-13)
  • Support for functions (3.8.2023-10-09):
    • /address/street/format/normalize
    • /address/street/format/normalize
  • checkCollation boolean parameter is added to infolink.conf. Setting this parameter to “no” will disable checking (and subsequently trying to modify it) for the recommended collation on metadata repository initialization (3.8.2023-10-02)
  • Metadata encryption now supports “Azure Key Vault - Key” in addition to secrets. Support for keys allows easily rotating the data encryption key (DEK). Using key (vs secret) is now the recommended method (3.8.2023-09-22)
  • Data viewer improvements (3.8.2023-09-22):
    • Filter redesigned to match the UI style
    • Support for result pagination
    • Column menu extended with “Add to filter…” and “Sort by”
    • Value cell context menu extended with “Add filter with this value”
  • Steward UI improvements (3.8.2023-09-22):
    • View data starting from source records or golden records. You could start only from golden records before. All manual operations are supported in both modes.
    • Displaying the target record redesigned to match the UI style and now more compact and fixed size.
    • Configurability is extended so that the UI can be used for reviewing data matched by a third-party matching engine: the following parameters added to the matching specification:
      • “Id column (default: data_id)” - to specify the name of an unique identifier of the match table
      • Settings -> “Match table - match group column name (default: set_id)” - to specify the name of the “set_id” column.
    • Steward UI benefits from all the data viewer improvements included in this release because the UI is based on the data viewer.
  • Export an application in YAML format. YAML export can be used to compare applications from the same of different InfoLink instances (3.8.2023-06-07-1248)
  • User groups (3.8.2023-05-26-1248)
  • Audit log (3.8.2023-05-26-1248)
  • UI applications: rapid low-code development of business user interfaces (aka UI) that use Infolink scenarios for data manipulation in the backend (4.27.2023-04-11-1248)
  • Environments (3.8.2023-04-11-1248)
  • Marketplace improvements: (1) support for publishing environments related to bundles; (2) bundle now identified by marketplaceId instead of name; (3) UI refreshed (3.8.2023-04-11-1248)

Bug Fixes

  • Import application -> Import into existing application: the app cache is not updated - the user still sees the content of the existing application until they do any operation that updates the cache (e.g. clicking on the checking all button) (3.8.2025-11-05)
  • DoLoop operation encounters a NullPointerException in the Java function truncateLogAfterRecentCheckPoint at the beginning of the second iteration when nested DoLoops are present (3.8.2025-08-13)
  • SnowflakeSource supports Key Pair Authentication: conflicting library that leads a class not found error during connection in some environments is identified and removed (3.8.2025-07-12)
  • System log in the trace mode prints credentials of application sources, environments, and on saving metadata (3.8.2025-07-25)
  • Variable not substituted in the properties of SnowflakeSource (3.8.2025-07-08)
  • LoadExcelFile does not show tabs in UI suggestion for .xlsx files (3.8.2025-06-12)
  • MessageConsumerService: prefetchCount is set to 1 for RabbitMQ to avoid acknowledge timeout errors (3.8.2025-05-012)
  • 3 retries on deadlock error in update activity log, which is called on job completion. It helps to avoid ghost “running” records in the activity log (3.8.2025-05-01)
  • Variable not substituted in the properties of RabbitMQSource and KafkaSource (3.8.2025-04-14)
  • Going to signout.jsp page when logged out returns the NULL pointer exception (3.8.2025-03-31)
  • WorkflowService: null pointer exeception during workflow execution (3.8.2024-12-13)
  • One source specification: “profile groups” in any Match tab throws an error about query not being an object (3.8.2024-11-19)
  • Difference operation only worked for one key column, now works for multiple (3.8.2024-11-13)
  • Incorrect handling of versions during editing in applications: “Do not have permissions” to see your own objects (3.8.2024-11-05)
  • Import bundle: privilege role_type is set to ‘user’ for backward compatibility with the previous version (e.g. 3.2) where there were no roles and thus no role_type in the bundle (3.8.2024-09-27)
  • LoadXML: not resetting the batch on each run led to accumulation of records when executed from inside a ForEachRecord loop (3.8.2024-09-23)
  • LoadXML: close the source file properly (3.8.2024-09-16)
  • Bundle export from 3.2 fails with missing file errors when imported to 3.8 (3.8.2024-09-03)
  • User password requirements changed: password must be 8-64 characters (3.8.2024-08-13)
  • Permission on user operations not checked (3.8.2024-08-13)
  • Password not saved on user creation. Required to change user’s password to make it work. (3.8.2024-08-13)
  • In Settings, one cannot view privileges for roles and users if the privileges are for deleted applications. For applications deleted before this fix, such privileges are now displayed with the object commenting that the app does not exist (e.g. app: <app 205 does not exist>). You can revoke such privilege manually. For newly deleted applications, the application deletion procedure is extended to remove such privileges automatically. (3.8.2024-07-31)
  • Maintain operation - trimActivityLog throws “Incorrect syntax near ‘l’.” when the metadata repository is in SQL Server (3.8.2024-07-11)
  • AWSSESSource: ‘region’ property is not saved (3.8.2024-06-28)
  • MatchOneSource temp tables with the name similar to il_matchrun_0_pairs_matched7954bd8f-9c28-414c-a091-ca57a9998ef9 are not deleted at the end (3.8.2024-06-21)
  • Hope page -> Settings -> Metadata repository does not indicate that the metadata is stored in the embedded database showing the configuration of the external metadata repository (3.8.2024-06-20)
  • “Page Unresponsive” popup in the browser caused by a log table suggestion list (3.8.2024-06-20)
  • “Check in”, “Check out”, “Undo check out” missing in the context menu on Model->Relationship specifications (3.8.2024-06-19)
  • MatchOneSource: applying manual merges and unmerges were not executed.
  • MatchOneSource: JSONObject["settings"] not found error resulted from different formats of the matching specification in 3.7 and 3.8. (3.8.2024-01-09)
  • Using filter in data viewer results in an error: “ORA-00933: SQL command not properly ended” (3.8.2023-10-13)
  • Transformation operation window -> Execute button shows an error (3.8.2023-10-05-1510)
  • “Column profile” in data viewer does not open (3.8.2023-10-05-1510)
  • OracleDatabaseSource.mapTypeToStandardType assumed that sourceType.scale cannot be null that led to null pointer exception (3.8.2023-10-03-0901)
  • Clone source did not encrypt properties resulting in an immediate error during cloning (3.8.2023-04-11-1248)

Migration Notes

  • Since version 3.8.2024-11-13, in Steward UI, we disabled the double click event to accept/reject records because many people use double click to copy values and thus accidentally accept/reject records.
  • LoadXMl operation does not support automatic table schema inference: you have to define a mapping for every output table.
  • If you are using metadata encryption, you must do the following before upgrading:
    • create folder “1” (without quotes) in the folder <Infolink Home Directory>/data. You can find <Infolink Home Directory> in the INFOLINK_HOME enviroment variable.
    • copy your encryption configuration file to <Infolink Home Directory>/data/1. You can find the path to your encryption configuration file: go to the InfoLink home page -> click on Setting tab -> scroll to the encryption section -> Config file path.
    • rename the configuration file to encryption.conf if it has a different name.
    • the result of the previous steps must be: your encryption configuration file is stored at <Infolink Home Directory>/data/1/encryption.conf
  • Issues feature, which allowed to identify long running jobs, is retired. To the best of our knowledge, none used this feature. Removal of the feature cannot brake anything: you will not just see “Issues” tab on the homepage.
Last updated on
.NET versionRelease Notes 3.7