You found it 9 months ago @htimmermans :
Hi @Tim de Lang , if I’m not mistaken, you haven’t (yet) deployed this on the demosite of the previous post have you? Would be awesome tbh…
From a technical point of view: When you are very certain on which column you could filter this could work. If you are not - a “select top” would bring a solution - in our case it was a search result which we reduced to a 1000 iirc… But this ofcourse, will result in an end user thinking there are only 1000 records in the system. Not sure if we also created some form of warning that says that the 1000 record limit has been reached. From an information/data/business perspective: What is the use of having so many records in a screen/subject? Will your decisionmaking be better with 100k records? Are you really going to evaluate each record to make your decision? Why has the data not been stored in a separate archive table? Just maybe you’d be better of reviewing your data/information model. But you get the idea I guess.
Depending on how much data you'd like to show in your screens/subjects at once - I've seen the memory usage of the tsf_dotnet client grow up to 4GB on my laptop, iirc we analysed which screens/subjects and the query behind it were responsible for said amount and reduced the max amount of rows returned. https://community.thinkwisesoftware.com/deployment-12/windows-gui-on-microsoft-rds-server-923 From what I’ve also remembered is that the windows GUI does not support paging (as for example TCP does) https://community.thinkwisesoftware.com/development-13/list-pages-in-the-windows-gui-470
@René W We indeed use the windows gui for know. From what I understand from your posts is that you have a webserver that is serving the preview.html right? That’s the part I’d rather not have, that’s another (web)service to maintain :-) (maybe it would be neat if indicium(universal) would serve said html file maybe?) But indeed the way you’ve described that - works just fine: https://www.dagevos.org/pub/test.html?link=https://cdn.2ba.nl/FCRL/ETIMPictures/EC000080.png -- succeeds https://www.dagevos.org/pub/test.html?link=https://cdn.2ba.nl/FCRL/ETIMPictures/EC00008022222.png -- fails and fallback to the acto logo <html> <body> <img id="myimage" src=""> <script> //test.html?link=https://cdn.2ba.nl/FCRL/ETIMPictures/EC000080.png var url = new URL(window.location.href); var imagelink = url.searchParams.get("link"); var img = document.getElementById("myimage") img.src=imagelink if (img.complete) {//do so
Hi Tim, You wrote: “We went from from a beta version to release candidate 1 this release.” “Release Candidate 1 Like with every blog, we've released a beta version so you can test Universal out for yourself. “ So when I look at the one I can test - is that a beta version, the release candidate 1 or a beta release candidate 1 or something all of the above? btw - Looking good!
In the future this feature will be configurable through the metamodel and will probably use table valued parameters instead of XML. We'll be able to automatically upgrade the model, but you'll need to change the code yourself! Gradually our codebase gets cluttered more and more with your originally suggested solution. Can you get us an update on when you expect the future will arrive on this matter?
Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. I think you may want to update this template you are using
Hi Mark, Thank you for your answer. Is there a reason your client only has 2 concurrent users per server? I would expect to be able to serve at least 10 users per server. Kind regards, John Sangers Hi John, Our client only set up these RDS for demo's and external developers like myself, and together with the 6GB RAM I do think they limited the amount of concurrent users to 2 to prevent RAM issues. I do think if every user had 2-4GBs to work with it would be enough for them. If only the Software Factory and the end product would be run on it, then 2GB should be enough I think but don't pin me on this. So I think in your situation, for 10 people I recommend a healthy amount of RAM and of course enough processing power to ensure the users have a smooth experience. But I do hope other Community users can add on this with their experiences. Kind regards, Mark Jongeling The limit of 2 users is actually to bypass the maintenance of a RDS license server. (Windows 10 allow 2 RDS users by
Things get automagically solved I see - well that makes no sense…
Hi Mark, Thanks - Doesn't have to be hotjar per se, any heatmap solution that implements user behaviour tracking will create the benefits as mentioned in the bullets. rgds Ricky
Already have an account? Login
Enter your username or 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.