What's new in Modeler 8.2
 |
This topic contains What's New information for a previous release of Modeler.
|
Headlines
• New Integration for PTC Integrity Lifecycle Manager add-in for integrating PTC Integrity Modeler with PTC Integrity Lifecycle Manager. For more information, see
Overview of Integration for PTC Integrity Lifecycle Manager (Integration for PTC Integrity Lifecycle Manager).
• New PTC Integrity Modeler Web Interface for viewing models through your internet browser. For more information, see
Overview of Web Interface (Web Interface).
• New User Roles for configuring Modeler for the different roles that users perform.
• Variability modeling now supports variability parameters and validation scripts. When using the Decision Set Editor and Variant Selector, you can set the value of the parameters, which can be used to set property values of artifacts in a product model. See
Overview of variability parameters.
• New Code Editor for editing the Body property of Operations. For more information, see
Overview of the code editor.
• Atego Studio has been rebranded as PTC Integrity Modeler. The add-ins have been rebranded as well.
Rebranding
As part of the rebranding:
• Artisan Studio is now named PTC Integrity Modeler. In the Help, PTC Integrity Modeler is referred to as Modeler.
• The Atego folder in the Diagrams and Dictionary panes has been renamed Proprietary.
• The Atego submenu that appeared when creating and populating items in Modeler has been renamed to PTC Integrity Modeler.
• The default installation path for Modeler is now as follows:
For 64-bit versions of Windows: C:\Program Files (x86)\PTC Integrity Modeler\
For 32-bit versions of Windows: C:\Program Files\PTC Integrity Modeler\
• The Atego License Server service is now named PTC Integrity Modeler License Server service.
• The name of the Atego Utilities Profile has been changed to Utilities Profile.
License Manager
The following changes have been made to License Manager:
• License Manager no longer has an admin mode.
• The Use Default User Settings and Use Current User Settings options have been removed. When you start License Manager you are now prompted to 'Manage license settings for yourself' or 'Manage default license settings for new users':
◦ The 'Manage license settings for yourself' option allows the current Windows user to set up licenses for use of PTC Integrity Modeler and its add-ins.
◦ The 'Manage default license settings for new users' option simply sets default options that appear in License Manager. These defaults do not license any users for use of PTC Integrity Modeler or its add-ins.
• The license file must now reside in a folder that cannot be virtualized.
• The Replace button copies the file to the folder that is specified as 'The Path to the Local License' on the License Manager Options page.
Miscellaneous
• The SQL Generator is no longer included with Modeler. SQL code is now generated through ACS. You can generate SQL code for SQL 2003, SQL Server 2012 and Oracle 10g. For more information, see
Overview of generating SQL code (SQL code).
• The Tool Options dialog now has options for configuring the Code Editor. For more information, see
Tool options dialog - code editor.
• After performing a rebase or reconcile operation from a sandbox (branch), Modeler now records any clashes and decisions made for those clashes in a Text Diagram or Change Note. The name of the Text Diagram or Change Note starts with 'Clashes: '.
• You can now lock Text Diagrams that are opened as read-only through the new Lock Diagram for Edit button that appears on the Text tab.
• When Modeler creates a Product Model, Variation Points are now removed if all their Variants are removed. For more information, see
Overview of creating product models.
• For C and C++ code generation, after copying project files to your target folder, ACS now updates the PTC and SDK paths in those files for your computer.
• New Script.AffectedItem Script object for On Drop scripts for diagrams. For more information, see
Script functions, attributes and objects - on drop scripts for diagrams.
• New Cabin model provided in the Examples database. The Cabin model demonstrates the use of variability parameters.
• The name of the isPersistent tag definition in the System Architecture profile has been changed to nonVolatile.
• When an Accept Event Action is linked to an Event of type Call, Modeler creates Output Pins on the Accept Event Action for each 'In' or 'In and Out' Parameter of the Operation that is the event trigger for the linked Event. For more information, see
Accept event action (dictionary item).
• On a Use Case Diagram you can now reconnect links.
• For a Server Only installation of Modeler, you can now set up the Oms user as a disabled local user account. For a Standalone installation of modeler, the Oms local user account is set up only when Web Interface is chosen for installation.
Item Properties
• A Dependency and a Variant now have the following properties:
• A Dependency now also has the following properties:
• A Variant now also has the following properties:
• A Model now has the following property to support the Code Editor: Language. For more information, see the related links below.
• An Operation now has the following properties to support the Code Editor: Language. For more information, see the related links below.
• A Package now has the following properties to support the Code Editor: Language. For more information, see the related links below.
• A Variation Point now has the following properties:
• The Script Type property of a Script item can now be VariableElement and VariantParameter. For more information, see
Script type (property).
Automation Interface
• New InstantiateDecisionSet function. The OpenTextEditor, CloseTextEditor and CloseAllWindows functions now open and close the Code Editor for an Operation Body. For more information, see the related links below.
• New Variant Parameter and Actual Variant Parameter objects.
• New attributes for Comments, Constraints, Dependencies, Event Action Blocks, Operations, Packages, Projects and Scripts.
• New Actual Variant Parameter association for Decision Sets, Parameter association for Dependencies and Variants, and Script association for Variants and Variation Points.