I would like to have the option to hide a detail tab if no data for it is present.
This obviously only useful for data that the user does not have to add, only for display, update or delete.
In some applications it can prevent inexperienced user for clicking on loads of empty tabs to find the information she/he is looking for.
Hi Theo,
This is already possible using Context logic. You could even make it a dynamic model concept to automatically apply it to all or a (tagged) subset of details in your application.
I agree with Jasper on this one. We have got a logic concept that will hide/disable tabs.
You can also consider using badges in order to let the user know if there are any records present in a specific tab.
All the votes have been transferred into this idea.
Continuing on the merged idea:
[...]
The main thing is that this could be decided client side based on offline data. At this moment we have a context procedure to hide tabs on which users don’t have to enter data, and that is a round trip to the server, plus additional logic, which is depended on the names of the references. and the expertise's of the user.
It would be nice to just not show tabs without questions. This way we only have to maintain the questions at an more abstract level and don’t have to edit the code when something changes.
For online scenarios, I doubt doing this client-side would be beneficial. Having the client determine the contents of a detail will require a roundtrip to fetch the data for every detail instead of having to do the roundtrip to execute context logic.
I suppose the detail should only be hidden when there is no data available for the user given only the authorization filters, not user filters. When a user filter or prefilter is applied in the detail, you probably don’t want to immediately hide the detail. This means it cannot rely on the regular data fetch but needs to do a separate call to check for data outside of the current user- and prefilters.
In offline scenarios, this setting could indeed be used to hide details based on available offline data for the selected parent record.
I think our requirement could fall under this idea. It is not about online or offline, but is about data not being available and with that, in the same record. We use Universal as target platform and the solution should support mobile devices. We have a data-entry form based on a definition which specifies what should be shown in the form. One of the options is to define if a document should be uploaded in the form or not. To show the form we use a screentype with a preview component in a second tab. However when the definition specifies that no document can be uploaded, the upload column will be hidden (using a layout procedure) but the preview tab should also be hidden which, as far as my knowledge reaches, is not possible at the moment.
I think our requirement could fall under this idea. It is not about online or offline, but is about data not being available and with that, in the same record. We use Universal as target platform and the solution should support mobile devices. We have a data-entry form based on a definition which specifies what should be shown in the form. One of the options is to define if a document should be uploaded in the form or not. To show the form we use a screentype with a preview component in a second tab. However when the definition specifies that no document can be uploaded, the upload column will be hidden (using a layout procedure) but the preview tab should also be hidden which, as far as my knowledge reaches, is not possible at the moment.
You have to add your previewer as a detail, then you can use a context procedure to hide the tab with the previewer. Having the previewer on the same screen or in a different tab but not as a detail would put you in the situation as described (if I read your comment correctly of course :))
Continuing on the merged idea:
[...]
The main thing is that this could be decided client side based on offline data. At this moment we have a context procedure to hide tabs on which users don’t have to enter data, and that is a round trip to the server, plus additional logic, which is depended on the names of the references. and the expertise's of the user.
It would be nice to just not show tabs without questions. This way we only have to maintain the questions at an more abstract level and don’t have to edit the code when something changes.
For online scenarios, I doubt doing this client-side would be beneficial. Having the client determine the contents of a detail will require a roundtrip to fetch the data for every detail instead of having to do the roundtrip to execute context logic.
I suppose the detail should only be hidden when there is no data available for the user given only the authorization filters, not user filters. When a user filter or prefilter is applied in the detail, you probably don’t want to immediately hide the detail. This means it cannot rely on the regular data fetch but needs to do a separate call to check for data outside of the current user- and prefilters.
In offline scenarios, this setting could indeed be used to hide details based on available offline data for the selected parent record.
Then this would be more maintainable or complete then (automated) context procedures that would check it on the backend..