Topics started by Jeroen de Klerk

10 Topics

Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick

Indicium service health checkCompleted

Currently, Indicium itself provides no way to check if the service (and its dependencies) is/are healthy. For our transition to a microservice architecture for internal systems, some of which connect to Indicium as a data source, such a health check would be great to have.Here are some elements I would say are required for a meaningful health check:Service availability This is the most basic check, basically just tells us if Indicium is running at all. Database connectivity In the context of Thinkwise software probably the second most important check, it tells us whether the Indicium service layer is successfully connected to the database. Database responsiveness Probably the most important check for Thinkwise software, it tells us the responsiveness of the database, which is generally a good indication of overall performance. Available memory It tells us how much system memory is available to the Indicium application. A useful indicator for performance, caching and, for Universal s

3
Jeroen van den Belt
Administrator
23 days ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Configure expire-time of cookie in Indicium

Hi, When logging in to the Indicium GUI, a session token is returned in the form of a cookie (named `.AspNetCore.Identity.Application`) upon successful login.By default, according to this topic answer, this token is valid for 30 minutes and automatically extended with every request.However, our users will sometimes not touch the GUI for hours, because they are busy doing work for which they do not require the application.In this case, having to log in again each and every time you don’t touch the GUI for any amount of time longer than 30 minutes, can get quite annoying.Is it possible for us to configure the expire time for these tokens, so that they remain valid for a longer amount of time? Thanks in advance!

1
V
Moderator
1 month ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick

Menu-based OpenAPI specs and metadataClosed

Our application is very large. This also leads to a very large OpenAPI spec (~50MB) and metadata file (~3MB).This is disproportionate for any external application that may wish to integrate with a Thinkwise application, which generally only need access to a small portion of the application.However, the OpenAPI spec is considered the industry standard for consuming an outward-facing API.In our Thinkwise application, we have several defined menu’s for different apps, which can be switched to in the Windows GUI through the context menu.See below screenshot for an example:The context menu within the Thinkwise Windows GUIThe “DMS app” and “Klantportaal” are menu’s containing a subset of views, tables and tasks which the respective applications use.Currently, these applications each required a lot of effort to implement each endpoint, because there is no tangible way of getting the specs for this menu.I understand, from this answer on a forum post, these specs and metadata files are filtered

4
Mark Jongeling
Administrator
7 months ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Indicium metadata endpoint per menu

In the Windows GUI, a user can switch between menus by right-clicking in the left-hand sidebar and selecting a different menu.In Indicium, according to the Thinkwise docs, there is a single endpoint to get the metadata (or OpenAPI spec) for an entire application.In our case however, the metadata is massive (the response body was 700+ MB).We have defined a separate menu in the SF, containing views, tables and functions we want to expose to a public-facing API.Would there be a way to only get the metadata or specs for that specific menu? Currently, we are managing model updates and exposed endpoints by hand and are actively looking for a maintainable alternative.Should anything be unclear, please do let me know!Thanks in advance!

1
Anne Buit
Community Manager
9 months ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Indicium service health check

We are looking internally to adopt a microservice architecture for one of our existing projects. This project partially integrates with Indicium as a data source.Our architecture design specifies a separate service for connecting to Indicium, which also deals with some of the implementations specific to the Thinkwise ecosystem (such as the TSFMessages header containing error messages instead of the response body).During start-up of this service, I would like to run a health check on the Indicium instance it has to connect to. This health check would be run inside Indicium and check on aspects such as database connections, database responsiveness, some general system checks and whatever else may be relevant to Indicium running properly.Does Indicium have any existing functionality facilitating this, or is this something we would have to implement ourselves in some way?Thank you in advance!

2
Jeroen de Klerk
Sidekick
10 months ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Indicium Basic throws "Invalid key segment" on PATCH request to view

