Promis.e CONNECT Update 5

The Promis.e product team is pleased to announce the availability of Promis.e CONNECT Edition x64 ( on Software Downloads.


If you would like the setup executable of Promis.e CONNECT Edition x64, please follow these steps to download it from Fulfillment Center:

  1. Sign in to               
  2. Choose Software Downloads from "My Support" section
  3. Select the Brand OpenUtilities and locate Promis.e in the list 

  4. Download the latest release by clicking on the arrow to expand the selection and then on Promis.e CONNECT Edition x64 version

Important installation requirements and notices are found in the Readme file.  

Please refer to the following link for the Resolved Issues in Promis.e CONNECT Update 5.  Also, be sure to visit the OpenUtilities forum on Bentley Communities to keep up to date with the latest information on Blogs, Wiki's, Announcements, and Support Forums.

What's New Highlights

Operating System and Database Changes

Support for Windows 7 is discontinued

Promis.e no longer supports Windows 7. 
This change is required to comply with the operating system support for our platform MicroStation CONNECT Update 14.

This change is driven by Microsoft's announcement to stop supporting Windows 7.
Bentley does not support its software running on Microsoft operating systems versions that Microsoft has "retired". For more information on Microsoft's application retirement policy, click here. For similar information on Bentley products, refer to the Bentley Product Support article.

It is  recommended to use Windows 10 (64-bit) - Home, Pro, Enterprise or Education Editions

Support for SQL 2019

Promis.e Update 5 is now certified to work with SQL Server 2019

Support for Windows Server 2016

Promis.e Update 5 is now certified to work with Windows Server 2016

Enhancements in Update 5

Enhancements in Options:

Changes in the Options Dialog – Addition of BOM Manager Settings 

The BOM Manager Settings are added to the Options dialog. 
BOM Manager Settings are utilized in the BOM Manager and Properties Control and need to be configured by administrators before users proceed with the project. 
BOM Settings similar to other System Options is controlled by Command Protection, so some users might not have access to the BOM Manager Settings.

BOM Settings:

Variables used in the BOM Settings are defined in default.UserOptions.xml 
(in the out of the box installation this file is located at C:\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\Promise ANSI-IEEE Example\Standards\Promise\Config\Options


Below is the default (out of the box view) of the BOM Manager Settings

The following mapping values can be defined in the BOM Manager Settings:

  1. Work order Symbol Text Mapping

    The user can specify the name of the symbol text attribute he/she intends to use for a Work Order. 
    By default, Work Order is mapped to a WorkOrder attribute
  2. Document Number Text Mapping 

    The user can specify the name of the symbol text attribute he/she intends to use for a BOM document number. 
  3. Revision Symbol Text Mapping
    The user can specify the name of the symbol text attribute he/she intends to use for a document revision. 
  4. Missing BOM Document Color
    Set the color that the software should apply to any records in the BOM Manager that are missing a BOM Document number.
  5. Device ID Color
    Set the color that the software should apply to any records in the BOM Manager that represent device IDs.
  6. Nameplate Text Color
    Set the color that the software should apply to the nameplate text fields in the BOM Manager.

Parts Settings:

Parts setting section is used to define parts attributes mapping:

Non Coded Part Field - This setting determines which parts database field is used to identify a part as being a non-coded part.  Obsolete Part Field- This setting determines which parts database field is used to identify a part as being obsolete.
Those attributes are used to define whether parts will be sent to the procurement system (SAP for example)
Parts Records data Source is used to determine whether the BOM Manager obtains a part record field from the parts database or from the instance stored in the project database.

In the next section, the internal predefined fields are mapped to equivalent fields in either parts database or project database

Nameplate Settings:

Nameplate Settings is used to define whether the item is a nameplate. 
By default, nameplate designation is mapped to User 31. 

Users can also define attributes for the nameplate. By default, the nameplate has 6 lines and mounting definition.  

Submission Setting

This section is used by the administrator to define the settings for the BOM submission.
The administrator will define the URL where the BOM payload will be submitted. 
The Local Test settings are used for the local testing purposes only (should b set to False when submitting payload to the third party application.   

Once the user is ready to submit the BOM to the third-party application, the user will be using the “Submit” option that uses the URL settings, user name, and password from the Submission Settings dialog.


Lifecycle Manager Settings:

Work Order Settings

This section is used to define settings for the work order and custom text attributes:

Once the "Enable third-party application" option is selected, further options become available.



Available options are: active project database server connection or other database connection. 
In the out of the box environment, Active Project database option is enabled and database SubstationDataExchange and table work order are selected. 

When a work order is imported or a new one manually created, mapped data is used to define the work order attributes



Custom Attributes

This section is used to define attributes used in the Property Control


In the attributes value section, values for each attribute can be defined.

The custom attributes defined in this section are available as selections in the Properties Control dialog.



Changes in the Default.SystemOptions.xml


New variables are added to the Default.SystemOptions.xml in the previous release (update 4). In this update, an additional explanations (comments) for those new variables are added. 


Productivity Enhancements:

Enhancing Symbol Text Import to use Excel

The current Replace Symbol Text function is working with text files only. This is now enhanced to import text from Excel files. 

Enable page copy between separate project databases

In addition to copying pages between projects that reside in the same database, Pages can now be copied between multiple databases, as long as both databases are on the same SQL server.

Performance Improvements:

Users can expect to see across the board improved performance when working with Promis.e. This was accomplished by improving the software logic and optimizing database queries.

A separate project text settings for part numbers

Part numbers setting is added to the Standards> Text Settings

Ballooning Enhancements:

Remove limitation for an only single set of Balloons allowed per part number per page

Users can now assign multiple balloons for the same part number. The typical use case is in construction drawings, a different balloon can be used for different views of the same symbol.  


Balloon attributes can be embedded into symbols during symbol creation.

Symbol creation option now has an option to define Balloon Number Attributes

Users can define the number of ballons to be placed (if multiple part numbers are associated with symbol)

Using a Place option, position for all ballons can be defined 
(“x” in icon field indicates that the balloon has been placed)

Once balloon number attributes are added, and the part numbers defined for the symbol, balloons will be automatically placed at the locations defined during symbol creation 

BOM Manager Enhancements:

When creating New BOM Document, User has the ability to Select the Work Order to associate the new BOM Document

When the new BOM Document is created in BOM Manager

User has the ability to select the work order to associate the BOM Document with (current work order is selected by default)

Users can also search for the work order

Users can also create a new work order or import work order to associate BOM Document with

Properties Control now has a combo box for mapped BOM Document and Revision Attributes. This allows user to select an existing BOM Document or type one in

In the Lifecycle Manager Settings, users can define control type for each Symbol Attribute.

BOM Number and Revision Number are defined as a Combobox. This means that the user can select from the values that are already available in the project or type in a new value.

Spare” Item Numbers (Balloons) – are not sent to SAP

All Spare items are classified with the  “SPARE” in the Long Description field which is mapped to BMData user1 field.

BOM Manager Sample view:

Since they are Non-Coded parts, the value is stored in BMData.

DBData Sample View:


All items on BOM Document being submitted which contain “SPARE” in "bmdata.user1" field will not be submitted to SAP and they will be excluded from the automatic validations that are excluded as a result of the user clicking the Submit button.

If the user manually creates a work order,  the following message will appear: "You are about to create a work order that might not exist in SAP"

If the user is manually adding a work order using the work order manager, the following message will be displayed.



Mounting Location symbol text field is added to default.SystemOptions.xml and Multi_Language_UI.mdb for nameplate symbol text mapping

The purpose of this backlog item is to add additional attributes that are commonly found in the customer’s standard configuration.





Nameplate view within BOM Manager:
(The Nameplate view in BOM Manager is shown below) 



Configuration settings are added to allow administrators to define preset selections for Nameplate Mounting Attribute using a picklist control

Configuration for Nameplate Mounting Pick List can be set in System Options Setting: LCM>Custom Attributes.

Example Configuration:


Expected Result of Nameplate Mount Attribute Field in BOM Manager:


When the user selects one of the options from the picklist, the corresponding "Value Name" value will be written to either dbo.symbolAttribute table (If the selected device has placed symbol) or dbo.ParentDeviceAttribute table (If selected Device Does Not Have Symbol Placed).


Example result using Above Configuration for MountingLocation attribute:

If the user selects "Back Only" from picklist AND there is a symbol placed in a page for the device, dbo.SymbolAttribute record will look like this:

ProjectWise Enhancements:

[PW] Create a user-specific default project folder

The purpose of this backlog item is to allow the user to customize the name of a default project folder and enable each user to access his own default project folder and ECAD.DGN

To accomplish this, a new variable ELEC_PW_DEFAULTFOLDERNAME is added to

C:\Program Files\Bentley\Promise CONNECT Edition\Promise\config\appl\Promise.cfg


ELEC_PW_DEFAULTFOLDERNAME  will set the default project folder name and will be used while opening Ecad.dgn from the respective folder.


"DefaultProject" is any user-defined name. After this change, OpenUtilities Substation will access ECAD.DGN file using the following logic:

PW datasource name + documents + "DefaultProject"[value defined by user] + ECAD.dgn

The administrator will have to create the DefaultProject folder manually, and place ECAD.dgn and Substation.cfg under that folder.


Performance Improvements in ProjectWise Environment

Users can expect to see an overall performance improvement when working in the ProjectWise environment. More noticeable improvements are made in the following areas:

Project Manager refreshing 

Performance is improved for Project Manager refreshing after switching projects  in ProjectWise cloud environment

File Opening

Performance is improved for opening Openutilities Substation files from ProjectWise environment 

Command Protection Enhancements:

Add Submit to SAP Function to Command protection – the purpose is to provide the ability to define user group/permission with access to submit a BOM to SAP

Command protection now includes Submit to SAP function as part of Project Management settings:


Configure Database, Configuration Variables, and Configuration Assignment Utility are added into command protection 

New Configuration options: Configure Database, Configuration variables, and Configuration Assignment Utility are now added to the command protection: