How Can We Help?
The TAB_ object group layout behavior appears to be missing something or it is not behaving as it should.
The TAB_ activityA specific step in a process. It will be the user interface for that step (web form or a screen), for example, the Leave Application (screen interface or web form) will be the first Activity in the Leave Requisition process. The Leave Application Authorization will be the second step or Activity in the Leave Requisition process. One Process can have multiple activities. and some object groups were added, which worked fine.
Elements could then be assigned to them and the tabs would be created.
Current experience with the behavior was:
– Ungrouped added to Main tab
– Each object group creates a new tab, but the tab becomes a holder for the object group.
Now although the tabs are quite nice, the object group becoming part of the page doesn’t feel that useful.
Here is the desired results:
– Create 3 Object Groups, Account Details, Address Details, Bank Details
– Add elements to each Object Group
– Each tab is rendered as a normal page rather than an object group
Maybe the same logic and prefix Object Groups with TAB_ could be used to get the behavior where the object group acts as a tab page rather than an object group?
Although obviously don’t know the exact amount of programming logic this would effect.
Maybe there was something missed.
Answer
There must be some miscommunication, misunderstanding about the tabs.
To clarify:
The tab styling affects how the object groups are rendered per activity.
Prior to the tabs, object groups were rendered as part of the page typically at the bottom stacked on top of each other and when using by ID as per the index option of their controls.
Tabs were introduced to move the rendering of the object groups from the bottom of the same page to a more aesthetically pleasing spot at the top of the page, to allow for quick access versus scrolling down.
How they currently functionIs a Stream Objects that performs mathematical and statistical operations.
When tab’s are enabled the page renders a Main where all ungrouped controls are rendered as per their ID, the object groups become tabs next to the main tab and function as per normal with regards to the addition and removal of lines.
The object groups are sorted according to their names to allow for the moving of them.
Each object group creates a new tab, but the tab becomes a holder for the object group.
When assigning some objects to an object group, the tab is created, but the objects only display when clicking the + button to add a line, and then the objects display as an object group.
This is by design, the tabs are a different render option for the object groups, their purpose was not to replace the core object groups functionality.
Here is what appears that you are asking above, is how to split a long scrolling form up into sections and each section is a TAB?
Where the controls making up the scrolling form are mostly ungrouped objects.
Comments are closed.