How do I render a Confluence page programatically?

[Sammo Gabay]

When somebody creates a blog post in one of our Confluence pages, we want to e-mail the content to a distribution list. I have successfully created an event listener using ScriptRunner to call a mail-dispatch API and send the raw page content, which renders all right as HTML in an e-mail client. However, any macros in the content are in raw wiki code form and are not rendered. How can I use the Confluence Java API to render the page content to (X)HTML and send that to my e-mail service?

I am well versed with the Jira Java API and ScriptRunner but am newer to the Confluence API, but I have noticed much overlap.

[PD Sheehan]

I do not believe there is any real archive option for Jira Server. This is a datacenter functionality only.

What we do is "archive" (big air quotes) at the project level. When a project is no longer used, we apply a special permission scheme that will hide the issues from everyone but administrators.

But the issues are still in the system, still using up space, still being indexed. But at least they don't clutter the user's experience.

The next step (which I've never actually taken) is to do a full xml backup of your instance and archive the XML with some attribute indicating that this xml is to archive that project. Then you would delete the project completely (all the issues will be gone and can't be searched). Should you need to view that project data in the future, you should be able to reimport just that project from your full instance xml.

As for workflow cleanup... just delete all "inactive" workflows. Those are backup and old copies of workflows that are not loner associated with any issue/project. Those are safe to delete.

You can't delete any workflows for projects archived using the fake permission-level archive as I described. Only after the project has been fully deleted (and the workflow is not shared) can you consider deleting the workflows.