MEGA Publisher (Level 1) - HOPEX - Lab Exercises
MEGA Publisher (Level 1) - HOPEX - Lab Exercises
Level 1
Version HOPEX – Lab Exercises
Document reference:
Code PUB1
Version: 1.0
No part of this document may be reproduced, translated or transmitted in any form or by any means without the
express written permission of MEGA International.
© MEGA International, Paris, 1992-2013. All rights reserved.
Contents
Contents......................................................................................................................................................3
General Conventions...................................................................................................................................5
1.3. Generating Reports (MS Word) from a Report Template (MS Word)........................................8
2.2. Explorer.....................................................................................................................................13
8.2. Scenario.....................................................................................................................................36
Corrections of Lab Exercise 2 Discovering the MetaModel and the Query Assistant...............................43
Appendix...................................................................................................................................................52
2 Operations.........................................................................................................................................53
5 Messages Sent...................................................................................................................................54
6 Messages Received............................................................................................................................54
General Conventions
Whenever directed to 'click', this is understood to mean clicking the left mouse button.
Lab Exercise 1.
Generating Reports (MS Word)
Reports (MS Word) may be generated using a report template (MS Word) that already exists in MEGA,
or one you can create from scratch. In this exercise, you will create a report (MS Word) using a report
template (MS Word) which is predefined in MEGA.
Update a report (MS Word) with new data from the repository
To start MEGA:
3. Click OK.
4. In the dialog box that appears, select the 03-MEGA 2009 Training Exercise Solutions repository.
1. From the Home Navigation Window, expand the “Process Models” library by clicking on the + sign.
6. Expand the Organizational Process folder, right-click the “Take product order” organizational
process and select New > Report (MS Word).
8. Click Next. You can then choose the location to save the created report (MS Word). For this exercise
leave the default location.
9. Click Finish.
1. In the report (MS Word) obtained, identify the text zones and MEGA links by using the keyboard
shortcut: ALT + F9.
10. Insert a “Conclusion” paragraph preceding the appendices, in which you can enter text of your
choice.
12. Note that your report (MS Word) is connected to the “Take Product Order” organizational process.
1. Modify the comment of the “Sales Assistant” org-unit and modify the drawing of the “Take Product
Order” organizational process flowchart.
14. Open the properties dialog box of the “Take Product Order” organizational process. In the General
tab, click the Documents sub-tab.
15. Right-click the “Take Product Order” report (MS Word) and select Reinitialize.
16. Note the result when the report (MS Word) has again been regenerated:
The “Conclusion” text you entered in the generated report (MS Word) no longer appears.
1. Right-click the “Take Product Order.doc” report (MS Word) and select Detach from MEGA.
18. In the Detach from dialog box, verify the report (MS Word) save location is the desktop and click
OK.
19. In MS Word, check that the report (MS Word) is present without a link to the folder that was
specified when detaching from MEGA.
Often companies have their own style sheets for documents. This style sheet can be applied to Word
reports (MS Word) generated with MEGA by replacing the default template with a template that uses the
defined styles. For this exercise we provide a sample replacement template to demonstrate.
1. Locate the file mycompany.dot that is in the folder <MEGA Environment path>/Training/Training
Samples/Publisher.
20. Place the mycompany.dot file in the Mega_usr folder of the environment.
21. In the Utilities Navigation Window, expand the Report template (MS Word) folder.
22. Duplicate the Organizational Process Documentation template and name it “Organizational
Process Documentation (Duplicate)”.
23. Right-click the “Organizational Process Documentation (Duplicate)” file and select Properties.
24. Under the Report Template (MS Word) tab, in the Stylesheet field, click the right-facing arrow and
select Style sheet.
25. Select Mycompany.dot, click OK and then close the Properties dialog box.
26. Create a new report (MS Word) for the “Take Product Order” organizational process, and assign it
the “Organizational Process Documentation (Duplicate)” template.
27. Open it and compare it with the other “Take Product Order.doc” report (MS Word) you created
earlier with the MEGA style sheet.
Vista\Windows 7
MEGA.
The reports (MS Word) you have created so far using the standard report templates (MS Word), do not
entirely meet your requirements. Since you need more advanced customizations, you will build the
various elements that will let you generate the new report (MS Word) on the basis of the requirements
given below.
The report (MS Word) describes an organizational process. The title will display the name of the
organizational process next to the corresponding icon. In the body the following elements will be
presented: general description, flowchart, operations, org-units, sent messages and received messages.
Messages will have to be retrieved by means of manual queries.
The generated report (MS Word) must look like the one shown in the annex of this training manual.
The next three lab exercises will guide you through the steps you need to create the required report
template (MS Word), notably:
2.2. Explorer
This lab exercise is intended as a review of the basic query features provided with the MEGA platform.
These features are covered in detail in the modeling courses (MEGA Process, MEGA Architecture, etc).
In order to study how the explorer functions, we will browse through the MetaModel from the Business
Process “Provide Small Appliances”. Follow the procedure below:
1. Open the Home navigation window and expand the “Process Models” library and the Business
Processes folder.
28. Right-click the “Provide Small Appliance” business process and select Explore.
30. Verify the different kinds of links between Organizational Process and Operation (see MetaModel
diagram below).
31. Change the order of the operations of an organizational process by right-clicking the Operations
folder in the MEGA Explorer, and then selecting Reorganize.
The order of operations you assign here can be used when listing the objects in a report (MS Word) or
Web Site.
32. Identify Messages sent and received by the “Examine credit issue” operation.
33. Find operations preceding and following the “Complete Customer Order Information” operation.
34. Find the business process to which the “Verify Stock” operation belongs.
A selection of Business Processes, Organizational processes and Operations that have the word
“optimize” in the comments.
1. Click the Open Query Tool icon in the Main tool bar.
Query
Tool
36. Display the query code by clicking on the Display icon and
selecting Query Code (as shown below).
Organizational processes that are class “Normal” and that are carried out “On Request”.
Org-units that are linked to the “Take Product Order” organizational process.
Structure type org-units that are linked to the Business Process “Provide small appliance”.
Organizational processes that do not have a comment and that are linked to a risk.
38. Open the properties of this query and enter a comment explaining its purpose.
By using the Cumulative mode it is possible to combine the results of separate queries. For example, if
you’d like to list all the org-units that are both function and structure type follow the steps below.
1. In the query assistant, click the Mode Selection icon and select Cumulative.
Mode
Selection 40. Click the push pin in the query window to keep this window open.
42. Run a second query for org-units that are type structure.
Note that the query results display both function and structure type org-units.
1. In the Query Results window, click the Query Display icon and select
Query Customize columns.
Display
43. In the Column Display Customization window, add field for Creation Date.
Click OK to validate.
44. In the Query Results window, click the Generate report for selected objects
icon.
Generate
report 45. View the report.
Lab Exercise 7.
Writing Queries
When producing documentation, queries prove to be useful because they allow you to accurately specify
the data you want to display on the pages.
1. Open the Query tool and click the Registered Queries tab. This mode allows you to type queries
directing in edit area.
PUB B1: List of org-units that do not execute any operation (two query methods).
PUB B2: List of org-units that execute a single operation (two query methods).
PUB C: List of all org-units that are components of the “CEO” org-unit.
For example, if we wanted to list all of the operations of a given Business Process, we would start from
the target “Operation”. However, operations are not linked directly to Business Processes; to find the
operations linked to a process, we must pass through an organizational process.
Use the method explained above to write the code for the following queries:
PUB E1: List of org-units of the flowchart of a given organizational process (“Take Product
Order”).
PUB E2: List of function type org-units of a flowchart (using a variable for the diagram name)
PUB E3: List of non-function type org-units of a flowchart (using a variable for the diagram
name)
PUB F: List of operations triggered by a message in the diagrams of the organizational processes
that describe the “Provide Small Appliances” business process.
Lab Exercise 8.
RTF Descriptors
RTF descriptors allow you to retrieve the repository data that you want to display in your reports (MS
Word) generated from MEGA. Descriptors can be added to reusable report templates (MS Word).
1. Open MEGA.
47. Open a transaction with Nathalie– (Publisher) in the 03-MEGA 2009 Training Exercise Solutions.
49. In the Options tree on the left, select Repository and in the right select the MetaModel Access level
Advanced.
1. In the Utilities Navigation Window, expand the navigation tree to the folder: Descriptors / Rtf
Format / Customized.
51. Right-click the folder Customized and select New > Descriptor.
55. Right-click the Organizational Process folder and select New > Text.
56. In the Data Tree area, expand the Object characteristics folder.
57. From the Object Characteristics folder, drag and drop Object picture, Short
Name and Comment into the text edit area (as shown below).
Save Changes
58. Click the Save Changes icon to save the changes to your descriptor.
Example Results:
Follow the instructions below to add a diagram group to the “PUB1 - Organizational Process Descriptor”
that will display the organizational process flowchart:
1. In the “PUB1 - Organizational Process Descriptor”, right-click the Organizational Process folder and
select New > Group.
64. In the Descriptor Texts Tree, right-click the Description group and select Insert > Diagram.
65. Run the descriptor for the “Take Product Order” organizational process.
Operations
Name of operation
particular organizational process and indicate whether the org-units are Functions, Managers or
Structures.
66. Right-click the Description folder and select New > Group.
70. In the Query or MetaAssociationEnd, locate the query created earlier in the training to select
Function type org-units on a given diagram (PUB E2).
If you have not already created the required query, you can use
the “Embedded query” option to type the code in the edit area.
1. In the “PUB1 - Organizational Process Descriptor”, right-click the Organizational Process folder and
select New > Group.
71. In the dialog box that opens, enter the name “Messages sent”.
73. Select the option Embedded query and type the query:
Select [Message]Where [Source Organizational Process] &”OrgPro”
74. Create the text groups that will display the section title and the short name of the message.
75. Follow the steps above to create a group that will display the Messages received by the
Organizational Process.
1. Exit MEGA, indicating that you will dispatch your transaction later.
3. Right-click the tree root, ie. MEGA, and select Options > Modify.
5. In the right of the window, in the Definition of path of MetaAssociation field, select “Compatibility
up to MEGA 2009”.
7. Restart MEGA and resume your transaction with Nathalie on repository 03-MEGA 2009 Traning
Exercise Solutions.
1. From the Utilities navigation window, expand the Report template (MS Word) folder.
76. Right-click the “Business Process documentation” template and select Duplicate.
77. For the duplication strategy leave the default setting “Duplicate descriptors and queries”.
78. Select the With Prefix option and type “PUB” in the adjacent field.
1. Open the “Duplication of Business Process documentation” report template (MS Word).
1. In the report template (MS Word) properties dialog box, open the Documented object tab.
82. Refresh the report template (MS Word) by clicking the Refresh button and selecting the Report
template (MS Word) option (as shown below).
83. Note in the navigation window that links with descriptors have been updated.
1. In the Utilities Navigation Window, right-click the Report template (MS Word) folder and select
New > Report Template (MS Word).
1. Open the “New BP Report Template (MS Word)” which you created in the
previous section.
Insert
85. Click the Insert Report Template Element icon in the MEGA report template
Report
Template (MS Word).
Element
(MS 86. Select Business Process for the Object (described).
Word)
87. In the Query field, select Name.
90. In the Value field, enter “BP_name”. (This same value must be used when inserting
all other report template elements in this report template).
91. Click OK to insert the report template element in the Report Template (MS Word).
Follow the steps described above to insert the following report template elements in the “New BP Report
Template (MS Word)”:
Create a new report (MS Word) using the “New BP Report Template (MS Word)” and view the results.
1. Open the “New BP Report Template (MS Word)” and type «Organizational Processes “.
92. Use the style Heading 1 to indicate that “ Organizational Processes “ is a new section.
93. Click the Insert Report Template (MS Word) Element icon.
94. Insert the document template (MS Word) element comprising the “PUB1 - Organizational Process
Descriptor” descriptor into the chapter you have just created.
However, pay attention to the fact that the template element Object must be Organizational Process
(not Business process) and that the Query field must contain Business Process (see figure below).
97. Refresh the report template (MS Word) so that your modifications will be taken into account.
98. Create a new report (MS Word) on the “Provide Small Appliances” business process using your
report template (MS Word).
Create and generate an Intranet Web Site from the MEGA repository
Add indexes
1. From the Documentation Navigation Window, right-click the Web Sites folder and select New >
Web Site.
99. Provide a name for your Web Site and leave the (Default) option selected for the Web Site template.
Use of the “Default” Web Site template means that we do not wish to use a
Web Site template, but that we wish to create a customized site.
101. Select the Objects tab to add objects that are to be described.
103. In the Add Object dialog box select the Type Business Process.
104. Enter Name field by listing the Business Processes and selecting the
“Provide small Appliance” process. Click OK.
105. Keep the Propagation box ticked and validate by clicking Apply.
1. In the Pages tab of the Web Site properties, add a page for the Business Process object.
106. Select EA_Business Process for the body format and click OK.
107. In the same way, add a page for the Diagram object, with body format as EA_diag.
108. Finally, add pages for Organizational Process, Operation, Message and Org-unit objects, and
leave the default “Body” Format as is.
109. Click OK, to validate your updates and close the Web Site properties.
Right-click your Web Site and select Generate. When generation has been completed, navigate around
the site to see the result obtained.
112. Select the desired object, e.g. operation, and specify an alphabetical index (default).
113. Generate the site and note that you can access the various pages from this generated index.
1. With Windows Explorer, locate the file “index-us.mth” (located by default in the Mega_std folder of
the MEGA site folder).
114. Copy and paste the file “index-us.mth” in the Mega_usr folder of the environment.
115. To remove the image that appears on the home page, open the “index-us.mth” file and delete the
following line located towards the end of the file:
You must copy style sheet NewLook.css (located by default in Mega_std) in the Mega_usr folder, and
then follow the procedure below:
1. Check that the style sheet associated with your Web Site is now newlook.
118. Double-click the style sheet to open. If it is not associated with a program, select Notepad to
open it.
PADDING-RIGHT: 3px;
PADDING-LEFT: 3px;
PADDING-BOTTOM: 3px;
PADDING-TOP: 3px;
123. Open the Web Site and note the result (presentation of object characteristics).
Often companies define their own style sheets for Intranet sites. It is possible to apply these style sheets to
Web Sites generated with MEGA. To do this, follow the procedure below:
124. Place the mycompany_intranet.css file in the Mega_usr folder of the environment.
125. Modify the style sheet associated with your Web Site (now mycompany_intranet.css).
127. Open the Web Site and note the result (presentation of object characteristics).
Description of applications
Based on a report template of “Property” type, we will create a report which displays the properties of
selected applications:
- Comment
- Creation date
- Application type
This report template of “Checkmark” type will enable indication in the form of a matrix of which
functionalities are connected to which applications.
Lab Exercise 23. Defining the Object Type and its Properties
When the report template type has been created, you must define the object type to which the report
relates (here Application) and the properties of the object you want to display (Comment, Creation Date
and application Type):
1. In the creation wizard, under Properties analysis: object type, click the Add a type for the row
objects button.
129. In the dialog box that appears, select the Application object type and click OK.
130. In the same way, under Properties analysis: properties, select types: Application
Type, Comment and Creation Date (you can make a multiple selection by holding the Ctrl key
down).
131. In the report template creation dialog box, click Next then Finish.
132. The report creation dialog box opens; name the report “My Applications” and click Next.
133. In the Parameters dialog box, select the applications you want to appear in the report
(Ctrl+A to select them all).
135. Click the icon located on the right side of the first chapter.
You obtain the list of applications with their creation date, comment and type. The “Edit”
command appears in the empty cells. By clicking this command you can complete the missing
description.
142. Click Cancel (the report will relate to direct links between applications and
functionalities).
144. The report creation dialog box opens; name the report “My applications and
Functionalities” and click Next.
You arrive in the report parameters definition dialog box.
145. For the Application parameter, select all the applications of the repository.
147. Click the title 2. Application x Functionality to refresh this part of the report.
The list of selected applications and functionalities appears.
By clicking the + button associated with the checkmark, you obtain detail of objects and their
interconnecting link.
Applications that do not have a link with the selected functionalities are listed under the table.
148. To see all org-units linked to each of the organizational processes, expand the Org-unit folder
under each organizational process:
150. The “Examine credit issue” operation receives one message (“Order blocked”) and sends two
messages (“Credit approved” and “Credit refused”).
151. The operation directly following the “Complete Customer Order Information” operation can be
found by opening the green Next folder. (Next in this case refers to the next operation).
Seeing the preceding operation is less direct. The “Complete Customer Order Information” operation
is directly preceded by a condition. To see which operation comes before, we must expand the
Previous-Condition and the Previous-operation folders.
152. To find which business process the “Verify Stock” operation belongs to, can be done by
exploring the operation and following the links Organizational Process and Business Process.
A selection of Business Processes, Organizational Processes and Operations that have the word
“optimize” in the comments.
To find the results of this query, you must select the query targets as shown below:
Organizational processes that are class “Normal” and that are carried out “On Request”.
Org-units that are linked to the “Take Product Order” organizational process.
Structure type org-units that are linked to the Business Process “Provide small appliance”.
Organizational processes that do not have a comment and that are linked to a risk.
And [Risk]
All the organizational processes of the Business Process “Provide small appliance”.
PUB B1: List of org-units that do not execute any operation (two query methods).
OR
PUB B2: List of org-units that execute a single operation (two query methods).
OR
PUB C: List of all org-units that are components of the “CEO” org-unit.
PUB E1: List of org-units of the flowchart of a given organizational process (“Take Product Order”).
PUB E2: List of function type org-units of a flowchart (using a variable for the diagram name)
PUB E3: List of non-function type org-units of a flowchart (using a variable for the diagram name)
PUB F: List of operations triggered by a message in the diagrams of the organizational processes that
describe the “Provide Small Appliances” business process.
Appendix
**********************************************
When an order is received, the Sales Assistant creates the order in the
application used for managing sales. The assistant then runs a credit
check. If the credit is accepted the assistant completes the customer order
information and verifies stock levels. If stock is available, the assistant
systematically confirms the order by fax to the customer at the end of the
day. In addition, the delivery is planned and the order details are sent to
the logistics department.
S a le s As s is ta n t S a le s Ma n a g e r
R o le
Ord e r Cre a te o rd e r
- C us tome r
D is p la y o rd e r s c re e n
R u n c re d it c h e c k
Ve rify c re d it ra tin g
Cre d it
a c c e p te d
? No
Ord e r bloc k e d
Yes
Co mp le te c u s to me r E x a min e c re d it
o rd e r in fo rma tio n is s u e
Cre d it ap prov e d
D is p la y o rd e r s c re e n
Ve rify s to c k
Produc tion
s c h e d ule Ma n a g e s to c k
R o le
No
- M a nufa c ture
goods S to c k
a v a ila b le
?
Cre a te p ro d u c tio n
o rd e r Y es
An d
Ma n a g e P O P la n d e liv e ry
Prod uc tio n ord e r
Ma n a g e d e liv e rie s
R o le
- De liv e r
finis hed goods Ord e r de tails
Co n firm o rd e r
P rinte r
a t e nd of
da y
Cre d it re fus e d
D is p la y o rd e r s c re e n
Ord e r c o nfirmation Fa x
R e fu s e o rd e r
Ord e r re fus e d
2 Operations
Complete customer order information
Comment:
Confirm order
Operation Code: CC
Create order
Operation Code: CO
Comment: The sales assistant creates the order in the system. This triggers
the verification of credit available.
Comment:
Comment: The Manager should try to resolve credit issues with client.
Plan delivery
Operation Code: PD
Refuse order
Operation Code: RO
Comment:
Verify stock
Operation Code: VS
Comment:
5 Messages Sent
Credit refused
Order confirmation
Order details
Order refused
Production order
6 Messages Received
Order
Production schedule