Absolutely agree!
@Dick van den Brink Update: we had to update some Compression settings in IIS on the webserver, as well as whitelist the relevant URLs in our antivirus, but now we indeed have a similar compression as you reported for TCP. That’ll definitely help quite a bit.
@Alban_T Is your Idea similar to this one?
@Mark Jongeling Idea raised for ‘Set source for Data migration’ in Deployment package screen:2023.1: Set source for Data migration in Deployment package screen | Thinkwise Community (thinkwisesoftware.com)
@Jasper Thanks for your swift response! Based on your response I decided to test the following Layout logic, but that also fails on a 422 error. Is the whole import_mode variable not supported by Indicium yet?if @layout_mode in (0, 1) and @import_mode = 0 begin select @attachment_type_id_mand = 1 endThis does work for the multi-file upload, but is not preferred, as we want the field to be mandatory on regular inserts:if @layout_mode = 1begin select @attachment_type_id_mand = 1end
Hi @Mark Leunissen We actually got the route via the MS Graph API working! We are creating Chats and sending Teams chat Messages including a Deeplink to the specific Subject and record in the Thinkwise (Universal) app. Quite a bit of the configuration steps can be found in my comment here: Let me know if you have specific additional questions.
@Jaycee_C Are you working with the Beta version of Universal GUI 2023.1.15 by any chance? We had similar errors, which seem to be resolved for us with the final version.
@Mark Leunissen A few more specific details I could quickly find:In the Azure AD App registration we added the following MS Graph permissions:Chat.Create: https://learn.microsoft.com/en-us/graph/api/chat-post?view=graph-rest-1.0&tabs=http ChatMessage.Send: https://learn.microsoft.com/en-us/graph/api/chat-post-messages?view=graph-rest-1.0&tabs=httpWe have a standardized Process Flow that handles all our integrations. As part of this Process Flow we first queue a message that will ensure the HTTP Connector performs the desired Create.Chat call and based on the response we add another message in the queue that will ensure the HTTP Connector performs the desired ChatMessage.Send call.We always perform both calls. If a chat between our Automation user and the target user has been created before, the Create.Chat will simply return the existing Chat ID (as you can read in the Microsoft docs), so all messages land in the same chat for the target user:
@ElenaTodirenchi in which Universal GUI version are you working? There have been some issues with this in previous versions, but both Ctrl and Shift + click are supposed to work (on the Grid component).A very particular and confusing thing which I hope gets resolved soon is the following though: after opening a Grid it seems as if the first row is selected, but in reality it is not. So you would have to explicitly click that if you wish to include it.
@Renée Evertzen the question from @Allard Lakerveld is about Grid grouping, while your answer refers to Tree settings. As far as I know there is currently no way to do this in the Universal GUI. If there is a way to expand all Grid groups, I’m curious to know too!
An great blog I just stumbled upon! And since it is still relevant (at least for us), herewith a little bump.
To further improve on this Idea: it would be great if the update of the Universal GUI and/or the Application model would be pushed to the user's cache in the background, even before a user navigates to the application. That seems possible with PWAs:https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/background-syncshttps://web.dev/learn/pwa/update/
@Vincent Doppenberg @Dick van den Brink Thanks for your feedback and suggestions!We'll definitely have a look at the Brotli compression! As for the 10.000ms limit: I discussed this with @Anne Buit too and we concluded that users having to wait 10 seconds is the main problem, increasing the limit is perhaps not the solution they would be looking for… On removing the Barcode scanner / HTML editor, are these packed in specific js chuncks that we could recognize and remove from the Universal GUI zip? On caching: the biggest challenge in our case is the fact that loading a new Universal GUI version or a new Application version happens upon login of a user. It would be great if a new GUI version or Application version would be pushed to the cache of a user in the background automatically. This would avoid the bottleneck at login. See my last comment below this Idea, any chance that this is picked up soon?
I just stumbled on this open Idea. In the Release 2023.1 event I believe someone asked for this functionality, and we're also happy to have it. Some more votes might help:
@Mark Jongeling We were just playing with this in our SF and noticed that re-using the same ‘Version name’ in the ‘Create deployment package’ task causes the Description in model_vrs to be removed from our latest Production release and added to the last Model version. This does not feel very comfortable to me, I would rather have that Description ‘locked’. Should this behavior not be prevented somehow?
@Jasper We ran the hotfix to get the Display type setting available in the SF already. As a result we currently see the following for one of our (still hidden) Grid double click tasks in SF 2023.1:To confirm: will this setting imply that from 2023.2 onwards the Task will be displayed on the Task bar? And if we wish to keep the Grid double click Task hidden I presume we need to use the ‘Hidden’ Display type option? If so, should we run a script to update the Display type setting to ‘Hidden’ for all Double click on record = true or will such a script be included in Release 2023.2? This to ensure that the GUI behavior is not changed unintentionally.
@Freddy I believe this message is added since the Breaking change in Indicium 2023.1.13I haven’t double-checked, but it could be that this message is shown for every primary key for which the default input/output parameters are still enabled on Subject settings.Most certainly @Vincent Doppenberg can clarify when exactly this message is logged.
@Freddy Totally agree that is should be disabled by default! Please make sure to add your vote to below Idea. @Vincent Doppenberg Promising! Haven’t seen any traction on below Idea, but is this planned for 2023.2 already?
@Tim de Lang Nice! Could you already give a hint on how exactly will this Idea be solved?
We are testing with Brotli compression and the initial results are promising! Indeed a 90% compression on loading the Universal GUI for the first time:
@Mark Jongeling kindly updated my original post, so for each Idea the current status is visible. Good to see that the low-hanging fruit has been picked and released in the last few Universal GUI releases 😀 Let's vote and hope to see more of these great Ideas being released soon!
@Freddy If I understand you correctly: you would like to be able to receive the Domain element translation as part of a regular API call to a record? So for example: if you wish to receive a Contact record and the gender is registered with a Domain with elements, you would like to be able to retrieve the gender translation (e.g. male or female) to replace the 0 and 1 domain elements as part of the regular API call to the contact table.If yes: sounds like a great idea to me!
FYI: we took this solution to our Production environment this week and our users love it! We took the solution provided by @Jasper as a starting point and tweaked it here and there to fullfill our needs (thanks for the support @Kevin Horst!).Some remarks on our setup:We use Dynamic model code to create the multi-file upload and attachment tables for Subjects with the applicable Tags. This makes it very easy to re-use this solution across our application. We parameterized the upload URL in the upload page, so we can use a single HTML page for this component, while showing the upload page at different Subject detail tabs. We improved the upload page javascript to provide feedback to the user on the status of the upload (e.g. orange = uploading / green = uploaded / red = error during upload). We also use the Auto-refresh and Change detection logic to refresh the Subject after upload Note: in above example we use Conditional formatting to highlight that a user has to update the Attachment
@Vincent Doppenberg Any insights on whether we can suppress this error if it is actually intended to get this record deleted?
FYI: after further investigation we found that Auto-edit somehow was still enabled on the Variant, while Edit was disabled (and thus causing the setting no longer be visible in the SF). After disabling the setting, our error is gone.For the SF issue we raised TCP 7209.
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.
