Page Approval for Confluence (Appfire)
Capable recognises 4 items from Page Approval (Appfire); none convert yet, and all 4 are reported and left as they are.
#About the app
Page Approval for Confluence is an Appfire app for requesting and recording page approvals from the byline.
Requests can use all approvers, a quorum or an approval chain, add acknowledgers, a due date and a priority, and report macros list approvals and acknowledgements.
#How Capable is different
Nothing converts yet: pages with an Appfire approval and its report macros are counted so you can see the scale, and left as they are.
Pages are found by their stored approval state, not by a macro on the page.
Capable Approval has no approval chain, acknowledgers, request due date or priority.
#At a glance
Macro | In Capable | Support |
|---|---|---|
Page Approval | Not converted | Reported only |
Page Approval Report | Not converted | Reported only |
Page Acknowledgement Report | Not converted | Reported only |
Page Approval Macro | Not converted | Reported only |
#Detected but not converted
These are counted so you can see how many you have. They stay on the page exactly as they are.
#Page Approval
Becomes | Not converted |
|---|---|
Support | Reported only |
Pages are found by their stored approval state, not by a macro. Capable Approval has no approval chain, acknowledgers, due date or priority.
#Page Approval Report
Becomes | Not converted |
|---|---|
Support | Reported only |
Counted and left as it is.
#Page Acknowledgement Report
Becomes | Not converted |
|---|---|
Support | Reported only |
Capable has no acknowledgements, so it is counted and left as it is.
#Page Approval Macro
Becomes | Not converted |
|---|---|
Support | Reported only |
The older macro found on pages imported from Server or Data Center. Counted and left as it is.
#Related
State, not content. That is why it is careful.
