https://community.thinkwisesoftware.com Stay up to date on the latest official Thinkwise news and participate in discussions regarding Thinkwise services & products https://community.thinkwisesoftware.com/ideas/branch-switching-qol-show-branch-description-7052 With MCP development in the SF, I am working on several user-stories/branches at the same time. So I am switching a lot between them.To make this easier/faster, I would like a small change to the ‘Switch branch’ task so that the branch field has a lookup showing the tbranch] - ]branch description]. This way I know which branch includes what from just the dropdown (without having to open the popup). Also with the create branch task, it would be nice to have the branch description as input field. Mon, 19 Oct 2026 15:30:37 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/set-focus-not-to-combined-filter-when-subject-is-opened-from-a-process-flow-7053 Is there a method the focus does not ends up in the combined filter, especially when we are opening a subject from a proces flow. We apply a filter and we want the focus to be set to the filtered line.Now we always need to do a user action to select the line again. In this case we activate a tree structure in the correct node. The selected node is highlighted but the focus is set to the combined filter, so we always need to select the line again before we’re able continue to work.  Questions & Conversations Mon, 19 Oct 2026 14:31:57 +0200 https://community.thinkwisesoftware.com/ideas/double-click-in-scheduler-7051 In  the WIN GUI to trigger a task, for example to add an activity, you had to double click in an empty cell. From some reason in the Universal Schedular the task is already triggered with a single click. Can we change this somehow to a double click.Now everry time a task is added, the task is triggered twice because in the brains of our users the double click triggers this action, resulting in 2 task windows opening up.Really painful for our users.In addition to this, the double click is needed to start the task if you double click on an existing task.Is not logical that for editing a task you need to double click and for adding a task you need to single click. This is for users pretty confusing.. Mon, 19 Oct 2026 10:16:36 +0200 https://community.thinkwisesoftware.com/ideas/workspace-listener-for-linux-macos-6568 At the moment, there are no plans to create a Workspace Listener for Linux (source).It would be great to not be limited to Windows and have support for automatic opening of your IDE on Linux. Context:Automatic opening of local code files  For additional convenience, Windows users can install the new Thinkwise Workspace Listener. This tool automatically opens the selected code file in your preferred IDE when clicking on the pencil icon. The Workspace Listener is optional. Without it, you can still edit and synchronize code locally (provided you use a browser that supports the Filesystem API), but you will need to manually open the files in your IDE.    Browsers with File System Access API  Chrome & Edge  Browsers without File System Access API  Safari & Firefox  Windows   Automatic syncs   Automatic opening (using the Workspace Listener)   No automatic sync   No automatic opening    Local code editing requires manual copy/paste  MacOS   Automatic sync  No automatic opening  Linux   Automatic sync  No automatic opening  Sat, 17 Oct 2026 18:05:12 +0200 https://community.thinkwisesoftware.com/product-updates/platform-improvements-for-week-42-2026-7050 Hi everyone!We’ve released the following platform improvement this week: SF 2026.320261013 - SF generated manifest path property for Install During the implementation of the V4 support into the manifest generation of the Software Factory, the Install type was not provided a path towards the Install folder. This has been fixed. Fri, 16 Oct 2026 15:21:10 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/issues-connecting-to-mcp-with-chatgpt-on-version-2026-3-7048 Hello, guys. How are you? I need your help with the configuration of the MCP on Thinkwise.I configured the client app, the applications and user to have delegated access. I also configured chatGPT (when I set the connection it finds everything automatically). The thing is: ChatGPT can connect to the applications with the correct scopes, but it says that there are no tools available for him: "I can see your plugin selection, but its callable tools were not exposed.That doesn’t prove the MCP server has no tools—only that I cannot currently list or invoke them. I also can’t determine the cause from the information available."On version 2026.2.14 it was working just fine.My indicium environment runs on podman and is behind a reverse proxy (NGINX).This is my client application configuration:Client Application FormsClient Application Access Delegation  Questions & Conversations Fri, 16 Oct 2026 08:24:24 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/ai-translations-for-crystal-reports-7032 Inspired by the Thinkwise Summit, I was wondering whether anyone has experience with using AI for the bulk translation of Crystal Reports.What would be a good approach or workflow for:Extracting translatable content from Crystal Report (.rpt) files Translating that content using AI Applying the translations back to the reportsTaking the idea one step further, has anyone explored using AI to generate a DevExpress report based on an existing Crystal Report? Questions & Conversations Wed, 14 Oct 2026 16:49:47 +0200 https://community.thinkwisesoftware.com/ideas/make-multiple-search-code-screens-independent-like-all-other-screens-7014 Current behaviorWhen multiple instances of the same screen are open in the Software Factory, they work independently. Search code is the only exception, because its instances share state:Open Search code and search for term X. Open a second Search code screen and search for term Y. Return to the first screen and click Search again.The first screen now shows the results for Y, and its search term has changed to Y.Why this is a problemUsers learn from the rest of the platform that each screen instance keeps its own context. Search code breaks that expectation without any visual indication. A user who opens a second Search code screen to compare results, or to keep an earlier search at hand, silently loses the first one and may act on results they did not ask for. Even if this is intended, from a user's perspective it is indistinguishable from a defect.ProposalMake behavior consistent (orthogonal) across the platform:Preferred: each Search code instance keeps its own state (search term, filters, results), just like other screens. Alternative: if shared state is a deliberate design choice, make it explicit. For example, reuse the existing Search code screen instead of opening a new instance, or clearly indicate that the instances are linked.What matters most is predictability. Either all screen instances are independent or none are, with no silent exception for a single screen.ContextI originally reported this as a bug. It was closed as intended behavior, with the suggestion to submit it as an idea, which is why I am posting it here. Wed, 14 Oct 2026 15:17:18 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/custom-component-setup-for-running-application-7000 We have two different applications in one iam environment having two different urls for the custom component having two different url’s not in the same proxy.Is it possible to fill in a expression (sql) in the location (subject) setting for translation the url when the application is running? The solution of two different branches is not a nice one for maintenance. What could be a good solution?   Questions & Conversations Wed, 14 Oct 2026 13:28:39 +0200 https://community.thinkwisesoftware.com/product-updates/extra-release-universal-gui-2026-3-10-1-7047 Hi everyone!This is an additional release for the Universal GUI with the following changes: Fixed uploading a file or image in a default editable screen sometimes not working correctly. We have disabled the “All rows” option when executing e.g. a Task if the grid was filtered on an interval, such as a date grouping by year, as this action could affect rows outside the filter. Fixed action bar search wrongly keeping getting focus when switching component tabpages. When a user selected another row, the marker's pop-up on the map no longer opened automatically. This has been fixed. Fixed the Maps component turning partially grey when switching component tabpages and back, open documents and back and when moving the splitter. The 2026.3.10.1 release is now available for download in TCP. Wed, 14 Oct 2026 11:35:58 +0200 https://community.thinkwisesoftware.com/ideas/double-click-grid-to-edit-6158 I would like the option in the SF to set a subject to grid edit mode if a users double clicks on a row (optional: clicking on a specific column like with tasks). I know this can be done already with creating a double click task that uses a proces flow to go to grid edit mode. But it gets quite cumbersome when you want to implement this at almost all subjects that use edit in grid in an application, specially in combination with roles. Tue, 13 Oct 2026 14:19:12 +0200 https://community.thinkwisesoftware.com/ideas/branch-validations-7006 Create a filter under creation, validations to show only validations that are new in the branch.For example main branch has still 30 open validations, feature branch has 50 open validations. When the filter is active only show the 20 validations. Tue, 13 Oct 2026 12:48:55 +0200 https://community.thinkwisesoftware.com/ideas/way-to-hide-all-validation-messages-for-a-branch-at-once-5204 I have created a new branch. Consequently, I inherited 14,060 validation messages from the original branch. Among this vast number, any new validation messages introduced by me are obviously not noticeable. This compromises the quality of the product I am developing.I believe the original branch should be "clean," but in practice, this often proves difficult to achieve. Until that ideal is met, I think it is a good practice to hide all existing validation messages for the branch immediately after creating it so that I can start with a "clean slate."This can be done from SF, but it is a laborious task because:Some validation messages produce an error when trying to hide them, which interrupts the task. Not all validation messages are displayed, as a summary item appears for more than 25 of the same type, requiring manual expansion of each. It involves handling a large number of validation messages.There should be a way to hide all validation messages for the branch at once. Tue, 13 Oct 2026 12:48:55 +0200 https://community.thinkwisesoftware.com/ideas/make-validations-part-of-the-merging-process-3883 Hello, we have recently started using the latest version of the SF and are extremely happy with the ease of branching and merging and are trying to ensure stability with unit tests and smoke tests.Currently, a branch can be merged into the trunk without having to do any validation. We would like to make running validations part of the merge process, as is currently done in the upgrade process. At the moment this is already possible of course, but it would be more convenient to see the merge sessions on one screen.Personally, we would at least like to see if there are unfinished/failed unit tests, if there are unfinished/failed smoke tests and if there are control procedures that are still under development/in review. Tue, 13 Oct 2026 11:15:53 +0200 https://community.thinkwisesoftware.com/ideas/merging-branches-7023 When creating a merge session a option to validate if all functionality templates are reviewed and not on status development before the merge will be executed, all kind of checks that can be done before executing the merge session (a option to validate) would be nice. Tue, 13 Oct 2026 11:15:52 +0200 https://community.thinkwisesoftware.com/ideas/multi-line-support-for-label-control-6832 We miss the possibility of making Label Control columns multiline.A typical scenario, is a dynamic questionnaire, like belowWe worked around this by means of a read only Multi line text control, which is not ideal   Tue, 13 Oct 2026 11:14:35 +0200 https://community.thinkwisesoftware.com/ideas/paste-multiple-options-in-a-search-bar-or-filter-7013 Our users need to search for multiple articles or other options in their work, to change statusses of those, or edit other data combined with the selection, therefor they paste a total selection with multiple search terms seperated by a character.They want to search / filter like this: 2508*|2517*|etc… - it can also be with a comma to seperate the keywords, or other regex variants.But now they need to filter for them one by one by one. Which takes a really long time.Can we add the possibility to search or filter on multiple option by filling in the options in one long query or string? Tue, 13 Oct 2026 11:12:48 +0200 https://community.thinkwisesoftware.com/ideas/bring-back-quicksearch-6671 In previous iterations of the Thinkwise GUI you could perform an action called quicksearch. How it worked:Bring focus to a specific column (in the grid) Type what you want to search  First match of your search gets selected/highlighted. Can we please have this back?Why Quicksearch is valuable (and missed)1. Strong productivity gain for keyboard usersQuicksearch enabled fast, uninterrupted workflows:No mouse interaction requiredNo modal dialogs or filter configurationImmediate feedback while typingFor users who work with data grids all day, this shaved seconds off every lookup — which adds up quickly.2. Ideal for exploratory and ad‑hoc searchingQuicksearch was perfect when:You don’t know the exact valueYou just want to jump to something that looks rightYou don’t want to define a full filter for a one‑off checkCurrent alternatives (filters, column search fields) feel heavier for this use case.3. Lower cognitive load than filteringQuicksearch required almost no mental overhead:Focus columnTypeFirst match selectedCompared to:Opening filtersChoosing operatorsApplying / clearing filtersThis made it especially useful during conversations with users or while debugging data.4. Excellent for large datasetsIn grids with many rows:Scrolling is inefficientSorting doesn’t always helpFilters can be overkillQuicksearch acted as a “jump to value” mechanism, not a data‑reduction mechanism — a subtly different but very useful interaction.5. Consistency with legacy behavior & muscle memoryMany long‑time Thinkwise users built muscle memory around this feature.Its removal:Breaks established workflowsIncreases friction when moving to Universal UIMakes Universal UI feel like a regression in this specific area, despite its overall improvements6. Complementary, not a replacement, to filteringQuicksearch didn’t replace filters — it complemented them:Filters = structured, intentional selectionQuicksearch = fast navigation and orientationBoth serve different user intents and can coexist. Tue, 13 Oct 2026 08:42:10 +0200 https://community.thinkwisesoftware.com/ideas/native-tag-functionality-7046 We often receive request from users to filter and organize data from different perspectives and dimensions. as responsibilities vary between users. For example, one user may be responsible for purchasing, while another focuses on planning.In addition, we are seeing a growing demand for different types of classifications, both among users and across different business entities. To avoid having to create a dedicated column for every new classification, we would like to provide users with more flexibility with the use of tags. We have noticed that this functionality is available in most modern web applications but is currently not supported in Thinkwise. While it is possible to display tags using an HTML column combined with custom CSS, extending this with functional behavior is not user-friendly. In such a setup, multiple tags (text) are stored and displayed within a single column, meaning that filtering is currently only possible using LIKE operators. This is not ideal from a performance perspective, especially when working with large master data tables. It would be valuable if Thinkwise offered native support for working with tags. This could potentially be achieved through a new domain or control type, allowing tag elements to be created and managed dynamically within the application. In the ideal scenario, users would be able to:Select one or more tags when filtering data. Create new tags directly from a grid or form. Click on tags to instantly apply a filter. Sort and group data based on tags. Manage tags dynamically without requiring database schema changes or additional columns.This functionality would improve usability, flexibility, and scalability, while reducing the need for customizations and additional database columns whenever new classification requirements arise. Example of the current solution using HTML and custom CSS:  Mon, 12 Oct 2026 15:05:43 +0200 https://community.thinkwisesoftware.com/ideas/multi-value-lookup-tag-box-3723 Please add a more simple way for end users to assign more than 1 value from a source table to a target table.Like this:It will make screens less more complicated for end users and will increase the adoption of new applications.Must not be missing in a modern application!   Mon, 12 Oct 2026 15:05:43 +0200 https://community.thinkwisesoftware.com/ideas/use-prefilters-as-badge-code-7003 In most cases that we use badges, the badge is the number of lines on the screen based on certain active prefilters. If something changes in the definition in one of those prefilters, the developer has to remember to check the badge code and make the equivalent change there.To reduce this maintenance, I would like the option to model a badge as a combination of prefilters on the table/view and that the SF generates the badge code from this.Of course it should still be possible to write own badge code for exemptions. Mon, 12 Oct 2026 10:33:10 +0200 https://community.thinkwisesoftware.com/ideas/show-that-a-pre-filter-is-active-6960 We have pre-filters behind the three dots in a menu.Users are sometimes not aware that pre-filters are active as you cannot see this directly on screen.Is it possible to add some kind of notification or icon to show pre-filters are active?  Mon, 12 Oct 2026 10:31:40 +0200 https://community.thinkwisesoftware.com/ideas/option-to-rename-the-form-tab-6959 We would like to be able to use a different label for the form tab in different menu's.For example: we would like to rename the form for purchase orders to Purchase order and the form for sales orders to Sales order.I have been told this is only possible by using a different screen type for each screen. We would like the option to use the same screen type, but a different label.  Mon, 12 Oct 2026 10:15:45 +0200 https://community.thinkwisesoftware.com/ideas/store-sas-token-expiration-date-in-application-file-storage-settings-6978 In the 'File storage locations' tab of Application / General settings, it would be valuable to have an additional column that stores and displays the expiration date of the configured Azure SAS token.The expiration date can be derived directly from the SAS token itself (from the se parameter). Because of this, the field could be populated automatically whenever the SAS token is saved.Additional optionsHighlighting tokens that are nearing expiration Generating notifications for application administrators before expiration occurs Add badge to the tab  Mon, 12 Oct 2026 10:14:52 +0200 https://community.thinkwisesoftware.com/ideas/have-domain-control-copy-to-clipboard-form-support-multiline-visualisation-6943 The function of the domain control “Copy to clipboard (form)” is fine and does support multiline data. It is only unfortunate it has no ability to make a multiline visual in the GUI.Probably it would require a different component to also have a scrollbar available for the longer texts, but it would help a user to be able to see the text and decide to copy it with the control. Copy to clipboard (form) control Multiline control Mon, 12 Oct 2026 10:14:35 +0200 https://community.thinkwisesoftware.com/ideas/validation-global-shortcut-conflicts-7027 Recently, a lot more shortcuts have been added to Universal. Such as ALT + R to Refresh the model, ALT + M to search the Menu and CTRL + K to activate search on a Subject. This list seems to keep on expanding, which is great.However, some of these shortcuts can conflict with existing tasks, without developers being warned about this.Why?This would improve the overall quality of the application (since there are no overlapping shortcuts, or they are intentional). For the conflict on the ‘Application’ subject in the IAM on the shortcut CTRL + K; both Copy application and Search on the subject, TCP Ticket 16075I was created.How?Create a validation on the model, that checks conflicts with global shortcuts.Optionally give a warning message to the developer that this shortcut is conflicting, when setting the shortcut. Mon, 12 Oct 2026 10:13:08 +0200 https://community.thinkwisesoftware.com/ideas/making-the-deployment-center-more-advanced-6998 Modified by moderator:This idea should be changed to making the Deployment center more advanced so you can use one Deployment center installation to maintain your entire Thinkwise platform:The deployment center can check/download updates of all Thinkwise products itself (including the deployment center itself). You can register all your environments (multiple dev/tst/acc/prod) in it. It gives an overview of all your environments x installed TW products in which it shows available updates/hotfixes that are not installed yet (with a button to initiate the process). For hotfixes could also be considered to let you install them from within SF/IAM hotfix screen.  Old idea:Please make it possible to download Thinkwise products without Deployment center and Workspace listener in TCP. Currently TCP always adds the Deployment center and Workspace listener to Thinkwise products downloads, even if you are just downloading hotfixes. This make the download unnecessary big/slow (180mb for 2kb hotfixes). Mon, 12 Oct 2026 10:11:52 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/what-happens-to-exclusions-during-a-merge-6999 I have some changes in a DEVELOPMENT branch that I want to merge to the RELEASE branch. After creating the merge I exclude a particular line from being merged. What seems to happen after the merge is completed is that the excluded part is overwritten by the code from the RELEASE branch, so my original code is gone. Is this intentional? It looks like the merge is bi-directional. Questions & Conversations Mon, 12 Oct 2026 10:01:21 +0200 https://community.thinkwisesoftware.com/product-updates/platform-improvements-for-week-41-2026-7045 Hi everyone!We’ve released the following platform improvement this week: SF & IAM 2026.320261007 - Disable relative file storage for db file storage Files or images uploaded to a newly configured database file storage were emptied right after a new value was provided. Indicium then showed the following error: System.Collections.Generic.KeyNotFoundException: The given key '...' was not present in the dictionary. This has been fixed with this hotfix. Fri, 09 Oct 2026 15:48:49 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/what-happend-with-edit-in-grid-6878 The Edit in Grid mode, as we knew it from previous versions, no longer seems to be available. Is there any plan to bring this functionality back?We would very much like to see it return, allowing end users to enable Edit in Grid for specific datasets. The ability to navigate from record to record and modify field values directly within the grid, without having to repeatedly click Save and Edit for each change, was very powerful.This functionality is also missed in the Software Factory, where it provided a much more efficient editing experience.Could you share whether this feature is on the roadmap? Questions & Conversations Fri, 09 Oct 2026 09:47:52 +0200 https://community.thinkwisesoftware.com/news-blogs-21/one-week-to-go-join-us-at-thinkwise-summit-2026-7011 Next Wednesday, 30 September, hundreds of customers, partners and IT professionals will come together at the Thinkwise Summit.Here’s some of what you can expect:See MCP in action Discover how the Model Context Protocol (MCP) connects AI with the Thinkwise Platform. Dive deeper during the sessions and see MCP in action in the Software Factory during live demos in the foyer. Explore what’s next for the Thinkwise Platform Get a closer look at the latest developments around AI, MCP, MQTT and the AI-Upcycler – and what they could mean for your applications and development process. Learn from other Thinkwise users Hear how organizations including Syngenta Flowers, Antea Group, Huuskes and the European Association of Urology use the Thinkwise Platform to develop their business-critical software. Meet the people behind the platform Have a question, want to discuss a specific topic or simply curious about what’s coming next? Use the Summit app to schedule a meeting with a Thinkwise specialist and meet them in the Networking Café.And don’t worry: it’s not all sessions, software and AI. There’s plenty of time to catch up with other Community members, grab a drink and have some fun in between. Not registered yet? There’s still time to join us on 30 September at NBC Nieuwegein. View the full program and register here News & Blogs Fri, 09 Oct 2026 09:42:08 +0200 https://community.thinkwisesoftware.com/news-blogs-21/thinkwise-summit-2026-what-to-expect-on-30-september-6950 The Thinkwise Summit is getting closer. On 30 September, we’ll bring the Thinkwise community together at NBC in Nieuwegein. And this time, we can tell you more about what to expect.The programme is now live, with customer stories, platform developments and live demos across the business and tech tracks.A few highlights:See in live demos what AI can already do within the Software Factory. Huuskes, Antea Group and EAU share how they develop their business-critical applications around their own processes. Discover what MCP means for developing and using Thinkwise applications. Dive into topics including MQTT, AI and digital sovereignty.And of course, the Summit is also a chance to meet other Thinkwise customers, exchange experiences and catch up with the Thinkwise team.Curious about the full programme?View the programme and register for Thinkwise Summit 2026 News & Blogs Fri, 09 Oct 2026 09:42:00 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/upgrading-iam-from-2026-2-14-to-2026-3-7042 Hi all,In an shadow environment we are trying to upgrade from IAM from 2026.2.14 to 2026.3 and we get the following error:Mind you, we are using the SQL Server 2022. Is there any workaround? Or do I need to submit a ticket? Questions & Conversations Fri, 09 Oct 2026 09:18:10 +0200 https://community.thinkwisesoftware.com/news-blogs-21/try-mcp-on-our-insights-application-7044 A project manager wants to know which projects are running over budget. A colleague needs to log last week's hours across four projects. With MCP (Model Context Protocol), both just ask: one gets an answer straight from the data, the other gets the hours booked for them.You've read plenty about MCP by now. Time to try it on a real application. See it in action Try it yourself!Our Insights demo application is now available through MCP. If you have a Thinkwise Community account, and you probably do if you are reading this, you can connect to it right away with ChatGPT or Claude. A free Claude account works too. Note: This is a demo application, so the data isn't always as realistic as in your own. You can change, insert or delete anything, but remember that everyone shares the same data. The database resets every night. How to connect In Claude or ChatGPT, add a Custom connector   Enter a name, for example Thinkwise Insights, and this URL: https://insights.thinkwise.app/indicium/mcp     Under the OAuth settings, select ‘Use your own OAuth client’ and enter insights_mcp as the client ID. Leave the client secret empty. If it requires a value, enter insights_mcp again.   Click Connect and sign in with your Community username and password.No option to add a custom connector? Business accounts often restrict this. Ask your infrastructure team for permission, or have them add the connector for you.  Prompts to get you startedNot sure what to ask? Try one of these (or ask your AI assistant for inspiration):AskWhich projects are currently running, and when are they planned to finish? Which unread emails have a high priority? Show me all high-priority tasks that are not completed yet. Which employees have a birthday this month?AnalyzeWhich active subprojects will run out of budgeted hours before their planned end date at the current pace? Compare hours booked per activity over the last year. Where does most of the time go? Which employees spread their time across the most projects? How long does it take on average for an invoice to go from concept to paid?VisualizeBuild a small dashboard with the invoice pipeline: how many invoices and how much money sits in concept, approved, sent and paid. Put our customers on a map, sized by the number of hours we worked for them. Create a timeline of all active subprojects with their planned start and end dates, and highlight the ones running late. Show the hours booked per month over the last two years as a line chart. Are there seasonal patterns?ActBook 3 hours of Analysis and 2 hours of Meeting on Chema centro comercial for yesterday. Complete the hour registration for this week. Mark all low-priority emails from this week as read.CombineFind all hours that are booked but not invoiced yet, group them per customer, and generate the invoices for the three largest. Find the subproject that is furthest over budget, explain where the extra hours went, and draft an email to the project manager. Which employee spent the most time on projects that went over budget? Show it in a chart and suggest what we could learn from it. Tip: start with a broad question and drill down from there. Your AI assistant remembers the context of the conversation, so a follow-up like "and why is that one over budget?" works fine. From demo to your own applicationNow picture this on your own application. Think of the questions that land in your inbox, or the ones your users never ask because the answer is spread across three screens. Try similar ones on the Insights demo and see how far you get.Ready to try it on your own data? MCP is available from Thinkwise Platform 2026.3 and free to use in your Develop and Test environments. Here's how to set it up:What is the first question your users would ask? Share it in the comments below. We're curious to see what you come up with. News & Blogs Fri, 09 Oct 2026 08:11:45 +0200 https://community.thinkwisesoftware.com/ideas/feedback-regarding-the-new-ticket-layout-in-tcp-6791 Good improvement that tickets which require user action are only counted for the badge now and are default sorted on top.   Please add the ‘Product’ field (Universal/SF/IAM/etc.) back to the grid, this helps with finding an issue when you don’t remember the title.   After executing the ‘Annulering beoordelen’ task, an issue stays visible with status ‘Opgelost’ while the prefilter ‘Gesloten tickets verbergen’ is active. For example ticket 14568i.   ‘Activiteit’ and ‘Commentaar’ are a bit confusing/redundant: In ‘Activiteit’ I see the whole conversation, but the Add button doesn’t work (all fields are read-only/hidden). My expectation was that I could add a ‘Commentaar’ line here. In ‘Commentaar’ I only see a small part of the conversation. For example messages that are written when the issues switches status between 'In behandeling' and 'Reactie gewenst' are missing.   The default screentype could be improved if it shows the form below/next to the grid. So you could see the ‘Toelichting’ when browsing through the issues without extra clicking. I am currently using the Master-detail screentype myself. If this is changed, a bit smaller grid height would be appreciated too.   When I use the ‘Kopieren’ button to create a new ticket, I cannot edit the ‘Toelichting’. Thu, 08 Oct 2026 16:03:26 +0200 https://community.thinkwisesoftware.com/ideas/change-prefilters-as-starting-point-in-process-flows-7041 I wish to have the “On Change Prefilter” event available as starting point in process flows. Would that be possible?Based on the activated prefilter, other prefilters can than be automatically set on or off. By doing this, invalid filter combinations can be eliminated, that improves usability, and guides users toward valid selections only.We do of course make use of prefilter groups, but this is not always possible.  Thu, 08 Oct 2026 15:40:25 +0200 https://community.thinkwisesoftware.com/news-blogs-21/rolling-out-mcp-for-your-thinkwise-application-7043 A sales employee opens an email from a customer who wants 40 units of a product, delivered next Friday. Instead of retyping the order, she hands the email to her AI assistant. The assistant reads it, finds the customer and the items in your Thinkwise application, and creates a draft sales order for her to review. This is what MCP (Model Context Protocol) makes possible: users talk to their business application in plain language, and agents act on their behalf.AI is very good at turning unstructured input into structured data, and that goes well beyond order entry. With an MCP connection to your application, users can:Ask questions about their data, such as "Which customers have open invoices older than 60 days?" Prepare for a meeting by asking for a summary of a customer's recent orders, open quotes and service tickets. Spot problems early, for example "Which production orders are at risk of missing their delivery date this week?" Register work from a short note, such as turning "Spent 3 hours at Jansen BV fixing the pump" into a time entry.Getting there takes more than switching on an MCP server. This blog gives developers and IT leads practical tips on choosing a client, securing access, improving answer quality and rolling out MCP in your organization.MCP is officially available from Thinkwise Platform 2026.3.For more information about how to get started, please read this blog:Also keep in mind that Claude.ai and ChatGPT web desktop connect to your MCP server from the cloud, not from your users' laptops. Your Indicium's /mcp endpoint must therefore be reachable over HTTPS from the internet. On Thinkwise Cloud, that is already the case. Running Indicium on premises? Involve your network team early, and use Claude Code on your internal Indicium in the meantime.Use your application on any device, including your phone Choosing a clientThe AI client you pick determines how your users connect and how much work it is to manage. We recommend a client that supports OAuth with a predefined OAuth client ID. That way, every user signs in with their own account, and you decide which client application may connect. Client capabilities change quickly, so check the current documentation of your AI platform. At the time of writing, we have confirmed both Claude and ChatGPT support OAuth and can connect to the Thinkwise platform. We only got Microsoft Copilot to work with Personal Access Tokens.Whichever client you choose, set up the connector at the organization level wherever possible. As the IT expert, you configure the connector once. Users only need to enable the connector and sign in with their own account.Ready to connect your first client? The Getting started with MCP blog on the Thinkwise Community walks you through it step by step. Secure access and trace every changeThe official MCP connector of the Thinkwise Platform is enterprise grade and designed with security in mind. Apply the recommendations below for optimal configuration:Avoid personal access tokens for organization-wide connectorsMost AI platforms also support authorizing an MCP server with a personal access token (PAT). We do not recommend this for MCP servers that you deploy to your entire organization. The PAT handles authorization. Everyone using the MCP server gets the same rights as the user who created the token. Your trace columns and logging will not work as expected either, because every action is logged under that user's name. If you have to use a PAT, only grant read rights on this MCP server.Autonomous AI agents and bots are a different case. An agent that runs without a user, such as a process that handles incoming emails overnight, has no user to sign in as. For such an agent, a PAT for a dedicated service account is a valid choice. Give that account its own user name and only the rights the agent needs, so its changes stay traceable and separate from your users' work.Data accessMCP does not bypass your authorization model. It inherits it. The AI can only read and change what the signed-in user's roles allow, including prefilters. Review your roles with that in mind before you roll out MCP: data a user can technically reach but never opens in the user interface is now one question away.You can narrow this down further with access delegation roles. The AI only receives the roles you explicitly make available for delegation in IAM, and only for users and applications that allow access delegation. That gives you a separate, smaller set of rights for the AI next to the rights a user has in the regular user interface. The access delegation roles documentation explains how to set this up.Also check the data-processing terms of your AI platform. Make sure your business data is not used for model training and that data residency meets your requirements.Data manipulationLetting AI insert, update or delete data is powerful, but mistakes are harder to spot than in a regular screen. A misunderstood instruction can update the wrong records or delete more than intended. Decide per role which changes you want to allow through MCP. A safe starting point is read, create and task rights. Add update and delete rights only once you trust the results. Tasks are a good fit for data changes, because your business logic validates the input before anything is written.Your statuses are a natural place to draw the line between AI and human work. Most processes already move a record through steps such as Concept, Open, Waiting for approval and Approved. Decide for each step whether the AI may take it or whether a person has to. An AI can create a concept order from an email, for example, but only a manager can approve it. Then enforce that choice in your model: include the task that creates the order in the role you delegate to MCP, and leave the approval task out. Also mention in the tooltip of the status column which statuses the AI may set. That way, the AI can tell the user who needs to take the next step. The AI does the typing, and a human stays in control where it matters.If you do allow direct updates and deletes, add a safety net. History tables let you see and restore previous values, and handlers or dynamic model code can replace hard deletes with soft deletes.TraceabilityTo keep track of who changed your data, extend your logging so you can see whether a row was inserted or updated by the user directly, or by an AI on behalf of that user.Since Thinkwise Platform 2026.2.13, Indicium sets the session variable tsf_is_delegated_request. Its value is 1 when a request is authenticated via a client application or PAT that is scoped using access delegation roles, and 0 for any other method, including a client application configured with Full access. On SQL Server, you read it with SESSION_CONTEXT, for example in the default or trigger that fills your trace columns:set @is_delegated = coalesce(cast(session_context(N'tsf_is_delegated_request') as bit), 0);We have applied this ourselves in the Software Factory. Since Thinkwise Platform 2026.3, the Software Factory trace fields use this variable to show which changes were made through delegated access. Your own application does not do this automatically, so you’ll need to update your trace fields logic. We will be updating the Thinkstore trace fields solution in the near future to incorporate this session variable as well.Update your trace fields to show if it was changed by AI Improving answer qualityThink of the AI as a smart new colleague on their first day. They are quick and eager to help, but they know nothing about your company yet. Everything they learn comes from what you show them. So the better you prepare them, the better their answers. Let's build that up one layer at a time.Optimize your application modelStart with the foundation. When the AI connects through MCP, it sees your subjects, columns and tasks with the names, translations and tooltips you defined in the Software Factory. Because the AI receives the model’s  translations and tooltips in the user's language, your users can also work with your application through AI in their preferred language. If a user asks a question in a language not supported by your application, the AI will still answer the question, but the results might not be quite as good.Use tooltips to explain. A tooltip translation is the perfect spot to tell the AI what a column or task means and when to use it. Take a column called "Delivery date." Is that the date you promised the customer, or the date production planned? A tooltip such as "Delivery date agreed with the customer, not the planned production date" settles it. As a bonus, your users see the same explanation in the user interface.Speak the language of the world. Language models learned from enormous amounts of general text. They already know what a "customer" or an "invoice" is. What they don't know are your internal abbreviations and legacy names. Faced with a table called "deb_mut" or a column called "status_2," the AI can only guess. So where you can, rename these to standard business terms. Where you can't, explain them in the tooltip.Use one term for one concept. Imagine a colleague who hears "client" in one meeting and "customer" in the next. They would wonder whether those are two different groups. The AI wonders the same thing. Pick one term and use it everywhere in your model.Give tasks a clear name and purpose. A task called "Process" leaves the AI guessing. Call it "Approve sales order" and add a tooltip that explains what happens next. Now the AI knows exactly when to use it.Teach your workflows with skillsOnce your model is clear, the AI understands what your data means. Skills teach it how your company works. A skill is a set of written instructions that the AI picks up whenever a request calls for it. Basically, skills are a manual for AI.Take the sales order from the start of this blog. A skill for that job can tell the AI to check the customer's credit limit first, use the default delivery address, and always create the order as a draft for review. You write these rules once, and the AI follows them in every conversation.Share team context with projectsSome knowledge doesn't belong to a single workflow, but to a whole team. That is where projects come in. Both Claude and ChatGPT let you create a project with its own instructions and files, shared by everyone who works in it. A "Sales team" project could hold your pricing policy and a short explanation of your customer segments. Every conversation in that project starts with that knowledge, so nobody has to explain it again.Test before you invite usersFinally, put yourself in your users' shoes. Before you open the connector to anyone, ask the questions they will ask. Watch which subjects and tasks the AI picks, and note where it hesitates or guesses. Each wrong turn points you to something to improve, such as a missing tooltip or a skill that needs one more rule. Then test again. After a few rounds, you'll notice the answers getting sharper. Roll out step by stepA read-only MCP connector can be deployed with low risk, provided you have set up your data access and roles properly.You can roll out in two ways: make everything available at once, or open up your application step by step. For most organizations, we recommend the second path.Create a dedicated MCP role that exposes a limited set of subjects and tasks, and assign it to a small pilot group on a test environment. Use their questions and feedback to improve your descriptions, tooltips and skills. Then widen the scope and the audience step by step, so you know everything works as expected before all your users start using MCP.Don't forget to prepare your users as well. Tell them what the AI can and cannot do in your application: it can create a concept order, for example, but a manager still approves it. Remind them to always check what the AI proposes before they confirm it. And give them one clear place to report wrong or odd answers. Every report points you to a tooltip or skill you can improve, so your users become part of making the AI better. Let's get startedMCP turns your Thinkwise application into something users can talk to and agents can work with. The best way to find out what it can do for your business is to try it. Set up an MCP connector on your own application, start with a read-only role and a handful of test questions, and see what value it adds for your users.Want to get hands-on with MCP? You can try it right now on our Insights application!Using MCP Server in a Production environment will require an amended license agreement with Thinkwise, as Agentic AI via MCP typically automates and replaces human user interaction. MCP Server will be freely available in Develop and Test environments to empower you to experiment with MCP for end users and speed up development in the Software Factory. News & Blogs Thu, 08 Oct 2026 09:57:41 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/using-a-hidden-base-prefilter-alongside-multiple-prefilter-groups-7033 Hello,I am working on filtering for a custom component and I am trying to achieve this using prefilters.I would like to have multiple prefilter groups, with one main prefilter that is always active, regardless of which filters the user selects. This main prefilter should ensure that the original items belonging to the current user are always shown and cannot disappear because of the other filter selections.Conceptually, I am looking for something like:Main prefilter: always active and preferably hidden from the user Shows the user's own/original items Filter group 1: optional filters Filter group 2: optional filters Filter group 3:  optional filtersThe desired result would be that the main prefilter is always applied, while the other prefilter groups can be selected/deselected independently.Is this possible with Thinkwise prefilters? If so, what would be the recommended way to configure the prefilter groups and the hidden/main prefilter to achieve this?Thanks in advance! Questions & Conversations Wed, 07 Oct 2026 16:59:16 +0200 https://community.thinkwisesoftware.com/ideas/cube-view-filter-should-support-does-not-contain-6333 Currently, the cube view filter only supports “Contains” (or “equal to”) as a filter option.Additionally, I would like to have the option for "does not contain” (or "not equal to”) as a filter option.Now I have solved it with a prefilter that excludes my values from the cube, but it would be better if the filter option was editable from the SF  Wed, 07 Oct 2026 12:48:04 +0200 https://community.thinkwisesoftware.com/news-blogs-21/mcp-on-the-software-factory-6992 As you probably noticed, we have launched MCP support for our Platform as a beta feature with release 2026.2.12! The initial communication has been about using MCP on customer applications. And because the Software Factory and IAM are built with the Thinkwise Platform itself, MCP is technically available for those applications too!Given the eagerness to work via MCP on the Software Factory, we invite you to start using it now. Keep the known limitations below in mind. Specifically, double-check that you are applying the best practice of setting your MAIN branch to Read only.Knowledge Session & WorkshopsBefore you start, we strongly recommend watching the recording of our Knowledge Session MCP on the Software Factory: application development with prompts:We are happy to help you get started with MCP on the Software Factory and have organized a bunch of Workshops. Make sure to enrol via the Community Events if you are interested!Known limitationsThe main reasons for not advertising the use of MCP on the Software Factory so far, have to do with our desire to implement additional controls:More granular access control for MCP: in its current form, MCP would be able to alter every branch for which you as a user have edit permissions. We will adjust this by adding a Branch-level setting that determines whether mutations are allowed via delegated access. Clear tracing of mutations made by MCP: changes made by MCP are currently not explicitly traced in the Software Factory. With Indicium 2026.2.13 we have launched a new session variable tsf_is_delegated_request, which we intend to use to explicitly show in the Trace fields what changes are made via delegated access.Both improvements will ship with STS 2026.2.14 on the 28th of September and with LTS 2026.3 the 5th of October.Other known limitations with the current version of MCP:Subject Variants are not yet exposed via MCP For Tasks available in both the menu and as Table task, only Table tasks work with MCP Creating Unit Tests via MCP does not yet work Only Role Software developer is available, effectively giving MCP All rightsMost of these limitations will be resolved with LTS 2026.3. Set up MCP on the Software FactoryThe steps in the Getting started with MCP blog apply to an IAM with the Application SF in combination with the Role Software development. Configure the following four settings:User: Allow access delegation Application: Allow access delegation Application > Authorization settings > Access delegation roles: Available for delegation for the Software development role Client applications: Create Client with related configuration Thinkwise Skills repositoryClaude Code proves surprisingly strong at getting its job done on the Software Factory. Among other things, it will use Tooltip information from the model to get additional context with all available Subjects and Tasks via MCP.But as you all know, there is more to good application development than finding your way in the Software Factory. For that reason we have already prepared a significant list of Skills that are smartly applied by Claude Code, provided that they are available to it. Download our Skills repository here and use them to your advantage! News & Blogs Wed, 07 Oct 2026 11:10:02 +0200 https://community.thinkwisesoftware.com/ideas/add-apply-to-tree-to-conditional-layout-setting-6967 The option Apply to Tree is missing here:      Wed, 07 Oct 2026 08:32:21 +0200 https://community.thinkwisesoftware.com/ideas/infinite-scrolling-5029 Will it be possible in the future to apply Infinite Scrolling to certain Card Lists, Form Lists and Grids in our applications? We would like to see it as an extra option in subjects.For some screens it is desirable to have this, especially for small mobile devices, this can gain some extra available height, and avoid scenarios like below:Is this technically feasible or are there good reasons not to want this?Or is this something that can now be achieved in the Univeral GUI, using custom CSS? Wed, 07 Oct 2026 08:31:22 +0200 https://community.thinkwisesoftware.com/ideas/load-on-scroll-instead-of-pagination-6987 When there is a lot of data needed in a view / screen. It takes a lot of performance to load everything all at the same. Sometimes we need to load 50.000 rows or items or lines.To make sure the performance is okay, we use pagination in our grids. So we only load everything per page.Use case: our users need to select multiple rows / items over several pages, but when you go to the new page, it loses the selection of the previous page. Which causes inefficiency for them to execute tasks over several pages.Our proposed solution:Load on scroll. You still can load chunks of data instead of everything all at the same, but you start loading a new chunk ones you hit a scroll depth. Used frequently in webshops to load products on product listing pages. Wed, 07 Oct 2026 08:31:21 +0200 https://community.thinkwisesoftware.com/ideas/question-to-sql-generation-686 I came across a story , and it mentioned a few AI cases that seemed interesting. Are there any movements towards adopting these type of technologies? There is a specific mention on 'question to SQL generation'. It would be great to have a user type in a question and the systems generates the right query to fetch the data and show it. Wed, 07 Oct 2026 08:07:16 +0200 https://community.thinkwisesoftware.com/ideas/markdown-control-for-rendering-formatted-text-6872 Currently, Thinkwise supports a Multiline control for plain text and an HTML control for formatted text. However, the HTML control requires HTML input, which is difficult to generate and maintain — especially in AI-driven workflows where markdown is the natural output format of language models.A native Markdown control would allow developers to store content as plain markdown text and render it as formatted output (headings, lists, bold/italic, code blocks) in the Universal GUI — read-only in grids and forms.Use cases:AI-generated content (user stories, descriptions, summaries) rendered directly in the application Documentation or knowledge base fields Any field where structured, readable text is needed without the complexity of HTMLProposed behavior:Read-only rendering of markdown in form and card list components In edit mode: plain text editor (like Multiline), or optionally a markdown editor with preview Available as a domain control, similar to how Multiline and HTML are currently offeredThe HTML control already proves there is demand for rich text rendering in Thinkwise applications. Markdown would be a lightweight, developer-friendly complement to it. Tue, 06 Oct 2026 19:24:14 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/how-to-export-html-in-universal-as-plain-text-without-all-the-tags-7025 Hi,We noticed that when exporting HTML columns in Windows, the data would automatically be stripped off html tags and only output the plaint ext.In Universal, the raw html is exported, which is much less readable.I was wondering if this is expected? We are on Universal and Indicium version 2026.2.12I thought of implementing a workaround, by adding an expression column that strips the html to plain text, but I can’t easily ensure users will export that instead of the regular column and it seems messy to add this to the tables.Might a next release support automatic html to plain text conversion? I’m not sure if I am missing something, or what the status is of this, hence I would like more info/advice instead of creating an idea. Thanks!  Questions & Conversations Tue, 06 Oct 2026 15:51:21 +0200 https://community.thinkwisesoftware.com/ideas/showing-columns-moved-to-query-suffixed-tables-as-a-detail-of-their-parent-table-in-the-sf-6910 Query fields were moved to _query-suffixed tables in the 2026.2 version of SF. As a result model-info is no longer (correctly) usable on any query field. This is inconvenient when you want to develop dynamic functionality or query metadata at a higher level. I happen to be aware of this change from the latest SF release because I was involved with upgrading to the 2026.2, but a developer who was not involved in the upgrade would have a very difficult time figuring out where the query columns are actually stored. It would require a significant amount of investigation and trial-and-error to uncover the correct locations.My suggestion would be to add the _query-suffixed tables as a detail in the form of their parents to alleviate this issue. Tue, 06 Oct 2026 14:12:34 +0200 https://community.thinkwisesoftware.com/ideas/create-allowed-tenant-and-login-option-rows-when-adding-a-web-domain-6607 In case only one tenant exists it would help to create default rows in these tables when a web domain is added: :web_domain_allowed_tenantweb_domain_login_optionElse nobody will be abble to open the application and there is no other way to solve the problem via the IAM database   Tue, 06 Oct 2026 13:54:42 +0200 https://community.thinkwisesoftware.com/ideas/search-and-open-documents-always-visible-on-top-of-menu-5956 Can the search and open document always be visible on top, also when you are scrolling down.In Windows GUI, the search is at least always visible, in Universal GUI all disappears when scrolling down in the menu   Tue, 06 Oct 2026 11:55:52 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/universal-gui-version-doesn-t-automatically-update-for-some-users-7026 Hi,We noticed that after a Universal GUI update, some users were stuck on the old version.It especially seemed to happen for users who used “Install as app” from the Edge browser.App installed from Chrome I have seen automatically update. In the browser it also seems to update within a day or so. What is your experience with Universal GUI updates?Are there certain browsers that we should avoid? How reliable is installing the application as an app? Should we tell all users to clear their cache after an update? Questions & Conversations Tue, 06 Oct 2026 11:14:50 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/different-session-duration-for-specific-users-in-universal-7030 We're running into an issue with session duration. We're currently transitioning from the windows GUI to the universal GUI, and that's where this comes up.We use entraID as openID provider in IAM, with a session expiration of 30 minutes on the provider. That works fine for most users, but a few users shouldn't be logged out at all during the day.As far as I can tell, session expiration can be set on 3 levels:- Global settings- Per tenant- Per openid providerFor SSO users only the openid provider setting applies, so I don't see a way to set this per user or per user group.The only option I've found so far:2 openid providers with different session expirations.A second app registration in entra and a second openid provider in IAM with a longer expiration. To avoid two SSO buttons on the login page, each provider gets its own web domain. This should work, but it requires an extra URL, certificate, and it adds extra management overhead for just a small number of users.My questions:- Is there another way to set session expiration per user or per user group for SSO users?- Is what I found a recommended approach, or is there a better alternative?Thank you in advance! Questions & Conversations Tue, 06 Oct 2026 10:55:28 +0200 https://community.thinkwisesoftware.com/news-blogs-21/guided-wizards-beat-training-manuals-6882 It's the new hire's third day. They open the incident screen for the first time: four tabs, a detail grid, 50 fields, and no clue which ones matter right now. They fill in what they recognize, skip what they don't, and hit save. The record looks fine. It isn't. A required detail is missing, a business rule quietly broke, and three weeks later someone must work out why that incident never triggered an action. As a developer you didn't do anything wrong. You trained your users how to use the application, and most days that holds. But training lives in people's heads, and heads forget, leave, and improvise. So instead of teaching users where to look, bring every field they need straight to them, one step at a time. Most of us already know that pattern by another name: a wizard. This post shows two ways to build a guided, multi-step process in the Software Factory, and how to pick the one that fits. Why guide the user at all?There are lots of reasons to guide your users. We've listed a few that would most impact Thinkwise customers, roughly ordered by impact.   Data integrity (probably the most important one)  A process is rarely one record. It's a parent, a couple of detail rows, maybe a record in another table entirely. Do that freehand and skip a step, and you not only get confused users, you get a broken record that violates your own rules and that someone must hunt down and repair later.    You control the sequence  Because you decide what the user sees and when, you can validate, set defaults, and bring the user to the right next step based on earlier answers. No more dumping every error at the end.     Consistency across users  Without guidance, ten people run the same process ten slightly different ways, and your data shows it. A wizard makes everyone walk the same path, so what lands is uniform.    The process lives in the app, not in someone's head  Often a process survives in your most senior user's memory and in documentation nobody reads. Put it in a wizard and the knowledge stays in the application, where it belongs.    Faster onboarding, less training  New people get productive without a colleague walking them through where everything lives. In enterprise settings that hand-holding is a real, recurring cost. A wizard hands that time back.    Lower cognitive load  Enterprise screens are dense: many fields, tabs, nested grids. That's the norm here, not the exception. A new user staring at all of it doesn't know where to start. One focused step at a time fixes that.  Two ways to build a wizardThe SF gives you two approaches: tasks chained into a process flow, or a modal document with details. You can even mix them, if you're feeling brave.  Guiding with tasksIn the example below we want users to report an incident. Getting this right matters: an incorrect report means the incident is handled wrong, or not at all. So we split it into a handful of tasks, each a pop-up with grouped fields and labels that explain themselves. No onboarding is required. One button, a few steps, done.   What stands out Use layout procedures so each step shows only the fields that are relevant right then. Focus stays where you want it.  Use defaults to guide even further. If the brakes aren't working, set the report to immediate action and push the severity to high automatically.  Make the last step a read-only overview of everything entered. This is the moment the user catches their own mistakes before the report goes in. Highly recommended.   How to build oneUse the steps below to build your wizard using tasks. Create one task per step, each with its own parameters.  Add the step counter to the task's name translation: (step 1/5).  Add an alternative translation to the confirm/cancel button called next/back.  Drop all tasks into a process flow with a process variable for every task parameter.  Map both input and output parameters to those variables. This is what lets the user move back as well as forward.  Optional but recommended: add an overview step at the end. That final task is the one that actually does the insert. The earlier tasks are just collectors, and the process variables carry their values to the final task.  The final step can show every field from the earlier steps, or smarter summaries of them. Keep them all read-only. You want users editing in the earlier steps, where the logic and instructions live.   Guiding with a modal documentThis time we're adding a new employee. That means the person's contact details, plus emergency contacts, a photo, and their employment record.  Complete a step and the modal carries you to the next. The big advantage over tasks: it's more future-proof. Add a new column to the table later and it shows up in the modal on its own, with no task to adjust.    Spotted that the header and footer are gone? That's a setting introduced in 2026.2.11. Disable them in the modal settings of the screen type, and lean entirely on the action bar, where you can add as many tasks as navigation buttons as you like What stands out Here we only used forms, which covers most cases. But these are just normal screen types and subjects, so get as creative as you want: pick a workshop from a map component instead of a dropdown, or preview the document the user just uploaded.  Need multiple rows in one step? A modal handles that natively. With tasks you're stuck reaching for workarounds to get the same result. Smart defaults again: set hours per week to 40 the moment the contract type is fulltime.  After the insert, drop the user on the new record in the grid, so they see exactly what they added and where.   We used standard horizontal tabs in this example, but you can also set the tab page vertically, which lists the steps from top to bottom instead.   How to build oneUse the steps below to build your wizard using a modal document. Create a variant for the main subject and for its details.  Add an alternative translation to each ‘page.’ Incorporate the step number in this translation.  Give those variants a screen type. In our case that's just an action bar for navigation plus a form.  Switch on auto edit and auto save in the variants so the user doesn't do either by hand.  Build tasks and process flows for the navigation. The flow should use "activate detail" to move to the next page, and "add row" so the user can start typing right away.  In the SF, disable show footer, and optionally hide the header.   Making your wizards even betterA wizard that runs and a wizard that helps are different things. The mechanics above get you a flow that works. These (UX) rules decide whether it feels like guidance. Want to learn more? Read this article.  One job per step. The whole point is lower cognitive load, so don't rebuild the dense screen inside the modals. If a step needs a scroll bar, it's probably two steps.  Always show their progress. People will sit through five steps if they can see the end coming. A "step 2 of 5" in the title is enough.  Let them go back and lose nothing. A flow you can only move forward through feels like a trap. Mapping your input and output parameters to process variables (which we did above) is what makes "back" safe.  One catch: this only holds for "next.” If the user hits back (so cancel), the output parameters never get mapped to the process variables, so whatever they typed in that step is gone. Validate as they go, not at the end. The point of splitting the process up is to catch a problem while the user still has the context to fix it. Don't let someone reach the overview step only to learn step one was wrong.   Your turnCreating these wizards, thinking through the user flow, and actually implementing them takes more effort than building a standard screen. But that effort pays off. You can drastically improve the usability of specific flows in your application, especially the important ones for your organization. We're curious what use cases you can think of in your own application. How would a wizard help your users?   News & Blogs Tue, 06 Oct 2026 10:19:07 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/connecting-thinkwise-mcp-server-to-openai-codex-cli-oauth-shows-as-unsupported-6971 Hi,I am trying to connect the Thinkwise MCP Server to OpenAI Codex CLI.My environment:Thinkwise Platform / Indicium / Universal UI: 2026.2.12 Codex CLI: 0.142.4I completed the IAM setup (access delegation, client application, client secret, roles and callback URL).The MCP server can be added successfully to Codex, but:codex mcp list→ Status: enabled→ Auth: UnsupportedAnd:codex mcp login thinkwise→ Error: No authorization support detectedThe Thinkwise documentation mentions Claude and other MCP-compatible AI tools, but currently provides setup instructions for Claude Code.Has anyone successfully connected Thinkwise MCP to OpenAI Codex CLI?Is additional OAuth configuration required for Codex, or is the current MCP beta OAuth flow not yet compatible with it?Thanks! Questions & Conversations Mon, 05 Oct 2026 19:22:24 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/lookup-control-is-there-a-reason-not-to-use-combo-everywhere-7009 The Universal GUI used to have a performance problem with ‘Combo’ lookup control so we defaulted to ‘Suggestions’. In the recent GUI’s the performance increased and also the functionality improved so that ‘starts with’ is shown before ‘contains’ in the result. So we are changing most look-ups to ‘Combo’.So I am wondering, is there still any reason left to use anything else than ‘Combo’ as a lookup control since it has the ‘Suggestions’ functionality included? Questions & Conversations Mon, 05 Oct 2026 16:44:41 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/azure-sql-serverless-database-does-not-auto-pause-despite-no-activity-6994 Title: Azure SQL Serverless – Database does not auto-pause despite no activityHi,I have recently migrated my development environment to AZURE.The Thinkwise environment is running on Azure, and the SQL database is configured using the Azure SQL Serverless tier, with auto-pause enabled.I have scheduled all IAM/SF System Flows / IAM-related processes so that they only run during working hours, approximately 08:00–18:00.However, when I check the Azure SQL metrics, I can see that the database never seems to enter auto-pause, including during the night when there should be no SF/IAM activity.Is there anything in SF/IAM, or any specific setting/configuration, that I should check to make sure that no background process, connection, health check, or other activity is keeping the SQL database active?Any advice on how to identify what is preventing the auto-pause would be appreciated.Thanks!   Questions & Conversations Mon, 05 Oct 2026 15:30:49 +0200 https://community.thinkwisesoftware.com/product-updates/release-notes-thinkwise-deployment-center-4-0-0-7029 Hello everyone,In this release, we have added support for deploying IAM to IBM Db2 for i databases, from both the GUI and the command-line interface. To make this possible, we have introduced manifest schema version 4, which allows a single manifest to contain packages for multiple database platforms. We have also added a dependency check for SQL Server 2022, and the command-line interface is now available for Linux.Upgrade to version 4.0.0 of the Thinkwise Deployment Center. It remains fully backward compatible with existing SQL Server manifests and scripts.Windows SmartScreen may prevent you from opening the application. To solve this, open the properties of the executable and select Unblock. Then open the application again.Download the Thinkwise Deployment Center 4.0.0 here. ContentsBreaking DbConnection settings in 'twdeployerGUI.appsettings.json' New in the Thinkwise Deployment Center Support for IBM Db2 for i  Required for Db2: the IBM i Access ODBC Driver Manifest schema version 4 Compatibility level 160 (SQL Server 2022) Command-line interface for Linux Changed in the Thinkwise Deployment Center Connection settings per database platform .NET 10 Questions or suggestions?BreakingDbConnection settings in 'twdeployerGUI.appsettings.json'GUIThe DbConnection section of twdeployerGUI.appsettings.json is now divided per database platform. This only applies to the GUI. The command-line interface does not use a appsettings.json file, so existing CLI scripts are not affected. Move your existing settings into a SQLServer or DB2 sub-section in the twdeployerGUI.appsettings.json. Otherwise, the Server Connection step no longer fills in these settings for you. Before:"DbConnection": { "Host": "example.com\\instance", "AuthenticationMethod": "UserPassword", "Username": "sa"}After:"DbConnection": { "SQLServer": { "Host": "example.com\\instance", "AuthenticationMethod": "UserPassword", "Username": "sa" }, "DB2": { "Host": "IBMI-SYSTEM", "Username": "<IBM i USER PROFILE>" }} New in the Thinkwise Deployment CenterSupport for IBM Db2 for iGUI CLIWith the Thinkwise Platform 2026.3 release, you can now deploy IAM to IBM Db2 for i databases. In addition to SQL Server, you can install, upgrade, hotfix, and synchronize IAM on an IBM i system.GUI When the manifest offers packages for more than one database platform, the Server Connection step shows a new Provider field. Select IBM DB2 to deploy to an IBM i system.Db2 connections use Username/password Authentication. The SQL Server Encryption and certificate options do not apply, so they are hidden. The library to deploy to takes the place of the database name. System libraries are excluded when you browse for a library.CLI The IAM commands (iam install, iam upgrade, iam hotfix, iam sync-model, and iam auto) have a new --rdbms option. Use it to select the database platform to deploy to: SQLServer or DB2.When you do not specify --rdbms, the platform is taken from the manifest. If the manifest contains packages for more than one platform, the Deployment Center uses SQL Server. Existing scripts against a SQL Server-only manifest keep working unchanged. Db2 always connects with an IBM i user profile and its password, so -u|--username is required. If you specify an authentication method that Db2 does not support, such as a Microsoft Entra method, you now get an error immediately instead of when connecting. Pass the library to deploy to with -n|--name, in place of the database name.Example:twdeployer iam install --server "IBMI-SYSTEM" --name "TW_IAM" --rdbms DB2 --username "<IBM i USER PROFILE>" --password "<USER PROFILE PASSWORD>" Select IBM DB2 as provider on the Server Connection step Required for Db2: the IBM i Access ODBC DriverGUI CLIThe Thinkwise Deployment Center connects to Db2 for i using ODBC. You must install the ODBC driver separately on every machine that deploys to Db2 as it is not included in the Deployment Center.Register the driver under the name IBM I Access ODBC Driver. The Deployment Center looks for the driver by this exact name. When it cannot find the driver, it shows the following message: ‘The IBM i Access ODBC Driver does not appear to be installed on this machine. Install it before deploying to a Db2 database.’.Windows installationDownload IBM i Access Client Solutions - Windows Application Package from IBM: IBM i Access Client Solutions (a free IBM ID is required). Run the installer and make sure the 64-bit ODBC driver is included. Verify the installation by opening ODBC Data Sources (64-bit). The driver IBM i Access ODBC Driver should be listed on the Drivers tab.Linux installationOn Linux, the driver is part of IBM i Access Client Solutions - Linux Application Package. It requires the unixODBC driver manager.Download the Linux Application Package (.deb or .rpm) from IBM i Access Client Solutions, or install it from the IBM i Access ODBC package repositories. Install unixODBC and the driver:# Debian / Ubuntusudo apt install unixodbcsudo apt install ./ibm-iaccess-<version>_amd64.deb# RHEL / Fedorasudo dnf install unixODBCsudo dnf install ./ibm-iaccess-<version>.x86_64.rpmVerify that the driver is registered under the correct name. The output should contain sIBM i Access ODBC Driver].odbcinst -q -d   Manifest schema version 4GUI CLIWe have added support for manifest schema version 4. The IAM product can now declare a providers list. This way, you can ship IAM packages for both SQL Server and Db2 in a single manifest. Each provider has its own version, dependencies, and packages.Manifests that use schema version 2 or 3 remain supported. The Deployment Center reads them as SQL Server products. { "schema": 4, "products": " { "type": "IAM", "version": "2026.3", "providers": { "provider": "SQLServer", "dependencies": "CompatibilityLevel160" ], "packages": { "type": "Install", "path": "IAM/SQLServer/Install" } ] }, { "provider": "Db2fori", "packages": { "type": "Install", "path": "IAM/Db2fori/Install" } ] } ] } ]} Compatibility level 160 (SQL Server 2022)GUI CLIWe have added support for the database dependency CompatibilityLevel160. The Dependency Check step now checks whether the compatibility level of the database is set to 160 or higher (SQL Server 2022). Command-line interface for LinuxCLIThe Thinkwise Deployment Center command-line interface (twdeployer) is now also available for Linux. This way, you can run deployments from Linux build agents, containers, and servers, without a Windows machine. The commands and options are the same as on Windows.The following builds are available:Platform GUI CLI Windows x64 Linux x64 (such as Ubuntu, Debian, and RHEL)    The Linux builds are self-contained, so you do not need to install a .NET runtime. After you extract the files, make twdeployer executable:chmod +x twdeployer./twdeployer --version Changed in the Thinkwise Deployment CenterConnection settings per database platformGUIPreviously, the Deployment Center remembered the last used database connection settings globally for all database platforms. It now remembers them per database platform.When you switch the Provider on the Server Connection step, the Deployment Center fills in the fields with the values you used last for that platform. .NET 10GUI CLIWe have updated the Thinkwise Deployment Center to .NET 10. All builds are self-contained, so you do not need to install a separate .NET runtime. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! Mon, 05 Oct 2026 12:39:59 +0200 https://community.thinkwisesoftware.com/product-updates/thinkwise-platform-2026-3-7028 Note: The original voice-over was lost after our Platform Ambassador spoke at the Thinkwise Summit. This video is an AI-generated replacement created with Claude Opus 5.5. With Thinkwise Platform 2026.3, the Model Context Protocol (MCP) changes how you interact with your Thinkwise applications and their data. MCP support was introduced as beta release in Thinkwise Platform 2026.2.12 and is generally available with this LTS release. You can connect any MCP client, such as your preferred AI tool, to your business applications and the Software Factory using the /mcp endpoint in Indicium. Instead of navigating to the right screen and searching for data manually, you can ask your AI tool to find and analyze the data for you. Adding data becomes easier too, because your AI tool can turn unstructured input, such as an email, document content, or a voice message, into structured data in your database without any manual typing.Because the MCP server is built into Indicium, you do not need any additional components; you set up MCP and manage its access in the Intelligent Application Manager (IAM). To give AI tools and AI agents secure and granular access, follow our best practices for role-based access control, access delegation, and logging. MCP is freely available in development and test environments, so you can speed up development in the Software Factory and test MCP with end users. Using MCP in production requires an amended license agreement with Thinkwise, so contact your account manager for more information.To learn more, read our Community blogs Thinkwise Platform as MCP Server, Getting started with MCP, and MCP on the Software Factory.You can also use MCP on the Software Factory, and together with our published skills, it significantly changes the way developers work. Your AI agent can take on tasks such as creating a data model, creating screen types, and setting up a Scheduler, so you can spend more time understanding, describing, and refining business needs. You can also hand over repetitive work while you review and decide, such as finally adding those missing unit tests for existing functionality. Unlike vibe coding, where AI leaves you with a mountain of generated code to maintain, your AI agent works with the model. This model-driven development and Technology-as-a-Service approach lets you deliver business value with as little code as possible.The MQTT broker capabilities from Thinkwise Platform 2026.2 let you publish messages, and with this release, you can also subscribe to MQTT topics. A subscription listens to a topic on your message broker and starts a process flow every time a message arrives, whether it comes from a machine, a sensor, or another Thinkwise application. Your applications can now receive sensor data and machine status updates directly, enabling real-time interaction between the shop floor and your business applications.With IAM on DB2 for IBM i, we take a major step toward running the entire Thinkwise Platform on IBM Power. We have already proven that it works, and we are now completing a dedicated Indicium distributable for IBM Power. You can then deploy Indicium and the Universal UI on a Red Hat Linux partition, on the same IBM Power machine that runs your DB2 databases.The inline action bar is our answer to a long-standing and popular community idea: showing tasks on grid rows. We took this idea further, so you can now configure any action inline. Note that this is still a beta feature. We plan to improve the user experience and add support for card lists.Besides MCP, developers also get a major upgrade to Model insight and the Thinkwise Workspace Listener for Linux and macOS. Thinkwise Deployment Center 4.0.0 is now also available for Linux, and you can use it to deploy IAM on DB2.This release includes 19 community ideas, representing 367 votes.A full overview of all the release notes of the Thinkwise Platform 2026.3 is available now!The Indicium and Universal UI 2026.3.10 features below are backwards compatible with previous Thinkwise Platform versions. Therefore, these fixes are not part of the release notes for Thinkwise Platform 2026.3.ContentsBreaking Important: Redeploy required objects to DB2 application schemas Restricted file access outside the base path Check custom CSS Removed support for Thinkwise Platform version 2024.3 New and changed in the Universal UI and Indicium (2026.3.10) Configurable timeout for i-net Clear Reports Select resources directly in the Scheduler Search and open documents pinned in the menu Application backplate shown after switching applications MacOS-specific keybind text in shortcut labels Fixed Indicium Universal UI BreakingImportant: Redeploy required objects to DB2 application schemasSoftware Factory DB2From Thinkwise Platform 2026.3, Indicium requires the following functions and procedures on the schema of DB2 applications:tsf_user and tsf_original_login - If these are not updated, user authorization does not work as expected. tsf_set_session_variable and tsf_clear_session_variables - If one of these is missing, Indicium cannot open connections to the application database.The DB2_DB base model adds these objects to your work model. You still need to deploy them to your application schema.Required action for all DB2 applicationsDeploy these objects directly after upgrading to Thinkwise Platform version 2026.3. Without these steps, the upgrade to 2026.3 does not succeed for DB2 models.To deploy the objects:Go to menu Business Logic > Functionality. Deactivate the prefilter Hide generated. Search for the object name, see the list above. Deploy the object to your application on the tab Deploy.Alternatively, upgrade the DB2 applications. The upgrade applies these objects automatically. Restricted file access outside the base pathIndiciumPreviously, in non-database file storage configurations, file paths outside the configured base file storage path could still be retrieved, downloaded, and previewed.From Thinkwise Platform version 2026.2.14 onwards, the database record is retrieved successfully, but with an invalid file contract. Trying to download or preview the file now returns a 404 Not Found error.Check that your file paths are within the configured base file storage path. To temporarily restore the previous behavior, set the extended property AllowPathOutsideBasePath to True. Only use this setting as a temporary solution, as it will be removed in a future release. Check custom CSSUniversal UIAs a result of improvements to the Scheduler in Thinkwise Platform version 2026.2.14, the structure of the HTML and the CSS classes used have changed significantly.If you have custom CSS for the Scheduler, review your styles and update the selectors if necessary. Contact support if any selectors are missing. Removed support for Thinkwise Platform version 2024.3Indicium Universal UIIn accordance with our lifecycle policy, we have removed support for Thinkwise Platform version 2024.3 in Indicium and Universal UI.Upgrade to Thinkwise Platform version 2025.1 or higher. New and changed in the Universal UI and Indicium (2026.3.10)Configurable timeout for i-net Clear Reportschange IndiciumPreviously, the timeout for generating reports with i-net Clear Reports was raised from 100 seconds to 5 minutes. Some reports need even more time than that, so you can now configure the timeout with the extended property clearReportTimeoutSeconds. The value is in seconds. If you do not set this property, the default of 5 minutes (300 seconds) still applies. Select resources directly in the Schedulernew Universal UIUsers can now change the active record of a resource by directly clicking on it in the Scheduler.The user can select a resource in the following ways:Selecting a resource directly in the Scheduler. Selecting a resource's activity. Selecting the corresponding record in another screen component, such as a form or grid.Once a resource is selected, the active record is shown in other screen components, such as a form or grid. Similarly, if the user changes the active record of a resource in another screen component, the corresponding resource in the Scheduler is highlighted.For example, if a user clicks on employee in the Scheduler, the data of that employee is displayed in the form. If the user then selects a different employee in the grid, the corresponding resource in the Scheduler is highlighted. This improves the user experience by keeping related screen components in sync and making it easier to navigate between resources and their corresponding records.Screen components show the active record of the selected resource Search and open documents pinned in the menuchange Universal UIPreviously, when a user scrolled in the sidebar menu, the Search field and the Open documents section scrolled out of view. Now, they stay pinned to the top of the menu while the rest of the menu scrolls underneath. This way, users can use them to navigate and to see the current state of the application. The collapsed state of Open documents is remembered across sessions.Search and open documents pinned in the menu  Application backplate shown after switching applicationschange Universal UIPreviously, when a user switched to another application using the application switcher, the previous application's document remained on screen. Because it was shown in the new application's theme, it could be unclear which application the document belonged to.Now the new application's backplate is shown, with the focus on the menu. The previous application's document remains available in the Open documents section. When a user selects it, the theme and menu switch to the application it belongs to. MacOS-specific keybind text in shortcut labelschange Universal UIShortcut labels used to show the same key combination on every operating system.On MacOS, shortcut labels now show MacOS-specific keybinds. Instead of Ctrl + E, the edit shortcut now shows Cmd + E.The shortcut itself still works the same way on every operating system. If you connect a Mac keyboard to a Windows computer, Cmd + E still works. On MacOS, Ctrl + E still works too.For non-MacOS users, nothing changed. Mobile devices still do not show shortcut labels. FixedIndiciumWith the extended property IgnoreDiacritics enabled, Search did not ignore diacritics if the lookup column was part of the primary key. This has been fixed.Universal UIUsers can sort a column by selecting its header in ascending or descending order, but could not disable sorting. This has been fixed. Sorting of grouped columns has not changed. When the parent record changed, sub-details nested under an unrelated detail lost their data. Their tabs stayed empty until you selected Refresh. This has been fixed. In a pivot table, selecting a row label, such as an employee, and then starting a task or report opened it with empty parameters. This has been fixed. In a Date control, you could not type a date later than 31/12/2500. This has been fixed. You can now type dates up to 31/12/9999. The date picker still goes up to 31/12/2500. When you went from a subject with an active variant to a detail without one, Model insight still showed the variant of the previous subject. Now, it hides the variant in this case. In a form, radio button labels did not line up vertically with other fields. Also, a radio button field that shared a row with another field could be too narrow. As a result, its option labels could be cut off or overlap. This has been fixed. Previously, when executing the Go to row process action, the newly added grid row would in some cases not automatically become the active row. The screen had to be refreshed manually for this to take effect. This has been fixed. In some cases, the action bar did not fully fit the screen and the Search field was next to the overflow menu. The overflow menu then sometimes opened unexpectedly. This has been fixed. When the action bar did not fully fit the screen, it would shift around when you opened a document. This behavior has been improved. Added translations for the NOT IN operator for older platform versions. When tasks are disabled, they are grayed out in the user interface and cannot be selected. Previously, a disabled task could still be executed using its keyboard shortcut. This caused the application to freeze, requiring users to restart it manually. This has been fixed. Users can no longer trigger a disabled task using its keyboard shortcut. Mon, 05 Oct 2026 12:39:51 +0200 https://community.thinkwisesoftware.com/ideas/scheduler-tooltip-more-rich-4596 Too really make the scheduler more useful, the tooltip should be HTML or at minimum have a more readable style + link for a deeplink for example.     Mon, 05 Oct 2026 07:52:14 +0200 https://community.thinkwisesoftware.com/ideas/the-option-to-use-in-as-filter-in-the-form-list-4052 The last couple of days we receive multiple questions from our end users that the standard form list in the GUI doesn't give the option to use ‘IN’ to filter results. We are very curious why there is no option to put multiple different values comma separated in the standard GUI filter?This group of around 25 end users just moved from a 20+ years old ERP system to our Thinkwise ERP system but they showed us how they worked in the old system and to be honest, it looks easy to implement in the Thinkwise GUI and we actually are a bit curious why nobody seemed to noticed this ‘gap’ before. Maybe we overlooked something but it seems that it can't be done in the GUI in the current version (2023.1.12.0).Not sure how to call the standard filter in the GUI, but in SF they call this filter a form list. In blue there are the options to choose from, they look like this in our Dutch version of the GUI: We miss ‘IN’ as option in this listWhat we need is the option ‘IN’ and a possibility to fill in the values comma separated. For example if you want to see details from 3 different orders 123, 567 and 999 in the old ERP system we would easily filter like this:Filter 3 different sales orders in the >20 years old ERP systemAs a select query this would result in something like:Select details from sales_orders where sales_order_id in (123,567,999)So nothing really difficult about this, so we hope you can put this very soon as a filter option in the GUI?In our old system the filter can also be built like this (see also the different options like ‘and’ and ‘ or’ on the left side as well):Ways to build a selection filter in the >20 year old ERP systemWe read in some other posts on the community about using AND or OR as a prefilter, so maybe this last picture can be helpful. Nevertheless for us the most important thing is to give our end users the possibility to just fill in multiple values comma separated. Maybe this is already possible, if so, hopefully somebody can explain how and if not, we hope Thinkwise can provide this awesome option very soon. Thank you in advance! Sat, 03 Oct 2026 13:56:48 +0200 https://community.thinkwisesoftware.com/ideas/activate-top-left-screen-component-upon-opening-a-screen-3760 Upon opening a new Document in the Universal GUI the first value in the top left (at least for Western writing) Screen Component should be activated. This especially goes for the Grid component, where it seems as if the first Row is selected. In below example it took me 44 tabs to get to the first column value of the seemingly selected Row. Could the Universal GUI be a bit smarter here?  Sat, 03 Oct 2026 13:55:58 +0200 https://community.thinkwisesoftware.com/ideas/show-parent-nodes-on-search-in-tree-structures-6949 When nodes are filtered using the combi filter, the parent nodes of the matching results should always remain visible. Otherwise, the context of the filtered nodes is lost, making it hard to understand where the results belong within the tree structure.Example and desired behaviour:As an enhancement, we would like to see a model setting that allows developers to control this behavior. For example, an option such as "Show parent nodes when filtering" could be added to the Tree View configuration. When enabled, all parent nodes of matching results would automatically be displayed, preserving the hierarchical context while searching. Fri, 02 Oct 2026 16:10:53 +0200 https://community.thinkwisesoftware.com/ideas/opening-a-second-instance-of-a-screen-from-open-documents-6947 Usability suggestion for the Universal version of SF: if you, for example, [Ctrl]+click on Subjects under User interface, a new instance of the Subjects screen opens. However, doing the same on Subjects under Open documents does nothing.Because of this, I have to look up the Subjects option again under User interface, even though I usually want to open a second instance of a screen at exactly the moment the first one is already open — and therefore already shows up under Open documents.Please make eCtrl]+click work under Open documents as well. Fri, 02 Oct 2026 16:01:57 +0200 https://community.thinkwisesoftware.com/ideas/better-layout-for-universal-errors-6975 Please improve the layout of universal errors. This is the error starting with the query.  Then I have to scroll down half way to even find the error.  Please put the error on top to greatly improve debugging time.   Fri, 02 Oct 2026 15:58:26 +0200 https://community.thinkwisesoftware.com/ideas/native-opentelemetry-support-for-indicium-6977 Indicium has supported Azure Application Insights (Blog post 2021) and AWS CloudWatch (Indicium 2022.2.13) for some time.OpenTelemetry would allow Indicium to expose standardized observability telemetry—such as traces, metrics, and logs—without requiring users to send their data to Azure or AWS.Why?Currently, telemetry is only available when sending the data to either Azure Application Insights or AWS Cloudwatch. Local, on-premise and hybrid deployments could benefit from OpenTelemetry support and route this telemetry to a stack such a Grafana, Prometheus, Loki, Tempo or Jaeger.How?To make this concrete, some suggestions for Indicium in order to support OpenTelemetry:Indicium can send telemetry using the OpenTelemetry Protocol (OTLP) An OTLP endpoint can be configured, using gRPC and/or HTTP. These settings can be setup for a Indicium container using specific environment variables (https://docs.thinkwisesoftware.com/docs/deployment/container_registry_indicium#environment-variables) Settings comparable to the Azure Application Insights (https://docs.thinkwisesoftware.com/docs/deployment/aws#log-to-aws-cloudwatch) can be setup for the OTLP endpoint.  Fri, 02 Oct 2026 15:46:49 +0200 https://community.thinkwisesoftware.com/ideas/webdomain-allow-disallow-applications-6993 The introduction of the Webdomain has given the possibility to give a different login experience based on the domain.We can allow certain tenants on domains and give them specific login methods to login.What's missing?We still miss the option of allowing / disallowing a certain application on a webdomain.In our scenario, we have two applications hosted on the same IAM/Indicium/Universal combo.It would be great that we could create two webdomains where app-1.mydomain.nl only allows the users to acces app-1 and app-2.mydomain.nl only allows the users to access app-2.Why?Especially in production environments, the switching between applications has to be done right, without question. Switching inside the same Universal GUI instance (say browser tab or PWA), can be tricky, especially when the look and feel of both applications are the same.When allowing the Webdomain to allow / disallow the applications, you could create a PWA for each application easily. Fri, 02 Oct 2026 15:40:08 +0200 https://community.thinkwisesoftware.com/ideas/configure-search-fields-as-a-user-preference-6989 The global search is often configured to the most used fields. However this doesn’t always match all use cases. As a user I would like the option to configure this myself on certain subjects. I would like to have at least the option to exclude certain search fields as configured in the model. But preferably also have the option to add other search fields. Fri, 02 Oct 2026 15:39:41 +0200 https://community.thinkwisesoftware.com/ideas/application-log-on-the-software-factory-7020 Could the Application log be enabled on the Software factory please?I think it would help finding out ‘how something got there’ when a developer created a strange situation. It could also help with tracing what AI did through MCP.And of course it could help with analysing performance issues. I would prefer it to be available SF-wide (over all models/branches), with the possibility to filter on a model/branch (prefilter for current branch). Fri, 02 Oct 2026 15:36:21 +0200 https://community.thinkwisesoftware.com/ideas/enable-mcp-on-tcp-7015 We would like to use MCP on TCP to:-Add tickets and ticket-comments.-Retrieve open tickets.-Download Thinkwise products. Fri, 02 Oct 2026 15:34:57 +0200 https://community.thinkwisesoftware.com/ideas/max-min-width-settings-for-form-task-and-report-fields-6428 We like to have more control over field widths, because often you wish to give fields a absolute widthExamples:house number postal code dates bank accounts etc..When fields are on the same line it can have a mix of fixed and flexible widths.It should be more easy to set this up in the Software Factory.          Fri, 02 Oct 2026 09:49:05 +0200 https://community.thinkwisesoftware.com/ideas/add-menu-subtitles-support-in-sf-6990 Now I am used to subtitles in my own applications, I am really missing them in the SF.Specially for:-Data model (Tables)-Subjects-Functionality-Tasks-Process flowsCould some workaround be made to support subtitles in the SF please? Fri, 02 Oct 2026 09:41:25 +0200 https://community.thinkwisesoftware.com/ideas/turn-off-hyperlink-for-image-in-readonly-form-7004 For an image-upload control, it is currently not possible to disable the hyperlink/download feature in the form (read mode).It is annoying that clicking anywhere on the field opens a new browser tab with the image while the user is never interested in downloading the image in this case.In the example below, the image field is the full width of the page, so clicking anywhere right of the actual image opens a browser tab with the image.The GUI could maybe use the domain ‘Show action button’ setting to configure this behaviour. An alternative could be that the GUI is changed so that not the whole image field is the button, but that images get an small action button in the corner as is done with other type of controls.  Fri, 02 Oct 2026 09:37:34 +0200 https://community.thinkwisesoftware.com/ideas/enhanced-scheduler-multi-select-drag-drop-and-auto-scroll-while-dragging-7018 While using the Enhanced Scheduler for production planning, we've identified two improvements that would significantly increase usability and planning efficiency. 1. Move multiple activities/orders at onceCurrently, activities can only be moved individually. In real-life planning scenarios, it is often necessary to shift an entire group of activities or orders together due to schedule changes, machine downtime, or capacity adjustments.Suggested functionality:Select multiple activities using Ctrl/Shift or a selection box. Drag and drop all selected activities together. 2. Auto-scroll when dragging beyond the visible time rangeWhen moving an activity to a date outside the currently visible time range, dragging stops at the edge of the scheduler.Suggested functionality:Automatically scroll the timeline when the cursor reaches the left or right edge during a drag operation. Allow users to continue dragging activities to dates that are not currently visible without manually navigating first. Fri, 02 Oct 2026 09:36:52 +0200 https://community.thinkwisesoftware.com/ideas/drag-and-drop-between-two-rows-7024 Currently, the drag-and-drop function works by dragging one record onto another. The second record is the only drop target data available for determining the subsequent actions.It would be more intuitive if the drop behavior worked like in most applications, where a thick line is displayed between two rows in the UI to indicate where the record will be placed.From a technical perspective, the result could always return the row data of the record directly above the line (or an empty value when the record is dropped at the top). Alternatively, it could return the data of both surrounding rows. Fri, 02 Oct 2026 09:36:35 +0200 https://community.thinkwisesoftware.com/ideas/handler-for-copy-action-6973 I would like to be able to set a handler specific for a copy action that also uses the source row primary key as parameter(s). This way we do not need to create a specific copy task every time we want to include weak-entities in the copy action but the handler can execute that logic.This also has the advantage that the copy action is always at the same position in the action bar. Fri, 02 Oct 2026 09:26:18 +0200 https://community.thinkwisesoftware.com/ideas/visibility-of-inactive-tab-7008 Can you change something on the visibility of the inactive TABS. In the WIN GUI the colored Icons were made grey on an inactive tab. When the tab was active the colored icon was shown. So it was very clear for users when the tab was inactive. And with using color it was also very clear when the tab was active.In the current Universal version the inactive tab is shown with very lightly reduced colors. As wel the text of the tab as the icon. This is the inactive variant And this is the active variant. When you see them here in exploded format and next to each other the difference can be seen. However in the application you see one or the other, and they are much smaller. So for the user it’s much harder to see if the tab is active or not.The grey variant for the inactive variant in the WIN GUI was much and much better and much more clear to the user  Fri, 02 Oct 2026 09:23:30 +0200 https://community.thinkwisesoftware.com/ideas/better-filter-control-for-source-branch-type-of-object-on-merge-conflict-overview-6928 Having countless of program object types makes it kind of a pain for filtering when dealing with merge conflicts (especially merge sessions with numerous conflicts).  Long long list of object typesIn my instance I know a majority from the conflicts originate from Translations. Now I have to manually scroll all the way down to the ‘T’ area and still look around there. Would be nice if I could just type and search instead. Fri, 02 Oct 2026 09:17:56 +0200 https://community.thinkwisesoftware.com/ideas/make-software-factory-metadata-available-to-ai-so-i-can-generate-sql-templates-from-my-ide-6496 I want to use generative AI to draft the bulk of my SQL templates, directly from my own IDE (e.g., VS Code) together with tools like GitHub Copilot. For this to work reliably, the AI needs first-class context from the Thinkwise Software Factory (SF): the application’s model metadata and relevant UI information. The SF already maintains a rich, structured model of tables, columns, and references; exposing that to the AI is the missing piece.Why this metadata is essential for AI-assisted SQL When the AI understands my model, its output stops being generic and becomes project-specific:Tables, columns, PK/FKs – enable correct JOINs, WHERE clauses, and integrity-awareness. The SF’s data model explicitly defines these entities and relations, which the AI can use to pick the right join keys, respect cardinalities, and avoid hallucinated columns. Domains (user-defined data types) – domains act as abstract data types that drive constraints and UI defaults. Sharing domains helps the AI choose correct data types, casts, default values, and validation logic in generated SQL. UI semantics – properties like control type or visibility can guide the AI to prefer filtered queries (e.g., hide inactive rows by default) or to shape parameter prompts and WHERE clauses that match what end-users actually see. Template description & intent – short, descriptive text per template (purpose, invariants, edge cases) gives the AI the business intent it needs to generate more accurate and consistent code.How I propose to make this work Expose a compact model export for use in VS Code MVP scope: tables, columns (incl. nullability), primary keys, foreign keys, domains (name, base type, constraints). Optional scope: UI hints (visibility, control), default filters, and template descriptions. Delivery options (any of these would work): Indicium OData endpoint that surfaces a read-only view of the SF model (Indicium already provides an open API and can expose SF branches when configured). CLI/export task that writes JSON files into a repository (consumed by VS Code). VS Code extension that authenticates to the endpoint and injects the model as inline context for Copilot prompts. Use the model export as AI context in the IDE In VS Code, I want to select a template and have the AI read the JSON/endpoint to generate the initial SQL ready for review and refinement. Expected resultsSpeed: AI drafts 70–90% of the SQL, I focus on edge cases. Quality: Consistent use of keys, domains, and defaults; fewer “missing join” or “wrong column” errors. Discoverability: As Thinkwise continues to add AI-powered features (e.g., model enrichments and support for storing LLM embeddings), a model-aware export aligns with that trajectory. Future fit: Community use cases already show value in combining Thinkwise models with LLMs (e.g., natural-language search using embeddings), reinforcing the need for structured model access.  Fri, 02 Oct 2026 09:17:42 +0200 https://community.thinkwisesoftware.com/ideas/web-help-f1-feature-to-universal-3419 As per the Roadmap it was mentioned like 2-3 months ago that the HELP(F1) feature in the WEB GUI is in the backlog to be transfered to Universal. Right now the HELP(F1) is completely gone from the Roadmap. Raising the IDEA to have it in Universal upon receiving the relevant Votes. Thu, 01 Oct 2026 17:35:18 +0200 https://community.thinkwisesoftware.com/ideas/universal-when-the-error-is-too-huge-show-a-snippet-instead-6101 Some errors, especially on views can be huge. This will make it not possible to click on the show database event log unless you zoom out to a tiny zoom level. Please set a maxium for the information thrown. And when too large show a snippet instead. normal zoom:  Zoom level 33% will show the hyper links:   Tue, 29 Sep 2026 15:54:20 +0200 https://community.thinkwisesoftware.com/ideas/file-link-and-universal-open-files-directly-6473 Hi all,In several applications within our environment, we use File link-domains in the Windows GUI to open files stored on a shared network drive. For example DWG drawings, but also PDFs: Drawings that open in AutoCAD / DWG True ViewIn the Universal GUI this does not work in the same way, because the GUI always downloads the file instead of opening it directly in the default application for the specific file type.As we move from the Windows GUI to the Universal GUI, I am curious to learn what other customers have done to address this. Tue, 29 Sep 2026 11:31:54 +0200 https://community.thinkwisesoftware.com/ideas/quick-button-to-take-you-directly-to-search-2057 Be able to assign a quick button to take you directly to "Search". For example assign "F1" button, when pressed,  to take you to "Search" Tue, 29 Sep 2026 11:25:08 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/behavioral-difference-in-default-logic-during-imports-windows-gui-vs-universal-gui-indicium-7019 While transitioning and testing our application from the Windows GUI to the Universal GUI, we noticed a fundamental difference in how Default logic executes during a data import.In the Windows GUI, the @cursor_from_col_id parameter always remains empty (NULL) during an import (where @import_mode > 0), evaluating exactly once per row.In the Universal GUI (via Indicium), @cursor_from_col_id is populated sequentially with the Column IDs currently being processed by the OData Import API. This causes the Default logic to fire multiple times per row.While we understand this stems from the architectural shift to Indicium's server-side processing framework, it breaks or causes unexpected side effects in our existing SQL logic. We would appreciate your insights on the following:- Is this specific behavioral discrepancy documented or mentioned in any specific whitepaper?- What is the best practice for structuring Default logic so that it handles imports predictably via Indicium?  Questions & Conversations Tue, 29 Sep 2026 10:37:55 +0200 https://community.thinkwisesoftware.com/ideas/improve-model-insight-to-same-level-or-better-as-windows-gui-s-path-location-5016 During development I regularly use the Windows GUI to find relevant information regarding screens, columns, parameters, etc. with the Alt + F1 combination (Path Location). Even though the Universal GUI has “Model Insight”, it is lacking many things the other option is giving.I think it is not the intent of ThinkWise to keep the need for using a different GUI to make your Universal GUI product complete. This idea is to make the “Model Insight” improve its usability and hopefully remove the need for a fall back GUI.Current issues or features missing that I am aware of:References more than 1 level deep, do still show the level 1 reference; References more than 1 level deep, do not show table / variant information; Unable to get info when a grid has no records to click on; No context information (Detail, Master, etc.); No Tab Control (What Detail group is being used); No Domain information; No Task name is mentioned, only the parameter as “Column”; No Report name is mentioned, only the parameter as “Column”; Lookup popups give no information, it still show the column/parameter of what it is a lookup on; No Translations. Tue, 29 Sep 2026 10:16:15 +0200 https://community.thinkwisesoftware.com/ideas/deep-links-from-model-insights-to-the-software-factory-7021 This idea originally comes from ​@Harm Horstman, who suggested it in: Right now, Model Insights shows you what you're looking at, but you still have to find it in the Software Factory yourself. Deep links would remove that step and make the jump from runtime to SF instant. The ideaAdd a button next to the copy to clipboard button to all relevant items in Model Insights. Clicking it takes you directly to that object in the Software Factory, such as a table, domain, task, screentype etc.   Tue, 29 Sep 2026 10:14:28 +0200 https://community.thinkwisesoftware.com/ideas/model-insights-window-variable-width-or-resizable-6934 I would like to see the Model Insights window to be variable in size. We use very long names and can only see the first part of it.For example:  Mon, 28 Sep 2026 15:17:49 +0200 https://community.thinkwisesoftware.com/product-updates/release-notes-thinkwise-platform-2026-2-14-7016 Hi everyone,This release extends deployment control to IAM administrators and strengthens governance for delegated and AI-driven access. Note that this release includes several breaking changes, covering the Execute all creation steps parameter order, Indicium file access, and Scheduler and theme behavior.To support safe delegated and AI-driven access, branches can now allow delegated mutations from a personal access token (PAT) or client application. The trace fields now show whether a change came through delegated access instead of directly from a user. The Software Factory also introduces eight default user groups, so you can scope down what developers and AI agents can do.Based on a request from the community, models with a single database type can now always show query details, for instance, to view historical versions of a query.Several quality-of-life improvements round out this release. Indicium can now resolve a lookup when patching a staged resource, and no longer requires create schema and create table permissions on the IAM database. In the Universal UI, keyboard focus improves when opening or switching documents, and Search bars can now be reached with a keyboard shortcut. The new  ‘NOT IN’ filter operator lets you exclude multiple values at once.Thinkwise Platform 2026.3 releases on October 5, 2026, shortly after this release. Because the two versions are released close together, the differences between them are limited.This is a short-term support (STS) release of the Thinkwise Platform. STS release support expires as soon as a new release is made available. For example, support for version 2026.1.12 ends when version 2026.1.13 is released.See our Lifecycle policy for information about supported versions.ContentsContentsContents Before you upgrade Demo and download Breaking Check parameter order of 'Execute all creation steps' calls Restricted file access outside the base path Check custom CSS Check application themes Model Context Protocol (MCP) and AI Models - Allow delegated mutations for a branch Generic - Delegated access trace field Deployment Deployment - Synchronization runs before the tests in Creation New and changed Data - Removed case type setting for columns, task parameters, and report parameters Quality - Description column in Code review changes Processes - Process action 'Activate Search' Access Control - Default user groups for the Software Factory Deployment - Application database name in post-synchronization code Analysis - Changed function point calculation to Easy Functional Sizing (ISO/IEC 25986) Maintenance - Toggle to show query details for single-RDBMS-type models Updated required permissions for Indicium for IAM databases Patch a staged resource with a lookup translation Server timings in response header Removed unused grant types in OpenID metadata document Updated Next.js to 16.3.3 Improved screen component focus Improved Search Show subtitles for focused detail subjects in Open documents Selection order stored for multi-row selections Enforce automatic 'Show top X' limit for cube views Combined filter search with 'Enter' Support for 'NOT IN' operator Model insight includes screen component ID Improvements to column header filter Autofill on fields no longer available Fixed Software Factory and Intelligent Application Manager Indicium Universal UI Data model changes Changes Software Factory Table changes Column changes Changes Intelligent Application Manager Table changes Column changes Before you upgradeFeatures for the Software Factory and the Intelligent Application Manager are only compatible with this STS version of the Thinkwise Platform. Indicium and Universal UI features are backward compatible with previous Thinkwise Platform versions, unless otherwise noted.Demo and downloadTry a demo of the Thinkwise Platform here. Download the latest versions of our components here. BreakingCheck parameter order of 'Execute all creation steps' callsSoftware FactoryAs a result of synchronization running before the tests in Creation, the parameter order of the task Execute all creation steps has changed.The synchronization parameters run_sync, sync_run_type, and sync_target_iam_id now come before execute_unit_tests and execute_smoke_test.If you start the task with named parameters, nothing changes for you.If you call the task directly from the database without parameter names, the values now bind to different parameters. No error message appears, so the task runs with settings you did not intend. For example, the task now reads a call that meant "run the tests, do not synchronize" as "synchronize to storage, do not run the tests."Positions 1 to 14 are unchanged. Following the CI/CD example from the previous release, the new order for positions 15 to 22 is:New parameter orderexecute_source_code_error_handling run_sync sync_run_type sync_target_iam_id execute_unit_tests execute_smoke_test debug job_idUse named parameters to avoid this. Supply every parameter, because the task procedure has no default values. You can pass null for parameters that your selected creation steps do not use:For example:declare @job_id id;exec dbo.task_add_job_to_do_complete_creation @model_id = 'MY_MODEL', @branch_id = '1.12', @execute_complete_creation = 0, @model_vrs_name = '1.13', @generate_definition = 1, @generate_definition_error_handling = 1, @validate_definition = 1, @validate_definition_error_handling = 3, @generate_source_code = 1, @upgrade_method = 0, @write_code_files = 0, @write_prog_objects = 0, @execute_source_code = 0, @runtime_configuration_id = null, @execute_source_code_error_handling = null, @run_sync = 1, @sync_run_type = 0, @sync_target_iam_id = 1, @execute_unit_tests = 0, @execute_smoke_test = 0, @debug = 0, @job_id = @job_id output; Restricted file access outside the base pathIndiciumPreviously, in non-database file storage configurations, file paths outside the configured base file storage path could still be retrieved, downloaded, and previewed.Now, the database record is retrieved successfully, but with an invalid file contract. Trying to download or preview the file now returns an 404 Not Found error.Check that your file paths are within the configured base file storage path. To temporarily restore the previous behavior, set the extended property AllowPathOutsideBasePath to True. Only use this setting as a temporary solution, as it will be removed in a future release. Check custom CSSUniversal UIAs a result of improvements to the Scheduler, the structure of the HTML and the CSS classes used have changed significantly.If you have custom CSS for the Scheduler, review your styles and update the selectors if necessary. Contact support if any selectors are missing. Check application themesUniversal UIPreviously, if a theme only had one image configured for either Light or Dark mode, the Universal UI would display that image for both modes. Now, the Universal UI displays the background color for the mode that does not have an image configured.After upgrading, check your themes in Light and Dark mode to ensure they behave as expected. Model Context Protocol (MCP) and AIModels - Allow delegated mutations for a branchnew Software FactoryIt is now possible to allow a PAT or client application to edit a branch via delegated access on behalf of a developer. You can use this to determine which branches can be edited via delegated access, which is useful for MCP in the Thinkwise Platform.You can find the checkbox Allow delegated mutations in the following locations:menu Model overview > Branches > Form. When you create a new branch via the menu Models > Switch branch. Generic - Delegated access trace fieldnew Software FactoryYou can now see whether a record was changed through delegated access, such as a personal access token (PAT) or an agent with the correct permissions.The trace fields now include a Modified delegated access checkbox. It is selected when the last insert or update on a record was made via delegated access rather than directly by a user. Any manual change to the record clears the checkbox.The 'Modified delegated access' checkbox in the trace fieldsDeploymentDeployment - Synchronization runs before the tests in Creationchange Software FactoryIn the previous release, we added synchronization to IAM to the Creation process. It ran as the final step, after the unit tests and smoke tests. However, during development, you often want your model available in IAM as soon as the application database is up to date. You do not want to wait for the tests to finish. For this reason, we moved synchronization earlier in the process. Moved synchronization before the tests - Synchronization now runs directly after the tab Execute source code, before the unit tests and the smoke tests. Your model becomes available in IAM sooner, so you can continue working with it while the tests run. Because each creation step waits for the previous one, this also reverses which step cancels which. Before, a failed unit test or smoke test canceled synchronization. Now, a failed synchronization cancels the unit tests and smoke tests. Moved the Synchronization to IAM tab - The tab now appears directly after the tab Execute source code (menu Deployment > Creation). Changed the order of the options - In the task Execute all creation steps (menu Deployment > Creation > Generate definition > Current), the synchronization options now come before the test options. The same order applies to the screen Creation presets (menu Maintenance). Your existing creation presets retain their settings after this update, and the new order applies to every creation. Changed the job that the task returns - The task returns the job of the last step in the Creation process. This is now the smoke test instead of the synchronization job. Automation that waits for this job still waits for the whole Creation process to finish. Breaking: Changed the parameter order of the task Execute all creation steps - See Check parameter order of 'Execute all creation steps' calls for more information.  New and changedData - Removed case type setting for columns, task parameters, and report parameterschange Software FactoryPreviously, you could set the Case type to determine the capitalization of text for individual columns, task parameters, and report parameters. This capability has been removed to keep the case type defined in a single place and reduce the risk of inconsistencies. You can still define the Case type for a domain.When upgrading to this version, the existing case type settings for individual columns, task parameters, and report parameters are migrated to new domains. Quality - Description column in Code review changeschange Software FactoryPreviously, the tab Changes in Code review did not show the description of a changed control procedure or template. You can now see this in a new Description column (menu Quality > Code review > tab Changes). It shows the control procedure description or the template description, depending on which object changed.The new 'Description' column in the Code review changes tab Processes - Process action 'Activate Search'new Software Factory Universal UIWe have added a new process action: Activate search (menu Processes > Process flows > tab Process actions). You can use it to activate the Search field in the context of a table. No input parameters are required for this process action.The process action cannot be used as a trigger or starting step in a process flow. It is useful to bring focus to the search field in a table after performing other actions in a process flow. Therefore, it is typically used as the last step in a process flow.For example, after a user selects a record in the main subject, the process flow can bring focus to the search field in the detail subject. This allows the user to continue their work seamlessly.This process action was added as part of Improvements to search in the Universal UI.Screen component tabs are automatically opened by this process action. However, detail tabs must be activated using the process action Activate detail. Access Control - Default user groups for the Software Factorynew Software FactoryYou can now limit what developers can do in the Software Factory using eight default user groups. This helps restrict access for AI agents and lets you scope down roles for specific tasks. For example, you can limit testers to registering test findings only, rather than giving them direct access to the data model, functionality, and more. You can create custom user groups in IAM based on these default roles.application_logic_developer - Writes business logic and behavior: process flows, tasks, reports, functionality, and the dynamic model. data_subject_modeler - Builds the data layer and how it is consumed: table, column, and domain design, plus settings for individual subjects. integration_automation_engineer - Sets up external connections and database- and AI-driven automation: all of integration and AI, plus enrichments and the Thinkstore. platform_model_administrator - Oversees the Software Factory rather than contributing directly: the whole model group, plus the non-QA-related half of Analysis. qa_test_engineer - Verifies quality and its dashboards: the entire quality menu group, plus the test- and validation-related parts of Analysis. rbac_administrator - Sets up who can do what and who they are: everything related to access control and user management. release_deployment_manager - Ships and operates: deployment, plus the operations side of Maintenance, such as runtime configuration, hotfixes, and jobs. ui_ux_navigation_modeler - Sets up the shell around the data, not tied to any one table: modeling the application's UI, navigation, and messaging. Deployment - Application database name in post-synchronization codenew Software FactoryYou can now use the name of your application database in post-synchronization code within a deployment package, using the new variable @tsf_appl_db_name. This variable sits alongside the existing @model_id and @branch_id variables.Post-synchronization code often needs to find or create the application registration in IAM for the database a deployment targets. With this variable, the same deployment package works in every environment, without hardcoding the database name into the code.You can add this code in the menu Deployment > Deployment package > tab Post synchronization code. The Deployment Center automatically sets the variable to the application database name.If you run the generated synchronization script yourself instead of through the Deployment Center, the script carries the SSMS template parameter <@db_name,,> in that position. Fill it in with the application database name to use the variable, or leave it untouched to keep the variable empty.For example, to look up the application database registration for the current deployment:declare @database_id idselect top 1 @database_id = database_idfrom appl_dbwhere db_name = @tsf_appl_db_nameThe variable @tsf_appl_db_name is not available for post-synchronization code for Synchronization to IAM or Synchronization to storage.Deployment application database name in post-synchronization code Analysis - Changed function point calculation to Easy Functional Sizing (ISO/IEC 25986)change Software FactoryYou can automatically calculate the number of function points for your application using the task Calculate function points (menu Analysis > Function point analysis).The task now uses Easy Functional Sizing (ISO/IEC 25986), a streamlined function point standard developed by Nesma (Netherlands Software Metrics Association) that measures the functional size of software. This standard allows you to compare objective metrics across your applications, such as:Productivity - effort hours spent per function point delivered. Cost efficiency - cost per function point delivered. Delivery speed - function points delivered per month.These metrics can be aggregated at different levels to support data-driven decision-making.Our implementation of Easy Functional Sizing (ISO/IEC 25986) is certified by AgileBenchmark. You can request the certification details via your Thinkwise account manager. Maintenance - Toggle to show query details for single-RDBMS-type modelsCommunity idea new Software FactorySince Thinkwise Platform version 2026.2, query data is stored in a dedicated query table per query type, for example tab_prefilter_query for prefilter queries. For models with a single RDBMS type, the detail tab showing this record was hidden because it held only one value.You can now always show these detail tabs, for example to view historical versions of a query. Select Always show query details in the menu Maintenance > Users > tab General.Select the checkbox 'Always show query details' Updated required permissions for Indicium for IAM databaseschange Intelligent Application Manager IndiciumIndicium no longer requires 'Create schema' and 'Create table' permissions on the IAM database from Thinkwise Platform version 2026.2.14 onwards.The following permissions for the database pool user (or maintenance pool user) are sufficient for SQL Server databases:USE db_name]GRANT SELECT, INSERT, UPDATE, DELETE, EXECUTE ON SCHEMA::dbo TO ;Note that creating a new database from the Software Factory does require the additional permission:USE master;GRANT CREATE ANY DATABASE TO Rlogin_name]; Patch a staged resource with a lookup translationnew IndiciumPatching a staged resource now supports resolving a property's value via choose, choose_by_display, or choose_by_element. This is similar to what we already support for patching on a table directly.For example, if you have a column named manager_id, Indicium can now look up the matching key for you, so you do not need to know it in advance. PATCH the staged resource like this:PATCH /iam/<appl>/staged_employee(#) HTTP/1.1Content-Type: application/json{ "manager_id": { "choose_by_display": { "display_value": "<Manager Name>" } }} Server timings in response headerchange IndiciumIndicium now adds server timings in the response header even if the timed action results in an error. Previously, this was not the case; server timings were only added when the timed action succeeded. Removed unused grant types in OpenID metadata documentchange IndiciumIn the OpenID metadata document, unused grant types have been removed to better reflect the capabilities of our OpenID clients. Updated Next.js to 16.3.3change Universal UIWe have updated Next.js from version 16.2.11 to version 16.3.3. This update addresses two reported vulnerabilities, GHSA-2xp9-vwfh-vxw4 and GHSA-p293-qw3h-jr36. Although Universal UI was not affected by either vulnerability, we updated Next.js anyway to include the latest security and performance fixes. Improved screen component focusnew Universal UIWe have improved the initial focus behavior when opening or switching between documents. This update improves keyboard navigation and overall user experience.The focus behavior is as follows: By default, focus is placed on the most top-left interactive component of the main subject. Focus is placed on the Search element whenever the first interactive component is an action bar with a Search element. This allows users to immediately filter data upon opening the document. If the Search element is displayed as an icon, it expands to reveal the search bar. Users navigate away from it using the Esc key. If the action bar has no Search element, focus is placed on the next screen component (for example, Grid, Tree, or Cardlist). This allows users to immediately navigate within the screen component. Focus is placed within a detail tab if it is the most top-left interactive component of the main subject. Tab bars are never focused when opening a document or switching between documents. Users can use F6 or Shift + F6 to navigate to the tabs. When no documents are opened, focus is placed on the menu's search bar. This focus behavior applies in the following situations:Opening a document Switching between documents Opening a document as a Modal document (by using Shift + Click) Opening a document as a Zoomed document (by double-clicking a detail tab)This focus behavior does not yet apply to nested detail tabs or lookup pop-ups. Support for these is planned for a future update. Improved Searchnew Universal UIA Search bar in a screen component can now be quickly focused using the shortcut Ctrl + K. When multiple Search bars are present (for example, if each tab or screen component has one), the priority is as follows:If a Search bar exists on the current tab, this is focused. If not, but a Search bar exists on an ancestor tab, this becomes focused. If not, but a Search bar exists on a child tab, this becomes focused.This also works for icon-only Search bars and even if it is inside the overflow menu. Note that the sidebar menu has its own Search bar, which can now be quickly focused using the shortcut Alt + M.As part of this update, we also added the process action Activate search, allowing you to activate the Search field in the context of a table. See also Process action 'Activate Search'.Use keyboard shortcuts to quickly focus the different 'Search' bars in the Universal UI Show subtitles for focused detail subjects in Open documentsnew Universal UIThe option to add subtitles to open documents was introduced in the 2026.2.12 release, allowing the active record context to be displayed. Open documents now also show the subtitles of focused detail subjects. If the detail subject is nested several levels deep, the subtitle displays a condensed version of its path. Selection order stored for multi-row selectionsnew Universal UIIn grids or trees with multirow selection enabled, the order in which rows are selected is now stored. Any task executed on the selection now receives the selected rows in the order they were selected, instead of in dataset order.The order depends on how the rows are selected:Ctrl/Cmd + click - Rows are ordered by click order. Deselecting a row with Ctrl/Cmd + click only removes that row from the selection. Shift + click - Rows are ordered from the anchor row towards the clicked row, with the clicked row last. Shift + arrow keys - The anchor row is first, and the other rows follow in the order they are added. Reversing direction now correctly shrinks the selection, deselecting rows one by one as the cursor moves back through the previously selected range. Ctrl + A - Rows follow the dataset order. Enforce automatic 'Show top X' limit for cube viewschange Universal UI Software FactoryPreviously, if a cube view had no Show top x value configured, all records would be loaded. This could result in performance issues, especially for applications with large datasets.The Universal UI now automatically caps the number of items displayed on each axis to 1000 if no Show top x value is configured. If you have configured values for Show top x on an axis, those settings take precedence over the automatic limit.The limit applies to all cube views in the Universal UI and is enforced separately for each axis and nesting level. Totals and subtotals still reflect the full underlying dataset, not just the items displayed in the cube view. Combined filter search with 'Enter'new Universal UIFor faster search performance, it is now possible to use Enter after entering a value in the Search field in the action bar to immediately trigger the search action. This skips the delay caused by the configured debounce time. Support for 'NOT IN' operatornew Universal UIYou can now exclude multiple values in Filter pop-ups and Filter forms, using the NOT IN operator. Previously, you could only include values through the IN operator when you applied filter conditions with multiple values. Model insight includes screen component IDnew Universal UIThe Screen section of Model insight now includes the screen component ID. This makes it easier to identify the exact screen component you are inspecting, for example when a screen contains multiple components of the same screen type. Improvements to column header filterchange Universal UIPreviously, the column header filter in a grid listed all domain element values, even if no matching records existed in the current dataset. Now, it only shows values present in the current dataset. If filters are applied to the dataset, the shown values reflect the filtered dataset.Additionally, the column header filter now includes a search bar, allowing users to quickly find specific values within the filter options.The column header filter now includes a search bar Autofill on fields no longer availablechange Universal UIPreviously, selecting a field could suggest values that a user previously entered in similar fields. This type of suggestion and autofill is browser-specific behavior and unrelated to, for example, the Software Factory's own controls with suggestions and autofill.We have removed the browser-specific suggestions and autofill. This prevents unwanted behavior where autofill was not working as expected or other fields were cleared after an accepted suggestion.Due to technical limitations, Safari is not included in this change and will still show autofill suggestions based on saved contact information. A user can choose to turn this off in Safari's autofill settings.A browser may still prompt the user to generate and save passwords when entering a value in a password field. If the user disables password management for their application, this should no longer happen. For example, in Chrome this can be done by selecting Never when prompted to save a password:Example: Select 'Never' when prompted to save a password FixedSoftware Factory and Intelligent Application ManagerThe Software Factory allows you to translate check constraints, so you can define a custom error message per language for each constraint violation. Since the introduction of support for multiple RDBMS types for a model in the Thinkwise Platform 2026.2 release, these translations have not been displayed correctly in the user interface. This has been fixed. Previously, if an encrypted Web connection was edited, the Layout logic still required the Password field to be entered, resulting in failed attempts to save the edits. This has been fixed. Previously, an attempt to start a model synchronization to IAM without configured pool user credentials would result in an error message stating that it had been canceled. However, the synchronization run would still proceed and be reported as successful, even though no synchronization had effectively taken place. This fixes an issue already mentioned in the 2026.2.13 version release. Previously, a variant default value query override for a column, task parameter, or report parameter returned NULL through the Indicium interface view. This happened when there was no base default value query, and it led to incorrect behavior. This has been fixed in the platform improvements for week 37, 2026. IAM was not affected. The overall performance of the i_ui_col view in the Software Factory has been improved, resulting in faster screen loading times when developing your applications.IndiciumContent type values for Web connection endpoints rejected charset=utf-8 specifications. For example, text/xml worked, but text/xml; charset=utf-8 did not. This has been fixed. Web connections still only support UTF-8 encoding, so a different charset still results in an unsuccessful status code. DB2 Deleting a record could fail when the subject had an expression field and a SQL authorization prefilter. This has been fixed. Fixed an issue where the Application connector process action returned incorrect status codes if the target database did not exist and Azure Active Directory authentication (for example, Managed Identity) was used. This affected process flows that rely on the status code, such as the Creation screen in the Software Factory. As part of this fix, the Provision database connector timeout has been increased from 30 seconds to 5 minutes. This prevents the provisioning step from failing due to a timeout. Previously, the printing orientation configured in the Software Factory was ignored. This has been fixed in extra release Indicium 2026.2.13.1. The configured orientation now takes precedence over the orientation of the document itself. If you set an explicit orientation, check your printed output. An incorrect setting is now visible in the print result.Universal UIFor the Scheduler:Improved the performance of the Scheduler, for example: when opening a Scheduler, navigating to the next or previous time frame, and when expanding or collapsing all items in a hierarchical Scheduler. Resources are now displayed in the same order as they appear in the dataset. If one of the Activity linked columns (Title, Tooltip, Start date or End date) is within the sort columns, activities within a resource are now displayed in the same order as they appear in the dataset. If vertical space can be saved by moving an activity into an otherwise empty time slot, this will take precedence over the dataset order. Fixed an issue where the conditional layout of a child resource would not be applied after its collapsed parent was expanded by the user. Fixed an issue where the red arrow and line indicating the current time would sometimes be placed incorrectly, for example at the start of the slot for hour "10:00" even though the current time was '10:59'. The Today, Previous, and Next buttons have been moved to the left of the Scheduler toolbar. This aligns with where these buttons are typically placed in other calendar applications. For Scheduler resources that did not use the full height of the Scheduler, a bottom border is now displayed for the last resource to show the end of the resource. Fixed an issue where the Scheduler toolbar would sometimes be sized incorrectly. This occurred in cases where many Scheduler views were configured or if a Scheduler view had long translation labels. Scheduler views with Hours set as the highest timescale now open on the current hour, instead of incorrectly opening on an earlier hour. The arrow and line indicating the current time are now correctly positioned relative to the current hour. Fixed an issue where the first timescale headers (e.g., "2026" or "August") sometimes had a gray background color. Fixed an issue where time cell borders sometimes had a doubled width when cell colors were configured. Previously, when certain network requests were delayed, it was not possible to drag an external row on a Scheduler. This has been fixed.  For cubes:In pivot tables, the highest-level series was not always collapsible or expandable. This has been fixed. In pivot tables, subtotals would sometimes be missing in series. This has been fixed. Weekdays were not translated in a cube, so 1 was displayed as 1 in the user interface. This has been fixed. For example, 1 is now shown as Monday for series and categories, depending on the translation in the Software Factory and the user language.For grids:Previously, when a field in a grid row was changed using a Combobox control before the record was saved, Indicium could apply default values to other fields in the same record (for example, filling in a date or checking a checkbox). These updated values were not displayed in the grid until the record was saved. As a result, the row appeared unchanged despite the defaults being applied. This has been fixed. Previously, for a grid column with checkboxes, the Filter icon could incorrectly show that a filter was active. This could occur, for example, when selecting and clearing the same value in the dropdown until all values were checked again. This was a display issue only, as filtering itself worked as expected. This has been fixed. Previously, executing a task on all selected rows of a page in a grid could cause performance issues. This could occur when Page size was set to a high value, for example 1000 rows. The Universal UI sent a separate request for each selected row, even when the selection matched all rows shown under the current filter. This has been fixed: the Universal UI now sends a single request for the entire selection. Previously, the search terms in Filter form fields using the IN operator could still be removed when the grid was in Edit mode. This has been fixed. Previously, when editing a row in a grid, read-only cells with a lookup had no icon to open a pop-up to view their values. Now, it has one. In a future version, read-only cells with a look-up will be displayed as hyperlinks instead. In some cases, navigating to a different page in a grid would cause the detail tab to display the wrong data. This has been fixed. Previously, automatic refreshes after editing a record, executing, or cancelling a task could override the user's manually selected active record. This occurred if the user selected a different record before the refresh completed. This has been fixed. When Add in grid row was enabled and a checkbox was changed in a copied row, the checkbox in the original row changed too. This has been fixed.For filters:The NOT BETWEEN operator now includes NULL values for column filter conditions in the Filter pop-up, Filter form, and prefilters. Previously, the value entered in an active field would disappear when scrolling down in a Filter pop-up with more than 20 fields. This has been fixed. Previously, Indicium could not provide searches on the columns Date, Datetime, and Time. This resulted in the columns not appearing as searchable columns in the search bar tooltip in the Universal UI. This has been fixed. Previously, the activation of a custom Prefilter was not remembered between sessions. In a new session, it was always inactive. Now, it is remembered.Other fixes:In some cases, the code editor control would not display any content. This has been fixed. Previously, when clicking outside the input window in an HTML or Multiline pop-up editor, any available default procedures were run instead of waiting for the pop-up to be closed. This also happened when the user made an edit in an HTML pop-up editor and then selected one of the available styling buttons. This has been fixed. Previously, the following controls would not adhere to their width setting if they were empty or in edit mode: Email, Url, Phone Number, and Google Maps. This has been fixed. On macOS, Cmd + Click now selects rows in multiselect grids and trees, matching the Ctrl + Click shortcut for Windows. Fixed an issue where exporting selected rows with an invalid OData URL would fail if the primary key was a Date, DateTime, or Time column. When Set tab icons is disabled, icons are no longer requested when rendering a detail tab.Data model changesData model changes for the Software Factory and IAM meta-models are listed here. This overview can be used as a reference to fix dynamic control procedures, dynamic model code, or custom validations after an upgrade.A complete overview of the data model changes is available in the upcoming Thinkwise Platform 2026.3 release next week.Changes Software FactoryTable changesSF - From table SF - To table install_code_file - Column changesSF - Table SF - From column SF - To column Mandatory Default value branch - allow_delegated_mutation 1 0 col case_type - - - control_proc_log - no_of_reads 0 - control_proc_log - no_of_writes 0 - control_proc_log - cpu_time 0 - deployment_run - iam_rdbms_type 0 0 disk_sync_job - iam_rdbms_type 0 0 function_point_analysis_function path - - - model_vrs - from_branch_id 0 - model_vrs - from_model_vrs_id 0 - model_vrs - definition_generation_finish_date_time 0 - model_vrs - archived_date_time 0 - prog_object_item_parmtr - parmtr_value_hash 0 - prog_object_parmtr - parmtr_value_hash 0 - rdbms - is_iam_rdbms_type 1 0 report_parmtr case_type - - - role use_for_ai_assistant - - - sync_target_iam - rdbms_type 1 0 task_parmtr case_type - - - usr - always_show_query_detail 1 0 Changes Intelligent Application ManagerTable changesIAM - From table IAM - To table - appl_db_deployment_run - appl_db_deployment_run_log - prog_object install_code_file - Column changesIAM - Table IAM - From column IAM - To column Mandatory Default value appl_db - last_deployment_run_id 0 - branch - model_vrs_id 0 - branch - from_branch_id 0 - branch - from_model_vrs_id 0 - branch - definition_generation_finish_date_time 0 - branch - archived_date_time 0 - branch - model_last_modified_date_time 0 - branch - model_last_modified_type_of_object 0 - global_settings - appl_db_deployment_run_retention 1 90 msg - alt_transl_msg_id 0 - role use_for_ai_assistant - - - Mon, 28 Sep 2026 09:41:44 +0200 https://community.thinkwisesoftware.com/news-blogs-21/getting-started-with-mcp-6923 With Thinkwise Platform STS 2026.2.12, MCP support lands as a beta feature. Connect Claude, or any other MCP-compatible AI tool straight to the applications you build on the Thinkwise Platform: your data, your logic, your rules, with your application roles and IAM doing the security work.If you have never touched MCP before, you are in good company, and you will not be figuring it out on your own. This guide assumes zero prior knowledge and walks you, step by step, from what MCP is through your first authorized chat with your own application's data.Grab a coffee. In about twenty minutes your AI assistant will be able to query live data straight from your own application, and only the data your IAM roles allow. Once you get there, tell us what you built. We are learning what works best from the same use cases you are. What is MCPMCP stands for Model Context Protocol: an open standard that lets an AI assistant call out to external tools and data sources in a structured, predictable way. Instead of copying data into a chat window, the assistant asks your application directly, through a defined set of actions you control.MCP is not an AI or a language model on its own. Think of it as a connector standard: it defines how a chatbot or agent talks to a server, not how that chatbot thinks. Indicium can now act as that server, exposing your application's data and logic as MCP tools that Claude, or any other MCP-compatible client, can call.Every call still runs through your platform's IAM roles and access delegation. The AI never sees more than the connecting user is authorized to see.Under the hood, this is simpler than it sounds. Indicium exposes a single MCP endpoint, typically something like https://your-indicium-host/mcp, and that is the one address your AI tool connects to. On first connection, Indicium walks the AI through an OAuth flow using the client application you registered in IAM: the AI presents the client ID and secret, your user signs in and grants consent, and Indicium returns a token scoped to exactly the roles you authorized. Every request after that, whether the AI is reading data or running a task, goes through that same /mcp endpoint and is checked against your IAM roles before anything happens.For more information, see: PrerequisitesBefore you start, make sure your environment is on these versions:Thinkwise Platform STS 2026.2.12 or later Indicium 2026.2.12 and Universal UI 2026.2.12 Indicium setupThe setup we recommend is simple: make Indicium reachable from the public internet. That might sound bold, but it is exactly how we run things ourselves. Every Thinklab and Thinkwise Cloud environment is already internet-facing, not tucked away on a local network, and it holds up fine.That includes development environments. Indicium authenticates and authorizes every request before it touches your data, so opening up a dev environment carries the same protection as production, and it should not introduce meaningful security risk.If Indicium runs on-premises, it's also worth confirming that the server can resolve its own external hostname over DNS. This is easy to miss, since it doesn't affect normal inbound traffic, but it can break outbound calls Indicium makes to itself.On-premises DNS occasionally has no record for that external name, so the call fails even though the server is reachable fine from the outside. It's a rare issue, and it's usually a quick fix for your system administrator: add an internal DNS record, or a hosts file entry, that resolves the external hostname to the server itself.Tip: Turn on single sign-on (SSO) wherever you can. It adds a layer of security and makes login painless for your users. LocalNot every environment can be open to the internet, and that is fine. MCP also runs locally, against an Indicium instance on your own machine or network.The trade-off is reach. Most browser-based AI tools cannot open a connection to something running locally, so your options narrow. Concretely, that rules out Claude's and ChatGPT's browser and mobile apps, and it rules out automation platforms like n8n too: none of them can reach a server sitting on your own machine. For this scenario, we recommend Claude Code with the Claude CLI, both of which run your local Indicium without issue. IAM setupMCP authorization runs entirely through IAM & Indicium. Three switches need to be set correctly before your first connection will work: user authorization, application authorization, and the client application itself. User authorizationEvery user who will connect an AI assistant needs delegation rights. Open the user record in IAM and enable Allow access delegation for each user you want to give MCP access.Enabling access delegation on a user record Application authorizationThe application needs the same switch. Open the application record and enable Allow access delegation there as well.Enabling access delegation on the application recordThen authorize each relevant role for both User groups and Access delegation. Skip one and you will not be able to authorize that role's scope for MCP later, so it is worth double-checking both boxes now. Client application setupIAM treats every external system that authenticates against your platform as a client application: a registered identity with its own name, secret, and permissions, separate from any individual user. Your MCP connector is just one more client application, so it gets set up the same way any other integration would.In IIS, the setting Load User Profile settings needs to be set to True for the Indicium Application Pool. For more information, see the Client applications documentation.Open the client application screen and create a new client application with the following settings:Creating a new client application in IAMGive it a clear name. You will reuse this name as the client ID when you connect the MCP connector to your AI tool later. This name should not include any spaces or special characters. Enable the client, set API access to “Limited access”, turn consent on, and switch offline access on.Using a client secret is optional for most AI clients. If you set the client application to be a public client anyone with the correct URL and client application ID can connect to the /mcp endpoint. IAM authorization is still respected and people will only be able to actually use MCP if they have the proper authorization set in IAM.We recommend using a client secret when you configure an MCP connector for your entire organization and make it available to internal employees only. In all other cases - especially when users need to configure the MCP connection themselves - we recommend using a public client application. To set a client secret, open the Secrets tab and create a new client secret. The MCP connector uses this secret to authorize itself when it connects.Treat this secret exactly like a production credential. Store it in a password manager or secrets vault, never in a chat log, command history, or shared file.Allowed login redirectsIn the Allowed redirects tab, I add the following record: http://localhost:8080/callbackThis field is essentially a guest list: once your user logs in, IAM only hands the result back to a web address on this list and rejects anything else. That is what stops a login response from ending up somewhere it should not.Which address belongs here depends on how you are connecting. Running Claude Code locally on your own machine, as in this guide, means the login result comes back to that same machine, typically an address like http://localhost:8080/callback (the port can vary depending on how the tool is set up), but this can be different for your environment.Connecting through a cloud-hosted AI tool instead, such as Claude.ai in the browser or the Claude desktop app, means the result goes to a fixed address the vendor publishes, for example https://claude.ai/api/mcp/auth_callback, rather than to your machine.If you are not sure which one applies, start with checking the AI chatbot /  tool’s own setup screen: it will often show you the exact address to add at the point where it asks for your client ID and secret. You can add more than one record in this tab, so feel free to list one for every tool or environment you plan to connect with.Access delegation roles Finally, open the Access delegation roles tab and enable every role you want available through MCP.Enabling roles for the client application under Access delegation roles Adding a custom MCP connector to your AI of choiceWith IAM configured, you are ready to point an AI tool at your new MCP connector. The options below all work the same way, but reachability decides which ones you can use. An internet-facing Indicium opens up the full list. An Indicium that only is accessible from inside your own network limits you to Claude Code based solutions for now.Claude web and desktop appTo successfully configure a Thinkwise MCP connector in Claude web or desktop you need to be running at least Indicium version 2026.2.14, released on the 28th of September 2026.Both clients run in Anthropic's cloud, so they can only reach an Indicium that is published to the public internet. An internal-only accessible Indicium will not work here.Claude currently looks for the authentication endpoints at the root of your host. We recommend placing Indicium in a subfolder (such as /indicium). To make this work with Claude, add three redirects at server level:/.well-known/...  => /indicium/.well-known/.../authorize => /indicium/connect/authorize/token => /indicium/connect/token Now add the custom connector in Claude. Open the Customize screen from the menu, go to the Connectors tab, click Add, and select "Add custom connector".Adding a custom connector from the Connectors tab in Claude.Enter a name and the URL of the /mcp endpoint of your Indicium.Entering the connector name and the URL of the /mcp endpoint.Click Continue to reach the authentication screen. "Sign in now" is selected by default. For the OAuth client, choose "Use your own OAuth client": two fields appear, where you enter the client application ID and the client secret you configured in IAM.Selecting "Use your own OAuth client" and entering the client ID and secret.To make Claude connect properly also set up the redirect URL for Claude in your client application. At the time of writing these are: https://claude.ai/api/mcp/auth_callback and https://claude.com/api/mcp/auth_callbackAdd the Claude redirect URL’s to your client applicationClaude then asks you to connect to your server. Press Connect. Indicium opens, where you authenticate and confirm the roles available to MCP.Authenticating in Indicium and confirming the roles available to MCP.Indicium sends you back to Claude, where the connector now appears in the list. I recommend turning on the always allow option for every tool the connector exposes, so a chat never stops to ask for approval mid-answer. That is it, your connector is ready to use.The connected connector in Claude, with always allow enabled for its tools. Claude CodeThree pieces of software need to be on your machine before you can add the connector:Visual Studio Code (only when using Claude Code in Visual Studio Code) The Claude Code extension for Visual Studio Code (only when using Claude Code in Visual Studio Code) The Claude Code CLIAlready have all three installed? Skip ahead to Install using chat below.Choosing a Claude Code clientYou can run Claude Code in multiples places, for example the Claude Code extension in Visual Studio Code, or the Code tab in the Claude desktop app. Both run on the same engine, so your MCP connector works identically in either one. The choice is personal. The Visual Studio Code extension suits developers, especially if you are also using RDBMS plugins in VS Code. While the Code tab in the desktop app is the easier starting point for everyone else and is presented in a more user friendly way.Claude desktop set to Claude code modePermissions in Claude CodeThe first time an MCP tool runs, Claude asks your permission. That is expected: it is the same guardrail that protects any file Claude touches on your machine.You might also be asked to save a file to disk now and then, if Claude decides that is more efficient than holding everything in memory, or if it needs to filter a dataset that is easier to work with as a file. Set your comfort level in the permission selector at the bottom right of the chat bar. The default mode asks before every tool call, Auto approves routine actions automatically, and Bypass permissions skips confirmation altogether, so pick the one that matches how much you want to supervise.Setting the permission mode in Claude Code's chat bar Install using chatYou can add a connector straight from chat. Open a new chat window and send the prompt below. I have also included this prompt as a skill in the attachments, this makes it more reusable if you have more than one MCP environment that needs setting up. Claude will ask, step by step, for the information it needs: your Indicium URL, the client ID (the client name you chose), and the client secret. It will then use that information to create the MCP connector in your Claude Code installation.Only add MCP connectors through chat when the Indicium is not publicly available. Otherwise we recommend using the Claude web / desktop app to add it as described above.Note that the below described MCP Manager tool provides a more user friendly way to configure local MCP servers.install an mcp connector using the following instructions:# Install an MCP connector in Claude CodeSet up and authenticate a custom MCP connector in Claude Code. Ask thequestions in Step 0 one at a time before doing anything — do not assumedefaults for values the user hasn't given you, except where marked "default."## Step 0 — Gather configurationAsk, in order, waiting for each answer before asking the next:1. **Server name** — the alias to register this connector under in Claude Code (e.g. `sf_mcp`). This name must be used consistently in every step below (add, get, config lookup, `/mcp` selection) — do not let the add command use a different name than later steps reference.2. **MCP endpoint URL** — the full transport URL (e.g. `https://<host>/<path>/mcp`).3. **OAuth client ID.**4. **OAuth client secret** — tell the user it will only be exported into the current shell session as an env var, never echoed, logged, or written to a file.5. **Callback port** (default: `8080`) — only needs to change if the server's OAuth client has a different redirect URI pre-registered.6. **OAuth discovery document URL** (default: `<mcp base URL without /mcp>/.well-known/openid-configuration`) — ask only if the user says the default path doesn't apply.7. **Config scope** (default: `user`) — `user` registers the connector once for every project on this machine; `local` restricts it to the current project only. Ask only if the user wants something other than `user`.Call the collected values `{{SERVER_NAME}}`, `{{MCP_URL}}`, `{{CLIENT_ID}}`,`{{CLIENT_SECRET}}`, `{{CALLBACK_PORT}}`, `{{DISCOVERY_URL}}`, `{{SCOPE}}`below. Derive `{{RESOURCE_BASE}}` by stripping the trailing `/mcp` pathsegment from `{{MCP_URL}}`.## Step 1 — Export the client secret for this shell sessionThe variable name is `MCP_CLIENT_SECRET` — fixed, not derived from theserver name. `claude mcp add --client-secret` reads only this name; anythingelse fails with *"No TTY available to prompt for client secret. SetMCP_CLIENT_SECRET env var instead."*(bash)```export MCP_CLIENT_SECRET="{{CLIENT_SECRET}}"```(PowerShell)```$env:MCP_CLIENT_SECRET = "{{CLIENT_SECRET}}"```Agent shells generally do not persist environment variables between toolcalls. Run this export and the Step 2 `add` in a **single** invocation(`;`-joined in PowerShell, `&&`-joined in bash) rather than as two steps.## Step 2 — Add the MCP server```claude mcp add -s {{SCOPE}} --transport http {{SERVER_NAME}} {{MCP_URL}} \ --client-id {{CLIENT_ID}} \ --client-secret \ --callback-port {{CALLBACK_PORT}}````-s {{SCOPE}}` is not optional — with no `-s`, `claude mcp add` defaults to`local`, which registers the server for the current project only.`--client-secret` with no value reads from the env var set in Step 1.`--callback-port` pins the OAuth redirect URI to`http://localhost:{{CALLBACK_PORT}}/callback` — required whenever theserver's OAuth client has that exact redirect URI pre-registered.## Step 3 — Add discovery metadataThe entry's location in `~/.claude.json` depends on the scope used inStep 2:| Scope | Path in `~/.claude.json` ||---|---|| `user` | top-level `"mcpServers"` → `"{{SERVER_NAME}}"` → `"oauth"` || `local` | `"projects"` → `"<project path>"` → `"mcpServers"` → `"{{SERVER_NAME}}"` → `"oauth"` |Locate the entry by searching the file for `"{{SERVER_NAME}}"` rather thanassuming either path. Under its `"oauth"` object, add:```"authServerMetadataUrl": "{{DISCOVERY_URL}}"```## Step 4 — Discover and pin scopes dynamically (do not hardcode)Do not type out a fixed scope list. Query the server itself for what itcurrently advertises, then write that into the config:1. **Query the server for its current scopes.** GET the OAuth protected-resource metadata document (RFC 9728), which is unauthenticated: ``` curl -sS "{{RESOURCE_BASE}}/.well-known/oauth-protected-resource" ``` This returns JSON with a `scopes_supported` array. If it 404s, retry against the MCP path itself: ``` curl -sS "{{RESOURCE_BASE}}/.well-known/oauth-protected-resource/mcp" ``` If both fail, ask the user to paste the scope list manually and skip to step 5 below.2. **Check for an existing scopes value.** Read `oauth.scopes` at the same scope-determined location as Step 3 — top-level `mcpServers.{{SERVER_NAME}}.oauth.scopes` for `user` scope, `projectse"<project path>"].mcpServers.{{SERVER_NAME}}.oauth.scopes` for `local` — or a `.mcp.json` in the repo for project scope. It's likely empty/absent on a fresh add — that's expected, just treat the server's list as entirely new.3. **Diff before writing.** Compare the server's `scopes_supported` array against any existing `oauth.scopes` string. - If they already match, say so and skip to Step 5 — nothing to change. - If this is a fresh add, or the server list only adds scopes, note what's being granted. - If scopes are being removed/narrowed from a prior value, note that too.4. **Confirm before granting.** Since this is a first-time authorization (or a widening one), use AskUserQuestion to show the discovered scope list and confirm before writing it — especially anything that reads like a write/approve/send/manage/create/delete capability. Don't silently apply an OAuth grant the user hasn't seen.5. **Write the config precisely.** Set `oauth.scopes` for `{{SERVER_NAME}}` to the confirmed list, joined with single spaces, in the server's own ordering: ``` "scopes": "<scope1> <scope2> <scope3> ..." ``` Do this with a targeted string replacement (Read the exact surrounding lines first, then Edit) — do not round-trip the whole `~/.claude.json` through a JSON parser/serializer, since it's a large shared file and reserializing risks reformatting unrelated content.6. **Validate.** After editing, parse the file (e.g. `Get-Content -Raw ~/.claude.json | ConvertFrom-Json` or `python -c "import json; json.load(open(...))"`) to confirm it's still valid JSON and that `oauth.scopes` reads back as expected.## Step 5 — Verify registration```claude mcp get {{SERVER_NAME}}```Expect `Status: Needs authentication`, the configured `client_id`,`callback_port {{CALLBACK_PORT}}`, and a `Scope:` line matching`{{SCOPE}}` (`User config (available in all your projects)` vs`Local config (private to you in this project)`).If `{{SERVER_NAME}}` is missing entirely, first confirm which scope it wasactually added under — re-run `claude mcp get {{SERVER_NAME}}` and read the`Scope:` line, or `claude mcp list` from the directory in question. Do**not** resolve a lookup miss by duplicating the entry under severalproject-path key variants: `JSON.parse` keeps only the *last* duplicatekey, so the added entries are inert, and strict parsers (PowerShell's`ConvertFrom-Json`) reject the file outright. If a project-scoped entry isgenuinely unreachable, re-add it with `-s user`.## Step 6 — AuthenticateClaude Code enumerates MCP servers at session start, so a server addedmid-session will not appear in the current one regardless of what the configsays. Tell the user to **restart or reload the session first**, then run`/mcp`, select `{{SERVER_NAME}}`, and complete the OAuth login in thebrowser window that opens. Claude Code should then report the server asconnected.Remind the user: this only registers the scopes in config — the actualOAuth token is issued during this authentication step, so it must run*after* Step 4's scopes are written, not before.## TroubleshootingIf authentication fails with "Client secret validation failed", **removeand re-add** rather than editing in place:```claude mcp remove {{SERVER_NAME}} -s {{SCOPE}}```then repeat Step 2. Claude Code links the stored client secret to a hash ofthe server's config — editing the URL or secret directly in`~/.claude.json` without going through `claude mcp` can silently orphanthat link.**Changing scope after the fact** requires a remove and re-add:`claude mcp remove {{SERVER_NAME}} -s <old-scope>`, then repeat Step 2 withthe new `-s`. Steps 3 and 4 must then be **redone**, because `claude mcpadd` writes only `type`, `url`, `clientId`, and `callbackPort` — the`authServerMetadataUrl` and `scopes` added by hand do not migrate to thenew config location and are silently lost.**If the MCP URL 404s**, check the transport scheme before anything else. Acorrectly configured OAuth-protected MCP endpoint answers an unauthenticatedPOST with `401` and a `WWW-Authenticate` header; a plain `404` (especiallyan IIS error page) usually means the path is not served over that scheme atall. Retry the same URL over `https://` before assuming the path is wrong. Note: Claude installs the connector by running PowerShell scripts through the Claude CLI. It will ask, repeatedly, for permission to run each one. Allow them, or set your permission mode to Auto or Bypass permissions as described above.Once the connector is added, open a new chat session, type /mcp, and select MCP servers. Your new connection appears with the label "Needs authorization." Click it, then click Authorize. This opens a browser window to Indicium, where you authorize your user with the rights they are allowed to use. Click Allow at the bottom of the screen.That is it, your MCP connector is live and ready to use. MCP managerManaging which MCP connectors are installed, authorized, or need their scopes refreshed can get fiddly from the command line alone. I built a small companion app to make it visual, and I think it is useful enough that I want to share it.The app lists every MCP connector installed in Claude on your computer, lets you add, remove, or refresh connections, and walks you through adding a new one with a short wizard.One important caveat: this is not an official Thinkwise application. There is no support ticket system for it. It is a personal project I am sharing because it makes my own life easier, and it might make yours easier too.You can find the companion app and setup instructions in this GitHub repository.The first time you open this application Windows might not allow you to open the application because of SmartScreen. In the properties of the executable enable Unblock. Then you can open the application.The MCP manager companion appChatGPT with OAuthChatGPT connects to your MCP connector through OAuth as well. Like Claude's web app, it runs in the cloud, so it needs an internet-facing Indicium. Set it up once in your workspace settings and the connector becomes available to every user in your organization.In your workspace settings, open the Apps screen and click Create.Create a new applicationNow configure the app. Name and description are free text, so pick something your users will recognize. Point the connection URL at the /mcp endpoint of your Indicium, set authentication to OAuth, and check "I understand and want to continue".Next, open "Advanced OAuth settings" and set the registration method to "User-defined OAuth Client". Enter the client ID (the client application name you chose in IAM) and the client secret you configured there.Setting up the MCP connector AppChatGPT then shows a callback URL, at the time of writing https://chatgpt.com/connector_platform_oauth_redirect. Copy it and add it to the Allowed login redirects tab of your client application in IAM. Skip this and IAM rejects the login: the callback is not on its guest list.The ChatGPT callback URL added to the allowed login redirects in IAMClick Create. The app lands on the Drafts tab of the Apps screen. Open it and click Publish to make it available to your users.Publishing the draft app to make it available to your usersEach user need to connect once before the connector works in chat. Open the Plugins tab in ChatGPT, select your new plugin, and click Connect. ChatGPT sends you to Indicium, where you sign in to your application and authorize ChatGPT to use your roles. That is it, your connector is ready to use in any chat.Connecting the plugin from the Plugins tab in ChatGPTEach user connects once before the connector works in chat. Open the Plugins tab in ChatGPT, select your new plugin, and click Connect. ChatGPT sends you to Indicium, where you sign in to your application and authorize ChatGPT to use your roles. That is it, your connector is ready to use in any chat.Creating a personal MCP app from the Add menu in the Plugins tab Authorization through Personal Access TokensNot every client speaks OAuth. Some skip it entirely, others support it only through Dynamic Client Registration (DCR), which the Thinkwise Platform does not support. When a client accepts a Personal Access Token (PAT) instead, that token can be your way in.There is one major downside to using Personal Access Tokens: everyone using the connector in that client authenticates with the same token, so every action lands in your application and Software Factory logs under one single user.This is why we recommend against Personal Access Tokens for production applications. You lose the ability to trace an action back to the person who triggered it. For AI agents running in the background the risk is smaller: those usually run under a service account anyway.The rule of thumb: use OAuth wherever the client supports it, and fall back to a Personal Access Token only when you have no alternative, for example when your organization permits one specific tool and nothing else. Never for users on a production application.ChatGPT Web & DesktopToday, ChatGPT connects only with a Personal Access Token. OAuth support for ChatGPT and Codex is on the roadmap.Adding an MCP connector to ChatGPT requires access to your organization's Workspace settings. Go to "Apps" and click Create. The first time, ChatGPT asks whether you want to enable ‘developer mode’, click yes.Creating an app in the ChatGPT workspace settings.Once connected, the plugin appears in each user's plugin overview, ready to use in chats. The first time someone opens it, ChatGPT asks them for a Personal Access Token.The connector in the plugin overviewIn a new chat, click the plus button in the chat box and select the MCP connector as a source.Selecting the MCP connector as a source in a new chat.Microsoft Copilot StudioCopilot reaches the Thinkwise MCP server through an agent, and you build that agent in Microsoft Copilot Studio.Start by creating a new agent.In the create agent screen, click the Tools button in the top right corner to add a new tool to the agent.Opening the Tools screen while creating a new agent in Copilot Studio.Click Add and select the Model Context Protocol (MCP) option.Selecting the Model Context Protocol (MCP) tool type.Now configure the MCP server. Server name and description are free text, used only for display. Point the server URL at the /mcp endpoint of your Indicium. Set authentication type to "API key", header name to "Authorization", and the key value to "Bearer IYOUR_PAT_TOKEN]". Click Add.Configuring the MCP server name, URL, and API key authentication.In the connection screen, click Create new connection.Creating a new connection for the MCP tool. Add the authorization key again, with the value formatted as "Bearer tYOUR_PAT_TOKEN]".Entering the authorization header value as Bearer plus your token.A successful connection appears. Click Add to create the MCP tool, and it shows up in the list of tools.Our custom MCP connector has been added as a toolFinally, give your agent a name and a description. This screen also takes context and skills, which is where you steer how the agent behaves. Test it in the preview tab, and once it works as expected, publish it and use it in Copilot.MistralMistral can be an interesting option because it is one of the few options to run a European model. In our experience this model is however not up to the level of Claude and ChatGPT.To configure a new MCP connection, in Mistral, select "Connectors" in the menu on the left.Open the connectors screenOn the right, click "Add connector" to open the connector marketplace, then click "Add custom connector".Adding a custom connector from the Mistral connector marketplace.Set up the connector by entering the connector name and the server, pointing at the /mcp endpoint of your Indicium. Set Authentication type to "API Token Authentication" and paste your Personal Access Token into the "Authorization header value" field. The type is already set to Bearer by default.Configure the MCP connectorClick Add connector, and Mistral adds it to your account. Allow all of the displayed tools so you are not prompted for each one while you chat.Allow all tools to be used, this prevents you from being asked during a conversation.ScopesWhat are scopes?A scope is simply the set of access delegation roles your client application is allowed to use. When Claude first authorizes against your MCP connector, it requests exactly those scopes, no more and no less, and your user consents to them in the browser.Scopes need a refresh any time you change the roles available to the client application. Add or remove a role in IAM, and the MCP connector keeps using the old scope list until you tell it to fetch the new one.How do you refresh them?You have three ways to refresh scopes after changing a client application's roles:Chat: ask Claude directly. Tell it to retrieve the scopes from the MCP server and update the local scopes, then reauthorize when it prompts you. Skill: use the attached skill, included with this post, so you never have to remember the exact phrasing. MCP manager: click the refresh scopes button.Whichever route you take, the browser flow that opens requests scopes fresh from IAM's current configuration. If consent is enabled on the client application, the updated scope list appears right there on the consent screen, your confirmation that the new scopes made it through.The road aheadThis beta is the starting point, not the finish line. MCP becomes an officially supported feature in the 2026.3 release, and that release also opens the Software Factory itself up to MCP, so your development environment gets the same AI-native access your application data has today. Every release after that keeps making the implementation faster and lighter on your infrastructure.Now it is your turn. Install a connector, point Claude at your application, and see what it finds. We would love to hear about it: which use case pulled you in, and where MCP started saving you real time.This post will keep growing, too. I am adding step-by-step guides for more platforms and AI tools over the coming weeks, and I will drop a comment below whenever a new one goes live. Please tell us in the comments which platform you would want to see next. Using MCP Server in a Production environment will require an amended license agreement with Thinkwise, as Agentic AI via MCP typically automates and replaces human user interaction. MCP Server will be freely available in Develop and Test environments to empower you to experiment with MCP for end users and speed up development in the Software Factory. News & Blogs Mon, 28 Sep 2026 08:29:36 +0200 https://community.thinkwisesoftware.com/product-updates/platform-improvements-for-week-39-2026-7017 Hi everyone!We’ve released the following platform improvement this week: SF 2026.2.13, 2026.2, 2026.1, 2025.320260921 - i_ui_col view performance improvement The interface view i_ui_col gives all kinds of column related information to Universal. The view has a complex structure that caused SQL Server to abandon the search for a good execution plan, degrading the performance of the view. We have revised JOIN related parts of the view which reduced the complexity, allowing SQL Server to more optimally determine a suitable execution plan. The performance of the view on the SF metasource has improved. Fri, 25 Sep 2026 11:57:22 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/cube-refresh-after-filtering-7012 After entering a value in the filter form for a specific cube field, the cube does not seem to refresh. Pressing the refresh button on the action bar also results in no activity.I can only get the cube to refresh when I swap to a different tab (chart in this case) and back to the pivotgrid.What am I missing here? Questions & Conversations Thu, 24 Sep 2026 08:02:34 +0200 https://community.thinkwisesoftware.com/ideas/add-validation-for-lookup-column-with-rights-but-are-not-available-6860 When you have assigned rights to a column that has a lookup and later you change the lookup display column, the column becomes unavailable and effectively has no rights anymore. I made a validation to detect columns with lookups that have rights but are unavailable, please add this to the validation basemodel.--Lookup has rights, but is not availableselect rco.* from role_tab rt join role_col_overview rco on rco.model_id = rt.model_id and rco.branch_id = rt.branch_id and rco.role_id = rt.role_id and rco.tab_id = rt.tab_id where rt.model_id = @model_id and rt.branch_id = @branch_id and rt.select_granted = 1 -- own table has rights and rco.col_access_type in (0, 1) --0=edit, 1=read only, 3=hidden and rco.available = 0 and rco.look_up_source_tab_id is not null and rco.sf_type_of_col <> 3 -- meta hidden fieldWhat also could be considered is to automatically assign rights when changing a lookup display column that previously had rights. Wed, 23 Sep 2026 16:05:17 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/zoom-detail-in-universal-7010 Hi,I have a main grid (complaints) and a detail grid (complaint actions).This detail grid in my test shows 3 records: Scrolling thru the community I discovered that instead of double clicking on the row (as we used to in the Windows GUI) we need to double click on the tab!?When I do that I always get to see the contents of the first row, not the contents of the selected row!?I suspect that this isn't what it is supposed to do?Might it be that this is caused by the fact that we are still on platform version 2025.1 and universal gui version  2026.2.11.1.0 ? Or is this something else? Any ideas? Questions & Conversations Wed, 23 Sep 2026 14:45:18 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/how-to-create-a-tree-view-in-universal-6966 Struggling to even get a tree to shape no matter the options I set, I hope someone could advice me how to get this test scenario to work.I have a view that has the following columns:parent_id child_id grand_child_idAll columns make the PK.In an example this is the data (with lookups):  I want to see something like (structure example, formatting is just for clarity):Parent A--Child A----Grand child A----Grand child B--Child C----Grand child CParent B--Child D----Grand child D----Grand child EI have changed the “Tree” settings under “Subject”. I have tried all combinations at “Tree” under “Component”. Chose different options for “Sort” with and without “Group until”.The screen type has the “Tree” as its component.All it ever shows is: Platform 2026.2I have compared it to an older product that still has the Windows GUI where a tree does work, but to no avail.What do I need to set to get the result as desired? Questions & Conversations Wed, 23 Sep 2026 10:24:58 +0200 https://community.thinkwisesoftware.com/ideas/code-search-more-options-for-debugging-6983 Code search is a great tool, but it gives too much results. For debugging a problem in a live application a lot of the results are irrelevant. Most time i only want to see task templates, triggers and procedure templates. To find which task/trigger etc affects a certain table. My suggestion would be:add a checkbox: exclude non-assigned templates (active by default)add a checkbox: exclude gui templates (this only shows code that would impact results, so only templates for tasks, procedures, subroutines, triggers (i might forget one here?)  Wed, 23 Sep 2026 09:01:23 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/use-value-from-other-field-as-default-for-field-in-form-6914 We have a form with settings for customers that is used for 2 types of customer, where one of those is basically a parent to the other. For a lot of fields the rule is that the setting of the parent is valid as long as the field is empty in the form of the child.This works fine, but we would like to be able to show the value that is used for the parent in the form of the child so it is clear which settings are used for the child.I think this basically means we would like to use an expression as the default for the childs form. That way we can show the parent's value without actually having to copy and store the value to the field on the form of the child.  Questions & Conversations Tue, 22 Sep 2026 11:42:40 +0200 https://community.thinkwisesoftware.com/ideas/print-pdf-files-on-linux-platform-6020 Currently printing files is only possible from Windows. To increase platform indepedence I would like to see file printing implemented on Linux as well.Follow-up for:  Tue, 22 Sep 2026 10:33:39 +0200 https://community.thinkwisesoftware.com/ideas/split-iam-sync-into-generation-and-execution-and-make-it-part-of-the-creation-screen-5500 When we do our upgrades (every 3 weeks) of our applications we take the application offline (deactivate in IAM) right before we execute the source code on the database and we put it back online after the IAM sync.However as time goes on our model grows and the IAM sync action in SF is taking up to 8min right now, the majority of that time goes into generating the sync code. If we could generate the sync code separately from the actual sync this would decrease the required downtime for upgrades by a big percentage because you could generate the sync code before taking the application offline. On top of that it is pretty easy to forget to do an IAM sync, it would be nice to have it part of the creation process/screen.  Mon, 21 Sep 2026 08:01:12 +0200 https://community.thinkwisesoftware.com/ideas/set-focus-to-filter-field-on-open-event-universal-screen-1394 In the mobile-GUI the filter-field automatic gets focus.In the Universal-GUI no field has focus. By setting the focus to the filter-field, the user can use a barcodescanner to enter data (without first having to give focus to the field). Thu, 17 Sep 2026 11:33:02 +0200 https://community.thinkwisesoftware.com/news-blogs-21/thinkwise-platform-as-mcp-server-6912 Since launch less than 2 years ago, the Model Context Protocol has become the de facto standard for integrating systems with LLM chat interfaces or AI Agents. MCP Servers are popping up everywhere, in varying quality when it comes to capabilities, security and governance. Either software vendors offer an officially supported MCP server, or else unofficial (often vibe-coded) MCP Servers pop up.As with any runtime component, an MCP Server for the Thinkwise Platform should work for all customers and all applications. Developing such a dynamic component takes a bit more time, but in return a Thinkwise-provided MCP Server works for all customers, all Application models and all future changes to your Application out-of-the-box. And since we develop the Software Factory and Intelligent Application Manager (IAM) with the Thinkwise Platform as well, we can implement MCP for the Software Factory and the Intelligent Application Manager in a similarly fast fashion as you can for your applications.We have made the MCP Server capabilities of the Thinkwise Platform part of runtime component Indicium, no separate installation is required to get your hands on this new technology. From a functional perspective we rely as much as possible on existing features in the Software Factory and IAM, mainly Roles and Client applications. This is our Technology-as-a-Service promise at its best: as soon as you upgrade to a supported version, MCP can be utilized!MCP will be launched in BETA with Short-Term Support (STS) Platform version 2026.2.12 and become an officially supported and licensed feature with Platform version 2026.3. More details on required setup will be shared in a separate blog. MCP democratizes integrationThe Model Context Protocol is often referred to as the USB-C for applications: one standard connector to power applications with AI capabilities. The OData protocol is a similar standard for REST APIs, but requires technical expertise by the user and is much more rigid to use. MCP places the responsibility and burden of integration at the supplier of the API, instead of the consumer of the API.The key differentiator of generative AI + MCP is that users can use natural language to interact with organizational data in an iterative manner. Essentially, this enables any user to set up an integration with an application and use a language they know to put that integration to work with trial and error. Without generative AI you needed to be capable of using a technical language like OData and without MCP you needed to know exactly how to construct the URL Endpoint and the JSON Body of the call.Now, all that’s needed is an AI tool that supports this (for example Claude Desktop, Claude Code, OpenAI Codex, Copilot Studio), is Setup MCP Server > Authenticate > Grant permissions and the user is ready to go!MCP as translatorMCP begs to be applied to compelling use cases, but where does it shine? Generative AI and related tooling is not a silver bullet and not a solution to all integration problems, but it does hold the promise of solving problems that couldn’t be solved before!MCP shines at the translation layer between structured and unstructured data: turning unstructured input into structured data, or structured data into something a person can read. A plain-language support request becoming a properly filed ticket. A pile of transaction data becoming a great visual report. An agent processing a messy email into a draft order.Compelling use cases include:Easier & interactive search and summary of data Performing specific actions like booking hours or processing meeting summaries Automating repetitive actions like processing an incoming PDF invoice Informed interaction with an AI agent like a Support agent that helps triage an IT issue AI-driven Development to speed up and improve Software DevelopmentMore elaborate examples of compelling use cases will be shared in a series of follow-up blogs.MCP poses risksBefore going all out on MCP, it’s important to mention the risks that AI imposes. While people tend to refer to generative AI tooling as if it has some sort of personality ("he"), it is wise to be aware of the fact that it’s a trained mathematical model that algorithmically predicts the next best word or action.Importantly, AI at this stage can’t substitute for human judgment or experience. In other words: "AI is as good as its user" and AI doesn’t suffer consequences for being wrong. An extreme example of the potential negative impact is the deletion of the entire Production database of PocketOS.For business-critical applications built with the Thinkwise Platform this means that you shouldn’t want your users or AI agents to connect to an unofficial MCP server and hand out credentials and entire permission sets in the process. Instead, you should treat any MCP-connected user or AI agent as less knowledgeable than your most junior hire initially.While it makes sense for any human being that "write all open hours" refers to booking 8 hours for each past working day, AI might as well decide to book hours for 24 hours for each past or future day available. Or worse, "clear approved invoices" for a finance person might mean paying these invoices, while AI might as well decide to delete the invoices altogether without ever paying them.Enterprise-grade Thinkwise MCPApplications built with the Thinkwise Platform are business-critical, which is why we prioritized providing an enterprise-grade MCP Server solution with granular controls that allows you to mitigate the above-mentioned risks. We utilize Client applications in IAM, authentication via OAuth 2.1 or Personal Access Tokens (PAT), and granular permissions based on IAM applications, users, and roles that explicitly need to Allow access delegation.We recommend applying the Principle of Least Privilege and putting a Human-in-the-Loop for any AI-powered workflow, especially in the beginning stages. More specifically, we recommend creating and granting access to delegated Roles with permissions for Read data or Create data / Execute tasks (that result in data with concept status), but not for Update or Delete of existing data to begin with.The initial implementation of MCP supports a core feature set of the Thinkwise Platform, including CRUD on subjects (variants are not exposed via MCP), Execute (table) tasks, and Data authorization pre-filters.RoadmapMCP will be launched in BETA with STS Platform version 2026.2.12 on the 3rd of August and become an officially supported and licensed feature with Platform version 2026.3.During the MCP BETA you get to experiment with MCP for customer Applications, and we continue to improve the capabilities and efficiency. In parallel, we implement MCP support for the Software Factory with Release 2026.3. This includes an authorization and logging concept (tsf_is_delegated_access) and a granular setup of Roles in the Software Factory.In parallel with our MCP development, many of you have been experimenting with custom MCP servers, AI-assisted development on the Software Factory and the use of Skills. We have already offered a Skill to update your Dynamic code with Release 2026.2 and are now testing to what extent Skills prove to be needed in addition to MCP integration with the Software Factory. We anticipate Skills over MCP will be adopted soon, and intend to use that to distribute Software Factory-related Skills in the future.Using MCP Server in a Production environment will require an amended license agreement with Thinkwise, as Agentic AI via MCP typically automates and replaces human user interaction. MCP Server will be freely available in Develop and Test environments to empower you to experiment with MCP for end users and speed up development in the Software Factory.We look forward to your implementation of compelling MCP use cases! News & Blogs Thu, 17 Sep 2026 09:43:23 +0200 https://community.thinkwisesoftware.com/questions-conversations-78/turn-off-hyperlink-for-image-in-form-6991 For an image-upload control, is it possible to disable the hyperlink/download feature in the form (read mode)? It is annoying that clicking anywhere on the field opens a new browser tab with the image while the user is never interested in downloading the image in this case.In the example below, the image field is the full width of the page, so clicking anywhere right of the actual image opens a browser tab with the image.We already tried setting the ‘Show action button’ to ‘When editable’, but this doesn’t seem to have effect.   Questions & Conversations Wed, 16 Sep 2026 13:52:05 +0200 https://community.thinkwisesoftware.com/ideas/navigation-buttons-previous-next-for-details-4887 A use case that happens ins many cases is where you have the grid with a detail tab with the form and other elements. For the user It's quite cumbersome to be going back and forth every time he wants to see the details of a couple of items in a row. I really miss the previous and next navigation buttons in the detail, where you can jump easily to the next or previous item in the context without the need to go back.  Wed, 16 Sep 2026 13:08:22 +0200