Promis.e Readme

New and Changed in Promis.e CONNECT Edition Update 12

The following items summarize the new features and enhancements in the Promis.e CONNECT Edition Update 12 release:

  • Add a label rotation option to allow user to place balloon text rotated.

    Users are able to choose the label rotation Horizontal or Vertical to place balloon.

  • Add ability to select multiple pages in Project Manager and send them directly to Print Organizer.

    Users are able to sort or filter pages according to custom page attributes in Project Manager, then choose one or more pages and select the Send Pages to Print button from right-click menu to open Print Organizer dialog.

  • Add ability to prompt the warning message about some page files missing from project folder.

    Users execute the commands such as rebuild project database, backup project and restore project.

    • If one or more DGN files were missing from the project folder, the software will prompt the warning message like below.
    • It is able to save log file by clicking the Save Details button in Warning dialog.

    For Auto backup project feature, it will add missing DGN files into AutoBackup.log file.

  • Enhance Read-only permission for ProjectsOptions.xml in ProjectWise integration.

    After setting Read-only access to the ProjectOptions.xml:
    • When user does rename a project, delete a project, modify a project, move to database, move project to file system or archive a project with deleting the project after archived in ProjectWise, the software will prompt that the project is Read-only and you do not have proper permissions to perform this operation, please check permission about ect.fid and ProjectOptions.xml on Project folder.

    • Enable to copy page, renumber page, rename page, delete page, modify page, refresh page, update page and clear up page.
  • [Technology Preview] Would like to abandon using Microsoft Access Database(.mdb) from Multi_Language_UI.mdb and catalog.mdb.
    Provide the conversion tool to generate txt files from Multi_Language_UI.mdb and catalog.mdb.
    • Conversion tool “Mdb2Txt.exe” is in $\Program Files\Bentley\Promise CONNECT Edition\Promise\Assemblies\.

    • Choose path of catalog.mdb file and covert them to .txt files.
      • Symbols.txt
      • Families.txt
      • Macros.txt
      • TitleBlocks.txt
    • Choose path of Multi_Lanaguage_UI.mdb file and covert it to the same named folder.
      • Attributes.txt
      • Dialogs.txt
      • DialogTexts.txt
      • Languages.txt
      • Modes.txt
      • Phrases.txt
    Enable to use txt model for Multi_Language_UI.mdb and Catalog.mdb.
    • Step1: Add two configuration variables “txtMultilanguage = 1” and “txtCatalog = 1” in Workspace setting. Choose one of three files.
      • $\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaceSetup.cfg
      • Or $\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\Promise ANSI-IEEE Example.cfg
      • Or $\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\Promise ANSI-IEEE Example\Standards\Promise\Promise.cfg
    • Step2: Set ELEC_LANGUAGE_DB_PATH = $(AppWorkspaceStandards)Databases/Multi_Language_UI/
      Note: <Make sure it must add “/” in ProjectWise integration >

      • $\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\Promise ANSI-IEEE Example\Standards\Promise\Promise.cfg

    • Step3: Start Promis.e, it will automatically use .txt files for multi_Language_UI and catalogs.
      • Add check for ELEC_LANGUAGE_DB_PATH. If txtMultilanguage = 1, it will check a folder path that should include 6 .txt files. Otherwise, the software will prompt user that the path is invalid or the .txt file is missing. If txtMultilanguage = 0, it will check .mdb file.
      • Add check for ELEC_CATALOG_PATH. If txtCatalog = 1, it will check 4 txt files. If txtCatalog = 0, it will check mdb file.
    ProjectWise management workspace:
    • Catalogs and multi_language_UI.mdb in ProjectWise integration need to be downloaded to local folder, then convert to txt files. System administrator can directly copy “Mdb2Txt.exe” and “MDBProxy.dll” to covert Multi_Language_UI.mdb and catalog.mdb.
    • After conversion, users need to upload all txt files to the same folder as catalog.mdb file. For multi_language_UI, users need to upload the same named folder.
    • Do step1 and step2 above in local, then check them in ProjectWise.
    Change back from txt to mdb:
    • Step1: Set two configuration variables “txtMultilanguage = 0” and “txtCatalog = 0” in Workspace setting.
    • Step2: Set ELEC_LANGUAGE_DB_PATH = $(AppWorkspaceStandards)Databases/Multi_Language_UI.mdb.
    • Ensure catalog.mdb and multi_language_UI.mdb available.
    • Don’t support conversion from txt to mdb. Users need to rebuild catalog.mdb to include what catalogs were added in txt file.
Parent topic: What's New