Difference between revisions of "QPR BusinessPortal Processes View"

From Mea Wiki
Jump to navigation Jump to search
(First draft down.)
Line 7: Line 7:
  
 
All processes can be published from the top of the process hierarchy, or starting from a specific lower-level branch.<br>  
 
All processes can be published from the top of the process hierarchy, or starting from a specific lower-level branch.<br>  
[[File:BPProcessesMainPage.png|500px|border|QPR BusinessPortal Processes Main Page]]<syntaxhighlight lang="Text">
+
[[File:BPProcessesMainPage.png|500px|border|QPR BusinessPortal Processes Main Page]]
Modeling client settings:
 
Grouping elements are element, for which the behavior "Group element" is ticked.
 
The elements within the grouping elements must have "Can belong to a group" ticked.
 
Grouping elements can be within grouping elements, if both "Grouping element" and "Can belong to a group" are ticked.
 
  
</syntaxhighlight>You can drill down to a lower process level by clicking on a process card or by navigating to a lower level using the process hierarchy in the left-hand side. You can also see the process details by clicking '''See Details''', or by switching to the '''Diagram View'''.
 
  
==== Modeling client settings ====
+
You can drill down to a lower process level by clicking on a process card or by navigating to a lower level using the process hierarchy ('''[[Sider]]''') on the left-hand side. You can also see the process details by clicking '''See Details''', or switch to the '''Diagram View'''.<syntaxhighlight lang="text">
 
+
Modeling tool settings:
* Grouping elements are elements, for which the behavior "Group element" is ticked.
+
Grouping elements are elements, for which the behavior "Group element" is ticked.  
* The elements within the grouping elements must have "Can belong to a group" ticked.
+
The elements nested within the grouping elements must have "Can belong to a group" ticked.
* Grouping elements can be nested within grouping elements, if both "Grouping element" and "Can belong to a group" are ticked.
+
Grouping elements can be nested within grouping elements, if both "Grouping element" and "Can belong to a group" are ticked.
</div>
+
</syntaxhighlight></div>
 
</div>
 
</div>
  
Line 27: Line 22:
  
 
== Card View ==
 
== Card View ==
The Card View visualizes the processes modeled in QPR EnterpriseArchitect / ProcessDesigner as cards. A card shows the name of the process and its description. Also, a link to See Details is provided.
+
The Card View visualizes the processes modeled in QPR ProcessDesigner / QPR EnterpriseArchitect as cards. A card shows the name of the process and its description.  
  
Cards can be clicked to expand lower-level processes or to view details about the selected process step by clicking '''See Details'''.
+
By clicking a card, lower-level process content becomes visible. Process details can be viewed by clicking '''See Details'''.
  
If the lowest hierarchical level does not contain hierarchical elements, the activities are visualized as an activity table instead of card components.
+
If a process level does not contain diagram elements, contents are visualized as a table instead of card components.
  
If a process does not contain any lower-level elements (or if there are connectors only) the card is displayed in greyscale and cannot be clicked.  
+
If a process does not contain any elements (or if there are connectors only), it cannot be clicked. This is indicated to users by showing the card in greyscale.  
  
