Applications
An application in the Intelligent Application Manager is a combination of a branch, a server and a database that will appear as a standalone application in the user interfaces. A branch can therefore result in several applications on different servers and/or for different databases. Each application has its own authorization and user preferences.
Create an application
menu Models > Model overview > tab Branches > tab Applications > tab List/Form
A new application can be created via the applications screen.
Create an application
The table below lists the more specific attributes with their meaning.
Attribute | Meaning |
---|---|
Sequence no | The order in which the application is listed in the user interfaces. |
Active | Specifies whether the application is shown. Only activate an application after it has been set up completely. |
Platform | The platforms for which the application is available. |
Application alias | The alias used for the Indicium OData API. |
Max. # sessions per account | The maximum number of sessions that a user can log into an application simultaneously. |
Claim timeout (min) | The amount of minutes before a claim is automatically released when the application is not in use. |
Themes
menu Models > Model overview > tab Branches > tab Applications > tab List
To distinguish between multiple applications for the same branch, for instance in DTAP environments, it is possible to set a different theme for every
application using the Set theme task.
Application and splash screen title
menu Settings > Global settings
The following rules apply to the Title field:
- Newly installed environments initially get 'Thinkwise Platform' as splash- and application title.
- Upgrades will not override manual changes to the Title field.
- When installing the Software Factory in an IAM environment, the title is set to 'Thinkwise Software Factory'. This may override a manually configured title.
Apply user rights
menu Models > Model overview > tab Branches > tab Applications > tab List
Tasks are available to apply the required rights to the databases:
Task | |
---|---|
Creates the roles on the application database. See also: Apply roles to the application database. | |
Creates the users and user groups on the application database | |
Creates the users on the IAM database |
To be able to apply the rights to an SQL Server database, an IAM administrator who is not a database system administrator needs additional database rights. This can be done using the following code snippet:
use master
go
grant view server state to [login_name]
go
Apply roles to the application database
Per branch, roles can be assigned.
menu Models > Model overview > tab Branches > tab Roles
Tab List contains an overview of the available roles. Check out tab Role rights for a more detailed view of a role's granted rights.
To apply the selected role to a database, press the Apply roles
task.
This task is also available in the menu Models > Model overview > tab Branches > tab Applications > tab List.
Apply a role to a database
Only when roles are assigned to a user group, users can access an application. To assign a role to a user group:
Select a role in tab List.
Open the User groups tab, select a user group and press the Assign role
task.
Assign a role to a user group
Translations
menu Models > Model overview > tab Branches > tab Applications > tab Translations
In the Translations tab page, it is possible to provide a translation and a tooltip for every application language.
File storage locations in IAM
IAM > menu Authorization > Applications > tab File storage locations
Here, you can:
- Override the branch' file storage location or switch the location type as set in the Software Factory,
in menu Models > Model overview > tab Branches > tab File storage locations.
Execute task Switch file storage location type
to switch the type. See also File storage locations in the Models manual.
- Set the file storage location for the system flows used in several deployment processes. See: Configure the file storage location in the Creation manual.
Override OAuth server settings
For OAuth process actions, an OAuth server is configurated in menu Models > Model overview > tab Branches > tab OAuth servers.
To override these settings in IAM:
menu Authorization > Applications > tab OAuth servers
Meta files
menu Models > Model overview > tab Branches > tab List
The Upload icons and reports to database task can be used to upload images and reports from the file system to the database. This task should be run if the branch was created prior to the 2020.2 release and it has any images or reports linked.
Copy an application
It is also possible to copy an existing application, including its translations, settings, user preferences and authorization using the Copy application task.
Copy application task
Login language for web applications
When logging in to a web application, a user's identity and application language are not yet known. In that case, Global translations are used to provide the correct language.
These translations are not used by the Universal GUI's login screen. Login-related processes in the Universal GUI are often relegated to Indicium (for example, OpenID, 2FA, password changes, etc.).
Some language tags will be available by default during the installation or upgrade of IAM.
menu Settings > Global translations
An administrator can:
- Change the translations in the Global translations detail tab.
Add new language tags.
Delete existing language tags.
View all untranslated objects with filter To be translated.
The language tags used here do not, by definition, correspond with
application languages used everywhere else in the Thinkwise Platform.
Browsers provide the web application with the desired language for the login process via the Accept-Language
header.
The values are also known as 'Locale identifiers'. For instance: Accept-Language: fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5
The values and weights provided by the browser in this request header will be used by Indicium or the Web GUI
to determine the proper translations for the login process.
Global translations for login with web applications