Release Notes Contact

Release Notes Contact:

Method Park Wetterkreuz 19a 91058 Erlangen Germany

Phone +49-9131-97206-550

Fax +49-9131-97206-200

E-mail [email protected]

Internet www.methodpark.de

Version: 7.1

Date: 1.12.2017 Contents

1 Terminology...... 5 2 Literature...... 6 3 General...... 8 4 New features for 7.1...... 9 4.1 File Management...... 9 4.2 PDF Export Creation...... 10 4.3 Custom Process Attributes...... 11 4.4 Users and Roles...... 11 4.5 Configuration...... 12 5 New features for 7.0...... 14 5.1 User Experience...... 14 5.2 Navigation & Search...... 14 5.3 Process Experience...... 16 5.4 Process Definition...... 16 5.5 Process Versions...... 17 5.6 Process Modules...... 18 5.7 Administration...... 19 6 New features for 6.6...... 20 6.1 Stages RTC Integration...... 20 7 New features for 6.5...... 21 7.1 Issue Tracking Enhancements...... 21 7.1.1 Create Issues From Process Elements...... 21 7.1.2 View Related Issues of a Process Element...... 22 7.1.3 List Issues Across Workspaces...... 23 7.1.4 Parent-Child-Relation of Issues...... 24 7.1.5 Set Attributes of Related Issues...... 26 7.1.6 Change State of Process Element From Issue...... 27 7.2 Multiple CMS Profiles for Resources...... 28 7.3 Maximum File Upload Size...... 28 7.4 Java 8 Support...... 28 7.5 Subversion CMS Interface...... 29 7.5.1 Web-service-based Interface...... 29 7.5.2 Subversion Server 1.9 Support...... 29 7.5.3 Read-only Stages System Account...... 29 7.6 Changes from 6.4 to 6.5...... 29 8 New features for 6.4...... 32 8.1 Resource Synchronization...... 32 8.2 New SVN CMS interface...... 33 8.3 Create File from Template...... 33 8.4 Tailoring Enhancements...... 35 8.5 State Filtering for Documents Overview...... 37 8.6 Changes from 6.3 to 6.4...... 37 9 New Features for 6.3...... 41 9.1 PDF Document Generation...... 41 9.2 Stages Unified Configuration...... 42 9.3 Composer Excel import...... 44 9.4 Resource Overview...... 45 9.5 Changes from 6.2 to 6.3...... 46 10 New Features for 6.2...... 49 10.1 Visualization Improvements...... 49 10.2 Serena Dimensions Interface...... 50 10.3 SVN Server to Server Interface...... 50 10.4 Editor Table Plugin...... 51 10.5 Editor HTML Description Plugin...... 52 10.6 Auto-Mapping via Fuzzy-Match...... 53 10.7 Metamodel exchange in Composer...... 54 10.8 RTC Enactment Improvements...... 54 10.9 Changes from 6.1 to 6.2...... 55 11 New Features for 6.1...... 57 11.1 Microsoft SharePoint...... 57 11.2 Element State management...... 57 11.3 RTC...... 58 11.4 Stages Composer...... 59 11.5 PTC Integrity...... 59 11.6 Editor 2.0...... 60 11.7 Process View Menu...... 61 11.8 Visualization...... 62 11.9 Performance...... 63 11.10 Usability...... 64 11.11 Metrics...... 65 11.12 ARIS...... 65 11.13 Administration...... 66 11.14 Changes from 6.0 to 6.1...... 67 12 Mandatory manual actions...... 69 12.1 Mandatory manual actions Upgrading from 6.5 or 6.6...... 69 12.2 Mandatory manual actions Upgrading from 6.4...... 71 12.3 Mandatory manual actions Upgrading from 6.3...... 72 12.4 Mandatory manual actions Upgrading from 6.2...... 73 12.5 Mandatory manual actions Upgrading from 6.1...... 74 12.6 Mandatory manual actions Upgrading from 6.0...... 75 12.7 Mandatory manual actions Upgrading from 5.1...... 77 13 Installation...... 81 13.1 Fresh Installation...... 81 13.2 Upgrade Installation...... 82 14 Known Limitations...... 83 1 Terminology Release Notes 7.1

1 Terminology

Instructions, warnings and other important notes are marked in this document with the following symbols:

Notice: Shows an additional information

Warning: Indicates that a problem can happen

Important: Indicates an important aspect.

Danger: Indicates that in special cases data loss may happen.

Instructions

Used to show steps to perform

Example

Shows an example

Related Links Terminology on page 5

2 Literature

The following documents provide you with information about working with Stages:

User Documentation

Name Description Editor Guide The Editor Guide describes the handling of the Stages Web Editor. Stages User Guide The User Guide describes typical work processes which quality managers, project managers and developers carry out on a day-to-day basis using Stages. Metric Guide The Metric Guide describes how Stages metric reports can be created. Script Reference Guide The Script Reference Guide describes how the Stages scripting API is working. Process Versioning Guide The Process Versioning Guide describes how processes can be versioned (baselined).

Configuration/Administration

Name Description Upgrade Guide The Upgrade Guide describes the required steps for upgrading to a newer version of Stages. System Requirements Describes the system requirements of the Stages system. Metamodeling Guide The Metamodeling Guide will provide you with assistance in defining an appropriate metamodel. Administration Guide The Administration Guide gives you guidance in the administration of Stages. Starting with the installation and customization to your company’s requirements, chapter two helps you to prepare Stages for the usage. Issue Tracking Guide The Issue Tracking Guide provides information about the definition of your specific issue tracking configuration. PDF Printing Guide The PDF Printing Guide describes how PDF documents can be created from different process elements. People Application Guide The People Application Guide provides information about activating your People Application and how to handle it. Permissions Guide The Permissions Guide describes in detail all the different permission settings. Release Notes The Release Notes describes the major enhancements and changes of the Stages version.

Name Description Last Changes The Last Changes document is a change log with detailed information about all changes made in this version.

System Integration

Name Description Autologin Guide The Autologin Guide describes the single-sign-on feature of Stages. ARIS Integration Guide The ARIS Integration Guide describes how ARIS process models can be imported into Stages. CMS Prefetch Guide The CMS Prefetch Guide describes the caching configuration of the CMS status informations. ClearCase Integration Guide The ClearCase Integration Guide describes the integration with IBM Rational ClearCase. PTC Integrity Integration Guide The PTC Integrity Integration Guide describes the integration with PTC Integrity. Subversion Integration Guide The Subversion Integration Guide describes the integration with Subversion. Sharepoint Integration Guide The Sharepoint Integration Guide describes the integration with Microsoft Sharepoint. Serena Dimensions Integration Guide The Serena Dimensions Integration Guide describes the integration with Serena Dimensions. LDAP Integration Guide The LDAP Integration Guide describes how LDAP informations can be imported into Stages.

Application Lifecycle Management Tools

Name Description JIRA Configuration Guide This Guide describes how to configure the ALM Tool JIRA to work with imported Stages Processes. RTC Configuration Guide This Guide describes how to configure the ALM Tool RTC to work with imported Stages Processes.

These documents are delivered with Stages. They can be accessed via the Stages Info page.

3 General

Stages is the leading system for managing engineering and product development processes. It allows you to define, share, and use processes and has a strong focus on the end users. In addition, Stages allows you to assure that processes comply with standards or regulations, even when they are tailored to project or program specific needs.

Figure 1: Overview

Important: Please check the mandatory manual actions before and after upgrading to this Stages version. Mandatory manual actions Upgrading from 6.5 or 6.6 on page 69

Version terminology

Important: This Release Note is for Version 7.1 (EA)

Version Description Early Access (EA) This version is mainly provided for testing and evaluation purposes. The documentation could be incomplete. Can be used in a production environment after testing by the customer. General Availability (GA) Production Version

4 New features for 7.1

4.1 File Management Files, external guidance (e.g. templates, checklists, examples), and work product instances can be directly managed with Stages: • Physical objects can be stored in internal or external storage repositories. • Storage repositories can be located in Subversion, CVS, MS Sharepoint, IBM ClearCase, Serena Dimensions, or a Stages-internal version management system. For exact versions of the supported systems, please see the System Requirements document. • Download, update, lock/unlock, version history, etc., of files works through the Stages GUI. • New files and new file versions can be created comfortably through drag & drop.

Figure 2: Manage files, templates, and other work product instances

The mapping between files and the storage repositories can be managed in a hierarchical storage management plan.

Figure 3: Manage the storage plan

4.2 PDF Export Creation Process content from Stages can be exported to PDF: • Different export details (e.g. process handbook, process changes, single process content pages) can be defined in fully scriptable PDF templates. • PDF exports can contain change markers to previous process versions, table of content, title pages, headers, footers, etc. • Standard set of templates is provided, customized templates can be created upon request.

Figure 4: Select between different PDF templates

The PDF documents are created on the server and automatically downloaded to the browser.

Figure 5: Sample PDF document

4.3 Custom Process Attributes Custom attributes can be configured for processes and process elements: • Attributes can be configured in various formats (e.g. string, number, date, text) for storing process or project level data. • Attributes can be efficiently changed via inline editing. • Process visualizations can display attribute values, e.g. for start & end events or BPMN task types.

Figure 6: Show and modify element attributes

NOTE:The configuration of the attributes was moved from the PKitConfig.xml to the process.xml file so that declaration and use of attributes are contained in the same file.

4.4 Users and Roles Users can now be assigned to roles: • Assigned users can be shown in configurable role view. • User assignment is possible via "find as you type". • Users can be marked as stand-ins for a role. • Assigned users can also be displayed in other process elements, e.g. the responsible role for an activity.

Figure 7: Show and manage users for roles

