Recently active topics

Hello Thinkwise,We are experiencing an issue where a SQL DATE column (subsidiary_calendar.date) is serialized by Indicium as a UTC datetime string ("2025-06-08T00:00:00Z") in the OData response. The Thinkwise Universal GUI running in the Netherlands (CEST = UTC+2) subtracts 2 hours, rendering the date as the previous day.This causes a visible bug in our pickup overview: Monday June 8 disappears from the day window because Sunday's is_work_day = 0 ends up being shown on Monday's slot.We confirmed this via a direct OData call:GET /subsidiary_calendar?$filter=subsidiary_id eq 1186 and date eq 2025-06-08&$select=date,is_work_dayResponse: { "date": "2025-06-08T00:00:00Z", "is_work_day": 0 }The database correctly stores 2025-06-08 with is_work_day = 0 (Sunday). The serialization introduces the offset.We know that $apply=Compute(Date(date) as date) returns a pure date string as a workaround, but this cannot be applied at SF model level since our views and subjects are driven by the model.

Hi all,We are investigating the use of external signature pads together with the standard Thinkwise signature control (UI/domain signature field).Our use-case: Retail/store environment Browser-based usage User clicks the signature field in Thinkwise Customer signs on an external signature pad Signature should be captured by the existing Thinkwise signature control We are specifically trying to avoid: Heavy custom integrations Browser plugins/extensions where possible Custom Thinkwise components Questions: Has anyone successfully tested external signature pads with the standard Thinkwise signature control? Which devices/models worked well? Did the device work as standard HID/mouse/stylus input, or did it require SDK/software integration? Thanks!

Hi,I’m in the process of testing our Windows GUI apps in the Universal GUI and I noticed that messages seem to display differently: The text is done thru the translation: How can I fix this?

Is it possible to set the default Filter Condition of a column to the “IN” condition?I am working on 2025.3 and do not see this option. Next to this, the docs do not provide any information about this feature as well. If this is not possible, I would advise having this implemented asap. 

Hi everyone!We’ve released the following important platform improvements this week: SF 2026.120260611 - Fix context output for unit test enrichment When generating a unit test with AI for a context, the output was not processed correctly. This issue has been fixed.  IAM 2026.1.1520260612 - Switch the domain used for default value of process variable With the implementation of the Multi-RDBMS feature, the domain used by the Default value field in Process variable was changed. This caused the column to only hold a maximum of 200 characters, which had the potential of supplying a stripped value to its process flow. This has been resolved. If you are already on platform version 2026.1.15, and have any process variables that have a default value that exceeds 200 characters, you will need to synchronize to IAM again after installing this hotfix. All upgrades to or past 2026.1.15 will be unaffected.

Struggling a lot to get a Web connector call to work, even though it gave a 201 response status code.We have a Checkbox with a BIT data type in use and have this value used in the body of a call. In this example to set the two factor authentication type to “Password and TOTP token” and if one want to enable/disable “Allow fallback to em-mail”.It turns out that the boolean value is starting with a capital letter (True):{ "two_factor_authentication_type": 3, "allow_fallback_to_email": True }After a test with setting the body value manually and not through a flow parameter it does actually change the requested data when it is lower case (true):{ "two_factor_authentication_type": 3, "allow_fallback_to_email": true }What do I need to do to have the parameter not be starting with a capital letter?

Hello,I have a quick question about the recent release notes for the 2026.1.13 platform version.The new parameter in translations feature seems very useful, and we have use cases where this would be useful in grids. However, the release notes only mention tasks, reports, and forms. Is this feature also supported for grid column names? Or is this something planned for the future?Thanks in advance! 

Hi all,I'm not sure whether this is a new idea, but I haven't found any related community posts yet.I have a client using UGUI (2025.3) for order entry. A significant amount of their order entry is done in succession using the + button. Users create a row, then click + again to add the next row rather than clicking Save between entries. The challenge is that users still want to see the newly created row immediately after adding it. Currently, the grid only selects and scrolls to the new row after a Save action, not when a new row is created using +. As a result, newly added rows at the bottom of the grid may not be visible until their final save.From the users' perspective, this slows down the order entry process because they cannot quickly verify that each line was added successfully before moving on to the next one. I imagine there are other scenarios where users repeatedly use the + button without saving between entries, so this behavior may not be unique to this client.Would it mak

Hi everyone,We are using Auto Refresh with Change Detection on a view in our Thinkwise application.Our Change Detection query is based on the standard trace columns, for example:where update_date_time > @last_refresh_utcDuring testing we noticed that the view was refreshing every refresh interval, even when there were no actual changes.After some investigation we found the following: @last_refresh_utc is supplied in UTC by the GUI/Application Tier. Our insert_date_time and update_date_time trace columns contain local SQL Server time. On our environment the difference is currently +2 hours (CEST). For example:select sysutcdatetime() as utc_time, getdate() as local_time, max(update_date_time) as latest_updatefrom stage_sales_order;Result:utc_time = 2026-06-03 13:41local_time = 2026-06-03 15:43latest_update = 2026-06-03 15:43Because of this, Change Detection keeps finding records where:update_date_time > @last_refresh_utceven though no new changes have occurred.

I have a Resource Scheduler in the Windows GUI. Double-clicking an appointment already runs a table task that edits the block (change workshift type and/or time), which works well.I now want a second, separate action on an individual appointment: opening a document that shows the appointment configuration specific to that appointment (keyed on task_id).What I've found so far:Right-click / context menu doesn't seem to surface table tasks on appointment blocks. (This would be the preferred option) The scheduler only supports a fixed set of trigger actions (refresh after execute, double-click appointment, resize, drop, delete, double-click time cell, drop external row), and double-click is already in use for the edit.My current plan is to repoint the double-click at a process flow that starts with a chooser step and branches to either the edit task or an "open appointment configuration" task, both receiving the auto-filled task_id. The downside is that editing then takes an extra click.Qu