Each process level is separated by a divider that states the number of the process level and in parentheses how many processes belong to it. The process level can be closed by clicking on the divider’s '''X icon'''.  
+
Each process level is separated by a divider that states the number of the process level and in parentheses, how many processes are on the given level. The process level can be closed by clicking on the divider's '''X icon'''. <syntaxhighlight lang="text">
 +
Modeling tool settings:
 +
Diagram elements are shown as cards.
 +
Diagram elements refer to elements that have the diagram behavior ticked.
 +
Please note, that diagram elements are also shown in the diagram/process hierarchy.
 +
</syntaxhighlight>
 
</div>
 
</div>
  
Line 41: Line 41:
  
 
== Diagram View ==
 
== Diagram View ==
The Diagram View simply shows the diagram view of the selected process. Clicking on a hierarchical element drills down to a lower process level – the view contents and URL update accordingly. You can scroll up to see the higher-level process level(s).  
+
The Diagram View simply shows the diagram view of the selected process. Clicking on a diagram element drills down to show the diagram view of the selected element – the view contents and URL update accordingly. You can scroll up to see the higher-level process level(s).  
  
Each process level is separated by a divider that states the name of the parent process that you are viewing. The process level can be closed by clicking on the divider’s '''X icon'''.
+
Each process level is separated by a divider that states the number of the process level and the name of the process that the user is viewing. The process level can be closed by clicking on the divider’s '''X icon'''.
  
If a hierarchical process element does not contain any lower-level elements (or if there are connectors only), this is indicated by the mouse pointer remaining an arrow (instead of turning into a hand).
+
If a diagram element does not contain any elements (or if there are connectors only), it cannot be clicked. This is indicated to the user by the mouse pointer remaining an arrow (instead of turning into a hand).
  
The diagram contents and layout are coming from the MEA WebService. If the layout or contents of the diagram need to be changed, this needs to be done in the modeling software.
+
The diagram contents and layout come from the MEA WebService and are displayed exactly as modeled in QPR ProcessDesiner / QPR EnterpriseArchitect. If the layout or contents of the diagram need to be changed, the changes need to be made in the modeling software.<syntaxhighlight lang="text">
</div>
+
Modeling tool settings:
 +
Only diagram elements can be clicked to drill down and view the diagram of the selected process, if the diagram element has content (other than connectors).
 +
Diagram elements refer to elements that have the diagram behavior ticked.
 +
</syntaxhighlight></div>
  
 
</div>
 
</div>
 
<div style="display: flex;flex-wrap: wrap;">
 
<div style="display: flex;flex-wrap: wrap;">
 
<div style="flex: 1 0 210px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#FFFFFF;margin:10px 0px 0px 10px;">
 
<div style="flex: 1 0 210px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#FFFFFF;margin:10px 0px 0px 10px;">
=== Details Dialog ===
+
=== Details View ===
To see the process details, click the '''See Details''' link on the process card. The Details dialog shows the name of the process, its description, selected attributes, the Inputs and Outputs graphic, and a table of lower-level processes. The Details dialog can be closed either by clicking outside the dialog or by clicking the close button at the bottom of the overlay.
+
To see process details, click '''See Details''' on the process card. The Details View shows the name of the process, its description, selected default attributes (Owner and Documents), the "Inputs and Outputs" graph, and lower-level process information in table(s). If the process in question contains both diagram elements (e.g., Business Processes in ODM, Sub-Processes in BPMN) and non-diagram elements (e.g., Activities in ODM, Tasks in BPMN), they are shown in separate tables. The Details View can be closed either by clicking outside the view box or by clicking the close button at the bottom.<syntaxhighlight lang="text">
</div>
+
Modeling tool settings:
 +
Diagram elements refer to elements that have the diagram behavior ticked. These types of elements are usually used at the top and intermediate process levels.
 +
Elements that do not have the diagram behavior ticked are usually used at the lowest process level.
 +
Documents refer to Information Items.
 +
</syntaxhighlight></div>
 
</div>
 
</div>
 
<div style="display: flex;flex-wrap: wrap;">
 
<div style="display: flex;flex-wrap: wrap;">
Line 62: Line 69:
 
== Sider ==
 
== Sider ==
 
<div style="display: flex;flex-wrap: wrap;">
 
<div style="display: flex;flex-wrap: wrap;">
The Sider on the left side of the screen shows the tree hierarchy of processes that are modeled in QPR EnterpriseArchitect / ProcessDesigner.
+
The Sider on the left side of the screen shows the diagram / process hierarchy. It is automatically generated with diagram elements, same as in QPR ProcessDesigner / QPR EnterpriseArchitect.
 
</div>
 
</div>
 
<div style="display: flex;flex-wrap: wrap;">
 
<div style="display: flex;flex-wrap: wrap;">
 
[[File:BPSider.png|250px|border|right|QPR BusinessPortal Sider]]<br>
 
[[File:BPSider.png|250px|border|right|QPR BusinessPortal Sider]]<br>
You can expand and collapse the hierarchy by clicking the small arrows. Clicking a process level on the hierarchy will select that process level and update the Card / Diagram view to show the contents of that process. The currently selected process level and path are highlighted in the process hierarchy shown on the Sider.
+
You can expand the hierarchy by clicking the small arrows. Clicking on a process on the hierarchy will select that process and update the Card / Diagram view to show the contents of that process. Selected process and path are highlighted in the process hierarchy.
</div>
+
The entire Sider can be resized, collapsed, and expanded using the small tab handle on the right edge of the Sider.<syntaxhighlight lang="text">
<div style="display: flex;flex-wrap: wrap;">
+
Modeling tool settings:
The Sider can be resized, hidden, and shown using the small tab handle on the right edge of the Sider.
+
The sider is automatically generated of elements that have the diagram behavior ticked.
</div>
+
</syntaxhighlight></div>
 
</div>
 
</div>
  
Line 76: Line 83:
  
 
== Page Header ==
 
== Page Header ==
The Page Header shown on the top part of the view displays basic information about the selected process on top level of the process hierarchy.<br>
+
The Page Header shown at the top of the Card / Diagram view displays basic information about the selected process branch - how many processes fall under the branch, on how many levels, and how many unique roles are featured.<br>
 
[[File:BPPageHeader.png|500px|border|Processes View Page Header]]<br>
 
[[File:BPPageHeader.png|500px|border|Processes View Page Header]]<br>
 
The Page Header also contains buttons to switch between the Card View and the Diagram View.  
 
The Page Header also contains buttons to switch between the Card View and the Diagram View.  
</div>
+
<syntaxhighlight lang="text">
 +
Modeling tool settings:
 +
The processes statistic counts diagram elements, as these are usually used for higher-level processes. Lower-level process flow elements (non-diagram elements) are left out.
 +
Levels counts the maximum number of process levels that the process branch features.
 +
Roles counts the number of unique roles (swimlanes) present in all of the processes present in the branch.
 +
</syntaxhighlight></div>
 
</div>
 
</div>
  

Revision as of 12:17, 13 June 2023

Processes Main Page

This is a starting point in exploring process content. This page presents process content in two alternative views: the Card View and the Diagram View. In the Card View, processes are shown as cards, whereas the Diagram View shows the process content exactly as it has been modeled in the modeling tool (QPR ProcessDesigner or QPR EnterpriseArchitect).

Processes on the top level are often classified within some grouping elements. If this is the case, the view shows the process cards and the name of their grouping element.

All processes can be published from the top of the process hierarchy, or starting from a specific lower-level branch.
QPR BusinessPortal Processes Main Page


You can drill down to a lower process level by clicking on a process card or by navigating to a lower level using the process hierarchy (Sider) on the left-hand side. You can also see the process details by clicking See Details, or switch to the Diagram View.
Modeling tool settings:
Grouping elements are elements, for which the behavior "Group element" is ticked. 
The elements nested within the grouping elements must have "Can belong to a group" ticked.
Grouping elements can be nested within grouping elements, if both "Grouping element" and "Can belong to a group" are ticked.

Card View

The Card View visualizes the processes modeled in QPR ProcessDesigner / QPR EnterpriseArchitect as cards. A card shows the name of the process and its description.

By clicking a card, lower-level process content becomes visible. Process details can be viewed by clicking See Details.

If a process level does not contain diagram elements, contents are visualized as a table instead of card components.

If a process does not contain any elements (or if there are connectors only), it cannot be clicked. This is indicated to users by showing the card in greyscale.

Each process level is separated by a divider that states the number of the process level and in parentheses, how many processes are on the given level. The process level can be closed by clicking on the divider's X icon.
Modeling tool settings:
Diagram elements are shown as cards. 
Diagram elements refer to elements that have the diagram behavior ticked. 
Please note, that diagram elements are also shown in the diagram/process hierarchy.

Diagram View

The Diagram View simply shows the diagram view of the selected process. Clicking on a diagram element drills down to show the diagram view of the selected element – the view contents and URL update accordingly. You can scroll up to see the higher-level process level(s).

Each process level is separated by a divider that states the number of the process level and the name of the process that the user is viewing. The process level can be closed by clicking on the divider’s X icon.

If a diagram element does not contain any elements (or if there are connectors only), it cannot be clicked. This is indicated to the user by the mouse pointer remaining an arrow (instead of turning into a hand).

The diagram contents and layout come from the MEA WebService and are displayed exactly as modeled in QPR ProcessDesiner / QPR EnterpriseArchitect. If the layout or contents of the diagram need to be changed, the changes need to be made in the modeling software.
Modeling tool settings:
Only diagram elements can be clicked to drill down and view the diagram of the selected process, if the diagram element has content (other than connectors).
Diagram elements refer to elements that have the diagram behavior ticked.

Details View

To see process details, click See Details on the process card. The Details View shows the name of the process, its description, selected default attributes (Owner and Documents), the "Inputs and Outputs" graph, and lower-level process information in table(s). If the process in question contains both diagram elements (e.g., Business Processes in ODM, Sub-Processes in BPMN) and non-diagram elements (e.g., Activities in ODM, Tasks in BPMN), they are shown in separate tables. The Details View can be closed either by clicking outside the view box or by clicking the close button at the bottom.
Modeling tool settings:
Diagram elements refer to elements that have the diagram behavior ticked. These types of elements are usually used at the top and intermediate process levels.
Elements that do not have the diagram behavior ticked are usually used at the lowest process level.
Documents refer to Information Items.

Sider

The Sider on the left side of the screen shows the diagram / process hierarchy. It is automatically generated with diagram elements, same as in QPR ProcessDesigner / QPR EnterpriseArchitect.

QPR BusinessPortal Sider

You can expand the hierarchy by clicking the small arrows. Clicking on a process on the hierarchy will select that process and update the Card / Diagram view to show the contents of that process. Selected process and path are highlighted in the process hierarchy.

The entire Sider can be resized, collapsed, and expanded using the small tab handle on the right edge of the Sider.
Modeling tool settings:
The sider is automatically generated of elements that have the diagram behavior ticked.

Page Header

The Page Header shown at the top of the Card / Diagram view displays basic information about the selected process branch - how many processes fall under the branch, on how many levels, and how many unique roles are featured.
Processes View Page Header
The Page Header also contains buttons to switch between the Card View and the Diagram View.

Modeling tool settings:
The processes statistic counts diagram elements, as these are usually used for higher-level processes. Lower-level process flow elements (non-diagram elements) are left out.
Levels counts the maximum number of process levels that the process branch features.
Roles counts the number of unique roles (swimlanes) present in all of the processes present in the branch.