News & Blogs

Virtually every table in an application has a primary key. The primary key is unique per record and can be used to refer to the record. For instance, the table Person can use a number as primary key. However, when a person is referenced in the application, we do not want to see this number. When we are referring to a person, we want to see the name of the person. The name of the person is said to be the display value of the person. The display value of a person could be variable, depending on the context of where this person is referenced. The display value might even be stored in another table, especially when dealing with link tables. Obtaining a set of keys and display values and translating a key into a display value is called a look-up. This blog is about look-up display values and how to use them effectively. TerminologyIn the example with persons, the Person table is used as a look-up tab

Because the Thinkwise GUI’s and Service Tiers use a connection pool for database connections, they will automatically try to reconnect with every new statement. This can cause locking problems during maintenance or upgrades. In the upcoming GUI’s a new feature will be introduced which will automatically close any application that is no longer available in IAM. Every five minutes a check is performed which will compare the currently loaded applications with the available applications for the current user. If an application is made inactive or the access rights are revoked then the GUI will close all the corresponding documents and removes the application from the menu. This feature ensures that all users are disconnected from the application and no new database connections will be opened by the Thinkwise GUI’s. Example In this IAM we find a Software Factory and three versions of a customer end product.