Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
In a process flow you can choose different actions, like activate form and activate grid, but you cannot choose to active a card list, we are missing this because in some situations we only show the card list and the form, and not a grid, and we want to send the user back to the “overview” which in this case is a card list.https://docs.thinkwisesoftware.com/docs/sf/process_flows_actions#activate-gridactivate-form
Currently task “Code difference” has been disabled for Control Procedures with same name, same baseline, updated in both branches.As we have a lot of these situations it would be very helpful if we easily could compare both code-files and make decision.So please always enable the task in case the object-type and object-name is equal.
Currently Universal loads all data from the table or view that the user has access to, regardless if the data is shown in the table or not. In our experience this massively increases the load on the database, not only when using views that have logic and many sources in them but especially when you have a table/view that has many relations with other tables with lookups defined. Every lookup creates a join or an apply. We even ran into situations where the query became so complicated that compiling the query by the SQL engine was taking multiple seconds (4+) while if I take the query thats been generated by Incidium and alter it to only include the columns that are actually shown the compilation only takes about half a second. The plan is barely cached due to parameters + the fetch offset being used in the front end. I can supply TW with example query thats been generated and my altered version if requested. Suggestion:Only load the actual data being shown instead of the entire row(s)
I would like to use the open lookup action (clicking the lookup icon) as a start action for a process flow.This would allow us to guide user actions when they click this icon.We often find that users click this icon while editing or adding a row because the lookup column did not display the object they needed. So they open the lookup and often need to disable a prefilter to see the rows they needed. Our users complain that this is hard to understand and to much of a hassle.With a process flow we would be able to automatically disable prefilters when they open the lookup, making the entire process more intuitive. Using a process flow for this allows us to configure which prefilters should be disabled and which may remain active.Implementing this also opens up all kind of nice features since so many things are already possible using process flows. We could also configure it to send a user to a form in edit mode so they can immediately add a missing row without any extra clicks for example.To illustrate how this feature could help, I have an example we are all very familiar with:Lets say I’ve been asked to review code in a branch that currently isn’t active for me. The ‘Branch’ lookup column doesn’t contain my colleagues’ branch so I open the lookup:It’s still hidden by the prefilter, which I need to disable to find the branch. This particular lookup is quite slow for us so this entire process is slightly infuriating.It would be very nice to immediately have the prefilter be disabled by a process flow so I only have to wait once and to save me a click.
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.
At this moment, if I state in the SF that a detail is not visible, the parameter to make it visible is not offered to the context procedure, and the settings in the SF database always win.This has 2 disadvantages;1) If we change the visibility in the SF and forget to recompile the context procedure, we get an error.2) If the internet is slow, or something goes wrong the user can see tabs, the user should not see. ( We have one place where we switch between 10 tabs … ).It would be nice to have 3 or 4 states; show, don’t show, or only show when the context stored procedure wants it, with “this” as default ... 4 states would be possible with one additional checkbox.This is kind of related to my previous idea, but technically requires more. User preferences can differ, and I like to build by enabling things, instead of disabling things. ( We have a row based security on top of the Thinkwise security… that is an important reason why I would like to have the possibility to only show things when the stored procedure allows it ).
I was just reading “filtering in a pivot grid”, and remembered that I had this Idea.If you have a list and a detail, you can select multiple items in the list, but the detail is only linked to the main focus item.I have a use case in which it would be great if you could expand this to, this key or … that key, or …, etc.With a filter it is possible to have a filter to select multiple options, but this could be less clear to the user, and the fact that it is not possible to make the filter mandatory makes that we can’t use this option. We have a large “fact table”, and I’m looking for a clear way in which a user can select some options to query, without ever selecting everything. The user should not start with everything, but with nothing. If you have a graph, and 1000 categories, you don’t want to start with “show everything”.If the graph would be a detail of a list with categories, the user could select one category and see the graph, or use the control key to select more.
At this moment there is a big limitation on how you can build a screen.Each new detail is a rectangular box with a new layout. One thing I would like to be able to do is this;---------- --------------------------------- A---------- C B----------- ---------------------------------With a relationship A → B → CWith the current screen engine this is not possible, and it will become; ---------- A---------- --------------------------------- B C----------- ---------------------------------It would become possible to create different screen layouts, and give much more freedom if a detail area could be linked to another detail area, instead of the main subject, within one screen.I understand that implementing this would be a huge change, but it would give much more freedom.
It is very annoying when a model import fails because of invalid characters in the model.I did a invalid XML character test, but pipe symbols in Screen Type ID's were not detected. Errors also occurred for Runtime Configuration ID's with brackets in it.It would be better to enforce a proper validation in the model export routine.
Enrichments and the AI that comes with it are a great tool to improve functionality of the SF. Troubleshooting these can be cumbersome however. Please add the last X results from AI/DB data. This makes troubleshooting a lot more efficient. Not sure how much data it would store if a request becomes too large. So maybe add a parameter setting for how much days/rows to keep. This goes for the tables: enrichment_run_ai_dataenrichment_run_db_data
The HTML control in the Universal is very limited, a user cannot do anything HTML like. It would hugely increase its value when it's something like there in the forum, where you can do text layouts including colors, links, quotes etc…
Currently we have two variations when it comes to uploading documents to an application. One where the documents are placed in the filesystem and one where filestreams are used. In the first one it is possible to resize images when needed, but it's all manual labour. But when filestreams are used, this is no longer the case. We are not to keen on limiting the size of uploads, but some users go absolutely mad it seems. We could use different Storage types & locations for various upload columns and limit what kind of files (extensions) are allowed in a default procedure. But it would help if we could resize images on the flight when they are beïng uploaded. I've seen JPEGs that could cover a decent size wall when printed, which is totally unnecessary. If the upload control could automatically resize these kinds of images (dimensions, number of colors, DPI etc) based on a setting that's made on a Storage type or on domain level, would be a great feature. Various examples can be found on the web. Limiting anything else than images, that's up to the organisations policy.
In Windows GUI, the translation is used for detail tabs, incl. case sensitivity In Universal, are only CAPITALS used? Why? Please make this consistent with Windows in order to comply with our styling guidelines
The good part about working the the Thinkwise platform for quite some years now is that you build up a lof of reusable parts. However it is very difficult to extract reusable parts from a model, export it and import it as a reusable base model. Two main ideas:Most basic, export model for environment A and import in into environment B, if the base models are not available in the new environment import fails. Also when a base model has a different name. In this case in both environments the date_helper was downloaded, however in one it had a different name. More powerful, and if you really want to become a 10x developer ( @Arie V ) is to have the ability to export a part of an existing model to reuse in a different model or even better create a base model of it. Now it's pure manual labor to or remodel the things you want in a new model, or copy the whole model and clean up the parts you don't want. All manually. Being model and relation driven, a nifty solution to pick a table, a menu item or starting point as such, and determine everything you need to export everything that relates to it. Another thing I would love to see is to have a function/procedure repository. The overhead of the Thinkstore model download is too large. You end up with 50 base models, all with 1 or 2 functions/procedures etc.. that do generic stuff. Would be great if for example the functionality/subroutine parts could talk with a type of github repository that could be forked. No need to import full models, just reusable pieces of SQL code.
When using the “Export” option in the GUI it uses the name of the window you are exporting the data from for its filename. It would be nice to also allow a custom name to be entered.Probably the screen where you choose the File format is the location this optional field would fit nicely.
Quite often users need to upload multiple files from Windows Explorer and/or Outlook (attachments). I wish there was something like a ''Multi File Upload" control, with drag & drop, that enables this. After this I like to handle each incoming file with a process flow. Or is there already a workaround, to achieve this?
As an IAM administrator, I want to see the last and next scheduled runs directly from the list of available system flows, so that I can quickly understand the execution timeline and sort flows by these dates for easier management.Additionally, I would like a dedicated screen (e.g., "Scheduled Runs") to view all upcoming runs across all system flows, so that I can gain a complete overview of future runs for the next day, week, or month without having to check each system flow individually.This will significantly enhance usability and provide better insights for managing scheduled flows.
In the list Scheduled systemflows I am missing a few columns that could make life a bit easier. The query to show the list already has the fields I am looking for, but the GUI doen't show them. I am talking about Schedule_id, last run and next run to be added to the list. These columns combined with a pre-filter like “Unscheduled flows” would make it much easier to find jobs that may need attention (an active schedule for instance) or may be marked as no longer needed for a next release of the application…. Query result of non scheduled jobs Query result of scheduled jobs
I would like an option to invoke the standard import functionality through a process flow or another method. Currently, the import/export function is hidden behind the three dots, making it difficult for some users to find. It would be great if this functionality could simply be started from a regular task.
Having search and pre-filters together, it makes much more sense to move the filters also to those 3 dots And maybe also manage prefilters
As an export sometimes can take quite a while or you want to limit a user in its (export) options, it would be nice to have a process flow action “Export” that can take care of this.This way you can define the settings beforehand and possibly have it run in the background.A nice benefit could also be that you do not need to put the actual table/view as a screen in the GUI.
I have made a Conditional layout rule that highlights values in the (nullable) Year end and Year end old columns if they are different, the condition being specified as such:This produces the following result in the application. I think it is unintuitive that the two null values get marked as Not equal to each other. I understand this is how sql works, and I think it would be useful to allow tsf users to specify that null values should be marked as not equal to each other.This could be done with a manual null check:t1.year_end = t1.year_end_old or (t1.year_end is null and t1.year_end_old is null)for Equal to, or simply something like isnull(t1.year_end, '') = isnull(t1.year_end_old, '')This option to enable Null value comparison in this way would be toggleable with a checkbox.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK