Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
In an action flow I have the ability to read/write/move/delete files and folders. I have no option to get a list of files inside of a folder. This would be very helpful. Currently I have an external document generator that creates PDF files and puts them on a file share. The filename convention of the generator contains a timestamp and some other variables that I am not aware of. Because of this I can’t READ FILE since I don’t know when the file was generated or what other variables are part of it’s file name.
When you start working on your project the amount of tables is often not that vast. However as you progress the list of tables and number of tables sharing parts of their name will become a lot bigger. This will make it more difficult to select a specific table or view to display in the datamodel designer, since there is no filter available here.It would really help having a filter bar on top of the list of tables to display in the datamodel designer.
If I have a lot of details in one screen, I mainly use grids instead of grid and form. But if I want to add a record I have to use add in grid or make a task to add a record. It would be really nice to have generated CRUD tasks, this would prevent modelling the same thing multiple times.
We require a change of the translations of the “Forgot Password” link in the Universal Login page as well as the subsequent screen objects in Indicium Universal as they do not really correspond to our liking.Idea:There needs to be a way to have access to the translations of these screen objects to be customizable according to the corresponding audience that is using the application.
Since a recent version of the Software Factory it is possible to create unique indexes that exclude NULL values. This is a useful feature, however, I think it would be great if we can take it one step further.I’d like to propose the possibility to create filtered indexes, where the developer him/herself can supply a where clause that will be applied to the index.For myself, I have this working using some dynamic model fiddling, but I think it would be pretty straight-forward to implement as a default feature.This is an example from the index script that is being created using my adjustment:/* Create index 'ix_un_def_dimensions_len' on table 'article_default_dimension'. */*snip*create unique nonclustered index ix_un_def_dimensions_len on "article_default_dimension"( article_id, default_length)where default_width is nullgo/* Create index 'ix_un_def_dimensions_len_width' on table 'article_default_dimension'. */*snip*create unique nonclustered index ix_un_def_dimensions_len_width on "article_default_dimension"( article_id, default_length, default_width)where default_width is not nullgoThese indexes ensure that I can have unique records for either article_id / length where width has not been provided and have unique records for article_id / length / width where width has been provided.The only thing the developer has to do, in my example, is provide the where clause, i.e.where default_width is nullAt the moment, I use a tag on the indexes to do this, but this could just as well be a field on the index-table/screen.
Currently when setting up a task or subroutine within the Software Factor the checkbox Atomic Transaction is set to false by default. It be better if the default is set to true instead of false. Normally all tasks and subroutine (procedures) will have to be set up using an atomic transaction. In some exceptions you would like to disable this feature.
Hi all,In order to synchronize data from a local MS SQL database to a MS Azure database, Microsoft offers a tool named the “SQL Data Synch”. In order to use this tool, a table cannot be using a user defined datatype. By default the Software Factory generates tables in MS SQL Server based on user defined types. You need to be able to disable this and instead use system datatypes when deploying.Therefor I would like to be able to configure this within a project version. And I would like to specify whether this is done for tables and or stored procedures. In some cases you would like to enable this for tables, but not for stored procedures.Currently you can set this by manually setting the column “alias_allowed” in the table dttp to 1 and after that alter the column user_defined_dttp on the table dom. This should be something that you can configure within the project version.Do keep in mind that you should still be able to deploy the user defined datatypes so that they can be used in SQL code templates. If you change to alias_allowed column that will also cause the user defined datatypes not to be generated within the upgrade/db create code groups. You should still be able to deploy the user defined datatypes in those script.
Of course we’re all very aware of the possible pitfalls when deploying a new version of our application. It does happen that we run a deploy with one cup of coffee to little and miss something.The [sf_product_info] table contains a lot of usefull information about what has been deployed, but missing in there is what previous version the deployment was based on. We recently had an issue on a non production enviroment that we had a difficult time to diagnose and even more difficult to repair. The root cause was that the environment went from version 2.55.7 to 2.55.16 but the .16 reployment was based on the .9 version. Would it be possible to add a sf_project_vrs_previous column to the sf_product_info table? That way we can check for constancy when deploying new versions.
For each projectversion, authorising new objects remains a hassle. Sometimes, you, as a programmer, immediately sets appropriate authorisation to roles when adding new functionality, Sometimes others add things or things get lost while handeling all kinds of new functionality… All in all, after weeks or months of building stuff, the day arrives when you go from test to acceptation or production… To get an idea if everything new has been, at least, reviewed for authorisation related stuff, it would help to see you or someone else has already taken a look at the new object. Also, when a new table is authorisised with a task in the SF, all fields could also be marked, which can reduce the number of new, unauthorised, new objects quite a bit. A pre-filter in the screen below, default ON, to sift out already “handled” new object is also much appreciated. Something like this, or by using a conditional format:
Hotfixes for the Thinkwise Platform are released on regular basis. Now, I have to subscribe to the updates and releases subforum at the community to be notified. I'd like to be able to get notified about hotfixes and execute them from within the SF. In the current situation I have to open TCP, download the Deployment Center application for the hotfixes, and execute them. It would improve the developer experience if this gets easier.
Currently when using a tree based upon a grouped column, the label of this column is displayed on top of the value of that grouped column. I would like to be able to disabled this label. Often I do not need this label and for some users this is very confusing. In this example I would like to hide the label text Ship Manager. All I have to see is the value “Athena Marina Co. Ltd. This will also keep the tree view much smaller, since currently this takes up two rows instead of one.
For my client it would be very much welcome to have a new Process action that can Zip and Unzip a file. Since we will use Indicium to help us import files, we need to be able to Unzip uploaded/incoming files. Most times these zipped files are compressed with Bzip2. We currently run code to use 7-zip to unzip the files to the desired location. I do think other companies can benefit greatly from this too. The parameters for this action will most likely be but not limited to: File location (where the zip file currently is) Zip/Unzip to (location where to zip/unzip to) Compression type (Type of compression used or to be used to zip/unzip - Bzip2 for instance) Password (In case the file is or needs to be protected) The Process action should return a list/variable of what files have come out of the zip file
With 2020.2, the icons are stored in database. But when you would reuse an icon already used in your project, you have to select it again as image upload, so the icons are stored multiple times.Would be better if there is a central repository (per project / version) where the icons can be maintained and where you can refer to.An example is the info icon, what can be used on multiple subjects.See also
In the applications we create with SF, there are tables that are used in multiple applications. We call these “basic data” tables. For example, the tables for countries, states and cities are the same for all our applications. We would like to share these tables without the need to copy them from 1 project to another. This becomes cumbersome when there is a change in the table, we need to manually update all projects that incorporate this table. We did a research project, where we created a base project. This base project contained the tables that we wanted to share. We then imported this base project in a “normal” work project. This resulted in the tables to become available in the SF. Allowing the creation of relations between the tables in the base project and the tables in the work project. Updating the base project resulted in a warning that are is an update of this base project, and that it needs to be updated again. However, when we generate a version of the work project, all imported base projects are reimported. E.g. tables are removed and inserted. As a result, all references between the tables are removed and need to be manual recreated again. As you can imaging, this is an error prone process. TL/DR: Provide a method for sharing table configurations between multiple projects from a single source. When the source is updated, there should be a convenient way to update the depended projects with the new configuration. Where the references in the work project are maintained during the update process.
When developing it can be easy to create new objects and validate after all development is done. This can mean that you have used disapproved object names and have created and even deployed all kinds of objects with this disapproved name. Having to rename all these objects can be a pity.It would be nice if during adding or editing objects, that I would be notified that my object name matches with a disapproved sub name. This could be inside the default procedure throwing a pop-up message explaining to me which sub name is used but disapproved.
When a new release is created, the SQL scripts contains statement like ‘grant … on … to public’The role public is part of every user who can make connection with the database. This results in the effect that I’m not able to give developers rights to look into production databases, because if I give these rights, they are also able to mutate the content of the database. In my configuration only the applicationpooluser of indicium/indicium universal/webgui needs rights to the database. So, my request is not to grant rights to the role public, but to a rolename defined by myself. This gives me the ability to create a difference between the rights of the applicationpooluser and any other users I want to give access to the database.
Now that our processflows have become more powerful I find myself programming more code templates for specific processteps. At the moment this requires quite a bit of work. I have to go to the functionality screen and create a new control procedure and template from there and then search for my specific processtep, which sometimes can be a bit of pain. Also reviewing process procedure templates within a processflow is a bit of a pain. Because there is no quick way to see the code linked to a processtep.What would of great help is being able to create/manage control procedure and templates from a specific processflow step. This will save alot of time during development and will make the review work of processflows alot easier aswell. Within the processflow screen you will get a control procedure screen that automatically filters on code group process. And it should also include a prefilter for showing control procedures that have at least 1 template linked to a step of this processflow.Next to this, this same tab is also available on processflow step level. In that screen the prefilter will only display control procedures that have at least 1 template linked to this processflow step.And finally you will get a direct detail from the processtep that will show you all control procedure templates linked to this processflow step.Update: I almost forgot, the program object items that are shown when assigning a template from this new control procedure/template screen should only contain the processteps of this processflow.
We will be working with multiple model DBs in 1 IAM.In this case, our IAM has 1 Model and several Model DBs which are linked to this model (e.g. DB_1 and DB_2)To upgrade these databases we now need to run 2x twdeployer; 1x for DB_1 and 1x for DB_2. It would be much nicer if twdeployer had the option to upgrade all model DB's at once based on the contents of the gui_appl.
When using https://docs.thinkwisesoftware.com/docs/sf/overview#file-storage---allowed-extensions Please add the selection for file type in de upload dialog to prevent selections not accepted in the next stepso this error doesnt appear
Hello everyone,Wouldn’t it be nice to have the existing Universal GUI Login screen having the option for login in to the Applications either via existing local account (IAM) or click on a button “Sign in with Microsoft” ? We have currently 6k+ seafarer Users using our app with Local IAM account and planning to introduce another 300 Office Users having their Microsoft SSO enabled. User experience will be changed for our existing 6k + seafarer users using the application as a Mobile App. Using the SSO brings a long process to login for both users types (office, seafarers). For the office users it is only once until session expiration, but for our seafarers it will always be the case for each login.Right now if enabling the SSO with Microsoft or other external provider you have to be redirected through Indicium Login. This defeats the purpose of having the custom.css on the Universal GUI. This SSO should be merged into a Universal Login.Indicium to be left as only an Admin tool not being accessible by simple users unless specifically mentioned in the URL.Since applications are developed on Universal GUI then their login should remain on same interface.E.g.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.