Skip to main content

linqi update as of 20.01.2024

· 2 min read

⭐️ Features

  • Table control: There was a recurring need to enter any number of table rows in forms. A new table control has been implemented for this purpose. You can now use this control to enter order items, times and much more, for example. In addition to entering new table rows, you can also use this control to select from existing elements such as a customer database.

  • Connection points: So that you can design processes even more clearly, it is now possible to insert breakpoints for connections in the process designer. All you have to do is click on an existing connection and move the connection point using drag'n'drop. This allows you to route connections around nodes, for example.

  • Copy elements: We are always interested in speeding up work with linqi and making it even more efficient. For this reason, we have implemented a function that allows you to copy control elements in forms, dashboards and document templates. For example, you can copy a process table and simply adjust the filters to display rejected processes next to a table with approved processes.

  • Word file generation: As documents are essential for a wide range of processes, we have expanded the document generation functions. You can now use the new Generate Word Export action to generate Word files as well as PDF files. These Word files are generated as usual on the basis of the existing document templates.

  • Vertical pools in BPMN: It is now possible to customize the alignment of pools within the BPMN Designer.

  • Exchange Connector: Assign categories: A function has been added to the Exchange Connector that allows you to add categories to emails and appointments. For example, you can mark emails that have been processed by linqi accordingly.

  • Throttling in HTTP request: The HTTP request function has been extended to automatically react to throttling and resend the request with a corresponding delay.

🐞 Bug fixes

  • Input of invalid numerical values: Via Capslock it was possible in certain situations to enter invalid numerical values in number fields.

  • SharePoint event: In very rare cases it could happen that SharePoint event processes were not stared correctly.