@SanderAdam I did encounter the same issue when applying Input Constraints on Domains. Somehow this constraint is also blocking the Cancel option. The only way to get out of the screen if clearing the triggered fields or correct the input.I cannot confirm the default stopping, but that is probably related to the same functionality that block the Cancel button.I did create a TCP ticket (9030S) for it and is on the Backlog. Hopefully it will be fixed soon, as the Input Constraint is a great feature, but not really deployable for users the way it block everything now.
I hope this idea will not remain too long an idea to vote for, but become an actual implementation.Experienced today that upgrading to 2024.1.13, where we have changed the “Page size” to fit the “Max no. of records” setting, as it reacts different now than previous versions, the TOP 500 was giving ~130k records to users that were still on the old version.The TOP 500 is already applied because of performance reasons, so you can imaging it blowing up like that did not do us good.
@Blommetje I can inform you that I recently got a “Solved” response to my TCP ticket (8477S) with the message that this will be available in Universal GUI version 2024.1.14.0. This will likely be available May 13th 2024.Lets see what the result will be it releases.
I partially like the idea, but would suggest make it that the Universal GUI has a registered minimum Indicium version to check. Both products could get development done that have no dependability to each other.
@jurrejanssens Thanks for informing this might not be a permanent fix. Any idea what update may have happened that it started giving issues again? That way we can keep an eye out and perhaps delay this update for the time being.
I would still like the option in a Model or Branch for the projects that are not actual products, Like an experimental branch or just a playground. It could help that in those situations there is no need for that validation to run and prevent causing an expected “Error”.
The advice that Mark gave by reinstalling .NET seems to look promising so far. In my case it stopped after installing the .NET 6 and 8, both the SDK version.I had done the Runtime only at fist, but that seemed to only make the issue a guarantee when closing the Windows GUI. Afterwards with the SDK it is gone so far and have closed the Windows GUI on several occasions without a BSOD.
Created a ticket for it: 9199S
@Mark Jongeling I think those are all set as supposed to.Lookup on the task parameter:Lookup referenceSetting on the view (subject):Lookup setting view (subject)Only one column in view with specified domain used (datamodel):Column of the view used in the lookup
@Mark Jongeling Thank you for your quick response. It clicked now that Regular Expression = RegEx. Now it makes more sense what my options are for the Input constraints. 😅For the inability to cancel when a constraint triggers, I will create a TCP ticket.
@Tejo van de Bor Have you tried changing the task icon size in the screen type (Under User interface in the SF) window yet? When you go to the Screen types and select the Task bar component, there is a property “Icon size”. Task bar component Several size options for the Task bar icons Here an example of the icon sized 24x24 and 64x64 24x2464x64
This is probably related to the pixel size used for the grid row. I still have a TCP ticket open myself about this issue where I disagree about the need for a “huge” grid row size to only make an aggregation readable.The correlation between the value is explained here:snippit from release notedEven though it says the minimum value of the summary is 40px, it still cuts of the text, but leaves white space the have the bars height 40px.The latest Universal GUI as mentioned by Mark, still has this issue of cutting off the summary.
@Jasper Is the Model insights still in development for more options or is the current version considered complete?I find the Model Insights only partially usable as it does not work when you want to know the screen where there are no records in the grid available. A task you are not able to get information from either and probably the same for report as well. Tab control and Context is also not shown. Expression seems to be missing.These are the things I can just think of, at the top of my head, as a reason to need a Windows GUI version next to it while developing.
@Mark Jongeling Thanks for the response. I don’t think the “Clear all filters” would be a replacement for the “Clear” button of the form, as the first one also clears possible combined filters, while we only wish to clear the form.Hopefully it will become available in the original concept and it will be fine as a optional feature instead of default.
@DenisaViuletIt seems somewhat similar to a post I made some time as well and Arie V commented about the Task Tile issue too.With some luck this issue will be fixed in a future update of the Universal GUI as mentioned by Tim de Lang: This has been finished and will be in the 2024.1.12 release that is expected on March 18th, 2024.
Created a TCP ticket: 8717S
Created a TCP ticket: 8715S
@Erwin Ekkel I am quite surprised by this answer. I understand the use of paging, but when a result is limited by manually configuring a “max. no. of records” or the default 100, does this really feel like a situation where you do not want to inform in any way that the screen has a limit? I would suggest to have a marking when the resultset is equal to the number of “max. no. of records”, so a user has some indication that this might not see all results that he/she tries to filter on.I could make an idea for this, but I would hope that this is not necessary.“max. no. of records“ is also used to not have to load all data as it can be loads, but one cannot limit the result yet as the requested filtering is not known (users will filter what they need at the time).
@Erwin Ekkel I could do that, but does this also say that currently the functionality of the Web GUI and Windows GUI is not going to be implemented in the Universal GUI as is? In this case the context of the “Export immediately” functionality. Meaning it will behave differently.To clarify, this is currently the result with the “Export immediately” on the same screen.Web GUI:Windows GUI:Universal GUI:Just making sure so I do not make an idea for something that is part of the project to make Universal compatible with currently existing Web/Windows GUI functionality.
HI Erik,Thanks for mentioning this little trick to have some control to make some fields wider. This might be an option for some task, but those partially limited by IAM visibility or show/hide by layout procedures, make this not viable for all.Will use this for now, but really hope a better control over the task/report form will come soon.
Hi Mark,I find it strange that a seemingly basic functionality needs an idea to be voted for. As I understand the priority is getting Universal feature compatible with the current ones of Web en Windows (those have it). Looking at the idea linked, it is from November 14th 2022……Working with 33 languages, we always struggle to get fields/labels big enough to be workable for all. Not having this option in Tasks/Reports feels as quite the handicap. I don’t think it realistic to tell customers now, to drag the downright corner everytime, to make the window bigger.I have added my vote, but I really hope this will not take X months or more to become available.
@Erwin Ekkel They are indeed PK columns, but the main problem with this, is that it has different behaviour between the Web GUI and Universal GUI. As a developer I understand the need for the PK columns for the possible use of importing (if that is your intention with the export).Colleagues from other departments will not understand why Thinkwise had to “break” a functionality they are accustomed to. It seemed a relatively safe feature to have enabled for customer, as the “export immediately” only export the visible columns in the Web GUI.I’ll pass on this answer, but I don’t think they’ll just accept it. Thank you for your response.
@Erwin Ekkel That is a link to the “In House section”, which I am not authorized to access.
Looking for something else, I accidentally came across the solution for this question. Add a value in milliseconds for the parameter “searchDebounceTime” in the config.json.Ex."searchDebounceTime": 750 At time of writing, it can be found here: https://docs.thinkwisesoftware.com/docs/deployment/universal#delayed-search
It seems Anne Buit also attempted to reply and maybe I have clicked the “solved” too quickly, but just to add part of the response for other users. The quick answer is appreciated!“Having multiple Indicium instances running on the same Intelligent Application Manager will not cause any issues. Both Indiciums will attempt to run system flows but a system flow instance from a schedule can only be started once - only one Indicium ‘win’ the right to run it. This also takes the Multiple running instances setting of a system flow into account. Indicium will not be able to start a system flow instance if the same system flow is still running on another Indicium.”
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