Using Indicium Universal, I am trying to update two values through a view using a PATCH request. The view in question has two columns specified as PK and 3 additional mandatory columns, all of which are supplied in the request body. However, every time I execute the request, I get a 500 Internal Server Error response, and in the Indicium logs the following exception;System.ArgumentException: Invalid key segmentAs far as I can tell, all mandatory fields and primary keys are present in the request body and I am confident the URL is not missing any required segments (https://<server>/indicium/<app_id>/<app_version>/<view>). I have also tried including all the columns of the view in the request body and only updating the values of the columns to be updated, but that also resulted in the exception. Am I missing anything? I am not quite sure what else I could be doing wrong or what other issue there could be that could result in this exception. Thank you in advance!

3
Jeroen de Klerk
Sidekick
1 year ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Lifetime of idle staged resources

In our internal application, we utilize Indicium Universal's resource/task staging functionality for executing tasks and updating forms with layouts and default values. However, a developer questioned what would happen when a resource or task is staged and then left idle.Say a client is improperly closed or disconnected (the active Universal GUI tab is closed, connection is lost, a power outage, etc.) just after they staged a resource. Indicium Universal has no way of knowing what to do with the staged resource, at least not through client instruction.Is there some default configuration for cleaning up memory taken up by idle staged resources? Is that something individual implementations should configure?If not, I would say a good default expiry time is equal to the lifetime of the user’s session. That way, when a user's session is expired, all their staged resources are cleared from Indicium Universal's memory.

2
Jeroen de Klerk
Sidekick
1 year ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Indicium Universal Task execution

In Indicium Universal, executing seems to contain 2 steps;A staging step, in which a task's default and layout procedures are called, and the context of the parent subject is checked to see whether the user is authorized to execute the task.The URL for this task looks as such:http://<server>/indicium/(iam|sf)/<app_alias>/subject(id=1,idtwo=2,idthree=3)/task_execute_task/stageThe response of this request contains a Location header, in which a URL to the staged task is supplied with a GUID.Step 2, which is the actual execution of the task, is much simpler; we simply make a POST request to http:///indicium/(iam/sf)//staged_execute_task()/commit, which will execute the task on the resource specified when staging the task (subject with id 1, idtwo 2 and idthree 3) and returns a response. We implemented this in our external API based on what happens in the Universal GUI, where we had previously implemented Indicium Basic. However, we noticed a pretty severe downgrade in performan

4
V
Moderator
1 year ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Difference between "choose" on dropdown and PATCH request on staged resource

When calling a specific task in our Universal web GUI, a dialogue appears containing a form, in which I can change and enter the form values required to execute said task.This specific task contains a dropdown select-element, as well as some regular text fields and a few check boxes. Below is one such dialogue:2 checkboxes, an autofilled textfield, a dropdown and another text fieldWhen I change a value, like (un-)checking one of the checkboxes, I can see in the network inspector of my browser a PATCH request is made on the staged resource.The request body contains only the changed value, and the response returns two booleans indicating whether the layout and/or resource have changed, respectively.When I select an item in the dropdown however, I can see in the inspector a POST request is made to a “choose” endpoint, also on the staged resource. The response of this request is similar to the PATCH request.The request does not contain a body, but the URL looks like below;staged_task(guid_

4
V
Moderator
1 year ago
Jeroen de Klerk
Sidekick
Jeroen de KlerkSidekick
asked in Questions & Conversations

Indicium Universal login URL

We have an internal API which consumes data from our Thinkwise application through Indicium. Up until recently we had been using Indicium Basic, however recently we have started our upgrade to Universal. For authenticating users with Indicium through the API, in Basic we used the URL indicium/(sf|iam)/<app_id>/$logout, to which we would send a basic authentication header supplied by the client calling the API. However, in Universal this endpoint does not seem to exist anymore. Is there a similar endpoint in Universal which allows us to authenticate users through a basic auth header? Other ways of authenticating users are of course also welcome, but some form of username/password authentication is preferred.Thanks in advance!

10
V
Moderator
1 year ago

Badges

Show all badges
Terms & ConditionsCookie settings