Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
What we need A grid view where the columns are a resource (channel, room, stage), the rows are time slots, and each record is a block in its column. The top of a block is its start time and its height is its length. Our use case For live surgery at our congress, we run several channels at the same time. We want an overview with one column per channel and the day's time down the left, so it's clear what is live where at any moment and where there are gaps or overlaps. Today we can only show this as a list or a table. That works, but you can't see at a glance what runs in parallel.Why it's useful beyond our case The same layout fits room and stage planning, staff rosters, equipment bookings and booth or meeting-slot planning: anything where several resources are scheduled side by side over a day.Nice to haveConfigurable time step (for example 5, 15 or 30 minutes) and day range
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.
Current situation We have a screen with a Cube (master) and multiple detail tabs. The cube itself is read-only, while the underlying data is modified via the detail tabs (using Edit in grid or Drag & Drop between details).Whenever a change is made in one of the detail tabs, the parent cube automatically refreshes to reflect the updated aggregates. During this refresh: The cube's scrollbar jumps back to the top. The visual highlight of the previously selected cell is lost. Interestingly, the detail tabs retain their filtered data, which indicates that the cube still knows which cell/context holds the focus in the background—it is simply not reflected visually in the UI anymore.Proposed solution When a Cube refreshes due to changes in a detail subject (or a general refresh where the selected coordinates still exist): Automatically scroll the cube back to the position of the active/focused cell so the row/column is back in view. Visually re-apply the cell selection highlight to the active cell. Business value / Impact When users are actively planning or adjusting records in detail tabs based on cube totals, losing the visual anchor in the cube forces them to manually scroll and search for the cell they were just working on after every single edit. Retaining the visual focus and scroll position will significantly improve usability and speed up data-entry workflows.
Problem / Current situation Currently, when viewing a Cube with many rows in the Universal GUI, the Grand Total row scrolls out of view along with the rest of the data.While we can set the Total position to Near (placing the Grand Total at the top instead of the bottom), the row still disappears as soon as the user scrolls down through larger datasets. The same applies to the Grand Total column when scrolling horizontally across wide cubes. This forces users to continuously scroll back to the top/bottom or left/right to verify overall totals while analyzing detailed records.Proposed solution Add an option (either at the Cube View / Pivot settings level in the Software Factory and/or as a user toggle in the Universal GUI) to freeze/pin the Grand Total row and/or column so it remains visible as a sticky header or footer while scrolling through the pivot table.
IdeaThe Software Factory already supports smart upgrades, which upgrade only what has changed. I'd like the same principle for unit tests: when running an upgrade or a creation, only execute the unit tests of objects that were affected by the changes, and run the full set separately.WhyWe now generate a large share of our unit tests with AI, which makes our test suites many times bigger than when we wrote them by hand. On one application with about 125 tables we have around 1,500 unit tests, and a full run takes 30 to 40 minutes. While it runs, the branch is occupied: we can't generate the definition, so development on that branch stops for the duration.Most of that time is spent for nothing. In a typical change only a small part of the model is touched, yet every test is executed, including the tests for the large majority of objects that did not change at all.ProposalSmart run during upgrade/creation. Only run the unit tests whose object is affected by the changes since the last successful run. Ideally this includes dependencies: a test on a task that calls a changed subroutine should also run. Full run on schedule. The ability to schedule a run of all unit tests, for example nightly, so the full regression still happens without blocking development during the day. Full run on demand. Keep the option to start a full run manually, for example before a delivery or release.ResultShort feedback loops during development, no idle time on the branch, and the full safety net still in place where it matters: nightly and before delivery.
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.
We would like to have the ability to show table tasks on a grid line. This is especially useful for the mobile GUI and when just a couple of table tasks are available. Currently you can show tasks on the top or bottom of a grid in mobile. To start a task for a specific record you should select a line first and then select the concerning task. In the described case it is faster to select the task direct on the line. See print screens for further explanation. Task on top of grid (current situation) Example tasks on grid line
It’s not possible to give weekend days a background. That helps planners in their overview of there planning.It now can be done in CSS, but if you could add a simple option in the scheduler : Highlight weekend days eventual with the colornumberWhen this option is turned on, the css code is added to the css file when generating the application.Or is this too simple?
We regularly see expression columns or prefilter with heavy constructs that effect the performance. So it would be nice if we can review expression columns and prefilter just like control procedures. Which would include the following features: · Approve/disapprove prefilters and expression columns · Add comments when disapproving prefilters and expression columns
Thinkwise Guideline validations (found in the Thinkstore) are an important tool for improving the quality and consistency of our models. They help developers follow best practices and highlight potential issues early in the process.Currently, these validations are available in the Thinkstore, but they need to be manually added to each project. This increases the chance that teams don’t use them, missing out on valuable guidance.By including these validations by default in every new project, we make sure all projects start with the same important checks in place, helping teams build better, more maintainable applications from day one.
For our applications, we would like to use as much of the screen as possible.End users will have multiple document open at the same time, sometimes on a relatively small screen.To give the end users some more screen space, we would like to set the default setting of the sidebar menu in the Universal GUI as collapsed.So when they open the application, the menu is automatically set as collapsed.Side bar menu fullsizeSide bar menu collapsed
After adding a field or parameter, all associated stored procedures must be updated, because else error messages will appear when using the appropriate task or table after refresh. Very often it is then a matter of going through the following steps: 1. generate 2. execute The code generation can be done once for multiple control procedures. As far as I know, executing the code, must be done 1 by 1 and takes a relatively long time. A task that automatically performs the 2 steps in sequence for all selected control procedures would be great and speed up the development of applications.
AI came up with the following proposal: Summarytsf_optimize touches every index and every modified table on every run, regardless of whether there is anything to gain. On larger databases this makes it slow while doing almost nothing useful. We propose adding thresholds (with parameters and safe defaults) so that it only maintains indexes and statistics that actually need it.Observed situation (customer database, SQL Server, ~100 GB)Run time of tsf_optimize: 2 h 22 min. After the run: ~850 indexes (~54 GB) have 0.2–0.9 % average fragmentation, but all of them are REORGANIZEd every run because the only rule is frag <= 30 → REORGANIZE. The actual REBUILDs (83 indexes > 30 %) are all tiny (< 1,000 pages, 14 MB in total) and take seconds. Afterwards UPDATE STATISTICS <table> runs for every table with modification_counter > 0, including large temporal history tables (5–7 GB each), and also for tables whose indexes were just rebuilt (and so already have fresh full-scan statistics).Why the current logic is costlyNo lower bound on fragmentation. An index with 0 % fragmentation still gets a REORGANIZE. That read is pure overhead. No lower bound on size. Small indexes (< ~1,000 pages) gain nothing from defragmentation. Microsoft and the common maintenance scripts skip them. REORGANIZE is the expensive path for large indexes. It is single-threaded and fully logged, and LOB_COMPACTION = ON also reads all LOB pages. Running it on every large index costs time, log volume and I/O, and in AG/log-shipping setups also extra log traffic. Statistics are updated per table, for any change, and twice after a rebuild. A single modified row triggers a statistics update for the whole table. Statistics already refreshed by an index rebuild are updated again, and with sampling, so the full-scan statistics from the rebuild are replaced by sampled ones.Proposed changes# Change Default 1 Skip indexes below a minimum fragmentation @frag_low = 5 (%) 2 Skip indexes below a minimum size @min_pages = 1000 3 Keep the REORGANIZE/REBUILD boundary, but make it configurable @frag_high = 30 (%) 4 REBUILD ONLINE = ON when the edition supports it (Enterprise, Developer, Azure SQL); otherwise keep the current behaviour automatic 5 Update statistics per statistic (UPDATE STATISTICS t s), not per table, and only when the change is significant relative to the row count e.g. modification_counter > 0.1 % of rows or the SQL Server dynamic threshold (sqrt(1000 * rows)) 6 Skip statistics of indexes that were just rebuilt automatic 7 Optional: @max_duration_minutes to stop starting new operations after a time limit null (no limit) Expose the thresholds as optional parameters with these defaults. Existing calls without parameters keep working, and customers can tune them without overriding the template.Expected effectOn our database the run would drop from about 2 h 20 min to minutes. Hardly any index is above 5 % fragmentation after the first run, and statistics are only refreshed where needed. The index and statistics quality stays the same, because the skipped work does not change anything measurable.Does this hold in all cases?Skipping low fragmentation and small indexes (1, 2): yes, safe everywhere. The worst case is that an index with slightly more than 0 % fragmentation stays as it is, which is the standard in Microsoft guidance and in Ola Hallengren's scripts. On SSD storage, fragmentation matters even less. REBUILD vs REORGANIZE (3, 4): depends on the edition. On Standard Edition, REBUILD is offline and locks the table, so REORGANIZE (online) remains the right choice for applications in use 24/7. That is why the boundary should stay configurable and ONLINE should only be used when available. Statistics (5, 6): yes, safe everywhere. AUTO_UPDATE_STATISTICS keeps covering the rest. Customers with very skewed data may want a lower threshold or FULLSCAN, so this should be configurable. Very small databases: no noticeable gain, but no harm either. Other RDBMS (DB2, Oracle, PostgreSQL): this proposal only concerns the SQL Server template.
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?
We are in the process of porting our application from the Windows platform to the Universal UI. In Windows the resource scheduler (extender version) has the functionality to delete an activity with the delete key.Can the functionality to select an activity and then delete it via the keyboard also be implemented in the universal version?
This is just a small pet peeve of mine, because in my mind I always have “Merge sessions” so I type “Merge”, but then the actual menu item in the SF does not show up. Not sure if it is possible to include it in the search, maybe by putting the word merge in the description and then including the description in the search?
We would like to be able to rotate Markers on the Maps component, ideally based on a column value in the Maps view. This allows us to display our vessels in the exact direction they are heading (now they all sail east):An alternative solution would be for us to use custom CSS, but due to the fact that the CSS transform property is already used by the default Maps component, we don't seem to be able to do that at the moment.
We would like to dynamically set the zoom level of the map per row.Sometimes this would be automatic, but the most ideal would be to be able to link this via a zoom level column, so that we can control this ourselves based on the data.
Our user finds the scrollbar too thin to easily drag with the cursor, especially when doing horizontal scrolling.Of course there are options like using the scroll wheel, but many users aren’t accustomed to horizontal scrolling shortcuts.For people with disabilities it can be especially difficult to get the cursor on narrow spots.The compact/comfortable option currently does not affect scrollbar size.It seems that in browser settings it is not possible to adjust scrollbar size.We could apply custom CSS but (application wide) custom CSS is not preferred.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.