Approvals for Confluence (Appfox)

Capable recognises 3 items from Approvals for Confluence (AppFox): page approvals convert, and 2 macros are reported and left as they are.


#About the app

Approvals for Confluence is an AppFox app for page review and sign-off.

Authors request approval of a whole page from the byline, approve parts of a page with a Section Approval macro, and show approval status with a status macro.

#How Capable is different

  • Page approvals become Capable Approvals on the same page, with status, approvers and their responses, quorum, expiry and history.

  • The page body is not changed, and the AppFox approval data is left where it is.

  • Comment text from the history is not copied: the event says a comment was provided but not migrated.

  • Email notification settings do not carry over.

  • Section Approval and the Status Macro have no Capable equivalent and stay on the page as they are.


#At a glance

Macro

In Capable

Support

Page Approval

Capable Approval on the same page

Converted

Section Approval

Not converted

Reported only

Status Macro

Not converted

Reported only

#New in this release

  • When an AppFox request has no quorum, every approver must approve after conversion too, as in AppFox.


#What each one does

#Page Approval

Becomes

Capable Approval on the same page

Support

Converted

The page body is not changed, and the AppFox approval data is left where it is. You need space admin permission in each affected space.

Carried over

  • Status: pending, approved or rejected

  • Approvers and each one's response and date

  • Quorum

  • Expiry on a date or after an interval

  • Requester and request date

  • History, with reasons

Not carried over

  • Comment text in the history: the entry says a comment was provided but not migrated

  • Email notification settings


#Detected but not converted

These are counted so you can see how many you have. They stay on the page exactly as they are.

#Section Approval

Becomes

Not converted

Support

Reported only

Section level approvals have no Capable equivalent, so the macro stays as it is.

#Status Macro

Becomes

Not converted

Support

Reported only

The approval status display has no Capable equivalent, so the macro stays as it is.



State, not content. That is why it is careful.