It appears that the Universal GUI is programmed to always open the Form when clicking on the record in the card list. Correct?
A form is not always present for a table/screen and in that case you want a specific detail tab to be activated when clicking a record.
I seem to remember that this was possible in the 'old' mobile GUI.
Is this something that is still being worked on or can this already be controlled in some way from the model?
Best answer by Mark Jongeling
Hi Harm,
For nr 2; In this process action, the table is the target table; the one you open in the detail. The reference refers to the reference that was followed to open said table.
So in you image the vw_document_universal view is not a detail of any other table/view.
Actually the awnser is ‘it depends’. The only trigger for it jump to the form is if the form goes into edit mode *except when this happens because of default editmode*. If there is no edit, I would expect it to stay on the card list. Other than that, the Universal GUI has less implicit behaviour than the ‘old’ mobile gui.
However you completely control what happens. If you set the executeTaskOnTouch screentype property to ‘true’, a cardlist on a touch device will fire the Double Click Task as defined under menu User Interface > Subjects > tab Default/Variant > tab Links > tab Tasks
This task can be a re-usable dummy task that you use as the starter for a process flow.
Once you have a process flow. You can make the GUI do what you want.
For nr 2; In this process action, the table is the target table; the one you open in the detail. The reference refers to the reference that was followed to open said table.
So in you image the vw_document_universal view is not a detail of any other table/view.
I'll make sure we add some more details on the Documentation page 👍🏻
It appears that the Universal GUI is programmed to always open the Form when clicking on the record in the card list. Correct?
A form is not always present for a table/screen and in that case you want a specific detail tab to be activated when clicking a record.
I seem to remember that this was possible in the 'old' mobile GUI.
Is this something that is still being worked on or can this already be controlled in some way from the model?
Page 1 / 1
Harm,
Actually the awnser is ‘it depends’. The only trigger for it jump to the form is if the form goes into edit mode *except when this happens because of default editmode*. If there is no edit, I would expect it to stay on the card list. Other than that, the Universal GUI has less implicit behaviour than the ‘old’ mobile gui.
However you completely control what happens. If you set the executeTaskOnTouch screentype property to ‘true’, a cardlist on a touch device will fire the Double Click Task as defined under menu User Interface > Subjects > tab Default/Variant > tab Links > tab Tasks
This task can be a re-usable dummy task that you use as the starter for a process flow.
Once you have a process flow. You can make the GUI do what you want.
I try to work out your suggested setup, but I get the feeling that we are not on the same page
I cannot find the option ‘executeTaskOnTouch’
When adding a action of type ‘Activate detail’ no details pop up, while they exists for sure
Platform/GUI version: 2024.1 / 2024.1.12
Any more idea’s
Hi Harm,
For nr 2; In this process action, the table is the target table; the one you open in the detail. The reference refers to the reference that was followed to open said table.
So in you image the vw_document_universal view is not a detail of any other table/view.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.