Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
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.
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.
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
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.
Currently text parsed to the parameter is handled straight as given. In some cases when you would show there some text like name of a company having special characters, then the message is not coming properly.When for example giving the input ‘<text>ROLLER Gmbh & Co. KG</text>, then the message comes incorrect showing like:To make it correct, you have to replace the '&’ with '&amp;’ before parsing it to tsf_send_message.Would be good if these special characters are handled within the tsf_send_message. Otherwise you have to implement a custom procedure as wrapper to do the replacement
I try to manipulate the filename of a SSRS report by with a default procedure, but it seams impossible.The file path is not accepted, the filename colors red and an error message occurs: What is the right approach to achieve this?In addition I like to mention that in the WebGUI I am not able to change the filename of the generated PDF report with the default procedure.For example to add a time stamp in the file name. (e.g. 20230628_083405_WeekReport.pdf)The documentation is also not clear, the property names do not match and it is not clear what is the difference between the properties File Path and Export PathFile specification = File Path ?Export location = Export path ?
In the past the filters in the role screen in the Software Factory worked different than how they currently work. When you would enable the prefilter “Read only rights” it also displayed the objects/tables for which you had set more than the read rights, for example update or insert.Currently those tables are only shown when you enable the prefilter “Full rights”. I can understand that you would like a prefilter that only shows table/object for which the read rights checkbox is checked and the insert, update and delete are disabled.However quite often I would like to filter on tables for which at least rights are checked. Currently this can only be done by manually filtering on the read checkbox.Could you please reintroduce a prefilter that shows all tables for which the read checkbox is enabled?
Would be very helpful to have a filter: has rights.There is a filter: full rights and a filter read-only rights. But a filter has rights (might be full, might be read only), would be helpful.
Currently after running a Platform upgrade the indexes on the IAM are fragmentated. This is the result of pushing the new IAM and/or SF model into IAM. Without executing a TSF optimize to rebuild the indexes and statistics, the loading of my applications is not as fast as it should be.I would like to see the TSF optimize step as a part of the Platform upgrade itself, instead of having to run it manually.After synchronizing the model into IAM, it should also optimize the indexes. This in order to prevent a performance issue.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.