1.255

This feature relates to the Run Outputs section, which is visible in the Properties view for run configurations. The run output settings now include an option called “Reuse policy”. Here users can decide when run configurations should automatically be assembled.

• Reuse policy = same version (default): Run Output Components will only be used in the same pool version that they were created in (i.e. the pool that their run configurations were assembled in). In newly derived pool versions, when assembling run configurations that use the run output components, the latest run output components will automatically be identified and their run configurations will automatically be assembled first.  
• Reuse policy = compatible version: In newly derived pool versions, when assembling run configurations that use the run output components, the system will check whether components with the specified component types and/or parameters have changed in the run configurations that will be created. If so, then the latest run output components will automatically be re-assembled. If none of the relevant components and/or parameters have changed since the run output components were created (i.e. their content/hash has not changed), then the run output components with the “old” content (from the previous pool versions) will be used. Note: This can only be done for a maximum of 10 pool versions so that the identification does not negatively affect the client performance.

This improvement relates to the ability to re-use run outputs based on the run output settings and the assembly input record. This process has been improved so that the assembly input record is now directly calculated.

This fix relates to the process of copying and pasting components. In the past, users received an error when pasting a component into a different group version. This has been fixed.

This fix relates to the process of editing components and entering a history comment to define the change. In the past, when editing multiple components, the history comment was only applied to some of the modified objects, but not to all of them. This has been fixed.

This fix relates to the process of entering a value into a parameter table. In the past, the first typed character was not entered into the cell. For example, when typing the value “12”, only the character “2” was entered into the cell. This has been fixed.