You can publish a document with the result of the gap analysis of a solution.

To each business process with requirements defined, a table is added with the requirements. For the not-business-process-specific requirements for the solution, a table is added in a separate 'General requirements' chapter. For each requirement, this information is shown: Requirement, Type, Status, Priority, Estimate, and Activity.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

Standard procedure

1.	Click Business process implementation.
2.	Click Publish.
3.	Click Gap analysis.
4.	On the Publish Gap analysis document dialog, define the required settings and click OK.

Notes

You can also publish a gap analysis document from the Analyze gaps page. To do so, click Publish, Gap analysis.

On the Publish gap analysis document dialog, you can define these Parameters:

• Language - If you have defined translations for the solution, select the language in which you want to publish the solution. The elements in your solution that are not translated into this language are published in the original language. You can only publish in another language if this language is defined for the solution itself. So, for example, all content of the solution is translated to a specific language. However, no translation for this language is defined for the solution itself. In this case, you cannot publish in this language.
• Business processes - Define which business processes are added to the document.
  • All - All business processes in the selected solution are added to the document.
  • In scope - Only the business processes that are in scope are added to the document.
  • Gaps - Only the business processes that are marked as a gap are added to the document
• Include business process descriptions - Set to Yes to add, for each business process that is published to the document, the description as well.
• Scope and gap summary - Set to Yes to give, for each business process that is added to the document, information on its scope and gap categorization. For example: This process is out of scope, categorized as fit.
• Scenarios - Set to Yes to publish business processes of type Scenario to the document.
  
• Attachment lists - Set to Yes to add a list with attachments to each business process or activity with attachments.
  
• Include version number - Set to Yes to add the version number of each element to the document.
• Include change history - Set to Yes to add the change history of each element to the document.
• Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published.