As documented in our docs you mentioned. When the "combined” filter is within the document, you should use that one to filter the subject first. So what happens in your video is expected behaviour. So, whats left? Do you like us to change the translation to declare not only a filter dialog could be expected?
It could be both the filter dialog or the combined filter, dependent on whats available in the document and the screentype User Preference applied by the user. I agree it could be a little confusing now.
Hi Johan, We found out an invalid casing check causes this functionality not to work for a task/report executed with a progress dialog on top. We will fix that in our next GUI release. Workaround: for now you could set the 'clear_panel’ message to lower case. Regards, Erik
The GUI compares the available screen types to the one the developer originally chooses. The list of options will be more short and we don't want to expose more data to the user.
Could you clarify which components are present on the original screen types of these subjects? And which components are present on the new added screen type `FF_detail_tiles`?
I assume one of the tabs in the upper screenshot contains detail subjects? I think you found a bug in our mechanism to strip screen types which are not allowed. Seems like a tab page containing details is not matched with a detail tab component in another screen tree. Would you like to report a ticket in TCP for this?
Does this feature also work for reports? Reports currently don't support this. We should think about this in a design and investigate whether report implementations are able to process these kind of structured data. I'd suggest to park this question in a separate post/idea to think about alternatives and to investigate the need for this. Link to the parked idea: https://community.thinkwisesoftware.com/ideas-18/multirow-report-execution-1048#post3001
Harm asked this question underneath this blog. That's the context.https://community.thinkwisesoftware.com/blogs-21/multirow-task-execution-159#post2833
What kind of reports do you use and do you have any idea if it is possible to work with xml data within these reports? Maybe a practical example will help us imagine what you are trying to accomplish.
That sound like a valid business case to me. As a workaround you could connect the report to a parent record which queries all related data. Of course you miss the user input of the record selection it that case. Thanks for reporting this great idea!
Hi Johan, Thanks for your response. So the panel is now cleared correct all the time? The new faulty behaviour sounds like a separate issue to me so I suggest to create a new topic for this. The screenshot you added is not very clear to me, so maybe you could describe the issue in a little more detail. I never seen show thing like this. Regards, Erik
Maybe load the link in a Preview component? You could offer a different set of tasks per GUI platform by using table variants started from a platform specific menu item.
Hi Johan, Maybe the Windows GUI deployment contains a custom DLL which is not available for our Web GUI? Notice that some of the custom made tasks JPDS is using are only developed to work with our Windows client. Please let me know whether this answers your question. Regards Erik
Hi Edwin, You could configure this in Subject->Data->Sort->Group until: Regards, Erik
Hi Hugo, Currently there is no way to suppress the title and the dotted border below from the Web GUIs login page. By using `ShowLoginInfo` ini parameter you are able to hide the database/product info from the login page. Regards, Erik
Hi Johan, Maybe you could post a full screen screenshot. What components are floating over the Infopanel. This panel should always be on top of everything. Maybe the browser tools (F12) will provide us some extra information about this faulty behaviour?
You could drag a preview component on your screentype in the SF which will present the result of the first found file or Url control in the subject. The preview component could present the web-address from your example to the user, so the user could directly go there to request support. Is that a helpful solution for your business case? Else try to work with table variants as a mentioned earlier.
Alright, maybe check the existence of the JPDS specific DLLs in the Projects folder of the Web GUI deployment?
Hi Mark, This idea is implemented now and the release of it is planned for next Tuesday 14th of April. Regards, Erik
Indeed, it will open the monitor on starting a task or report set to Await Result=No in the SF.
Hi Freddy, Sadly, our 3th party components don't support this together. So, you must choose between both. We will check the documentation again to see if something changed yet. Regards, Erik
Hi Hugo, These ini parameters indeed get overwritten by the similar settings from IAM. Our intention is to configure as much application settings as we can from IAM. We still need these settings from the static ini file for the first incoming user/login only, because we didn't connect to the IAM database yet. So, our advice is to give both settings the same value. Regards, Erik
We recently fixed this problem in Web GUI release 2020.1.13. Maybe that’s the reason it’s not reproducible anymore?
You could configure a task in the SF like this: The Object name refers to one of the task parameters surrounded by ‘ []’, providing the GUI the URL to navigate to. Hope this helps you to solve this business case.
This message belongs to the application claim expired mechanism we lately added to IAM. It seems like this message is shown unfairly when leaving the main page of our Web GUI without logging out first. Please bring in a TCP ticket for this telling use that it still happens in 2020.1.13 and we will take a look at it again. I guess this may occur when you open the "already login” page again, wait for the session to expire ± 20 to 30 minutes and try to login again?
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.
