Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,555
Community Members
 
Community Events
176
Community Groups

Page Status as a condition for automation purposes

Howdy,

I want to create automation rules that trigger based on a page status value. Are there any references for page status as a condition?

There already is a trigger for the page status. But if I want to combine that with a cron trigger...

 

Cheers

 

2 answers

Hi @Andreas Schmidt

this one gave me headaches.

From what I see, it seems like the content or page smartValues are not loaded with data inside a branch rule - don't ask me why...

Generally speaking, {{content.status}} should provide you with the status name for a page and whilst it does so in the first level of a rule (no branch), it is not working inside the branch rule.

Long story short: {{content.status}} inside an advanced compare condition should do the job - due to whatever reasons it does not.

I checked with different branching approaches (cql and the page one) but both seem to not work properly for that matter.

Furthermore, I checked with another trigger to proof my suspicion: When using {{content}} inside a branch rule with a trigger that sets {{content}} (e.g. Comment added) - the {{content}} smart value inside the branch will remain the one from the trigger. 

From my point of view, this is a bug. I will go ahead and contact the A4C product team about this and let you know if there are any updates.

Greetings
Gideon 

Hi Gideon,

Thanks for the reply. It confirms issues I had with {{content.status}}. 

Cheers!

@Andreas Schmidt 

Depending on what the automation action is you want to trigger, I recommend looking into the dedicated Confluence content lifecycle management app Better Content Archiving. In the past 15 years, the app has been the go-to tool for Confluence users for automatic page status classification, content owner notifications, content review workflows, and automatic archiving.

After the Data Center (Server) version, now it's available for Confluence Cloud! You can request the Early Access version by dropping me a line at levente.szabo@midori-global.com.

confluence-cloud-content-status-overview.png

Anyone who is interested in a dedicated app to manage the content lifecycle for Confluence (that also scales for large teams' requirements) instead of navigating automation rules is welcome to try Better Content Archiving for Confluence Cloud! (Join our Slack for faster exchange.)

Learn more here about the EAP and watch the tutorial video here!

It's free until the GA release and Early Access users are in for discounts at the official launch.

(Please note that I'm part of the team developing Better Content Archiving for Confluence.)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events