Unitfly Community - Recent Posts

Answer to: Fomatting Boolean property in E-mail notification.

Nika Tilic — Fri, 10 Jul 2026 12:43:16 +0000

Hi @karl-lausten,

At the moment, this is not on our roadmap. Supporting configurable boolean representations would require handling a large number of edge cases. For example, the same property may need to be represented differently depending on the module, or even differently within the same rule depending on where it is used.

As a workaround, you can use Property Operations to populate one or more additional properties with the desired values (for example, "X", "Yes", or an empty string) and then use those additional properties when composing the e-mail body. This approach provides the flexibility to format the output exactly as needed for each use case.

Best regards,

Nika

Fomatting Boolean property in E-mail notification.

Karl Lausten — Fri, 10 Jul 2026 11:54:25 +0000

When you insert a boolean property into the e-mail body configuration (html) you may want to configure the way it appears in the message.
For example I am working on message containing a table where a boolean True should appear as "X" in the relevant box, and a Boolean False should appear as a blank (nothing).
Elsewhere in the same message True should appear as "Yes" in the local language, which may be different from the server language.
Is that possible at all, and if yes, how can we configure it?

RE: Excel Reader - Range Input

Nika Tilic — Thu, 09 Jul 2026 14:30:32 +0000

The work item is currently included in our monthly development plan, which means it will most likely be resolved in the next release, expected in August.

The new version will be available for download from our Download center - Extension Kit for M-Files | Unitfly and you can find the release notes on our Release Notes page: Release Notes - Extension Kit for M-Files | Unitfly

I hope this timeline works for you. If you have any further questions, please don't hesitate to reach out.

Best regards,

Nika

RE: Excel Reader - Range Input

Kevin — Wed, 08 Jul 2026 14:50:15 +0000

@nikatilic Sounds good. When do you think this will be updated, how will I be notified, and how will I get the updated version?

Answer to: Excel Reader - Range Input

Nika Tilic — Tue, 07 Jul 2026 13:04:56 +0000

Hi Kevin,

Thank you for sharing the details.

We tested your use case in our environment and identified an unintended behavior. We have logged this as a bug under ID 3154.

Once the fix is released, this ID will be included in our release notes for tracking purposes.

Best regards,

Nika

Answer to: Save copy of sent notification in vault?

Nika Tilic — Tue, 07 Jul 2026 12:36:05 +0000

Hi Karl,

Thank you for the suggestion! We have created a User Story for this feature request under ID 3154. You can track the progress and availability of this enhancement through our release notes in future releases.

Best regards,

Nika

RE: Excel Reader - Range Input

Kevin — Mon, 06 Jul 2026 16:17:44 +0000

@nikatilic We are on version 5.3.1. Please see below:

217

Save copy of sent notification in vault?

Karl Lausten — Thu, 02 Jul 2026 15:02:43 +0000

Some external notifications are important, and we need to save a copy of them as documentation. We could add an internal mail address as BCC and then import those messages to the vault. However, it would be much more elegant to be able to create a new document as a copy of the notification mail including details like recipient, date and time, and of course the content from subject and body directly from the notification module.

I don't see any options to do so right now. Please note it as a suggestion for improvement.

Answer to: Excel Reader - Range Input

Nika Tilic — Tue, 23 Jun 2026 11:20:40 +0000

Hi Kevin,

Thank you for reaching out. Could you please let us know which Extension Kit version you are using? We would like to recreate the described use case and test it in our environment. Based on the information provided, your configuration appears to be correct.

Best regards,

Nika

RE: Excel Reader - Range Input

Kevin — Mon, 22 Jun 2026 15:34:15 +0000

Following up on this question.