I want to create an automation in which: * Gather pages last modified before 1st January 2020. * Move all those pages under a page that is already created. I am unsure why it is giving an error "Incompatible Components" to move those pages. Edit: I am adding SS for reference, I know why it isn't working. I want to know if it is feasible.

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

A automation where each page that was edited before certain time will be moved below different page

Nikhil Vichare

I want to create an automation in which:

Gather pages last modified before 1st January 2020.
Move all those pages under a page that is already created.

I am unsure why it is giving an error "Incompatible Components" to move those pages.

Edit: I am adding SS for reference, I know why it isn't working. I want to know if it is feasible.

Accepted answers

Aron Gombas _Midori_

You should paste a screenshot of the rule so that the community members can review this. Without that it is hard to tell what is the reason of the error.

Shawn Doyle - ReleaseTEAM

To add to @Aron Gombas _Midori_ answer, you need to add something that returns the set of pages. Multiple ways to do it, here is an example of adding the page branch.

All comments

Aron Gombas _Midori_

You should paste a screenshot of the rule so that the community members can review this. Without that it is hard to tell what is the reason of the error.

Nikhil Vichare

Done

Aron Gombas _Midori_

The problem is, I think, that the Scheduled trigger will not "provide" pages to the subsequent components.

Solution: after the trigger, you need to add another component that provides pages.

(I think you would want to periodically run a CQL search something like "lastUpdated < 2020-01-01" to collect the pages and then you can remove the "if" test.)

Shawn Doyle - ReleaseTEAM

To add to @Aron Gombas _Midori_ answer, you need to add something that returns the set of pages. Multiple ways to do it, here is an example of adding the page branch.

Nikhil Vichare

Thanks @Aron Gombas _Midori_ and @Shawn Doyle - ReleaseTEAM , the solution worked for me. You have been a great help. Thanks a lot.

Aron Gombas _Midori_

@Nikhil Vichare The "archive" automation has its own limits in Confluence Automation.

If you reach those and look for something more scalable and eventually "more intelligent", then make sure you try the automatic status tracking (which gives you access to CQL searches, macros, notifications, reports) and automatic archiving features of the Better Content Archiving app.

Related to your use case, here is an automation scheme which contains 2 automations. The first will archive all contents in the "To archive" status weekly on Sundays (midnight), while the second will delete all contents in the "To delete" status 2 hours later:

The two together give you a simple, but flexible page retention mechanism.

(Discl. it is a paid and supported app developed by our team. Free for 10 users!)

Nikhil Vichare

Hey @Aron Gombas _Midori_ , thanks for the suggestion. I think most of my usecases are covered by automation created before. But in future if I require, I will definitely check this out.

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