nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

first row in table (underneath header) has unwanted border / sort function

Volker Blum_xlsv7a

Hi,

after upgrading the COnfluence DC instance to 8.5 our customer suffers from a strange behaviour of the tables. The first row underneath the header generated the text in borders with grey background. They act as kind of sorting buttons. clicking on them does the same as the header does. I have no clue where this comes from and how to remove it. I have added a row and any empty field shows the buttons already. Changing header etc all of this doesn´t help. I am cunfused. Could someone give me a hint, hoiw to solve this?

This is how it looks in view mode:

Bildschirmfoto 2024-01-30 um 10.37.47.png

This is how it looks in edit mode: (it is capsuled in an excerpt macro, but that was the same in the previous version and did not affect the table)

Bildschirmfoto 2024-01-30 um 10.39.09.png

Thanks for any help and kind regards

Volker

Accepted answers

Zac Xu

Hi @Volker Blum ,

Do you mind sharing the storage format with us to diagnose the issue?

how-to-retrieve-the-storage-format-from-a-specific-confluence-page

Cheers,

Zac Xu

Alex Medved _ConfiForms_

This looks like this bug https://jira.atlassian.com/browse/CONFSERVER-56489

That was almost fixed (kind of) in 8.5.5

Alex

All comments

Zac Xu

Hi @Volker Blum ,

Do you mind sharing the storage format with us to diagnose the issue?

how-to-retrieve-the-storage-format-from-a-specific-confluence-page

Cheers,

Zac Xu

Volker Blum_xlsv7a

Thank you Zac Xu- this is what I got:

<p>This article describes the configuration items in Identity Manager.</p>
<p><ac:image ac:title="Configuration items in PRIME" ac:queryparams="effects=border-simple,blur-border" ac:alt="Configuration items in PRIME" ac:height="250"><ri:attachment ri:filename="DataPools_crop.png" /></ac:image></p>
<table class="wrapped"><colgroup><col /><col /></colgroup>
<tbody>
<tr>
<th>Data sources</th>
<td>
<p>Data sources provide the connection to the data stored in internal tables in Identity Manager or any external source, such as LDAP, JDBC, SCIM or CSV files. The data source describes the “physical” representation of the data pool fields.</p></td></tr>
<tr>
<th>Data pools</th>
<td>
<p><ac:link><ri:page ri:content-title="Set up data pool in Identity Manager" /><ac:plain-text-link-body><![CDATA[Data pools]]></ac:plain-text-link-body></ac:link> are abstract representation of data, that comes from a data source. Data pools consist of a list of fields and their data types. The processes in Identity Manager work on data pool fields. The processes are unaware of where the data is actually stored.</p></td></tr>
<tr>
<th>Core templates</th>
<td>
<p><ac:link><ri:page ri:content-title="Templates in Identity Manager" /><ac:plain-text-link-body><![CDATA[Core templates]]></ac:plain-text-link-body></ac:link> are an interpretation of the data pools. They describe usage and representation of the data from the data pools and one template for each type of data is needed. The core templates defines <ac:link><ri:page ri:content-title="Set up state graph in Identity Manager" /><ac:plain-text-link-body><![CDATA[states]]></ac:plain-text-link-body></ac:link>, start <ac:link><ri:page ri:content-title="Set up process in Identity Manager" /><ac:plain-text-link-body><![CDATA[processes]]></ac:plain-text-link-body></ac:link> and <ac:link><ri:page ri:content-title="Set up form in Identity Manager" /><ac:plain-text-link-body><![CDATA[forms]]></ac:plain-text-link-body></ac:link>.</p></td></tr>
<tr>
<th colspan="1">Core objects</th>
<td colspan="1"><span style="color: rgb(255,0,0);"><span style="color: rgb(51,51,51);">Core objects in Identity Manager are, for example, identity, card, and certificate.</span></span></td></tr>
<tr>
<th>State graphs</th>
<td>
<p>Every object has a life cycle with states and can change from one state to another. This is defined by <ac:link><ri:page ri:content-title="Set up process in Identity Manager" /><ac:plain-text-link-body><![CDATA[processes]]></ac:plain-text-link-body></ac:link>. <ac:link><ri:page ri:content-title="Set up state graph in Identity Manager" /><ac:plain-text-link-body><![CDATA[State graphs]]></ac:plain-text-link-body></ac:link> define the possible states of a core template.</p></td></tr>
<tr>
<th>Processes</th>
<td>
<p><ac:link><ri:page ri:content-title="Set up process in Identity Manager" /><ac:plain-text-link-body><![CDATA[Processes ]]></ac:plain-text-link-body></ac:link>are used to create objects in an initial state and to change states of objects.</p></td></tr>
<tr>
<th>Search configurations</th>
<td>
<p>To search for objects, a <ac:link><ri:page ri:content-title="Set up search configuration in Identity Manager" /><ac:plain-text-link-body><![CDATA[search configuration]]></ac:plain-text-link-body></ac:link> is used. Different <ac:link><ri:page ri:content-title="Users and roles in Identity Manager" /><ac:plain-text-link-body><![CDATA[roles]]></ac:plain-text-link-body></ac:link> defines what will be shown.</p></td></tr>
<tr>
<th>Forms</th>
<td>
<p>In order for Identity Manager to show the result from a search, <ac:link><ri:page ri:content-title="Set up form in Identity Manager" /><ac:plain-text-link-body><![CDATA[forms]]></ac:plain-text-link-body></ac:link> are used to define how the data shall be shown.</p></td></tr></tbody></table>
<p><br /></p>