Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Can this be achieved? From here start a task... etc.
I wish it was possible to show a google maps icon in a grid to open a popup with map, like it does in forms. Like below:
IdeaIn essence, the idea is to expand the quality dashboard with a manual test scenario section, where users can see the number of test cases, successful test executions, combined with failed tests, and the number of open findings.ContextOver the past few releases, we've introduced the Manual Test Scenarios feature, allowing for the easy registration of test scenarios, which are now centrally available for the development team. The most recent update consolidates the registration of both these test scenarios and test executions into a single location within the Software Factory.Another improvement is the introduction of a dedicated Test Role. This enables key users or process owners to register their test scenarios and test executions within the Software Factory without being distracted by other functionalities.Now, what we're aiming for is to provide a quick overview of the testing progress, not only for the development team but also for the product owner and potentially steering committees. Extending this capability to the quality dashboard seems like the logical next step.
Whilst it is really handy that I can configure Runtime configurations to any environment Indicium has access to, it ultimately can mean that in the speed of development I accidentially run code on the Production enviroment. Luckily with the "create or alter” addition, the code does not get replace if it contained errors, but when it does not contain errors, which of course is most of the time, it successfully deploys code a tad too easy to the Production environment.I would like to be able to label any Runtime configuration as Production environment. This way the default logic underlaying to the Execute task can withhold from auto-filling in this runtime configuration - exception being if the runtime is the Default runtime.Maybe expand it with more than just Production; like Acceptance and Test. Similar to the Model version status.
My idea is based on a way to speed up development by generating one table with his depdencies likes context, defaults and layouts. So you can quickly see a result in the end-product.For example, you have a table and you made a typo in a field. You quickly would like to correct this to continue the development process.Currently you have to generate the complete project and validate and execute the codegroups on deployment screen. And you result in creating a new version.Why not a quick generation button for a particulair table which you can use to just re-generate this table and drop/re-create the table.
The ability to run a task in the background in an endproduct should also be available when importing or exporting data in the various GUI's. I'm importing a table with postalcodes (no default or layout on the table, only a trigger for tracefiels) takes probably an hour for 50.000 rows I'm guessing after waiting for 10 minutes. It would be a great addition when such a job could be placed in the background so the GUI can be used to perform other tasks.
Primary idea:Currently when you want to create deployment package for a application you have the ability to choose a database or a specific point in history.What i would like to propose is an ability to login to an indicium service tier to retrieve the current version.So you don’t have to query the product info table and figure out what version currently is running on that database/environment. The ability to always connect to a SQL Server directly may not always be the case. So you would like to generate a package for an application management party to deploy.
As a Process Flow can have many decisions and loops etc it is impossible/difficult to give the User a progress in percents or even “step N of M” in a generic way.But I, as the developer, know where and with what content I could inform the user of the progress. I might have a process action A that takes 5 seconds, followed by a loop where a certain 2 second process action B is executed for all 3 relevant records.I would like to be able display messages:-- Executing A -- (1/3) Executing B for Customer ABC-- (2/3) Executing B for Customer DEF-- (3/3) Executing B for Customer XYZCurrently I cant use tsf_send_progress for this as it is not available in a Process Flow. (If it were available I would have some trouble faking a percentage). I don't want to reengineer the whole thing into a big task template just for this reason.And I also can't use tsf_send_message because that requires user input.I need something to display a popup message that does not require user input while processing continues. And I need to use it from code, as there I know how much processing needs to be done and what is currently being processed.The solution could be one or more of these:a new option to define a message for the start and end of a process action. It will be displayed with a button while processing continues. a new option on the Message and tsf_send_message to specifiy that there will be no button on the message and that processing will continue. a new option on the Message and tsd_send progress that works in a process flow and maybe only shows text and not a progress bar (or a sweeping one, that would be nice!) something else that solves it.
I would like to have a way to determine whether a user as a document tab open or not. In some case you would like to close a document tab when the user already has this tab opened.Currently you are not able to determine whether this tab is already open or not. The only way to close the tab when open, is to include a close document process step in your processflow.It is kind of redundant though, that you have to execute this process step (which costs performance) when the user does not have this tab open.
An editable GUI that modifies the setting of the Software Factory. Two-way communication. Both from the SF to the GUI, and from the GUI to the SF. Customizing: Menu Column size and height Putting columns on invisible Translations directly from the GUI Advantages: Fast operations and productivity Better user experience Involve the business more in the layout of screens Going one step further: An editable GUI that makes changes in both SF and IAM. Configure the above options per user group.
For most cases horizontal lists are the way to go as it displays the value from left to right. But sometimes I would like to be able to make the list vertical. For instance when I'm comparing products I would like to have a vertical list so I can see all the differences side by side. Product comparison websites also use this, see: I think this could make our end products even more great with creating the Wow-effect. Let me know if you agree!
When screens are configured for import, the default Import functionality is in most instances used in the same manner between different imports (and in many cases the import Excels follow a predefined format).As a result end users often find setting up the options on the “Select location of column names and data” part of the import wizard somewhat complex and cumbersome.If the options under “Headers” and “Data” could be preconfigured on subject level in the SF model + an option to skip the entire “Select location of column names and data” (for cases where only one worksheet is used in the import Excel and no data selection is necessary) could be made available, this would make the import easier and quicker to use.
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
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.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.