4.5 Configuration The configuration file structure is now much simpler and the system configuration is more secure. • All configuration files are now centrally stored in the /conf folder. This makes backup and restore of Stages configurations easier. • Each meta-model is stored individually in a /conf/METAMODELIDENT.mm file that contains all resources (e.g. process.xml, message properties, visualization scripts, PDF scripts) packed in ZIP format. • All log files are now centrally stored in the /logs folder. • The Stages service does not need to be run as root anymore on Linux. Important: The pre-7.1 configuration must be manually migrated into the new file structure via the following steps: • backup old configuration files • deinstall old Stages version • install Stages 7.1 • move and adjust configuration files from backup into new structure/naming Important: The format of the process.xml file has changed: • enclosing pkit-process tag has been removed • ident attribute of processtype tag has been removed • the process and element attributes definition has been moved from the PKitConfig.xml file to the process.xmlfile The configuration files have been renamed as shown in the following table:

V6 File Name V7 File Name /tomcat/webapps/pkit/WEB-INF/conf/ /conf/config.xml PKitConfig.xml /tomcat/webapps/pkit/WEB-INF/conf/ /conf/METAMODELIDENT.mm (contains PKitProcess.xml process.xml and all other meta-model dependent files) /tomcat/webapps/pkit/WEB-INF/conf/ /conf/request.xml PKitRequest.xml /tomcat/webapps/pkit/WEB-INF/conf/ /conf/license.xml PKitLicense.xml /tomcat/webapps/pkit/WEB-INF/conf/ /conf/signature.xml PKitSignature.xml

V6 File Name V7 File Name /tomcat/webapps/pkit/WEB-INF/conf/ /conf/metrics.xml PkitMetrics.xml /tomcat/webapps/pkit/WEB-INF/conf/ /conf/database.properties Database.properties /tomcat/webapps/pkit/WEB-INF/classes/ /conf/local.properties (for non-meta-model LocalPKit.properties dependent message properties) /tomcat/conf/server.xml /conf/server.xml /tomcat/webapps/pkit/local /local /etc/rc.conf (only Linux) /bin/rc.conf /pkit.log /logs/stages.log

5 New features for 7.0

5.1 User Experience

Figure 8: New User Experience

Stages 7.0 comes with a completely new user experience and user interface. • Stages can be used from desktop, tablet, or smartphone with any browser. • The user interface is fully responsive, so it will adjust to browser zoom, screen size, and orientation. • Browser back and forward buttons, using multiple browser tabs, and bookmarking pages is now fully supported. • Users can upload images to personalize their user account.

5.2 Navigation & Search All navigation is now found on the left side. The navigation is always shown if the screen resolution is wide enough. If the screen resolution does not leave enough space for the main content, the navigation panel automatically minimizes and can be activated again by using the "burger" menu.

Figure 9: New Navigation

The current workspace is shown on the top of the navigation panel. To change the workspace, click on the name and select a new one by • selecting a workspace from the favories • clickin on "All" and start typing the name Workspaces can be added to the favorites by clicking on the "star" icon.

Figure 10: New Search

The search can be used by clicking and typing into the box on the top of the screen in wide resolution or the search icon in low resolution. It supports "search as you type" and filtering the search results by workspace, element type, and process version. The "Recommended workspaces" filter setting searches in the current workspace and all others that are connected to it via process interfaces.

5.3 Process Experience Navigating process content can now be done completely through the navigation on the left side or as usual by navigating over the associated elements, e.g. from an activity to a role. The process users can now determine the diagram type (e.g. flow, grid, or table) and diagram details by clicking on the respective tabs and viewing options.

Figure 11: Selecting diagram type and details

If the users are allowed to see multiple process versions, they can switch between versions on every page, not just the start page.

Figure 12: Switching Versions

5.4 Process Definition Creating new content is now much faster and easier: • In the navigation. Multiple elements can be created by using the Enter/Return key. • Via the "Plus" button. Multiple elements can be created at the same time in the addition dialog by clicking on "Add one more" or using the Tab key. • New content is now limited to the supported element types in the current context. For example, an activity or decision can only be created below a workflow element, or no element can be created below an activity or decision. Editing descriptions can be done without leaving the page by clicking on the "Pen" icon.

Figure 13: Create new content

Associations between elements can now be created without leaving the page with the "Add" action at every association display. The element to be associated can be determined by typing the element name. If the element does not exist yet, it can be created with the "Create ..." selection. If the name of the element is not known, the elements can be browsed via the "Browse" button in the addition dialog.

Figure 14: Create new content

Copying content now works by first selecting the content to be copied and then selecting the target element, not vice versa. It is now possible to move content across workspaces. This makes restructuring and refactoring of processes much easier. Associations are kept and automatically converted into process interfaces. Sorting content can be done directly in the navigation. All operations now allow selection and modification or deletion of multiple elements at the same time.

5.5 Process Versions Process version management has been streamlined and simplified.

Figure 15: Process Version Management

The constraint checks are now executed each time a new version is being created to improve process quality and consistency. Multiple actions can now be executed in one step, e.g. creating a new version and make it valid. The "Working Revision" from previous releases has been renamed to "Working Version" for consistency. Import and export of ZIP files is now done in the "Process Versions" menu.

5.6 Process Modules Process modules replace the existing core process management concept.

Figure 16: Process Modules

All former core process actions (import, analyze, update, delete) can now be executed from the "Process Modules" menu. It is also possible to browse the list of processes where the current module is used in. It is now possible to update all integrated modules with one user action. The various import and update options have been greatly reduced.

5.7 Administration The administration of Stages was simplified. In detail, the following changes have been made: • All administrative actions can be accessed through the "Administration" navigation item. It is only visible with the respective privileges. • Workspaces can be directly opened by using the respective "Open" action. • Users are managed in a global list, not in multiple workspaces. • User groups replace roles as the concept to assign permissions to users. Permissions are managed directly for each user group, the users are added to the group as members. • Roles with permissions from previous Stages versions are automatically migrated into user groups. • Permission changes are immediatly activated. • User authentication is now performed by the application server. This makes it easier to adapt Stages to customer-specific authentication schemes. • If a user session times out, the user context is saved, so the user is directed to the desired page instead of the login page after re-login.

6 New features for 6.6

6.1 Stages RTC Integration Enactment Modeling

A new way of Process Enactment Modeling has been introduced. It emphasizes the usage of input and output relations for enactment automation actions. Besides post-save mode additionally a pre-save mode is available to check work-items process adherence. The user can select between one of two RTC Export modes. By default the new Enactment Modeling is activated which makes use of the input and output relationship of activities to be enacted. As legacy export the sequence-based enactment modeling is supported as well.

Figure 17: Process Enactment Export

7 New features for 6.5

7.1 Issue Tracking Enhancements

7.1.1 Create Issues From Process Elements When creating an Issue from a process element, now a link to the process element can automatically be stored in the new Issue. To create an Issue from a process element use the Actions menu:

Figure 18: Actions menu at process element

When the Issue form opens, the corresponding process element is already linked:

Figure 19: Linked process element in Issue form

Note: This feature has to be configured in PkitRequest.xml. For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)).

Example Configuration

...

7.1.2 View Related Issues of a Process Element When creating Issues from a process element, a list of these Issues can be displayed in the process element's view:

Figure 20: Display related Issues in process element view

Note: This feature has to be configured in PkitConfig.xml and PkitProcess.xml. For details please refer to Metamodeling Guide V6.5 (available with Stages V6.5 (GA)).

7.1.3 List Issues Across Workspaces Up to now Stages could only list issues of the current workspace. With V6.5 the Issue filter can be configured to list Issues of all workspaces having the same Issue Tracking configuration.

To activate this feature, the user has to set the "Consider all worksapces" option to "Yes" in the Issue filter configuration:

Figure 21: Issue Filter

Note: This feature has to be activated per Issue Tracking configuration in Pkit.Request.xml:

For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)).

7.1.4 Parent-Child-Relation of Issues Stages 6.5 offers the possibility to set up a parent-child-relation between two Issues.

Note: It is not possible to use multi-level hierarchical structure for Issue Tracking!

In order to assign an Issue to a parent Issue, you can either fill in the parent field in the child Issue form with the ID number of the parent Issue, or create a new child Issue by clicking the "+Add" link in the parent Issue form.

Figure 22: View parent

Figure 23: Create child

Note: This feature has to be configured in the PkitRequest.xml. For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)).

Example Configuration

7.1.5 Set Attributes of Related Issues With Stages 6.5, arbitrary attributes of related Issues can be set via an Issue tracker Event. For this a new Issue Action "setRequestAttributes" has been implemented.

Note: This feature has to be configured in PkitRequest.xml:

For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)).

Example Configuration

... ... ... function isInNewState(state) { return (requestElement.getAttribute("states").getProperty("databaseValue") == state); } function getChildRequests() { var ids = new Array(); var seeRequestsValue = requestElement.getAttribute('related- requests').getProperty('databaseValue'); for each (var requestId in seeRequestsValue) { ids.push(requestId); } return ids; } function getValues() { var valuesByIdent = new java.util.HashMap(); valuesByIdent.put("states", "released"); return valuesByIdent; } ...

7.1.6 Change State of Process Element From Issue The state of the process element, from which the Issue has been created, can now be set via an Issue tracker Event. For this, a new Issue Action "setElementState" has been implemented.

Note: This feature has to be configured in PkitRequest.xml. For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)).

Example Configuration

function isInNewState(state) {

return (requestElement.getAttribute("states").getProperty("databaseValue") == state); } ...

7.2 Multiple CMS Profiles for Resources With Stages 6.5 you have now the possibility to set up multiple CMS profiles for resources, previously only one CMS profile could be used for resources.

Figure 24: Select CMS profile when creating/editing a resource

7.3 Maximum File Upload Size The maximum upload size for files in Stages defaults to 100,000,000 Byte. Stages 6.5 offers the possibility to raise the maximum size up to 2,147,483,000 Byte. Note: The maximum file upload size can be set in PkitConfig.xml; the value has to be specified in kByte (1000 Byte).

...

7.4 Java 8 Support In order to launch Stages 6.5 on your server, Java 8 is needed.

Important: Stages 6.5 will not work with older versions of Java.

You can find the Oracle Java Standard Edition 8 Development Kit under the following link: http://www.oracle.com/technetwork/java/javase/downloads/index.html

Important: Before updating Stages you have to update the Java runtime, see mandatory manual actions

7.5 Subversion CMS Interface

7.5.1 Web-service-based Interface Up to Stages 6.4 two different mechanisms for the Subversion CMS interface could be configured. When using the sandbox-based mechanism, in rare cases errors could occur, when two users were working in sandboxes simultaneously.

Important: The sandbox-based mechanism is therefore no longer available in Stages 6.5.

Instead, Stages has to be configured to use the web-service-based interface to Subversion now, which has been introduced with Stages 6.2. Danger: CMS profiles using the old mechanism will no longer be available to the Stages user, until you migrate all your sandboxes from the old to the new interface. To do so, follow the mandatory manual actions. After this migration all CMS profiles will use the new interface automatically.

7.5.2 Subversion Server 1.9 Support Stages 6.5 now supports Subversion server version 1.9.

7.5.3 Read-only Stages System Account For the CMS Prefetch feature or the root user, Stages uses the Stages system account to access the CMS. During Stages start-up or after editing CMS profiles, Stages validates the CMS interface using several write operations on the CMS. If the Stages system account shall be configured in Subversion to only have read access, these write operations have to be disabled, otherwise Stages start-up or editing CMS profiles will not work. Note: To disable these write operations for the Stages system account, the following property must be set in PkitConfig.xml:

Warning: Disabling the validation of CMS profile configurations requires that you test the correct function of a CMS profile manually.

Warning: Write operations on the CMS by the root user are not disabled and will lead to a Subversion error.

7.6 Changes from 6.4 to 6.5 Following new features have been introduced for Release 6.5 since Release 6.4: • Metrics

Component Enhancement ID Description Metrics 30097 Enable resolving users by their username in metric scripts through pkit.getUserByUsername() call

Component Enhancement ID Description Metrics 26051 28894 28376 Integration of new BIRT version 4.4 for process reporting.Mandatory manual actions Upgrading from 6.4 on page 71

• Facade

Component Enhancement ID Description Facade 30386 Added Property "CreationDate" to ProcessClass. Facade 27329 Added compliance model to facade. Facade 30244 Added methods (newRequestFilter() and getRequests(projectId, filter)) to pkit facade in order to get filtered requests

• Global

Component Enhancement ID Description Global 30035 Support Java 8Mandatory manual actions Upgrading from 6.4 on page 71 Global 30206 Guided Tour provides external direct links. Global 30039 Upgrade Tomcat to version 8.0.30.Mandatory manual actions Upgrading from 6.4 on page 71 Global 30209 Adjust maximal file upload size to 2 GB (maximal supported filesize)

• CMS Enhancements

Component Enhancement ID Description CMS Subversion 30047 Remove old sandbox based subversion interfaceMandatory manual actions Upgrading from 6.4 on page 71 CMS 30207 File path proposal can be disabled via config property 'process.file.cmsFilePath.proposal.enabled'. CMS Subversion 30036 Support subversion servers 1.9 and read-only system accounts.

• Visualization

Component Enhancement ID Description PWB Visualization 30090 Enhance performance logging of diagram rendering

• Administration

Component Enhancement ID Description Administration 28642 Support information contains tomcat.log and rc.conf (linux only).

• Resources

Component Enhancement ID Description PWB Resources 15835 Resources provides multiple cms profiles.

• Issue Application

Component Enhancement ID Description Request Tracking 30138 Added parent and children attribute. Request Tracking 30137 Attributes of dependent requests can be set when an issue is saved. Request Tracking 29956 29957 30030 Issue filter can now be project independent (). Process element state can now be set via an issue tracker event (). Change management traces are now displayed as real links when using the CHANGE_REQUEST attribute type. Core process identity is now available via Facade v1 (coreProcessIdentity).

8 New features for 6.4

Stages 6.4 boosts productivity in every-day project use by introducing new capabilities for tailoring configurations and making it easier than ever using existing templates in your projects. A more detailed level of information on tailored elements adds to transparency on why an element has been tailored by whom. Stages can now migrate and synchronize existing process documents in external CM systems automatically. This decreases ramp up time and effort when switching from existing document based process documentation.

8.1 Resource Synchronization Stages 6.4 makes it easier than ever to integrate existing process resources, such as templates, into the Stages process. Process Modelers can now set up synchronization to existing Configuration Management Systems containing resources in order to have them synched automatically into the process. Resource Synchronization is available for Clearcase, Subversion, Sharepoint and Integrity.

Figure 25: Synchronization for existing CMS

To enable resource synchronization, the Stages configuration needs to be adapted and one of the CM Systems listed above needs to be added to the Stages configuration. Afterwards, the users have to enable the resource synchronization in the Workspace’s CMS Profile.

Figure 26: CMS Profile

The user can then enter the source and target paths to choose which documents will be synchronized to which destination.

Figure 27: Configuration for resource synchronization

Note: When upgrading to Release 6.4, please refer to the manual action needed - Mandatory manual actions Upgrading from 6.3 on page 72

8.2 New SVN CMS interface In stages 6.4 two different versions of SVN could be configured. Since errors occurred while two users are working in sandboxes at once, SVN hast to be configured via webservice now. To migrate all your sandboxes from the old to the new interface follow the mandatory manual actions:Mandatory manual actions Upgrading from 6.4 on page 71

8.3 Create File from Template With Stages 6.4, Work Product instances can now be created directly from existing resources without having to download them to the client computer. Stages will then offer (matching) templates to the user and upload them automatically into the CM System.

When creating a new file, either from the button at the top of the screen or from the context menu of an existing predefined file, the user can now select to create the file using a template:

Figure 28: Creation of a new file

Figure 29: Template Selection

If the user creates a new file using a predefined work product instance, Stages will only offer resources that match the file type of the instance used:

Figure 30: Template selection filtered

Important: Stages will not convert Microsoft Office template formats (e.g. .docm) to their respective document formats (e.g. .docx). The filetype of the document stays the same upon checking it into the CM System.

8.4 Tailoring Enhancements Tailoring Mode

The user can now select between one of the two tailoring modes when configuring a new tailoring questionnaire. By default, Stages will start with the full process. For tailoring configurations where only a small part of the process is needed the modeler can start with an empty process where all elements have been tailored away and then only add new elements, depending on the answers given in the questionnaire.

Figure 31: Selection of tailoring mode

Associating Tailored Elements The dialogue for associating elements to tailoring answers has been redesigned for easier usage. The user can now (de)select elements using checkboxes next to the elements. Also the user can chose not to

show elements that have already been handled by tailoring answers higher up in the tailoring questionnaire hierarchy.

Figure 32: Definition of dependent elements

Display of Tailoring Information at Element Level The tailoring reason for a specific element is now available at the element itself. The user no longer needs to consult the tailoring report to get information on an element. An element can be affected by tailoring by three different mechanisms: • A tailoring answer has been chosen which relates to the element • A parent or a child of the element has been tailored • The element has been tailored manually In addition to the tailoring reason, the user who last tailored the element and the timestamp of the tailoring are displayed at the element. The tailoring reason is displayed at the element itself as shown in the screenshots below:

Figure 33: Tailored by questionnaire

Tailoring Report The tailoring report has been upgraded to reflect the changes made on the element level. It now shows justifications, executing user and the timestamp of the tailoring as well.

Figure 34: Tailoring Report

8.5 State Filtering for Documents Overview The former Lifecycle State filter in the Documents tab of the Overview page was renamed to State and allows now the filtering by work products without instances ("No Files") or instances without uploaded file ("No Version"), regardless of an existing or non-existing Lifecycle configuration.

Figure 35: State filter for Documents Overview

8.6 Changes from 6.3 to 6.4 Following new features have been introduced for Release 6.4 since Release 6.3: • Resource Synchronization - for details see Resource Synchronization on page 32

Component Enhancement ID Description PWB Resources 27894, 28481, Resources can now be synchronized with the CM system. 27910 Browsing interface for Subversion and Sharepoint. Prefetch of CM items. See also manual action Mandatory manual actions Upgrading from 6.3 on page 72 PWB Resources 27903 Automatic synchronization of resources with a folder in the CMS. Depends on a cache for the CMS structure which is independently fetched. File Handling 27899 Rules for synchronization of resources can be managed per CMS profile.

• CM System Browser - for details see New SVN CMS interface on page 33

Component Enhancement ID Description File Handling 27904 Files from CM systems can now be selected with a browser. It is available for documents and resources.

• Create File from Template - for details see Create File from Template on page 33

Component Enhancement ID Description File Handling 28489 New files can now be created based on templates.

• Tailoring Enhancements - for details see Tailoring Enhancements on page 35

Component Enhancement ID Description

PWB Tailoring 27989 Log and show date and executing user of tailoring changes. PWB Tailoring 27991 For elements that are tailored implicitly by their parent or child element an appropriate note is displayed. PWB Tailoring 27992 Provide a detailed justification for elements tailored via the tailoring assistant. PWB Tailoring 27999 Allow the tailoring assistant to start with an empty process and add elements as needed instead of removing obsolete ones. PWB Tailoring 28512 Rename user setting "show invisible elements" to "show tailoring details". Show all tailoring details like justifications and date and user of tailoring only if this setting is activated. PWB Tailoring 28511 Disable the deprecated description add on tailoring by default. To reenable the feature set property "process.tailoring.enable.addon.tailoring" to "true". PWB Tailoring 28544 The tailoring justification is now required for single element tailoring. PWB Tailoring 9467, 27998 Prevent accidental modification of the set of assigned dependent elements of a tailoring answer.

• State Filtering for Documents Overview - for details see State Filtering for Documents Overview on page 37

Component Enhancement ID Description Overview 28507 State filter allows filtering for 'no versions' (work product instances without uploaded files) and 'no files' (work products without instances) regardless of the lifecycle configuration.

• Excel Export for Resource Overview

Component Enhancement ID Description PWB Resources 28508 Resource Overview in excel was extended so that it provides direct links back to Stages Web and full CM path for CM managed resources.

• User Feedback via Local email Application

Component Enhancement ID Description User Experience 28509 Improve user feedback functionality by sending the feedback via the local mail application to ensure a valid email address is available for call backs.

• Access CM managed resources through system or individual user credentials

Component Enhancement ID Description PWB Resources 26826 System credentials are now used for accessing CM managed resources. As resources are part of the process, they have to be accessible by all users that have access to the process. Individual user credentials are still used for write operations (i.e. when modeling the process). This is the new default behavior. If it is still required to use user credentials for downloading resources, the properties "cms.authenticate.user" or "cms.authenticate.anon" can be set to true. For older releases including 6.3, the user credentials for the CM system were used for all operations.

• Installer Enhancement

Component Enhancement ID Description Installer 28663 The Linux init script will now take system configurations in /etc/ default or /etc/sysconfig into account and will no longer expect Latin-1 file encodings.

• Further Improvements

Component Enhancement ID Description Compliance 28829 For the unified_configuration, we can define better constraint Workbench checks, which also check the quality of the process: - Understandability: No process or group should have more than 8 activities - Efficiency: No process or group should have more than 4 involved responsible roles - Robustness: No process or group should have more than 5 responsibility handovers The Efficiency and Robustness checks only apply to non-automated processes, i.e. when one of the activities has an execution work item type set in the enactmentWorkItemType custom attribute, the whole process is excluded from the constraint checks. The actual limits and metamodel idents are hardcoded into the consistency checks, because there is currently no way to specify parameters in the config file and the consistency checks should have no dependencies to other config mechanisms (e.g. config properties). To enable, use the "unified_configuration" metamodel from Method Park and add the following lines at the start of the metamodel configuration in PKitProcess.xml:

UE Usability 28666 Improved "edit properties" dialog for file-based and url-based resources. Now the content location (Stages database, external CM system or an url) can be selected and only the relevant properties for the chosen type will be displayed.

9 New Features for 6.3

9.1 PDF Document Generation The new PDF Document feature enables you to generate Process documents from your process models. The main focus of this enhancement is to create Process documents looking like manual written documents. The following capabilities have been added: • Printing whole process model (Process Handbook) • Support for multiple document templates • Document template specific Header- and Footer-Sections • Numbered Chapters and subchapters • Automatic generation of Table-of-contents • Introduction of cover-pages

Figure 36: Example of PDF Process Handbook

Notice: This feature is configured independently from the previous PDF print functionality. Please refer to the "PDF Print Guide" to enable it in your configuration.

9.2 Stages Unified Configuration Stages 6.3 is shipped together with a Configuration called Stages Unified Configuration. This configuration is the essence of best practices collected in over 13 years of process management practice.

It supports five process view types: • Author-view: designed to support process modellers showing sequence- and data-flow including process interfaces • SIPOC-view: top-down layouted process view showing Supplier-Input-Process-Output-Customer • Detailed-view: showing the process in a swimlane layout • Compact-view: designed to get a quick overview of process information • Execute-view: designed to execute processes in project instances

Benefits • Ready to use process metamodell • Theming capabilities to show processes in BPMN format • Maintained by Method Park Product Development • Immediate usage of new features and capabilities

Figure 37: Phase Execute View: direct access to the deliverables of a phase

Figure 38: Process SIPOC View: Modelling processes while considering process dataflow

Figure 39: Illustration of the Unified-Configuration-Metamodel

Notice: The Unified Configuration V1.0 for Stages is contained in the Stages Installer, but will be deployed on initial installation only. To receive the Unified Configuration please contact the Stages Support Hotline.

9.3 Composer Excel import This feature enables you to import process information captured in Microsoft Excel workbooks into a process model in Stages Composer. You may import process elements as well as process element associations into your process model.

Benefits • Rapid transfer of existing process information into Stages • Generic way of process synchronization into Stages • Updatable process import through storing external identifiers

Figure 40: Composer Excel import wizard

9.4 Resource Overview The overview application now allows also anonymous process viewers to access a full list of resources used in the process model.

Figure 41: Resource Overview

9.5 Changes from 6.2 to 6.3 Find below listed all changes for Release 6.3 since Release 6.2.

Component Enhancement ID Description Global 28413 Allow customer so specify login and logout redirects. Jazz / RTC Support 26031 Provide default enactment script resource for export to Rational Team Concert. PWB Editor/TWiki 28234 Log entry when user has been assigned to or unassigned from a role. CMS Subversion 28311 Admin can choose for each subversion repository whether he would like to use indivial user authentication or not. Facade 28316 Provide facade properties to access Enactment parameter. Facade 27886 Provide facade properties to access the TypeName and SubtypeName in sigular and plural. Facade 27086 Return the associations and child elements in the same order as they are shown in the gui. Global 28297 Arbitrary languages for the Stages GUI can now be specified in the "supported.languages" property [default: "en,de"] and providing the respective PKit_*.properties files or PKit_*.utf8 files in case UTF-8 characters are used. A call to updateConfig.bat|sh will convert the utf8 files to properties files in the desired format. Known limitation: The rich text editor is not fully translatable. Global 28058 with the config property "global.secureMode.enabled" a X- FRAME-OPTIONS = SAMEORIGIN header will be added to every response, preventing the application to be embedded into IFrames. PWB Editor/tWiki 27889 Added horizontal rule plugin which provides a command to insert Horizontal Rule (

element) in description. In order to use this feature the value 'HorizontalRule' must be appended to the config property global.editor.extraPlugins. PWB Editor/tWiki 27890 Added remove format which makes it possible to remove all text styling (bold, font color, etc) applied to the selected part of the description. PWB Editor/tWiki 27887 Editor has been upgraded to version 4.4.3 and is now minified for better performance. PWB Import/Export 26747 The values of custom attributes of type "selection" with "alphabetical=true" are now displayed in alphabetical order in Stages Composer, too. PWB PDF 27964 Links to anchors of the same description will now work even if an identical anchor name is used in multiple descriptions of the PDF printout. PWB PDF 27974 List PDF print templates on element index pages. PWB Visualization 28268, 15787 It is now possible to define multi label node shapes within the visualization. Tooltip text can now be defined separately from node or label text. See unified Configuration for an example. Administration 27869 Separate system and customer config for web.xml, log4j.xml and PKitCaching.xml

Component Enhancement ID Description At a Glance 27795 Resource overiew now shows all resources which are asscoiated to an element in the currently viewed process version. The document filter has been replaced by a resource type filter. At a Glance 27588 The anonymous user now can access the resource overview in the Overview application. Composer 27660 Associations are now displayed in the configured order. External 26560 Added the possibility to get informations about the health of Applications Stages via the RESTful interface. Facade 27577 Html descriptions of process elements and processes can be queried via the facade. Facade 27578 Index elements can now be easily queried via the facade, e.g. process.getEntities("containsActivityIndex@SYSTEM")[0]. Global 27756 Tomcat has been upgraded to version 7.0.54. Metrics 12611 Improves performance of the metric collector tab. Collector scripts are now validated only after editing and when the collector is triggered. PWB Basics 27624 Changing a process element state now updates the last modification time and user of the element. PWB Editor 27794 Export editor directive names for Stages Composer. PWB PDF 26847, 27576 Description selectors can be freely defined in the meta-modell and can be edited in the editor. PWB PDF 13803 Added PDF printing to the process start page. The Freemarker/ Facade template functionality introduced by 27579 allows for custom printouts of whole processes. PWB PDF 27579 Freemarker templates can now be used for more flexible PDF printing. The PDF print selection page was changed to a list of direct download links, one for each option. The old functionality is included in this list. For more information please refer to the updated PDF Print Guide. Global 27571 In left navigation panel the service section can now be disabled via configuration property "service.portlet.enabled". Facade 27539 Added property "Variables" to ProjectElement which returns a Map. Added getProjectByPath(String path) to Pkit in order to query projects by path. PWB Import/Export 27495 Resources may be downloaded without authentication by specifying "unauthenticated.resource.download.user" property, the given user will be used for the download Administration 26770 Include license log in Supportinfos. Metrics 27531 Added a new property named "Lob" to collector results which can be used to store serialized data. PWB Basics 27506 The default children subtype set by the parent element is now also proposed as default for the elements children. Jazz / RTC Support 26700 Enactment script errors contain a line number for easier debugging.

Component Enhancement ID Description Jazz / RTC Support 26750 The new enactment script method 'setTargetProjectArea' enables the ability to change Project Areas. Jazz / RTC Support 26738 Comments of enacted successor associations can be exported and used in Rational Team Concert. Jazz / RTC Support 26903 Ability to set default enactment script at resource to Rational Team Concert export. PWB Basics 27443 Process element state assistant can now set the states of an element and its subelements.

10 New Features for 6.2

10.1 Visualization Improvements The visualization Concept TableDiagram is enhanced by the following features: • Graph density can be controlled by properties • Visualization Shapes now support overlay icons, color gradients and shadows. • Shapes can now be defined by a Java2D path. • Overlay Icons can be recolored by one defined color.

Notice: This features are only visible if the visualization scripts are adapted. Please contact your Stages Product Consultant to request an offer for these changes.

Figure 42: Example of color gradients and shadows

Figure 43: Example of path shapes

Figure 44: Example of overlay icons

Notice: The shown examples are part of the demonstration metamodel and will not be visible on your specific Stages installation after upgrade.

10.2 Serena Dimensions Interface

Serena Dimensions CM provides extensive software configuration management and deployment capabilities that help you increase development efficiency (www.serena.com). The Serena Dimensions integration is technically based on direct server to server communication of Stages Server and Serena Dimensions server and supports Version 12.2.

Benefits • Full Access from Stages to your project documents in your Dimensions project and streams • Manage your process documents like templates or checklists in Serena dimensions • Easy to maintain because no sandboxes are checked out on the Stages server • Write operations are conducted with Serena Dimensions user related to current Stages User

10.3 SVN Server to Server Interface

Subversion is a free/open source version control system (VCS). That is, Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your data or examine the history of how your data changed. (http://svnbook.red-bean.com) The Subversion integration is technically based on direct web service interface for communication of Stages Server and Subversion server. It covers SVN versions 1.6, 1.7 and 1.8.

Benefits • Full Access from Stages to your project documents in your Subversion repository • Manage your process documents like templates or checklists in Subversion • Easy to maintain because no sandboxes are checked out on the Stages server • Write operations are conducted with Subversion user related to current Stages User

10.4 Editor Table Plugin The Rich Text Editor has now the possibility to create and maintain tables via a table plug-in. The following operations can be performed: • Creating a Table • Editing Table Rows • Editing Table Columns • Editing Table Cells

Notice: See the Editor Guide for more informations.

10.5 Editor HTML Description Plugin The Rich Text Editor has now the possibility to use HTML description templates. These templates act as a paste template for text snippets. The content of the selected HTML description template is pasted into the element description.

Notice: See the Editor Guide for more informations.

10.6 Auto-Mapping via Fuzzy-Match

This feature allows you to store the results of a process compare in terms of reference compliance mappings. It is designed to enable an easier way to switch to a later version of an reference model. For example: Your modeled processes are compliant and mapped to a reference model version 1. If now a revised version 2 of this reference model is issued, it would be very helpful to transfer your mappings from version 1 to version 2, especially for those requirements which have not been changed.

Steps to achieve this transfer 1. Create an fuzzy match compare between reference model version 2 to version 1 to find equal or similar requirements in the reference models and store those found matching elements as reference mappings 2. Use the transfer compliance mappings function to transfer your existing mapping to version 2 of the reference model

Figure 45: Transfer compliance mappings

10.7 Metamodel exchange in Composer Now it is possible to change the metamodel of a already imported process in the Stages Composer.

Notice: The Stages Composer has to be restarted to take the change into action.

10.8 RTC Enactment Improvements

The integration of Stages with IBM® Rational Team Concert™ has been evolved, to enable a quicker and more comfortable process enactment.

Benefits • Enablement of multi-process workflows and chained process enactment • Increased capabilities of the Stages API for RTC enactment scripts to increase reuse of those • Process compliant creation and maintainance of links between work-items • semi-automated creation of work breakdown structures • creation of track-links between work-items

10.9 Changes from 6.1 to 6.2 Find below listed all changes for Release 6.2 since Release 6.1.

Component Enhancement ID Description Jazz / RTC Support 25995 Enactment association type "connect" allows to perform workflows across multiple process element types. PWB Visualization 25991 The global method script.include can now be used in the visualization scripts to include scripts based on the webapp/WEB-INF/conf/diagram/scripttemplates folder: e.g. script.include("test.vm"); PWB Visualization 25985 Node Shapes now are able to place node labels in center-center position. Therefore LabelAutoSizePolicy.AUTOSIZE_NODE_WIDTH and LabelAutoSizePolicy.AUTOSIZE_NODE_HEIGHT set label- size to the minimum of either shape size or label-height and - width. NodeStylingShape now has default implementations for all methods except getText(...). CMS 25837 Added new Serena Dimensions CM interface PWB Visualization 25962 TableDiagramConcept now supports properties to control graph density. PWB Visualization 25608 Visualization Shapes now support overlay icons, color gradients and shadows. CMS 25864 Improved example configuration for MySQL-based cache stores in PKitCaching.xml. Also provided an example for Oracle. CMS Refactoring of Revision Properties PWB Basics 25812 Enabled usage of pdf header/footer variable $ Global 25716 Editor could not be opened in IE compatibility mode. This mode is now ignored. PWB Visualization Visualization scripts (velocity .vm files) now support an include mechanism for script libraries. Scripts can be included using #include or #parse, e.g. #include("MY_SCRIPT.js"), #parse("MY_TEMPLATE.vm"). CMS 25478 CMS prefetch can start faster due to reduced preparation overhead. Jazz / RTC Support 22178 Provided analysis function which tests if process workflow data are ready to be published to Rational Team Concert. Administration 25430 Authenticate user based on external HTTP header that can be configured with config property "autologin.header.userIdentifier". This can be used to perform external authentication (e.g. via SAML) and pass the user to Stages. WARNING: should only be used in conjunction with a Tomcat filter or realm (e.g. OpenAM) that validates the HTTP headers. Using this option without a filter or realm opens a security gap. PWB 24806 Process element state management handling is now fully configurable. The new config properties process.element.state.transitions.. = replace the existing "element.state.keepOnModify" property. must be either

Component Enhancement ID Description "modify" for the state transition when modifying the element or "associate" for the state transition when modifying an association to the element. Per default, all elements are changed to "draft" state if they are modified or an element is associated with them. This is also the previous behavior. State management is now enabled by default for newly created processes. Jazz / RTC Support 25369 Stages user who is assigned to a responsible role will be exported to Rational Team Concert and assigned to a task as work item owner. UE Usability 25447 Exchanged position of URL and name filed in edit URL properties dialog. Jazz / RTC Support 22592 New permission domain "Process Execution Configuration" for Rational Team Concert export. PWB Editor/TWiki 25364 Upgrade CKEditor to version 4.0.1.1. PWB Editor/TWiki 24760 The editor link plugin will now scroll the currently selected element into view. PWB Basics If successor or predecessor elements are created through the "[New]" link, we activate the newly create element instead of the originating element to faster create sequences. CMS 25332 This enhancement is for the deprecated Integrity interface (for Integrity versions prior to 2009 SP7): As a workaround for OutOfMemory problems of the Integrity client, Stages can be configured to restart the client process after a certain number of command executions (specify desired value with cms-option "clientMaxCommands"). At a Glance 5715 Document tab can now also be opened if there is no cm profile available. At a Glance Renamed artifact folder into document folder. PWB Editor/TWiki 25084 Textual references with relative paths can now be manually entered in the editor plugin dialogs to allow for robust links.

11 New Features for 6.1

11.1 Microsoft SharePoint

Microsoft SharePoint is the business plattform for collaboration in your company throughout the web. It provides a full set of tools that your people can use to create any kind of site, plus a single infrastructure that simplifies site management. From a team site for colleagues, to an extranet site for partners, to an Internet site for customers, people can share and publish information using one familiar system. The new Stages MS SharePoint integration is based on a direct web service interface to a MS SharePoint server.

Benefits • Full Access from Stages to your project documents in your SharePoint libraries • Manage your process documents like templates or checklists in Sharepoint • Easy to maintain because no sandboxes are checked out on the Stages server • Write operations are conducted with MS SharePoint user related to current Stages User

11.2 Element State management

The process management with Stages has been improved. The state management for process elements now allows the configuration of target states dependent on the current state and a event. The known events are modify which is fired when an element attribute has been changed. The associate event is fired if a elements associations are changed.

Benefits • No unrecognized changes meanwhile process maintenance • Optimal Support of process review proceedings

Figure 46: Example configuration for state management

11.3 RTC

IBM® Rational Team Concert™ is a software lifecycle management solution that enables real-time, contextual collaboration for distributed teams. Based on the IBM Rational® Jazz™ platform, Rational Team Concert provides a process configuration, guidance and enforcement framework that can support your entire software delivery environment. The Stages and RTC integration combines the process management of Stages with the application lifecycle management capabilities of RTC. Together Stages and RTC ensure efficient compliance with industry standards and best practices, such as CMMI, Automotive SPICE, ISO 26262, IEC 62304, DO-178/254. Create an environment to define, manage and execute software engineering processes across product development with a solid framework for process improvement.

Benefits • Automated execution of life cycles (including lean and agile methods) • Eliminate risk of non-compliance • Instant adoption of process changes • Support for RTC V3 and V4

Figure 47: Work items view Figure 48: Related process information

11.4 Stages Composer Faster, easier process modeling for process managers with the Stages Composer and graphic modeling with MS Visio.

Benefits • Distributed off line modeling • Easy and fast compliance mapping • Graphical process modeling with a seamless integration with Microsoft Viso • Easy usability with Drag & Drop, Undo and Copy & Paste • Spell checking for processes • Configuration and version management with complete history • Permanently running consistency checks • Multi select operations • Multi language support for processes

Figure 49: Editor view Figure 50: Compare view

11.5 PTC Integrity

PTC Integrity, an application lifecycle management solution, that manages all global software development processes and connects all software engineering artifacts, including requirements, models, code, and test, ensuring comprehensive lifecycle traceability. The new Stages PTC Integrity integration is based on a direct web service interface to a PTC Integrity server.

Benefits • Increased performance • Easy to maintain because no sandboxes are checked out on the stages server • Write operations are conducted with Integrity User related to current Stages Users

11.6 Editor 2.0 The stages build-in WYSIWYG editor is updated from TinyMCE to CKEditor. Beside this the complete Copy & Paste Handling is now based on HTML validation.

Benefits • Better usability of the editor • Pasted text fragments will be validated and transformed by Stages before storing the data into the database

Figure 51: Edit dialog with new editor

11.7 Process View Menu The process view menu allows the user to switch fast between different process appearances

Benefits • The right information for the different target groups • Possibility to zoom into a different detail level • Free configuration of additional levels allows any number of views • Also users using the anonymous (guest) account have the possibility to change the view

Figure 52: Detailed View

Figure 53: Compact View

11.8 Visualization

• TableDiagramConcept now supports option for consideration of label length when layouting an edge • Setting the "zoomPopupRemainsOpen" attribute of a meta-model diagram tag to the value "true" will keep the visualization pop-up open after navigation by clicking on one of the diagram nodes • Magnifier is now displayed on the upper left side of diagrams • Support multiple diagrams per page

Figure 54: Layers

Figure 55: Swimline

Notice: These example visualizations are not part of the Stages 6.1 delivery package. Visualization scripts are part of the product consulting. Please contact your product consultant for an offer.

11.9 Performance

• Improved performance of metric script execution • Improved performance for baseline retrieval • Improved performance by introducing warm caching of revision information of CMS managed documents. • Improved performance of displaying files • Improved tree performance for webkit browsers • Improved overall Wiki performance • Improved performance by using a cache for the ProcessElement Index page • Improved caching of document revision properties • Use cached sequences to improve insert performance on Oracle databases • Improved performance of core process updates • Improved performance of file open/checkin dialog • Improved performance of process and resource overview page • Performance improvement for compliance workbench • Improved build time of reference model tree in the compliance workbench • Improved performance of logentry news creation

11.10 Usability

• Modern and reduced user interface • Faster responses due to performance improvements • Added special "View Menu" on PWB main, index and view pages to allow user to switch between views quickly • Overview page is now a flat list of documents which makes it easier to search • Overview page can now be filtered by element folders • Files and URLs can now be created faster • The configuration property "cms.download.filename.extension" can be set to "true", if the file version and checkin date shall always be included in the proposed download names of CMS-managed files. • The WYSIWYG editor is now used for entering tailoring justifications • Analyze menu is now available in all process versions • Extended information for inaccessible URLs in Process Analysis and Resource Overview is given • Process version creation is now executed in a background job if the current user has a valid email address and e-mail notifications are configured • Analysis function which tests if process workflow data is ready to be published to Rational Team Concert.

Figure 56: New user interface styling

11.11 Metrics

• Updated all Business Intelligence and Reporting Tools (BIRT) components to Version 3.7.2. • Charting Improvements: Polar/Radar Chart

Figure 57: Radar chart • Open Office Emitters • Support for Office 2007/2010 data extraction and collection • Improved performance of metric script execution

Notice: See New and Notable Features within BIRT 2.6 and New and Notable Features within BIRT 3.7

Important: Please use the corresponding BIRT RCP Designer version 2.1.0. or later, available from your Stages support.

Important: For direct access from BIRT Reports to MySQL 5 DB please redeploy JDBC driver in \tomcat\webapps\pkit\WEB-INF\platform\plugins \org.eclipse.birt.report.data.oda.jdbc_3.7.2.v20120213\drivers\

11.12 ARIS

• Extended ARIS content import with support for ARIS 7.2 data format (only plain text content, no images in StyledElement tags). • Images from OLE definitions in ARIS process descriptions can now be imported and referenced as Stages resources by specifying the attribute "importImages" with value "true" on the corresponding model element in ARIS mapping. • Stages attributes can now be mapped to fixed values:

11.13 Administration

• New LDAP synchronization mode "ondemand": Users are automatically created from LDAP directory if • a) they try to log in • b) an admin tries to assign them to a role

11.14 Changes from 6.0 to 6.1 Find below listed all changes for Release 6.1 since Release 6.0.

Component Enhancement ID Description Administration 24612 New LDAP synchronization mode "ondemand": Users are automatically created from LDAP directory if a) they try to log in b) an admin tries to assign them to a role. The normal user synchronization is being replaced by updating the existing users individually with unique queries. To enable this mode, use

Component Enhancement ID Description Jazz / RTC Support 25369 Stages user who is assigned to a responsible role will be exported to Rational Team Concert and assigned to a task as work item owner. Jazz / RTC Support 22592 "New permission domain ""Process Execution Configuration"" for Rational Team Concert export. " Jazz / RTC Support 25029 Ensure compatibility between Stages Web and Rational Team Concert version 3.0 and 4.0. VERSION file contains installed Rational Team Concert version information. Jazz / RTC Support 24944, 24927 Rational Team Concert versions 3.0 and 4.0 supported. Jazz / RTC Support 24961 Rational Team Concert plugin "gmrtc" renamed to "rtc". Project Review 24471 Review readiness check will be executed in background. The Board user will be notified about the result via email. PWB 24806 Process element state management handling is now fully configurable. The new config properties process.element.state.transitions.. PWB Basics 25339 File upload contents for artifact instances and resources are now directly streamed from a FormFile and not hold in memory. PWB Basics 24975 The modification date of URL-based resources is now hidden. PWB Distribution 19784 Ordering of elements can be configured during process update. PWB Distribution 25088 Protected elements can be moved. The process update can be configured to push the hierarchy from the core process or to preserve the local hierarchy. PWB Editor/TWiki 25364 Upgrade CKEditor to version 4.0.1.1. PWB Editor/TWiki 24760 The editor link plugin will now scroll the currently selected element into view. PWB Editor/TWiki 25250 In the selection tree of the editor link plugin only the first level children should be shown when opening the dialog using the toolbar button. PWB Editor/TWiki 25084 Textual references with relative paths can now be manually entered in the editor plugin dialogs to allow for robust links. PWB Editor/TWiki 25250 In the selection tree of the editor link plugin only the first level children should be shown when opening the dialog using the toolbar button. Request Tracking 25131 Do not set focus on id search field so that label is visible. UE Usability 25447 Exchanged position of URL and name filed in edit URL properties dialog. UE Usability 24886 Easier removal of Quicklist entries. User Experience 24999 Adjust spacing in project navigation User Experience 24720 Moved feedback link to info area on login page. Wiki, Yellow Pages 24841 Wiki and Yellow Pages are now fully renamable.

12 Mandatory manual actions

12.1 Mandatory manual actions Upgrading from 6.5 or 6.6 This Actions must be performed when upgrading from 6.5 or 6.6

Component EnhancementDescription Mandatory manual actions or Error ID Installer 32248 Preserve the jdbc driver Relevant for Stages Linux RPM upgrade from jar (mysql.jar or ojdbc.jar) a previous version to this version. Backup the during Stages upgrades. existing jdbc driver jars (mysql.jar and ojdbc.jar) before upgrade to this version. Source location: [INSTALLDIR]/tomcat/webapps/pkit/WEB-INF/lib/ After RPM Stages upgrade copy the jdbc driver jars back to their original location. Installer 32449 Do not package mysql Driver must be downloaded (see and oracle driver due to SystemRequirements) and copied into the WEB- license issues. INF/lib folder. Global 32495 Stages 7 could not be Add the following valve to your tomcat server.xml inside the Tag: from older stages versions due to a cached redirect to index.jsp. Now all .jsp requests are redirected to index.html. Database 30733, Recreating the existing foreign The "URIEncoding" attribute in the "Connector" tag key constraints for the InnoDB 31216, MySQL database engine (all defined in the "server.xml" file has to be changed 30823, existing FK constraints were not from "ISO-8859-1" to "UTF-8". In order to have a created in MyISAM). Converting all 30634 columns, tables and the database complete UTF-8 data encoding the configuration to use UTF-8 character set and the property "default.encoding" has to be set also to utf8_bin collation. All new columns "UTF-8" if explicitly specified (UTF-8 is the default). and tables will be created with the UTF-8 character set. Capitalizing the quartz table names due to case sensitive file systems (e.g. ext3/ ext4). The last changed timestamp wasn't updated after changing an element in the element table, as well as in the history table in the database. Updating the MySQL connector from version 3.1.12 to 5.1.40. Database 30747 Introduced transaction The supported transaction level is READ- safety for MySQL. Tables COMMITTED. Therefore, the section [mysqld] are converted to the of the MySQL configuration needs to contain the InnoDB engine. line "transaction-isolation=READ-COMMITTED". Database administrators need to be aware of the conversion to InnoDB, since the data is stored differently now. By default, InnoDB stores multiple MySQL databases in one file. MyISAM used to store every database in its own directory and every table in one file. Backup strategies may need to be adapted. Please note that copying the directory formerly used by MyISAM will no longer back up any data.

Component EnhancementDescription Mandatory manual actions or Error ID SVN CMS 30047 remove old sandbox use the migrateSubversion.bat or based subversion migrateSubversion.sh to migrate all your sandboxes interface from the old to the new interface Administration 32233 Introduce the new This new permission must be manually assigned to permission domain those user groups who need to export and import 'process import/export'. processes. User with this permission are able to import and export the whole process without restrictions. Global 31267 Enabling gzip For performance improvement the "Connector" compression in tomcat element in the server.xml should be extended for various mime types with the following attributes: compression="on" (e.g. html, css, json, svg). compressableMimeType="text/html,text/ xml,text/css,text/javascript,text/plain,application/ javascript,application/json,application/xml,image/svg +xml,application/x-font-ttf" Global 30788 Refactoring the Stages The realm definition in "tomcat/conf/server.xml" has to be adjusted with the new Stages realms (SSLAuthenticatorRealm, SimpleAuthenticationRealm). login modules (SPNEGO, The following realms inside the Engine tag in server.xml have authentication. to be replaced with the following realms:

12.2 Mandatory manual actions Upgrading from 6.4 This Actions must be performed when upgrading from 6.4

Component Enhancement Description Mandatory manual actions or Error ID SVN CMS 30047 Remove old sandbox-based Use the migrateSubversion.bat or subversion interface and migrateSubversion.sh to migrate all your configure SVN to use a sandboxes from the old to the new interface. webservice based interface

Global 30035 Install Java 8 before updating You can find the Oracle Java Standard Stages Edition 8 Development Kit under the following link: http://www.oracle.com/technetwork/java/ javase/downloads/index.html

Global 30039 Upgrade Tomcat to version The file tomcat/conf/server.xml needs to be 8.0.30. adapted. Remove the listener element of org.apache.catalina.core.JasperListener. Replace the line by Metrics 26051 28894 Integration of new BIRT Linux installations only: After upgrading 28376 version 4.4 for process Stages move your custom jdbc drivers reporting. from ${RPM_INSTALL_PREFIX}/tomcat/ webapps/pkit/WEB-INF/platform/plugins/ org.eclipse.birt.report.data.oda.jdbc_*/ drivers/ to ${RPM_INSTALL_PREFIX}/ tomcat/webapps/reporting/WEB-INF/lib/ and prefix the jar name with 'stages-ext-' so they can be managed automatically during future upgrades. Example: a_jdbc_driver.jar is moved and renamed to stages-ext- a_jdbc_driver.jar

12.3 Mandatory manual actions Upgrading from 6.3 This Actions must be performed when upgrading from 6.3 and when upgrading from 5.1 to version 6.4.

Component Enhancement/ Description Mandatory manual actions Error ID

File Handling Enhancement Selecting a file from a CM system The structure of PKitCaching.xml has changed and must be adapted to be able to start the 27904 is now easier as you can browse Stages service. the CM structure from within Upgrade from 6.3.x: Stages. This is available for After Stages 6.4 is installed you will find a documents and resources as new example configuration file for the CMS long as one of the following CM cache at [install_dir]/tomcat/webapp/WEB- INF/conf/PKitCaching-customer.xml.dist systems are used: Sharepoint, and your customized caching configuration Integrity 2009 and newer, at [install_dir]/tomcat/webapp/WEB-INF/ conf/PKitCaching-customer.xml containing Subversion (New), ClearCase. your custom loader configuration that needs to be migrated. Use the PKitCaching- customer.xml.dist as template for a new PKitCaching-customer.xml. Replace both loader configurations of the template (...) with your own configuration as in your old PKitCaching-customer.xml. Run [install_dir]/ bin/updateConfig.bat|sh afterwards. Upgrade from 6.1.x or 6.2.x: After Stages 6.4 is installed you will find a new example configuration file for the CMS cache at [install_dir]/tomcat/webapp/WEB- INF/conf/PKitCaching-customer.xml.dist and your customized caching configuration at [install_dir]/tomcat/webapp/WEB-INF/conf/ PKitCaching.xml.orig containing your custom loader configuration that needs to be migrated Use the PKitCaching-customer.xml.dist as template for a new PKitCaching-customer.xml. Replace both loader configurations of the template (...) with your own configuration as in your old PKitCaching.xml.orig. Run [install_dir]/bin/updateConfig.bat|sh afterwards.

Details of upgrade from 6.3 for enhancement 27904.

PKitCaching-customer.xml (6.3) PKitCaching-customer.xml.dist

Details of upgrade from 6.1 or 6.2 for enhancement 27904.

PKitCaching.xml (6.1/6.2) PKitCaching-customer.xml.dist

12.4 Mandatory manual actions Upgrading from 6.2 This Actions must be performed when upgrading from 6.2 and when upgrading from 5.1 to version 6.3.

Component Enhancement/ Description Mandatory manual actions Error ID PDF Print Error 28396 The margin for the document body You may re-introduce the margin in printoutPDF.css with a CSS rule for body or is now set to zero by default. This @page. avoids an increased top border on the first page. Installer (Linux) Error 28303 RPM (linux) installation overrides All config options have been moved from the rc script to the rc.conf file, any rc modifications (to config settings in rc script the config options) must be ported to rc.conf Global Enhancement Tomcat has been upgraded to When upgrading Stages the Stages service will be reinstalled. All custom java settings have to 27756 version 7.0.54 be configured again. Further a strict user config separation is now in place, All custom settings from the PKitCaching.xml have to be ported to PKitCaching-customer.xml.

12.5 Mandatory manual actions Upgrading from 6.1 This Actions must be performed when upgrading from 6.1 and when upgrading from 5.1 to version 6.2.

Component Enhancement/ Description Mandatory manual actions Error ID CMS Enhancement Added new Serena Dimensions Replace the following lines from PKitCaching.xml with CMS Enhancement Improved example configuration If you created a MySQL JdbcBinaryCacheStore with the property "idColumnType" set to 25864 for MySQL-based cache stores in "VARCHAR(255)", you should consider PKitCaching.xml. Also provided an converting the column to the data type "INT" for example for Oracle. increased performance. CMS Enhancement Refactoring of Revision Properties In case of an update from 6.1.0.0 add de.methodpark.cms.subversion. SubversionRevisionProperties$ SubversionRevisionPropertiesExternalizer as an advancedExternalizer in PKitCaching.xml RTC Integration Enhancement Enhancements to Stages Plugin Due to incompatible changes in the Stages RTC Plugin API some enactment scripts must be API adopted. For details please refer to the RTC Integration Guide available from Stages Support if licensed.

12.6 Mandatory manual actions Upgrading from 6.0 This Actions must be performed when upgrading from 6.0 and when upgrading from 5.1 to version 6.1.

Component Enhancement/ Description Mandatory manual actions Error ID Web Export Error 24815 Navigation links in HTML exports service.jsp needs to be changed: were not working in Chrome. convert "onclick" events to ">a href..." (see local/service.jsp)" Jazz / RTC Enhancement Rational Team Concert plugin Change your current Rational Support 24961 "gmrtc" renamed to "rtc". Team Concert process template for Stages by inserting new values in workflow engine followup- action attributes "xmlns" and "id". CMS Enhancement Refactoring of Revision Properties In case of an update from 6.0.0.0 replace de.methodpark.cms. ExtendedRevisionProperties$ ExtendedRevisionProperties Externalizer by de.methodpark. cms.integrity. IntegrityRevision Properties$IntegrityRevision PropertiesExternalizer in PKitCaching.xml Metrics Error 16327 The data set script variable Update the corresponding BIRT currentUser is now set to the RCP Designer to version 2.2.0. report viewing user in case the report is rendered from within Stages Web; when rendered from BIRT the data source user is set. PWB Enhancement Process element state If you have been using one of the 24806 management handling is now deprecated properties, you need fully configurable. The new config to reconfigure your PKitConfig.xml properties process.element.state. with the new property style. transitions.. = replace the existing "element.state.keepOnModify" property. must be either "modify" for the state transition when modifying the element or "associate" for the state transition when modifying an association to the element. Per default, all elements are changed to "draft" state if they are modified or an element is associated with them. This is also the previous behavior. State management is now enabled by default for newly created processes.

Component Enhancement/ Description Mandatory manual actions Error ID Administration Enhancement New LDAP synchronization If you have been using 24612 mode "ondemand": Users are "ondemand" synchronization automatically created from LDAP with a previous version, you directory if a) they try to log need to rename the filter attribute in b) an admin tries to assign for unique user queries in the them to a role. The normal user PKitConfig.xml from "searchFilter" synchronization is being replaced to "ondemandFilter". by updating the existing users individually with unique queries. To enable this mode, use >ldap synchronize="ondemand" ...> mode and set config property "sync.ldap.autocreate" to "true". Then configure the "ondemandFilter" to find unique users. The '%' char will be replaced by the userId of the newly created user, e.g. "(sAMAccountName=%,cn=Users, dc=methodpark,dc=com)". Administration Enhancement Session handling for anonymous If your license file 23435 user changed. PKitLicense.xml has a limit then please contact Stages support to be provided with an updated license.

12.7 Mandatory manual actions Upgrading from 5.1 This Actions must be performed when upgrading from 5.1 to version 6.1. If you upgrade from 6.0 you can omit these.

Component Enhancement/Description Mandatory manual actions Error ID Administration Error 22829 Adapt the JVM options such Only for running Stages as a Windows that the exception stacktrace service: In a command prompt go is always logged. to the directory: [Stages Installation Directory]\tomcat\bin execute: tomcatw.exe //ES//projectkit Navigate to the "Java" tab. Add option "-XX:- OmitStackTraceInFastThrow" to the "Java options"

Administration Error 19762 The LDAP distinguished • The LDAP attribute name of a user entry could "maximumDeletionPercentage" [tag: ldap] be overwritten with a null is considered for all users to be deleted value if the user entry regardless of the provider they originate was matched by multiple from. Consider to adopt that setting. ldap provider settings in • The new LDAP provider attribute PKitConfig.xml. "strictSynchronization" [tag: ldap- provider] ensures that only attributes listed in a provider's LDAP attribute section [tag: ldap-attribute] are indeed synchronized. Consider to set this attribute for your LDAP provider especially when you want to sychronize user data across multiple providers.

Administration Enhancement First-Level-Support mail Custom support email address can no 16975 address can now be longer be configured through language configured by specifying properties (local/PKit*.properties -> a custom mail address in "support.mailaddress"). Now the address "support.email.address" must be configured through PKitConfig.xml property. ("support.email.address"). CMS Error 18212 Subversion: Usage of SVNKit If you already copied the SVNKit client library could cause a memory libraries to the folder stages\tomcat\webapps hole. \pkit\WEB-INF\lib (or if you want to use them know) you also need to copy the file trilead.jar downloaded with the SVNkit package to the lib folder. So from now on 3 files from the SVNKit package have to be copied to the lib folder: svnkit.jar, svnkit-javahl.jar and trilead jar. You can also request a new version of "Subversion Integration Guide" from Stages support. Database Enhancement Improved performance of Grant create view and create materialized 19938 association integrity checks view privileges to oracle user. for oracle. Use EnsureOracle AssociationIntegrity instead of EnsureDatabaseIntegrity in order to check association integrity with oracle.

Component Enhancement/Description Mandatory manual actions Error ID Database Enhancement Oracle statistics will now be If there is a planned job in Oracle 18273 computed by default every you should deactivate either the day at 11 PM. job or set the config property database.compute.statistics.enabled to false. It is strongly recommended to use the DBMS_STATS_PARAMETERIZED method provided by the application. The method can be activated via the config property database.compute.statistics.method and is default. Database Error 23487 Core process update could Broken resource links can be fixed by break valid links to resources running "updateTarget.bat resource" or after resource name affixes "updateTarget.sh resource". Caution: This had been modified. action may take some time. Global Enhancement Tomcat has been upgraded When upgrading Stages the Stages service to version 6.0.35 will be reinstalled. All custom java settings have to be configured again. Jazz / RTC Error 23918 The getUrl() method for You also have to install a latest version of Support workflow elements in the Stages plug-in for your Rational Team enactment scripts did Concert (Jazz Team) server if you want not return the URL to the to use the getUrl() method of workflow corresponding Stages elements in your enactment scripts. process element, but only an empty String. Metrics Enhancement Update of integrated BIRT If additional JDBC drivers have been 13831 engine to version 3.7.2. The deployed to "org.eclipse.birt.report.data.oda. corresponding BIRT RCP jdbc_2.3.2.r232_v20090212/drivers" in Designer version is 2.0.0. folder "WEB-INF/platform/plugins", then these drivers have to be saved manually before upgrade and to be restored after upgrade to "org.eclipse.birt.report.data.oda. jdbc_3.7.2.v20120213/drivers" within the same folder. PWB Basics Error 17668 If a visualisation graphic Set the CSS style "display: block" in was taller than the available style class "innerCenteredContainer" in page height, it was displayed printoutPDF.css. starting at the second page leaving the first page empty. PWB Error 17848 Importing a process (process The affected integrated core processes must Distribution type = process) with an be updated to resolve the problem. integrated core process made all integrated core process elements be displayed without core process icon. PWB Editor/ Error 24382 Enable migration of old Rich Custom format styles defined in config tWiki Text Editor description format property wysiwyg.editor.styles (syntax: styles. $label=$tag:$class;...) have to be replaced by new styling format in config property global.editor.format (syntax:$tag:$class,...) and define the labels in Pkit.properties as editor.format.$tag.$class=$label. The class name has to start with "stages_" Additionally

Component Enhancement/Description Mandatory manual actions Error ID you have to define a mapping from the old styles to the new ones, so Stages can automatically exchange the formats, when a description is reworked. This can be done by config property global.editor.format.migration (syntax:$oldTag:$oldClass=$newTag: $newClass,...). In all cases the tag is mandatory but the class is optional. The descriptions are only converted on demand (when they are edited), therefore the custom.css should include the old styles as well as the new ones. PWB Editor/ Enhancement Added new rich text editor Description templates defined in tWiki local properties must be converted to HTML in accordance to the new editor: Old: process.MyMetamodell.activity. descriptionTemplate = ---+ Purpose\n \n---+ Entry Criterion\n\n---+ Tasks\n\n New: process.MyMetamodell.activity. descriptionTemplate =

Purpose

Entry Criterion

Tasks

PWB Editor/ Error 20780 The getter method for The configuration property tWiki process descriptions in the 'process.description.languages' may either facade could not handle be empty or contain a comma-separated multilingual descriptions in a list of at least two language locales. Please monolingual environment. empty the configuration property in case of a monolingual configuration. Search Enhancement Initial index creation for solr The configuration properties for the 19892 fulltext search solr webapp (especially the port) have to be adapted. Default values are: global.search.solr.index.hostname: "localhost" global.search.solr.index.port: "8080" global.search.solr.search.hostname: "localhost" global.search.solr.search.port: "8080" Wiki Enhancement The wiki start page is no During Stages upgrade the configuration longer maintained via the folder local\process\pkit\wiki will be stages user interface. The backuped to local\process\pkit\wiki_backup page is now included in and replaced by a new configuration. If your freemarker templates. freemarker template is customized you have to merge these two folders. Otherwise the folder wiki_backup can be deleted. Yellow Pages Error 23546 Allow write access to Permissions have to be adapted for Wiki Yellow Pages departments and Yellow Pages access. Please see and overview page for Administration Guide for details. users without QM License. Therefore two new permission domains are introduced: "YellowPages- Users" and "YellowPages- Departments". Additionally
© 2017 Method Park Software AG Page 79 12 Mandatory manual actions Release Notes 7.1
Component Enhancement/Description Mandatory manual actions Error ID the Wiki permissions domains were cleaned up. Yellow Pages Enhancement Anonymous user can now If the default role has read permissions for 23301 be granted read access to Yellow Pages and it is not desired that an Yellow Pages feature. anonymous user has this permission, it must now be explicitly denied to one of his roles.
© 2017 Method Park Software AG Page 80 13 Installation Release Notes 7.1
13 Installation
13.1 Fresh Installation • Download and install Java Development Kit 8 • Stages installation on Windows: Execute Stages installer as administrator • Stages installation on Linux: • Install RPM package • A user with the name "stages" is needed if the command "stages start" shall be able to start the Stages search engine automatically. The user needs recursive read and execute permissions on the subdirecory "elasticsearch" and additionally write permissions on "elasticsearch/data" and "elasticsearch/logs". • Database installation with Oracle 11g or 12c: • Download Oracle JDBC connector for your Oracle version. • Copy JDBC connector to "stages/tomcat/webapps/pkit/WEB-INF/lib" and rename it to "ojdbc.jar". • Get Oracle database dump and installation instructions from Stages Support. • Database installation with MySQL5.7: • Download MySQL JDBC connector and installer for MySQL 5.7. • Copy JDBC connector to "stages/tomcat/webapps/pkit/WEB-INF/lib" and rename it to "mysql.jar". • Install MySQL 5.7 (if not already installed): • Install MySQL as "Server Machine" and with default encoding "UTF-8". • Adapt "[mysqld]" section in my.ini configuration file:
max_allowed_packet=100M transaction-isolation=READ-COMMITTED • Create database user "stages" and grant privileges:
grant all privileges on . to 'stages'@'%' identified by 'pass'; flush privileges;
• Create database "stages" and import dump file (downloaded from https://www.methodpark.de// downloads/stages/mysqlContent.zip and unzip the file):
mysqladmin -uroot -ppass create stages mysql -uroot -ppass stages < [PATH TO DUMP FILE]
• Edit "stages/tomcat/webapps/pkit/WEB-INF/conf/Database.properties" appropriately like in the following example:
torque.database.default.driver = org.gjt.mm.mysql.Driver torque.database.default.url = jdbc:mysql://localhost:3306/stages? zeroDateTimeBehavior=round&jdbcCompliantTruncation=false torque.database.default.username = stages torque.database.default.password = pass
• Start Stages: • Windows: Start the services "Stages Search" and then "Stages". • Linux: stages start
© 2017 Method Park Software AG Page 81 13 Installation Release Notes 7.1
13.2 Upgrade Installation • Download and install Java Development Kit 8 (if not already installed) • Stages upgrade on Windows: Execute Stages installer as administrator • Stages upgrade on Linux: • Upgrade RPM package • A user with the name "stages" is needed if the command "stages start" shall be able to start the Stages search engine automatically. The user needs recursive read and execute permissions on the subdirecory "elasticsearch" and additionally write permissions on "elasticsearch/data" and "elasticsearch/logs". • Database upgrade with Oracle 11g or 12c: • Download Oracle JDBC connector for your Oracle version. • Copy JDBC connector to "stages/tomcat/webapps/pkit/WEB-INF/lib" and rename it to "ojdbc.jar". • Database upgrade with MySQL5.7 • Download MySQL JDBC connector and installer for MySQL 5.7. • Copy JDBC connector to "stages/tomcat/webapps/pkit/WEB-INF/lib" and rename it to "mysql.jar". • If Stages was previously run with an older MySQL version, MySQL 5.7 has to be installed (see instructions in "Fresh installation" section). In this case export your old database into a dump file with "mysqldump" command and import it into the new database:
mysql -uroot -ppass stages < [PATH TO DUMP FILE] • Adapt "[mysqld]" section in my.ini configuration file:
max_allowed_packet=100M transaction-isolation=READ-COMMITTED • Go through the mandatory manual actions in chapter 11 and apply the necessary ones (for example some changes must be done in tomcat/conf/server.xml). • The metamodels in PKitProcess.xml must be adapted to new Stages 7 format (contact Method Park). • Start Stages: • Windows: Start the services "Stages Search" and then "Stages". • Linux: stages start
© 2017 Method Park Software AG Page 82 14 Known Limitations Release Notes 7.1
14 Known Limitations
Component Description Stages Web Processes While using process element linking make sure that the source processes are accessible by the current user in terms of permissions Stages Composer Multi Language Support does not work for Processes containing core processes Stages Composer Import of existing Microsoft Visio files is not supported Stages Composer Special features from Microsoft Visio 2010 are not supported Global Icons are not supported on element trees Global Tailoring Migration (Upgrade from 5.1): Manual adoptions to the result of tailoring assistant (i.e. re- adding tailored elements) will get lost in case no justification was specified for that manual action. This will take effect after the first tailoring action is performed on that process after upgrading from Stages 5.1 to 6.2. Stages Web Metamodelling When using
-Tags in Metamodel-views with relative positioning for the display of the element description the helper menu on inaccessible links does not work. Stages Web Core Processes In case of conducting a core process import with changed name of parent-element the mandatory sequence associations of child-elements get lost if import options "delete obsolete elements" and "overwrite sorting" is choosen. Stages Web Core Processes When copying a process element from a core process and the copied element is overlaid and owns an commentary association this may lead to a failing core process update when using the process with the copied process element.
© 2017 Method Park Software AG Page 83