Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
78:releasenotes [2022/01/04 04:24] – aakr78:releasenotes [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 Stages Version 7.8 is the second of a series of releases delivering smaller feature sets at a faster pace. Customers will be able to quickly benefit from new capabilities instead of having to wait for larger releases. Stages Version 7.8 is the second of a series of releases delivering smaller feature sets at a faster pace. Customers will be able to quickly benefit from new capabilities instead of having to wait for larger releases.
 +
 +===== Introduction Webinars =====
 +
 +Attend one of our Stages 7.8 introduction webinars, followed by a Q&A session, to learn more about the new capabilities.
 +
 +  * Europe (German): [[https://attendee.gotowebinar.com/register/7927532033175545358|Tuesday, February 8th, 2022, 15:00 - 16:00 MET]]
 +  * North America (English): [[https://attendee.gotowebinar.com/register/6045671702748599312|Tuesday, February 8th, 2022, 1:00 PM - 2:00 PM EDT]]
 +  * Asia (English): [[https://attendee.gotowebinar.com/register/74446153646032911|Tuesday, February 15th, 2022, 4:00 PM - 5:00 PM CST]]
 +
 +Missed them? Register anyway and we will send you a link to a recording of the webinar.
  
 ===== Work Product States* ===== ===== Work Product States* =====
Line 8: Line 18:
  
 With Stages 7.8, our customers can define process results with maximum precision. It allows to specify multiple states for work products like problem reports or change requests and describe the details of each state. With Stages 7.8, our customers can define process results with maximum precision. It allows to specify multiple states for work products like problem reports or change requests and describe the details of each state.
 +
 +[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=dc0c5f&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/wpaddstatesecondselection.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/wpaddstatesecondselection.png?direct&801x359  }}]]
  
 This provides more consistency than the mechanism to use comments on the input/output associations. Also, work product states show up on both sides of an association, so defining work products for value streams and milestones becomes more precise and more consistent. This provides more consistency than the mechanism to use comments on the input/output associations. Also, work product states show up on both sides of an association, so defining work products for value streams and milestones becomes more precise and more consistent.
Line 19: Line 31:
 In the image below, "Program A" needs to have interfaces with "Component A1 Hardware" and "Component A2 Software", but not "Component B1 Hardware", "Component B2 Software", or "Component B3 Software", even if the same process modules are integrated there. In the image below, "Program A" needs to have interfaces with "Component A1 Hardware" and "Component A2 Software", but not "Component B1 Hardware", "Component B2 Software", or "Component B3 Software", even if the same process modules are integrated there.
  
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=7dd61d&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png?direct&800x381  }}]]To correctly instantiate this structure, the algorithms that create process interfaces where changed to resolve interfaces within the **workspace collections**. By creating workspace collections depicted by the colored dots in the image above, the interfaces will be correctly created, because **all workspaces within all collections of the current workspace** are being searched for interface candidates. The interface search was modified to use internal identifiers instead of names, which made it even more robust and allows the workspaces to have arbitrary names.+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=7dd61d&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png?direct&800x381  }}]]To correctly instantiate this structure, the algorithms that create process interfaces where changed to resolve interfaces within the **workspace collections**. By creating workspace collections depicted by the colored dots in the image above, the interfaces will be correctly created, because **all workspaces within all collections of the current workspace**  are being searched for interface candidates. The interface search was modified to use internal identifiers instead of names, which made it even more robust and allows the workspaces to have arbitrary names.
  
 In addition, this new algorithm allows the same process module to be integrated into different workspaces. For example, the "Component B2 Software" and "Component B3 Software" workspaces can have the same software development process module integrated, but might have different tailorings or even different versions of the same module, and it will correctly interface with its parent "Program B" workspace. In addition, this new algorithm allows the same process module to be integrated into different workspaces. For example, the "Component B2 Software" and "Component B3 Software" workspaces can have the same software development process module integrated, but might have different tailorings or even different versions of the same module, and it will correctly interface with its parent "Program B" workspace.
Line 35: Line 47:
 If the working version is explicitely made the the valid version, two versions show up in the version selection: If the working version is explicitely made the the valid version, two versions show up in the version selection:
  
-{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/workingasvalid_2.png?nolink&800x462  }}+{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/workingasvalid_5.png?nolink&800x464  }}
  
 If the valid working version is selected, it will be treated like all other versions, e.g. modeling is not possible. When process interfaces are followed to other workspaces, the interface will point to the valid version of the other workspace. If the non-valid working version is being selected, the interfaces will point to the working versions of the other workspaces. If the valid working version is selected, it will be treated like all other versions, e.g. modeling is not possible. When process interfaces are followed to other workspaces, the interface will point to the valid version of the other workspace. If the non-valid working version is being selected, the interfaces will point to the working versions of the other workspaces.
Line 51: Line 63:
 ===== Automation API ===== ===== Automation API =====
  
-TODO+A new API was added to cover the following use cases:
  
   * Nightly build of integrated process modules   * Nightly build of integrated process modules
   * Automated update of process templates   * Automated update of process templates
   * Creation of process versions for backup and archival   * Creation of process versions for backup and archival
 +
 +Please ask your dedicated product consultant for more info.
  
 ===== Compliance with FastPass for improved accessability ===== ===== Compliance with FastPass for improved accessability =====
Line 67: Line 81:
 The Internet Explorer browser does not have the latest security features to suppress various vulnerabilities. Therefore the **access for users with Internet Explorer has been disabled by default**. Please note that the official support for Internet Explorer ended with Stages version 7.6. The Internet Explorer browser does not have the latest security features to suppress various vulnerabilities. Therefore the **access for users with Internet Explorer has been disabled by default**. Please note that the official support for Internet Explorer ended with Stages version 7.6.
  
-To allow users with Internet Explorer to acces Stages, set the ''global.secureMode.IEAccess''  config property in ''config.xml''  either to ''non_root''  (= all users except root) or ''all_users''. +[[:78:security_settings|See here for more details.]]
- +
-Unmanaged HTML sections in descriptions are an inherent security risk, because process modelers could open the system up to XSS vulnerabilities. Therefore, **those features were disabled by default**. +
- +
-To reenable the handling for unmanaged HTML sections in descriptions, set the ''process.description.displayUnmanagedSections.enabled''  and ''legacy.description.migration.unmanagedSection.templates''  properties to ''true''  in ''config.xml''. +
- +
-**We highly recommend to make those changes only if the respective impact on security is well understood.**+
  
 ===== Other Changes ===== ===== Other Changes =====
  
   * Process visualizations can now be closed to speed up multiple changes within the same workflow.   * Process visualizations can now be closed to speed up multiple changes within the same workflow.
 +  * A "Show Changes" button is now shown in the process release notification emails.
   * All custom attributes are now always found via search per default.   * All custom attributes are now always found via search per default.
-  * TODO: "combined elements" handlings 
  
 ===== How to Upgrade to Version 7.8 ===== ===== How to Upgrade to Version 7.8 =====
  
-Please [[stages-support@methodpark.com?subject=Upgrade to V7.7|contact our customer care team]] to request the installer downloads if you run Stages on-premise or request an upgrade of your managed Stages Cloud instance. Alternatively, you can talk to your dedicated product consultant for more info.+Please [[stages-support@ul.com?subject=Upgrade to V7.8|contact our customer care team]] to request the installer downloads if you run Stages on-premise or request an upgrade of your managed Stages Cloud instance. Alternatively, you can talk to your dedicated product consultant for more info.
  
 ===== Notes ===== ===== Notes =====