The Promis.e product team is pleased to announce the availability of Promis.e CONNECT Edition x64 (10.05.00.38) 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:
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.
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
Promis.e Update 5 is now certified to work with SQL Server 2019
Promis.e Update 5 is now certified to work with Windows Server 2016
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:
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 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.
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.
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
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.
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.
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.
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.
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.
Part numbers setting is added to the Standards> Text Settings
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.
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
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
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.
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 is manually adding a work order using the work order manager, the following message will be displayed.
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 for Nameplate Mounting Pick List can be set in System Options Setting: LCM>Custom Attributes.
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:
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.
ELEC_PW_DEFAULTFOLDERNAME = DefaultProject
"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.
Users can expect to see an overall performance improvement when working in the ProjectWise environment. More noticeable improvements are made in the following areas:
Performance is improved for Project Manager refreshing after switching projects in ProjectWise cloud environment
Performance is improved for opening Openutilities Substation files from ProjectWise environment
Command protection now includes Submit to SAP function as part of Project Management settings:
New Configuration options: Configure Database, Configuration variables, and Configuration Assignment Utility are now added to the command protection: