Contact: Method Park Wetterkreuz 19a Erlangen Germany. Phone Fax Internet

Transcription

1 Release Notes

2 Contact: Method Park Wetterkreuz 19a Erlangen Germany Phone Fax Internet Version: 7.1 Date:

3 Contents Terminology...5 Literature...6 General...8 New features for File Management... 9 PDF Export Creation Custom Process Attributes Users and Roles Configuration New features for User Experience Navigation & Search...14 Process Experience Process Definition Process Versions Process Modules Administration New features for Stages RTC Integration New features for Issue Tracking Enhancements Create Issues From Process Elements View Related Issues of a Process Element List Issues Across Workspaces Parent-Child-Relation of Issues Set Attributes of Related Issues Change State of Process Element From Issue Multiple CMS Profiles for Resources Maximum File Upload Size Java 8 Support Subversion CMS Interface Web-service-based Interface Subversion Server 1.9 Support Read-only Stages System Account Changes from 6.4 to New features for Resource Synchronization New SVN CMS interface Create File from Template...33 Tailoring Enhancements State Filtering for Documents Overview...37 Changes from 6.3 to New Features for PDF Document Generation Stages Unified Configuration Composer Excel import Resource Overview...45 Changes from 6.2 to New Features for Visualization Improvements Serena Dimensions Interface SVN Server to Server Interface...50 Editor Table Plugin... 51

4 Editor HTML Description Plugin Auto-Mapping via Fuzzy-Match Metamodel exchange in Composer...54 RTC Enactment Improvements Changes from 6.1 to New Features for Microsoft SharePoint Element State management RTC Stages Composer PTC Integrity Editor Process View Menu Visualization Performance Usability Metrics ARIS Administration Changes from 6.0 to Mandatory manual actions Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory manual manual manual manual manual manual manual actions actions actions actions actions actions actions Upgrading from 6.5 or Upgrading from Upgrading from Upgrading from Upgrading from Upgrading from Upgrading from Installation Fresh Installation Upgrade Installation Known Limitations...83

5 1 Terminology 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 are shown with this icon: Related Links Terminology on page 5 Page 5

6 2 Literature 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. Page 6

7 2 Literature 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. Page 7

8 3 General 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 Page 8

9 4 New features for New features for 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. Page 9

10 4 New features for 7.1 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. Page 10

11 4 New features for 7.1 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. Page 11

12 4 New features for 7.1 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/ PKitConfig.xml /conf/config.xml /tomcat/webapps/pkit/web-inf/conf/ PKitProcess.xml /conf/metamodelident.mm (contains process.xml and all other meta-model dependent files) /tomcat/webapps/pkit/web-inf/conf/ PKitRequest.xml /conf/request.xml /tomcat/webapps/pkit/web-inf/conf/ PKitLicense.xml /conf/license.xml /tomcat/webapps/pkit/web-inf/conf/ PKitSignature.xml /conf/signature.xml Page 12

13 4 New features for 7.1 V6 File Name V7 File Name /tomcat/webapps/pkit/web-inf/conf/ PkitMetrics.xml /conf/metrics.xml /tomcat/webapps/pkit/web-inf/conf/ Database.properties /conf/database.properties /tomcat/webapps/pkit/web-inf/classes/ LocalPKit.properties /conf/local.properties (for non-meta-model 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 Page 13

14 5 New features for New features for 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. Page 14

15 5 New features for 7.0 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. Page 15

16 5 New features for 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. Page 16

17 5 New features for 7.0 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. Page 17

18 5 New features for 7.0 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. Page 18

19 5 New features for 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. Page 19

20 6 New features for New features for 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 Page 20

21 7 New features for New features for Issue Tracking Enhancements 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: Page 21

22 7 New features for 6.5 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 <request-config... processchangemanagement="true"...>... <elementtrace ident="process_element"></elementtrace> 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: Page 22

23 7 New features for 6.5 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)) 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: Page 23

24 7 New features for 6.5 Figure 21: Issue Filter Note: This feature has to be activated per Issue Tracking configuration in Pkit.Request.xml: <request-config... globalfilter="true"> For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)) 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. Page 24

25 7 New features for 6.5 Figure 22: View parent Page 25

26 7 New features for 6.5 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 <parent ident="parent"/> <children ident="children" columns="#id, title" columntitles="request.attribute.id, request.attribute.title"> </children> 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. Page 26

27 7 New features for 6.5 Note: This feature has to be configured in PkitRequest.xml: <setrequestattributes requests=scriptable_option values=scriptable_option/> For details please refer to Issue Tracking Guide V6.5 (available with Stages V6.5 (GA)). Example Configuration <requests ident="related-requests"/>... <events> <onchange condition="isinnewstate('released')"> <setrequestattributes requests="getchildrequests()" values="getvalues()"/> </onchange>... </events>... <functions> function isinnewstate(state) { return (requestelement.getattribute("states").getproperty("databasevalue") == state); } function getchildrequests() { var ids = new Array(); var seerequestsvalue = requestelement.getattribute('relatedrequests').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; }... </functions> 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 <onchange condition="isinnewstate('completed')"> <setelementstate state="released"/> </onchange> <functions> function isinnewstate(state) { Page 27

28 7 New features for 6.5 return (requestelement.getattribute("states").getproperty("databasevalue") == state); }... </functions> 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). <properties> <property name="form.upload.maxsize" value=" "/>... </properties> 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: Page 28

29 7 New features for 6.5 Important: Before updating Stages you have to update the Java runtime, see mandatory manual actions 7.5 Subversion CMS Interface 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 Subversion Server 1.9 Support Stages 6.5 now supports Subversion server version 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: <cms-property name="read-only-system-account" value="true"/> 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 Enable resolving users by their username in metric scripts through pkit.getuserbyusername() call Page 29

30 7 New features for 6.5 Component Enhancement ID Metrics Integration of new BIRT version 4.4 for process reporting.mandatory manual actions Upgrading from 6.4 on page 71 Description Facade Component Enhancement ID Description Facade Added Property "CreationDate" to ProcessClass. Facade Added compliance model to facade. Facade Added methods (newrequestfilter() and getrequests(projectid, filter)) to pkit facade in order to get filtered requests Component Enhancement ID Description Global Support Java 8Mandatory manual actions Upgrading from 6.4 on page 71 Global Guided Tour provides external direct links. Global Upgrade Tomcat to version Mandatory manual actions Upgrading from 6.4 on page 71 Global Adjust maximal file upload size to 2 GB (maximal supported filesize) Global CMS Enhancements Component Enhancement ID Description CMS Subversion Remove old sandbox based subversion interfacemandatory manual actions Upgrading from 6.4 on page 71 CMS File path proposal can be disabled via config property 'process.file.cmsfilepath.proposal.enabled'. CMS Subversion Support subversion servers 1.9 and read-only system accounts. Component Enhancement ID Description PWB Visualization Enhance performance logging of diagram rendering Component Enhancement ID Description Administration Support information contains tomcat.log and rc.conf (linux only). Visualization Administration Resources Page 30

31 7 New features for 6.5 Component Enhancement ID Description PWB Resources Resources provides multiple cms profiles. Component Enhancement ID Description Request Tracking Added parent and children attribute. Request Tracking Attributes of dependent requests can be set when an issue is saved. Request Tracking Issue filter can now be project independent (<request30067 config... globalfilter="true">). Process element state can now be set via an issue tracker event (<onchange condition="isinnewstate('completed')"><setelementstate state="released"/></onchange>). 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). Issue Application Page 31

32 8 New features for 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. Page 32

33 8 New features for 6.4 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 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 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. Page 33

34 8 New features for 6.4 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: Page 34

35 8 New features for 6.4 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 Page 35

36 8 New features for 6.4 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 Page 36

37 8 New features for 6.4 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 Enhancement ID Description PWB Resources 27894, 28481, Resources can now be synchronized with the CM system. 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 Automatic synchronization of resources with a folder in the CMS. Depends on a cache for the CMS structure which is independently fetched. File Handling Rules for synchronization of resources can be managed per CMS profile. Component CM System Browser - for details see New SVN CMS interface on page 33 Page 37

38 8 New features for 6.4 Component Enhancement ID Description File Handling 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 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 Log and show date and executing user of tailoring changes. PWB Tailoring For elements that are tailored implicitly by their parent or child element an appropriate note is displayed. PWB Tailoring Provide a detailed justification for elements tailored via the tailoring assistant. PWB Tailoring Allow the tailoring assistant to start with an empty process and add elements as needed instead of removing obsolete ones. PWB Tailoring 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 Disable the deprecated description add on tailoring by default. To reenable the feature set property "process.tailoring.enable.addon.tailoring" to "true". PWB Tailoring The tailoring justification is now required for single element tailoring. PWB Tailoring 9467, 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 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 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 Application Page 38

39 8 New features for 6.4 Enhancement ID Description User Experience Improve user feedback functionality by sending the feedback via the local mail application to ensure a valid address is available for call backs. Component Access CM managed resources through system or individual user credentials Enhancement ID Description PWB Resources 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. Component Installer Enhancement Enhancement ID Description Installer 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. Component Further Improvements Component Enhancement ID Description Compliance Workbench For the unified_configuration, we can define better constraint 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: <global-constraints> <global-constraint classname="de.methodpark.pkit.process.constraintcheck.ch unicorn.unicorntoomanyactivitiesprocessqualityanalyzer"/ > <global-constraint classname="de.methodpark.pkit.process.constraintcheck.ch Page 39

40 8 New features for 6.4 Component Enhancement ID Description unicorn.unicorntoomanyrolesprocessqualityanalyzer"/ > <global-constraint classname="de.methodpark.pkit.process.constraintcheck.ch unicorn.unicorntoomanyhandoversprocessqualityanalyzer"/ > </global-constraints> UE Usability 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. Page 40

41 9 New Features for New Features for 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. Page 41

42 9 New Features for 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 Page 42

43 9 New Features for 6.3 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. Page 43

44 9 New Features for 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 Page 44

45 9 New Features for 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 Page 45

