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; } } }

Datenbank-Eintrag bleibt erhalten, obwohl Unterseite archiviert wurde

Thomas Löschner

Hallo Community,

in meinem Confluence Space gibt es eine Datenbank. Unter dieser Datenbank existierten 4 Unterseiten, die entsprechend auch in der Datenbank als Einträge vorhanden sind. Per Automatisierung wird eine Seite im Space archiviert, sobald sich der Page Status auf "Verified" ändert. Die Automatisierung funktioniert prinzipiell einwandfrei. Die Seite wird ins Archiv verschoben und ist auch nicht mehr im Page Tree gelistet:

Archivierung Menü.png

Allerdings hätte ich erwartet, dass der Eintrag der ins Archiv verschobenen Unterseite auch aus der Datenbank gelöscht wird. Dem ist jedoch nicht so, wie hier zu sehen ist:

Archivierung Datenbank.png

Wie kann ich sicherstellen, dass der Eintrag in der Datenbank ebenfalls gelöscht wird?

Accepted answers

Tomislav Tobijas

Hey @Thomas Löschner ,

Yeah... unfortunately, this isn't done automatically. 🫤

What you would need to do is, within that same automation that archives the pages, also create a 'call'/action that will actually update the database.

Now, actions related to databases are not supported at the moment. For example, there's this feature request: CONFCLOUD-77878: Please add a "Databases" component to Confluence Automation, like Triggers, Actions

What you could try instead is to create Rovo agent and call it in the automation. 🤔
Although I can say I'm not 100% if that will work or not, as Rovo supporting databases is relatively new, and I haven't tested this properly.

Apart from that, I would suggest playing around with APIs, but API for databases is not yet supported/released: CONFCLOUD-77328: Allow Manipulation of Confluence Databases using the REST API 🙁

Cheers,
Tobi

All comments

Tomislav Tobijas

Hey @Thomas Löschner ,

Yeah... unfortunately, this isn't done automatically. 🫤

What you would need to do is, within that same automation that archives the pages, also create a 'call'/action that will actually update the database.

Apart from that, I would suggest playing around with APIs, but API for databases is not yet supported/released: CONFCLOUD-77328: Allow Manipulation of Confluence Databases using the REST API 🙁

Cheers,
Tobi

Thomas Löschner

Thank you for your feedback!

Using Rovo agent might be a good idea, I will give it a try.

To be honest, it's a bit sad that Atlassian does not provide full functionality for Databases. In my opinion, new features like Databases should always come with basic API calls for the most common use cases (here: simply editing a database) as well as automation actions.

Cheers,
Thomas

Tomislav Tobijas

To be honest, it's a bit sad that Atlassian does not provide full functionality for Databases. In my opinion, new features like Databases should always come with basic API calls for the most common use cases (here: simply editing a database) as well as automation actions.

Agreed! I saw this as quite a highly requested feature 👀

I'll be at Team in a couple of weeks and I just might pop by the Confluence booth to give them a little nudge when it comes to some improvements for databases 😁

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud