Copy a page automatically via scheduled trigger

[Antonina Yudina]

hello,

hope, somebody can help me solve an issue. My plan is to copy a page automatically via scheduled trigger. Unfortunately, I does not work the way I would like to. As a trigger I can chose the change in the page status as a trigger but it does not fit my purpose. The page should be copied every 2nd week.

thank you in advance for your help.

regards,

[Cyrille Martin]

Hi @Antonina Yudina 

Yes, you can do it with Automation and a Scheduled trigger like that :

Hope it will help.

Regards,

[Antonina Yudina]

Hi @Cyrille Martin

I got it so far. What would be the next step? 

[Kristian Klima]

@Antonina Yudina 

You can configure the Copy Page action

[Antonina Yudina]

I was able to manage also this step. Unfortunately, Confluence requires a reference page before.

[Cyrille Martin]

Yes, mention the page you want to copy every two weeks.

Regards,

[Antonina Yudina]

in which step/action?

[Antonina Yudina]

how do I mention that page?

[Kristian Klima]

@Antonina Yudina is your use case to

• create a copy a single specific page every two weeks or multiple pages?
• is it within a space or between two spaces?

I'm asking because in certain scenarios (permutations of the above options), there might be a neat way to do that (involves an app).

[Antonina Yudina]

the scenario is as follows: every two weeks a report page must be updated. for this purpose the previous report has to be copied in the same space with a different title. a responsible person should be able to edit the current report which will be copied in the next step again. it is always the latest version which should be copied. is it somehow possible to automate?

[Cyrille Martin]

Does your generated page have a pattern for its title ? like "follow-up YYYY/MM/DD"

[Antonina Yudina]

yeap, it does: name of the report + currentdate {{now}}

[Kristian Klima]

I'd approach this from the opposite end. 

Warning: I'll speak as a content life-cycle manager now :) 

• I'd have a 'master' page of the Report.
• This would be the only page to be edited and updated.
• After each update, the updating person would create a snapshot (copy) of the page with the title following the agreed nomenclature. 

Benefits:

• only update a single page - which has its full version history
• that full version history is located in a single location.
• you end up with a clean series of dated report pages - clearly marked and easily trackable to the version history of your master page
• the process involves manual work anyway (updating the page) so adding an extra step of creating a snapshot page is a 10 second job (and it could be automated).
• the end result is the same
  • a series of report pages
  • the process is simplified (editing only one page)
  • the edit history is easier to track and follow up

[Antonina Yudina]

@Kristian Klima hm, an interesting idea from a different point of view. I think it ll be easier to solve the issue using your approach. I thank you a bunch for sharing it ;).