aspenONE Integration Foundation™

V9

Release Notes
Version Number: V9
May 2016
Copyright (c) 1998-2016 by Aspen Technology, Inc. All rights reserved.

Aspen Integration Designer, aspenONE Integration Foundation, Aspen Enterprise Integration Framework, Aspen
Manufacturing Master Data Manager, Aspen Operations Domain Model, aspenONE Infrastructure, and the aspen
leaf logo, are trademarks or registered trademarks of Aspen Technology, Inc., Bedford, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This document is a guide for using AspenTech's software. This documentation contains AspenTech proprietary and
confidential information and may not be disclosed, used, or copied without the prior consent of AspenTech or as set
forth in the applicable license agreement. Users are solely responsible for the proper use of the software and the
application of the results obtained.

Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS
DOCUMENTATION, ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR
PURPOSE.

Aspen Technology, Inc.

20 Crosby Drive
Bedford, MA 01730
USA
Phone: (1) (781) 221-6400
Toll Free: (888) 996-7100
URL: http://www.aspentech.com
Contents
1 About these Release Notes...................................................................................1
Related Documentation .....................................................................................1

2 New Features .......................................................................................................3

Aspen Enterprise Integration Framework (EIF) New Features.................................3
Aspen Manufacturing Master Data Manager (mMDM) New Features ........................3

3 Software Fixes .....................................................................................................5

Aspen Enterprise Integration Framework (EIF) Software Fixes ...............................5
Aspen Manufacturing Master Data Manager (mMDM) Software Fixes.......................5

4 Known Issues.....................................................................................................10
Aspen Enterprise Integration Framework (EIF) Known Issues .............................. 10
Aspen Manufacturing Master Data Manager (mMDM) Known Issues ...................... 10

aspenONE Integration Foundation V8.8 Release Notes i

ii aspenONE Integration Foundation V8.8 Release Notes
1 About these Release Notes

These Release Notes describe aspenONE Integration Foundation V9, the latest
release of aspenONE Integration Foundation. This document includes:
• New Features
• Software Fixes
• Known Issues

Related Documentation
In addition to these Release Notes, AspenTech provides the following
documentation for aspenONE Integration Foundation V9:
• aspenONE Integration Foundation Installation Guide
• aspenONE Integration Foundation Implementation Guide
• Aspen Integration Designer Help
• Aspen Manufacturing Master Data Manager Installation Guide
• Aspen Manufacturing Master Data Manager Implementation Guide
• Aspen Manufacturing Master Data Manager Getting Started Guide
• aspenONE Infrastructure Overview
• Aspen mMDM Editor Help
• Aspen mMDM Bulk Load Help
• Aspen mMDM Administrator Help

Notes:
• The web-based mMDM Configuration Manager tool had been disabled
since V8.8. The mMDM Editor can provide access to all the data
management features previously provided by mMDM Configuration
Manager.
• Go to the AspenTech Support Center at https://support.aspentech.com for
updates to aspenONE Integration Foundation documentation.
• Windows XP is no longer supported.

aspenONE Integration Foundation V8.8 Release Notes 1

2 aspenONE Integration Foundation V8.8 Release Notes
2 New Features

This section describes the new features in aspenONE Integration Foundation

V9.

Aspen Enterprise Integration

Framework (EIF) New Features
Aspen Enterprise Integration Framework (EIF) V9 has no new features.

Aspen Manufacturing Master

Data Manager (mMDM) New
Features
Instance Level Security Through mMDM
Web Services for Equipment-Related Data
In previous releases, mMDM uses Aspen Framework's role-based security in
order to limit or provide access to high-level components such as Equipment,
Location, Business Party, and Materials. As a result, a user with access to the
Equipment category had access to all of the Equipment Items.
Starting in V9, mMDM supports Instance Level Security, allowing the
administrator to limit the access of users to particular Equipment Items
through mMDM web services.
Within mMDM Administrator, you must set up the Security configuration
option. For further details, refer to Setting up Instance Level Security in
the mMDM Administrator Help.

aspenONE Integration Foundation V8.8 Release Notes 3

4 aspenONE Integration Foundation V8.8 Release Notes
3 Software Fixes

aspenONE Integration Foundation V9 includes a number of software fixes that

further improve the product.
This section describes the software fixes to aspenONE Integration Foundation
V9.

Aspen Enterprise Integration

Framework (EIF) Software
Fixes
This section describes the software fixes to Aspen Enterprise Integration
Framework (EIF) V9.
CQ Description Resolution
Number

499710 Aspen Integration Aspen Integration Framework log files are

Framework log files now correctly located in the DiagnosticLogs
were not located in folder
the DiagnosticLogs (C:\ProgramData\AspenTech\DiagnosticLogs).
folder.

