Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
In requirement management it would be nice that they are editable in the list. Can you make this possible in the SF?
Why is the UI of the breakpoints different from the normal way of working? You now have a + symbol on the first line and every time you somewhat in that line the line is added. Deletion can only be done from the lint menu. I think this is weird behaviour and inconsistent…I suggest to use the normal naviagion bar to add breakpoints
Wouldn't it be nice if we have knowledge on the location of a task in the code context? Now I have tasks that are coupled to more tables en views and there is not easy way to have this knowledge to work with in a default, layout and task.
I found the setting ‘Developer mode’ in IAM. In the Windows GUI this gives you the extra tab ‘Developer’. Unfortunatelly you won't get debug information. It would be nice if the developer mode in IAM works the same as the ini-parameter setting.
We would like to be able to hide a task on a form but show it on the task bar of the grid. I understand this is not possible right now but would be great. For example, we have a task for creating a XML export of a list of records. It makes no sense for this task to be available on the form. Of course, I’m still open to suggestions if someone has solution.
I would like to access email using IMAP. Is that a possibility somehow or something Thinkwise is considering, like an IMAP connector of some sorts? I know of the alternatives (exchange connector, MS Graph/OAuth2.0) but I was wondering whether Thinkwise could offer this as an alternative.
When developing a process flow, in the design screen it would be very usefull to have a viausal indication when a process procedure is used in a process step. Now you have to go to the step to check, and then going back to the design (which takes a bit of time rebuilding the screen).There is no visual indication that a process procedure is being used on a step.
For the File Storage locations AWS / Azure / FTP there is no standard supported way to delete files. For File Storage location FileSystem a Process action is available to delete files. We would like to be able to use the same/a similar Process action to delete files from other locations for (at least) the following reasons:Integrity & Clean-up: if there is no reference to a file from any record in the Database, there is no use in keeping the file, while still costing us storage capacity GDPR: a potential request based on the right to be forgotten requires to delete both records and files which are related to personally identifiable information of the requestor
SituationIn some processes the user needs to select multiple rows to process at once. For example generating a sales invoice based on multiple invoicing periods.We can support these action with the default multi select action in the interface. Only on desktop devices you need to Ctrl + Click on all the individual rows. This isn’t the most easy to use action for some users. In case of a miss click you lose your selection and with the different colors it isn’t always clear what your selection is. SolutionThe solution is already at hand; put a checkbox before every row like we do for touch devices.It would be great if the user has this action available in the non-touch version of Universal as well. I would be even better if we, the developers, could setup the subject to show them by default.
The current way of editing a Stored Procedure returns the following method to create the syntax on the database:if exists (select 1 from sysobjects where name = 'stored_proc_name' and type = 'P') drop procedure stored_proc_namegocreate procedure stored_proc_nameasbeginHowever, when using Query Store, the relevant data will be untrackable as the object_id is different after creating.A possible solution would be to make use of the CREATE OR ALTER dbo.stored_proc_nameASBEGINThis makes sure the object_id isn't changing, so performance impact of the new version can be tracked more easy and if a specific plan is forced, this won't break.
When validating prefilters that are changed from query to prefilters column it returns errors because the prefilter contains a query and a ‘prefilter column’.My idea is a simple solution by setting the query to NULL when choosing ‘prefilter columns’
Hi all,I recently did an uprade to new platform version and faced some issues. This forced me to restore a DB and fix the issues and rerun the process again until it was running successfully. This is costing me time to go through the process a few times. I suggest that the code script are written in a way that you can run as many times as you want without the need to restore DBs. For each statement that will be generated for the upgrade should have a delete statement right before it. It is already in place in other areas why not in the upgrade of IAM or SF.
Disable certain columns from exporting and if exportable, provided with at least a db_column header.A lot of our grid screens have columns that are expressions that show some sort of indication – for example a checkbox or some sort of status. Such columns do not have a translation (actually a space ‘ ‘), most of the time they have an icon in the column itself which says enough.Exporting such a column will mostly make sense for someone that doesn’t have to import it back again. Say for example a certain material order record has a status out-of-stock. Someone might want to export such a list and send it to someone to come up with alternative materials.It would be nice to be able to register in the SF that certain columns are not exportable to overcome the issue that it would imply that they are importable.It would also be nice if there is no translation registered (such as a space ‘ ‘) that the export would provide the DB column name.rgds Ricky
While you can choose the unit test type ‘Subroutine’ (i.e. functions and procedures), the analysis of unit test program object coverage does not take functions into account. This should be added to the cube.
I would like to propose the idea of having an Indicium debug mode.Currently if Indicium throws and error whiles using the Universal UI the user will get the following message “Unknown Error”. I can understand that we do not want to bother end users with specific database error messages.However it would be very useful if you can enable the display of such error message in the indicium settings. Currently when a client of mine gets this error message (unknown error) they will submit a ticket with a screenshot of this error message. That means that I have to go through the Indicium log and hope to identify the error message that was related to the message the client received. And to make matters worse, if you have load balancer enabled it can be a big issue determining which Indicium the client was logged into. Which makes finding the Indicium error near to impossible.Therefor it would be super useful have a setting which you can enable that will results in the actual database error message instead of the unknown error message.
When a query is slow and takes more time then for example 1 minute create automatic a log to the thinkwise folder (no database action).
In the data model generate and create the table tags for one table and display the sql script to synchronise to a database.
Currently a parameter of a task can have a lookup configured and the lookup control can be set to “Combo”, “Auto complete” etc etc.We would like to see a new option: “Contains words” or something in that matter. The functionality would be similar to Contains, but rows are selected like when using a combined filter in a grid.Below a taks with one parameter. The lookup control is defined as "Suggestion contains”. If a tabel contains the following valuesKleppen en injectoren afstellenKleppen en deksels afstellenKleppendekselpakking vervangen And the user types Kleppe afstelI'd like to see Kleppen en injectoren afstellenKleppen en deksels afstellen As the resulting options to choose from
Currently the only way to generate/deploy a view which is configured based on the option Auto or Meta Custom is through all of the the deployment steps. This is very time consuming (10-20 min each time). Often to identify whether the view is configured correctly you need to deploy more then once.It would be very usefully if you have the option to deploy a specific view via a screen, just as you can deploy a view which is based on a template.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.