contextual sidebars in configuration workspace

[VSN]

Hi team, 

i am using configuration workspace. i wanted to under the reason for why their is difference in the contextual side bars. for one of the table we do have only few elements in contextual sidebars and for another table record more elements and those are duplicated also..

did anyone knows the reason ?

[-O-]

Those are in the end routs to UX Screens which have conditions. The availability of the buttons depends on the availability of the UX Page the button is linked to.

Of course depending on how many UX Screens have been configured in the sidebar tab for the current standard record page and whether the current record fulfills the conditions or not, a button will be available or not.

In Xanadu those tabs are configured using Page Collections (you can find that module in the Navigator) which have routs and UX Screens attached to them. You can see there what is available. If you open a given UX Page you will find the related list of conditions under which a UX Page will be included or not.

In older versions of SN this is not Page Collections based, but the principle applies: it is still showing UX Screens associated with the Tab component and conditions on the those UX Screens govern when a button is available or not.

[-O-]

Attached is how this looks in older versions of SN. Here the Tab sidebar contains view ports which "link in" sub-pages. Which have conditions which set when a tab is available.

[VSN]

@-O- @-O- what will be the reason for displaying records in the same workspace? where I can find that extra configuration.

[-O-]

> what will be the reason for displaying records in the same workspace

Are you confusing pages for records?

The (sub) pages displayed in the sidebar could in theory be records, but in fact can be anything one can display in a page.

Like both the "Attachments" and "Templates" tab contents are actually (sub) pages/UX Screens.