Aspen Manufacturing Master

Data Manager (mMDM)
Software Fixes
This section describes the software fixes to Aspen Manufacturing Master Data
Manager (mMDM) V9.

aspenONE Integration Foundation V8.8 Release Notes 5

 CQ Number Description Resolution
Additional indexes
needed to be
416898 added to the Aspen Indexes are now implemented to the mMDM
mMDM’s Oracle Oracle schema, resulting in improved
schema. performance.
Web service now takes the attribute definition
There was an issue default value when:
524972
with updating • A class attribute value is null, and
mMDM classes. • Its inherited attribute value is also null.
The mMDM Publish
process was failing
548124
with a validation The code now allows both S95 Area and Site
error. levels to be children of the Enterprise level.
mMDM; update
exception message
564733 for adding in-active A newly-added message indicates that the
equipment when to specific data definition is not available at the
hierarchy. current active date.
The Excel Bulkload
file was The import process now uses "'" escape for the
567881 erroneously equal sign "=" as the first character in a long
importing an XML string value of a class attribute when importing
document. a bulkload XML file.
It was not possible
to prepare an RBV
hierarchy with
578196
similar nodes in the An issue with the bulkhead utility while
Excel bulkload preparing an RBV Hierarchy with similar nodes
template. is resolved.
The OpsNav sort
feature was not
584537
working for nested You can now sort mMDM class attributes by
nodes. name.
The UOM of a
variable wasn't
being changed if it
585909 was only modified
in mMDM when Add this feature to the
uploading CompareClassAttributeValues() method of the
equipment XML. ClassedItem class.
The mMDM
database was
becoming
corrupted when
objects were being
changed within the
591899 hierarchy. (A
"Missing Hierarchy
Node, id = 100144"
error message was A newly-added fkHierarchyNodesID SQL
appearing when condition resolves an mMDM database
hierarchies were corruption issue that was occurring when
being expanded. changing objects within the hierarchy.

6 aspenONE Integration Foundation V8.8 Release Notes

 CQ Number Description Resolution
The editor publish
process was
592674 encountering errors
but was still able to The publishing process now checks if caValue
pass validation. has “” empty string value.
S95 wbe services
GetDynamicValueF
594044
orIdentifiers The incorrect order in return message is
operation issues resolved as the same order in the request.
The name of the
duplicate data was
596516 not being included
in the error The name of the duplicate data is now
message. included in the error message.
The hierarchy level
definition for the Only data definitions whose type is defined as
597781 specified item was applicable in one of the children complex level
not being found for definitions of the current level are now being
certain hierarchies. added to the Advanced hierarchy.
The mMDM Editor
was crashing when
a data definition
598644
was being saved or Enhanced logic now validates a dynamic
the data set was attribute’s default value, preventing it from
being validated. referencing itself.
mMDM was not
receiving the
expected result
when using
602722
AspenCalc as the
calculation engine Using AspenCalc Adapter as the calculation
for class attributes engine for class attributes in mMDM now
in mMDM. works as designed.
The mMDM web
services was
crashing when an When requesting an AspenCalc class attribute,
603161
AspenCalc class the process cleans up the previous data in the
attribute was being ProcessData adapter logic. mMDM Web
requested. Services now works as expected.
An issue handling empty string "" in class
attribute value logic is resolved. You can now:
607053 mMDM was • Import xml files to the mMDM database.
experiencing • Drag and drop classes to existing Equipment
validation errors. definitions.
An error was
occurring while
creating, copying,
and/or modifying a
685408 Quantity Types/Unit An error in the Quantity type builder logic is
of Measure resolved by testing that the quantity type
Sets/Unit of builder does not belong to
Measures IClassedItemBuilder. The casting then works
definition. as designed.

aspenONE Integration Foundation V8.8 Release Notes 7

 CQ Number Description Resolution
The mMDM Editor
was crashing when
a new equipment
definition was
687236
added and
assigned to PB
Reactor Vessel
type. The validation error is now caught.
The mMDM
Bulkload was not
691451 importing all
Hierarchies defined The bulkload can now successfully store
in the XML file. empty class array attribute values.

8 aspenONE Integration Foundation V8.8 Release Notes

aspenONE Integration Foundation V8.8 Release Notes 9
4 Known Issues

This section describes known issues for aspenONE Integration Foundation V9.

Aspen Enterprise Integration

Framework (EIF) Known Issues
Aspen Enterprise Integration Framework™ V9 has no Known Issues.

Aspen Manufacturing Master

Data Manager (mMDM) Known
Issues
Aspen Manufacturing Master Data Manager (mMDM) V9 has no Known Issues.

10 aspenONE Integration Foundation V8.8 Release Notes