This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 77 Next »

You need Ad Hoc Workflows 3.0.3 or newer to be able to import the workflows. Find out how you can import workflows


Unknown macro: {repository-workflow}
Unknown macro: {repository-description}
  • Allows any user to submit topics, which are approved by a Subject Matter Experts and FAQ administrations.
  • Only the Author and FAQ Administrators can see the submitted FAQ until it is published.
Unknown macro: {workflow-body}
Unknown macro: {workflow}
Unknown macro: {description}

Multi-Step FAQ creation workflow which allows users to submit topic/pages to be approved by the assigned SME(s) and FAQ Admin. Only the SME's and FAQ Admin can see the submissions before they are approved.

Unknown macro: {workflowparameter}

confluence-users

Unknown macro: {workflowparameter}

confluence-users

Unknown macro: {state}
Unknown macro: {state}
Unknown macro: {approval}
Unknown macro: {state}
Unknown macro: {approval}
Unknown macro: {state}
Unknown macro: {approval}
Unknown macro: {state}
Unknown macro: {state}
Unknown macro: {state}
Unknown macro: {trigger}
Unknown macro: {set-metadata} <at:var at:name="user" />
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> has been submitting by [~<at:var at:name="user" />] and is waiting for your approval.

Unknown macro: {trigger}
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> has been approved by [~<at:var at:name="user" />] and is waiting for your review.

Unknown macro: {trigger}
Unknown macro: {send-email}

Your FAQ <at:var at:name="page" /> submission has been rejected.

Unknown macro: {trigger}
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> has been approved by [~<at:var at:name="user" />] and is waiting for your approval.

Unknown macro: {trigger}
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> has been rejected by [~<at:var at:name="user" />].

Unknown macro: {trigger}
Unknown macro: {add-restriction}
Unknown macro: {add-restriction}
Unknown macro: {trigger}
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> submitted by [~@FAQ Author@] has been approved by [~<at:var at:name="user" />>]
and is waiting for your review.

Unknown macro: {add-restriction}
Unknown macro: {trigger}
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> has been published

Unknown macro: {remove-restriction}
Unknown macro: {trigger}
Unknown macro: {send-email}

The FAQ <at:var at:name="page" /> has been updated by [~<at:var at:name="user" />] and requires your approval


Configuration

After importing the workflow to your instance in global administration, you can add and apply the workflow to a space.

In each space, you need to add the workflow parameters values that will be used in the workflow:

  • FAQ-Administrators.
  • Component Leads.

The values of the workflow parameters are used by the workflow to assign reviewers to content reviews in the workflow. They are also used as recipients for email notifications for workflow events.

These values can be any existing Confluence user group. The default group for each of the workflow parameter values is the confluence-users group.

A space administrator can add these values in the space tools Document Management tab for parameters.


The workflow parameter values can also be edited using workflow builder.


Workflow rules:

  • Any user can submit an FAQ
  • Only the Author and FAQ Administrators can see the submitted approval
  • FAQ Administrator determines if the FAQ is appropriate and assigns the appropriate Component lead
  • If the FAQ is approved, then the FAQ become visible to the Component lead and he/she is notified
  • If the FAQ is rejected, then the Author is notified
  • If the FAQ is approved by the Component lead then it is re-assigned to the FAQ Administration for publishing
  • If the FAQ is published then it becomes visible to everybody
  • If the FAQ is rejected in this state, then the Author and Component lead are notified
  • If the FAQ is updated after it has been published, then it has to be approved by the Component lead and FAQ administrator again
  • No labels