46 9 New Features for 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 Allow customer so specify login and logout redirects. Jazz / RTC Support Provide default enactment script resource for export to Rational Team Concert. PWB Editor/TWiki Log entry when user has been assigned to or unassigned from a role. CMS Subversion Admin can choose for each subversion repository whether he would like to use indivial user authentication or not. Facade Provide facade properties to access Enactment parameter. Facade Provide facade properties to access the TypeName and SubtypeName in sigular and plural. Facade Return the associations and child elements in the same order as they are shown in the gui. Global 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 with the config property "global.securemode.enabled" a XFRAME-OPTIONS = SAMEORIGIN header will be added to every response, preventing the application to be embedded into IFrames. PWB Editor/tWiki Added horizontal rule plugin which provides a command to insert Horizontal Rule (<hr> 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 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 Editor has been upgraded to version and is now minified for better performance. PWB Import/Export The values of custom attributes of type "selection" with "alphabetical=true" are now displayed in alphabetical order in Stages Composer, too. PWB PDF 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 List PDF print templates on element index pages. PWB Visualization 28268, 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 Separate system and customer config for web.xml, log4j.xml and PKitCaching.xml Page 46

47 9 New Features for 6.3 Component Enhancement ID Description At a Glance 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 The anonymous user now can access the resource overview in the Overview application. Composer Associations are now displayed in the configured order. External Applications Added the possibility to get informations about the health of Stages via the RESTful interface. Facade Html descriptions of process elements and processes can be queried via the facade. Facade Index elements can now be easily queried via the facade, e.g. process.getentities("containsactivityindex@system")[0]. Global Tomcat has been upgraded to version Metrics Improves performance of the metric collector tab. Collector scripts are now validated only after editing and when the collector is triggered. PWB Basics Changing a process element state now updates the last modification time and user of the element. PWB Editor Export editor directive names for Stages Composer. PWB PDF 26847, Description selectors can be freely defined in the meta-modell and can be edited in the editor. PWB PDF Added PDF printing to the process start page. The Freemarker/ Facade template functionality introduced by allows for custom printouts of whole processes. PWB PDF 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 In left navigation panel the service section can now be disabled via configuration property "service.portlet.enabled". Facade 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 Resources may be downloaded without authentication by specifying "unauthenticated.resource.download.user" property, the given user will be used for the download Administration Include license log in Supportinfos. Metrics Added a new property named "Lob" to collector results which can be used to store serialized data. PWB Basics The default children subtype set by the parent element is now also proposed as default for the elements children. Jazz / RTC Support Enactment script errors contain a line number for easier debugging. Page 47

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

49 10 New Features for New Features for 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. Page 49

50 10 New Features for Serena Dimensions Interface Serena Dimensions CM provides extensive software configuration management and deployment capabilities that help you increase development efficiency ( The Serena Dimensions integration is technically based on direct server to server communication of Stages Server and Serena Dimensions server and supports Version 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. ( 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 Page 50

51 10 New Features for 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. Page 51

52 10 New Features for 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. Page 52

53 10 New Features for 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 Page 53

54 10 New Features for 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 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 Page 54

55 10 New Features for Changes from 6.1 to 6.2 Find below listed all changes for Release 6.2 since Release 6.1. Component Enhancement ID Jazz / RTC Support Enactment association type "connect" allows to perform workflows across multiple process element types. PWB Visualization 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 Node Shapes now are able to place node labels in center-center position. Therefore LabelAutoSizePolicy.AUTOSIZE_NODE_WIDTH and LabelAutoSizePolicy.AUTOSIZE_NODE_HEIGHT set labelsize to the minimum of either shape size or label-height and width. NodeStylingShape now has default implementations for all methods except gettext(...). CMS Added new Serena Dimensions CM interface PWB Visualization TableDiagramConcept now supports properties to control graph density. PWB Visualization Visualization Shapes now support overlay icons, color gradients and shadows. CMS Improved example configuration for MySQL-based cache stores in PKitCaching.xml. Also provided an example for Oracle. CMS Refactoring of Revision Properties PWB Basics Enabled usage of pdf header/footer variable $ Global Editor could not be opened in IE compatibility mode. This mode is now ignored. PWB Visualization CMS Description 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 prefetch can start faster due to reduced preparation overhead. Jazz / RTC Support Provided analysis function which tests if process workflow data are ready to be published to Rational Team Concert. Administration 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 Process element state management handling is now fully configurable. The new config properties process.element.state.transitions.<sourcestate>.<op> = <targetstate> replace the existing "element.state.keeponmodify" property. <op> must be either Page 55

56 10 New Features for 6.2 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 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 Exchanged position of URL and name filed in edit URL properties dialog Jazz / RTC Support New permission domain "Process Execution Configuration" for Rational Team Concert export. PWB Editor/TWiki Upgrade CKEditor to version PWB Editor/TWiki 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 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 PWB Editor/TWiki Renamed artifact folder into document folder Textual references with relative paths can now be manually entered in the editor plugin dialogs to allow for robust links. Page 56

57 11 New Features for New Features for 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 Page 57

58 11 New Features for 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 Page 58

59 11 New Features for 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 Page 59

60 11 New Features for 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 Page 60

61 11 New Features for 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 Page 61

62 11 New Features for 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 Page 62

63 11 New Features for 6.1 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 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 Page 63

64 11 New Features for 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 address and 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 Page 64

65 11 New Features for Metrics Updated all Business Intelligence and Reporting Tools (BIRT) components to Version 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 or later, available from your Stages support. Important: For direct access from BIRT Reports to MySQL 5 DB please redeploy JDBC driver in <installationdirectory>\tomcat\webapps\pkit\web-inf\platform\plugins \org.eclipse.birt.report.data.oda.jdbc_3.7.2.v \drivers\ 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: <attribute> <bind-field name="securitylevel"/> <value>5</value> </attribute> Page 65

66 11 New Features for 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 Page 66

67 11 New Features for 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 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 <ldap synchronize Administration 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. At a Glance 5715 Document tab can now also be opened if there is no cm profile available. At a Glance Enable auto submit for artifact folder selection to allow more intuitive usage of document and resource tab. CMS CMS prefetch can start faster due to reduced preparation overhead. CMS 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""). CMS Support checkin with required Sharepoint attributes. (only certain types are supported) CMS Uploads into SharePoint are now executed with the FrontPage RPC interface instead of a SOAP web service. This enables an initial comment and is somewhat more performant. CMS Sharepoint "Default upload method is now Copy service again because of problems with ""Property promotion"". Improved performance of Copy service uploads by streaming the file contents. " Facade Extended UpdateProcessCommand in order to set hierarchy and sort order (setupdatehierarchy(string[]), setupdatesortorder(string[])). Facade File operations are now accessible via stages facade. File Handling An optional disclaimer can be configured for ArtifactInstance checkin and create dialogs, by defining the process.artifact.instance.disclaimer property Global Editor could not be opened in IE compatibility mode. This mode is now ignored. Jazz / RTC Support Provided analysis function which tests if process workflow data are ready to be published to Rational Team Concert. Page 67

68 11 New Features for 6.1 Component Enhancement ID Description Jazz / RTC Support 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 "New permission domain ""Process Execution Configuration"" for Rational Team Concert export. " Jazz / RTC Support 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, Rational Team Concert versions 3.0 and 4.0 supported. Jazz / RTC Support Rational Team Concert plugin "gmrtc" renamed to "rtc". Project Review Board Review readiness check will be executed in background. The user will be notified about the result via . PWB Process element state management handling is now fully configurable. The new config properties process.element.state.transitions.<sourcestate>.<op> PWB Basics File upload contents for artifact instances and resources are now directly streamed from a FormFile and not hold in memory. PWB Basics The modification date of URL-based resources is now hidden. PWB Distribution Ordering of elements can be configured during process update. PWB Distribution 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 Upgrade CKEditor to version PWB Editor/TWiki The editor link plugin will now scroll the currently selected element into view. PWB Editor/TWiki 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 Textual references with relative paths can now be manually entered in the editor plugin dialogs to allow for robust links. PWB Editor/TWiki 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 Do not set focus on id search field so that label is visible. UE Usability Exchanged position of URL and name filed in edit URL properties dialog. UE Usability Easier removal of Quicklist entries. User Experience Adjust spacing in project navigation User Experience Moved feedback link to info area on login page. Wiki, Yellow Pages Wiki and Yellow Pages are now fully renamable. Page 68

69 12 Mandatory manual actions 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 Enhancement Description or Error ID Mandatory manual actions Installer 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 Do not package mysql and oracle driver due to license issues. Driver must be downloaded (see SystemRequirements) and copied into the WEBINF/lib folder. Global Stages 7 could not be opened after upgrade from older stages versions due to a cached redirect to index.jsp. Now all.jsp requests are redirected to index.html. Add the following valve to your tomcat server.xml inside the <Context path="/pkit"...> Tag: <Valve classname="org.apache.catalina.valves.rewrite.rewritevalve" /> Database 30733, 31216, 30823, Recreating the existing foreign key constraints for the InnoDB MySQL database engine (all existing FK constraints were not created in MyISAM). Converting all columns, tables and the database to use UTF-8 character set and the utf8_bin collation. All new columns 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 to The "URIEncoding" attribute in the "Connector" tag defined in the "server.xml" file has to be changed from "ISO " to "UTF-8". In order to have a complete UTF-8 data encoding the configuration property "default.encoding" has to be set also to "UTF-8" if explicitly specified (UTF-8 is the default). Database Introduced transaction safety for MySQL. Tables are converted to the InnoDB engine. The supported transaction level is READCOMMITTED. Therefore, the section [mysqld] of the MySQL configuration needs to contain the 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. Page 69

70 12 Mandatory manual actions Component Enhancement Description or Error ID Mandatory manual actions SVN CMS remove old sandbox based subversion interface use the migratesubversion.bat or migratesubversion.sh to migrate all your sandboxes from the old to the new interface Administration 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 Enabling gzip compression in tomcat for various mime types (e.g. html, css, json, svg). For performance improvement the "Connector" element in the server.xml should be extended with the following attributes: compression="on" 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 Refactoring the Stages login modules (SPNEGO, Basic Authentication, SSL) to use container authentication. The realm definition in "tomcat/conf/server.xml" has to be adjusted with the new Stages realms (SSLAuthenticatorRealm, SimpleAuthenticationRealm). The following realms inside the Engine tag in server.xml <Realm classname="org.apache.catalina.realm.lockoutrealm"> <Realm classname="org.apache.catalina.realm.userdatabaserealm" resourcename="userdatabase"/> </Realm> have to be replaced with the following realms: <Realm classname="org.apache.catalina.realm.combinedrealm" > <Realm classname="de.methodpark.stages.containerauth.sslauthenticatorrealm" roles="pki_user"/> <Realm classname= "de.methodpark.stages.containerauth.simpleauthenticationrealm" roles="stagesuser" /> </Realm> Page 70

71 12 Mandatory manual actions 12.2 Mandatory manual actions Upgrading from 6.4 This Actions must be performed when upgrading from 6.4 Component Enhancement Description or Error ID Mandatory manual actions SVN CMS Remove old sandbox-based subversion interface and configure SVN to use a webservice based interface Use the migratesubversion.bat or migratesubversion.sh to migrate all your sandboxes from the old to the new interface. Global Install Java 8 before updating You can find the Oracle Java Standard Stages Edition 8 Development Kit under the following link: javase/downloads/index.html Global Upgrade Tomcat to version The file tomcat/conf/server.xml needs to be adapted. Remove the listener element of org.apache.catalina.core.jasperlistener. Replace the line <Resources classname= "org.apache.naming.resources.filedircontext" allowlinking="true" casesensitive="false"/ > by <Resources allowlinking="true" casesensitive="false"/> Metrics Integration of new BIRT version 4.4 for process reporting. Linux installations only: After upgrading Stages move your custom jdbc drivers 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-exta_jdbc_driver.jar Page 71

72 12 Mandatory manual actions 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/ Error ID Description Mandatory manual actions File Handling Enhancement Selecting a file from a CM system is now easier as you can browse the CM structure from within Stages. This is available for documents and resources as long as one of the following CM systems are used: Sharepoint, Integrity 2009 and newer, Subversion (New), ClearCase. The structure of PKitCaching.xml has changed and must be adapted to be able to start the Stages service. Upgrade from 6.3.x: After Stages 6.4 is installed you will find a new example configuration file for the CMS cache at [install_dir]/tomcat/webapp/webinf/conf/pkitcaching-customer.xml.dist and your customized caching configuration at [install_dir]/tomcat/webapp/web-inf/ conf/pkitcaching-customer.xml containing your custom loader configuration that needs to be migrated. Use the PKitCachingcustomer.xml.dist as template for a new PKitCaching-customer.xml. Replace both loader configurations of the template (<loader>...</ loader>) 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/webinf/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 (<loader>...</loader>) 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 PKitCaching-customer.xml (6.3) PKitCaching-customer.xml.dist Page 72

73 12 Mandatory manual actions Details of upgrade from 6.1 or 6.2 for enhancement 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/ Error ID Description Mandatory manual actions PDF Print Error The margin for the document body is now set to zero by default. This avoids an increased top border on the first page. You may re-introduce the margin in printoutpdf.css with a CSS rule for body Installer (Linux) Error RPM (linux) installation overrides config settings in rc script All config options have been moved from the rc script to the rc.conf file, any rc modifications (to the config options) must be ported to rc.conf Global Enhancement Tomcat has been upgraded to version When upgrading Stages the Stages service will be reinstalled. All custom java settings have to 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. Page 73