Changes in Archibus V.2022.04

• Online Help

• Web Central
• Workplace
• OnSite mobile app
• Smart Client, Smart Client Extensions for CAD and Revit
• Mobile Client and Mobile Apps
• Database
• System
• Real Property
• Capital Projects
• Sustainability & Risk
• Space
• Maintenance
• Workplace Services

Known Limitations of this Version of:

• Archibus Help
• Archibus SaaS
• Workplace
• OnSite mobile app
• Web Central
• Smart Client
• Smart Client Extension for AutoCAD
• Smart Client Extension for Revit
• Outlook Plugin
• System administration
• Database
• Mobile framework
• Mobile apps
• Workplace Services
• Space
• Maintenance
• Assets
• Leases
• Real Property
• Sustainability & Risk
• Connectors
• Archibus Extensions for BUILDER TM SMS

Changes in Online Help

• Installing Online Help Locally . Previously, users who wished to install the Archibus Help systems locally would obtain zip files containing the Archibus Help systems from the release download section of Allbound. Users requiring these zip files must now request them from Customer Support; they will no longer be available on Allbound. (DOC-2593)

• Archibus Extension for Lease Accounting topics . The Archibus Extension for Lease Accounting product is no longer sold, so we have removed all topics documenting it. If you require the documentation for the Extension for Lease Accounting, you can consult the V.2022.03 online help at https://help.archibus.com/user_en_v2022.03/archibus.htm#../Subsystems/webc/Content/fasb/concepts/overview.htm (DOC-2586)

• Adobe PDF LiveCycle Forms topics . We no longer support creating new views that integrate with Adobe PDF LiveCycle, and references to this integration feature have been removed from the System Management Help. If you require the LiveCycle integration topics, you can access them in Archibus V2022.03 online help at https://help.archibus.com/system_v2022.03/sysman.htm#wc_views/Adv_Views_Techniques/pdf_forms/PDF_forms_introduction.htm . Note that existing views that use this functionality, such as Sustainability & Risk / Health & Safety / Management Reports / Incidents Log , still work and their documentation has not changed. We will assess integration with Adobe Experience Manager Forms (the Adobe offering that replaces Adobe PDF LiveCycle) based on customer feedback in our UserVoice forum. (DOC-2730)

Changes in Web Central

• Data cache errors . We have resolved a problem with views working fine for several days and then at some point generating a "dataSource not found in cache" error. Restarting the Tomcat server would resolve this problem. This situation will no longer occur as we have replaced DataSource cache with Spring cache. (AD-5554)

• BIM Viewer. Sample Data . In the sample HQ project, building HQ no longer loads as a floor plan instead of a model. This occurred because in our Forge account, we had a CAD drawing that was linked to building HQ. (AD-9585)

• BIM Viewer . Now offers Work Request and Maintenance-related highlights such as: Oldest Request, Overdue PM Schedules, Preventive Work for the next 30 days and the next 90 days.

• Catalog BIM Models . Enables from Web Central assigning a new model to an existing building and existing floors if that building and its floors are not yet assigned to any model.

• Report Central . Workflow Rule Error . You no longer receive a workflow rule error when choose rm_id in both the main table and standard table. We have changed Reports Central so that once you choose a table, this table is not available for selecting as the standard table. Similarly, if you choose a field in main table and if same field exists in the standard table, Reports Central does not display it as a selection for the standard table. (AD-8257)

• Report Central . Charts . In order to see more of the chart, you might have attempted to resize the grid panel and found that you could not resize it. In this case, you could hide the filter, and then scroll the region to see the entire chart. This has been resolved and the workaround is not required. (AD-9149)

• User Interface

  • Add borders to dialog boxes when using High Impact theme.

  • Stop truncating user name in favorites task name to the suffix following a period (e.g. COM for emails)

  • Change font to Noto Sans, generally.

  • Improve visibility of scroll bars in some views

• Change interpretation of <field hidden=""> attribute when it evaluates to something other than true or false.

• Correct redirection to logout view when Single Sign-On enabled and session times out.

• Correct errors not finding content when loading some published drawings.

• Improve drag-and-drop functionality for document fields.

• Make localization improvements.

• Improve loading of data sources from related views.

• Improve detection of dependent views when restrictLoadingOfUnassignedViews is set.

Changes in OnSite Mobile App

• Notifications. Time Zones . Notification date/time is now set against mobile device's timezone and work request's location, instead of against the server's timezone and location. (ON-1230)

• Comments . When tagging an employee, you can now see a list of employees by typing "@". In the previous versions, you had to type "@" plus at least one character. (ON-1425).

• Location . You can now turn on/off the current work request's location. (ON-399)

• Usage Analytics . We now support usage analytics so that we can see how users are working with OnSite. We can then use these analytics to improve the user experience. (ON-547).

Changes in Workplace

• iPad Pro. Application Freezes . If you are in the process of using Workplace and close the device screen, Workplace no longer freezes and you can now continue your operation. (AD-9469)

Changes in Smart Client, Smart Client Extensions for AutoCAD and Revit

Changes in Mobile Client and Mobile Apps

• Archibus Mobile 4.0 on iOS 16. We have resolved a problem with compatibility with iOS 16 and disabled appcache. You can now log in to devices running iOS 16. (AD-11542)

• Compliance Surveys mobile app . Instruction Text on Questionnaire Form . We have resolved a problem with the questionnaire forms not showing the instruction text that is defined as part of the questionnaire. You could see this text when running the questionnaire in Web Central. (AD-8574)

Changes in Database

See the following topics in System Management Help: Database Schema Revision History and Upgrade Notes . Also note these changes:

• afm_ptasks table. Missing Translation. The "Configure Application Parameters for CAD and BIM" task is now translated in all languages. The translation was missing in V.2022.03. (AD-10583)
  

• afm_ptasks table. Missing Chinese Translation . The "Define Owner's Requirements with Building Occupant" task is now translated for Chinese. The translation was missing in V.2022.03. (AD-10582)

Changes in System

Changes in Space

• View and Print Floor Plan . With an Oracle database, loading the building list no longer takes over a minute to load. (AD-10426)

• View and Print Floor Plan . Highlight Legends When you export highlighted floor plans to PDF, the legend now includes the fields that correspond to the highlight, such as Room Category, Room Type, Room Standard, Division Name, and Department Name. (AD-11277)

• Space Console. Export Drawing to PDF. Drawing Units of mm . The unit is scaled from MM to M during publishing to ensure the PDF drawing can print successfully. Previously, if you were using mm as units in your drawing and you tried to export to PDF, you would run out of memory. (AD-8717)

Changes in Real Property

• Lease Profile. Parent Lease . Previously, if you assigned a child lease to a parent lease using the Lease Profile view and then attempted to edit the parent lease, you could not access it to edit it and received an error message. This has been resolved. (AD-10773)

Changes in Capital Projects

Changes in Sustainability & Risk

Changes in Maintenance

• Maintenance Console. Report Problem Button . If the restrictLoadingOfUnassignedViews property is set to true in \ web-inf\config\security.properties, a user with access to the Maintenance Console is no longer prevented from using the Report Problem button. (AD-8377)

• Maintenance Console. Priority Label . We have fixed a problem that the Priority Label was not shown if Priority Number was not 1 through 5. (AD-10964)

• Maintenance Console. Side Filter . We have fixed a problem with the display of the side filter. (AD-10049)

• Maintenance Survey Report. Checklists . The answers to checklists are now displayed for closed work requests. (AD-11320)

Changes in Workplace Services

Archibus Help known limitations

• Non-English help from the Navigator . If you use the right-click Help command on a Navigator process, you will receive an error message that the topic cannot be found. This is because the localized version of Archibus Help does not contain topics at this level of detail. In a future release, the right-click Help command will load the appropriate topic from the English version of Archibus Help. (AD-2786)

Archibus SaaS known limitations

• Home Page Publishing . SaaS Partner Administrator . If you sign in as a SaaS Partner Administrator (such as sample user AFM-BP), run the System / SaaS Partner Administrator / Manage Home Pages and Processes task, modify a home page, and publish your changes; you receive an error message. As a workaround: use System / Add-In Manager / Publish Home Pages by Role to publish home pages after modifying them. (APP-6426)

OnSite mobile app known limitations

• Android. Accessing Documents . If you attempt to open a DOCX file linked to a work request on an Android phone, you receive an error message. This is a result of the phone not having an app to open DOCX files. You can install an app for this purpose. (ON-1495)

• Android . Editing comments . If you have use Settings/Display to set enlarged text and enlarged fonts, the edit icon (three dots) for comments does not display. (ON-1528)

• VPA . Reference Documents . There is inconsistent behavior between OnSite and the Maintenance Console concerning reference documents and VPA. When there are reference documents that match the VPA setting, OnSite lists the documents, whereas the Maintenance Console hides the References tab and does not list the documents. (ON-1491)

• Notifications. Chinese . Push notifications are not yet supported for Chinese. (ON-1058)

• Notifications. Oracle. With an Oracle deployment, you cannot receive notification from OnSite; if you check the Web Central Notifications Log view, you will not see any messages sent from OnSite. (ON-1237)

• New requests. Cannot See. After you create a new request, you may not see it in the Request List because it is added to the end of the request list. You can use the pull-to-refresh feature to re-sort the requests according to the “order by” option. (ON-487)

• Work Request List . Updating . When you create a new request, it is added to the bottom of the list because the sort order of work requests is not updating to reflect a new request. Pulling to refresh solves this issue. (ON-723)

Workplace known limitations

• Service Catalog. Accessibility Mode . If Accessibility Mode is enabled, the .. archibus/schema/ab-products/essential/workplace/index.html?action=servicecatalog URL displays the pre-V2022.02 Service Catalog view and does not display the Dashboard, as is the behavior for V2022.02 and beyond without Accessibility Mode. (AD-8901)

• Employee Move Request . When you create an employee move request from Workplace and then view the request in Web Central (View Service Request task), you may find that there is incorrect or missing data. (AD-10440)

• iPad Pro. People & Places. UI. The email address in the right panel is not properly displayed. (AD-9466)

• Maintenance Requests. Comments . If a work request has a very large file attached, you cannot save a comment that you enter. This happens only for work requests with large file attachments. (AD-11360)

Web Central known limitations

• Export to XLS. Restriction . If a restriction is in effect and you use the view's Export to XLS command, when you open the Excel file you will find that the restriction message blocks the exported records and you will not be able to see all the fields. Manually adjust the format of the Excel file to see all the content. (DOC- 2749, AD-11606)

• Signing Back in After a Time Out . If your session expires and you sign back in, when you click anything on the Navigator, you will receive an error message. The workaround is to refresh the browser page. (AD-10570, AD-10602)

• BIM Viewer. Non-English Versions of Revit . The BIM Viewer can only work with models saved on English version of Revit. (AD-11279)

• BIM Viewer . Localized . In localized versions of Archibus, you will find that the tooltips on the Autodesk Forge toolbar are not localized. (AD-12210)

• Images. Firefox . When images have a larger vertical size than horizontal size (a portrait image), they may appear distorted on Firefox. This is not an issue for other Web browsers. (AD-7140)

• Select Values. Floors . For view 2.0 views that have a filter that includes the Floor Code field, the view may not show all available floors. The root cause is that the core UI grid control determines the number of pages based on the number of index records. For the Floor selector, the index uses the Building Code, i.e. there are 111 buildings with floors. Thus, the grid shows only two pages of floor records (one page = 100 records). (AD-3706)

• Menu options hidden . When a view title is too long, the top menu actions (User Menu, User Help, Add to Favorites) and client logo are not visible. (AD-4820)

• Navigator. Non-English Locale . If you launch Web Central from the Smart Client and are using a non-English locale, the Web Central Navigator will not display your applications and tasks. (AD-3866)
• Polish characters in V.25.x and later user interface . With the V.25.1 user interface refresh, special characters in UI titles translated to Polish do not appear like the other characters. For customers who have this issue, we recommend modifying all CSS files in the \schema\ab-core\views\navigator folder to replace this line: font-family: "Open Sans";
  with this line: font-family: "Open Sans", Arial; (AD-2292)
  
• Questionnaires. Non-English . Questionnaires, such as those in Condition Assessment and Sustainability Assessment, do not allow assessors to edit out-of-the-box, sample questions that have been localized from English (US) to other languages. The workaround is for Archibus Administrators to use Archibus Smart Client to edit the text of these sample questions. This issue affects only sample data questionnaires that have been localized from English. (AD-1547)

• Extended Questionnaires . Document/Photo . The Web Central questionnaire form (for both Compliance and Maintenance) does not currently support respondent-initiated submission of more than one document/photo attachment per question, whether or not the questionnaire designer specifies a value greater than 1 for Maximum Number Responses. The mobile app does support this feature. You cannot delete the uploaded document after Save the question-answer; there is no action when clicking the X button. A questionnaire designer should take this into account when designing forms. ( APP-2426, AD-4431 )

  • If the intended respondents will be using Web Central to submit documents and flexibility in number of document responses is desired, then the designer can work around the limitation by defining a parent question containing a follow-up question of type document and allow multiple instances of the parent question.

  • For example, parent question could be multiple choice "attach a document?" Yes/No. If Yes, then the application shows the document question as a follow-up. Set up the "Attach a document" question to allow multiple answers, such that the respondent can add another, answer "Yes" and so on.

• Home Page Editor. Maps . When creating home pages, you add only one map bucket to each home page. (WC-2790)
• Home Pages. Localized. For some international users, home pages may display English titles for columns in the Metric Trends panel. If this issue occurs, the user can switch to a different home page and go back, or sign out and sign in again. (WC-2373)

• Grid. Highlight ACAD Pattern (Swatch) fields . If working with a view in which you define highlight patterns (such as Space / Space Inventory / Background Data / Define Division and Department Highlight Patterns , ab-sp-create-dp-hatch.axvw), and you set a gradient highlight, create a swatch bitmap, and refresh the view, the Highlight ACAD Pattern (Swatch) field will not correctly show the swatch bitmap for the gradient highlight. Instead, the fields show the same color for all gradient highlight definitions. (WC-2748)
• Grid 3.0 . Grid Control 3.0, which is used in views such as PM Planner (ab-pm-planner.axvw) and Service Console (ab-request-console.axvw), presents an error if you try to sort by a field that is not from the main table. (AD-8474)
• Schema Change Wizard. Oracle . When using Schema Change Wizard on an Oracle database, you may face the error ORA-01031: insufficient privileges when choosing to re-create any of the Archibus security tables: afm_users; afm_groups. Resolution: Choose "Alter existing table structures (preserves additional fields)" option when trying to update afm_users/afm_groups tables. (3045736)

Smart Client known limitations

• Navigator . With a non-SaaS license, logging in to the Smart Client as AFM incorrectly produces a Navigator that includes an Archibus SaaS process. (AD-3794)

• SAML. Connecting to SAML requires user to make server selection on subsequent sign-ins. (AD-1996)

• Certificate Authentication. Web Central tasks . Cannot data transfer or launch Web Central if Certificate Authentication is in effect. (SMAR-626)

• Editing standards tables. If you edit Furniture Standards or Equipment Standards with the default database, the titles for the Length and Width fields will show incorrectly as "ft" or "M". If you log in with a different locale (e.g. view an Imperial project as a Metric user) the program will convert the values. The condition also occurs in Furniture or Equipment Standards views loaded in Web Central. To avoid this condition in both environments, load the Archibus Fields table (afm_flds), find the Length and Width fields, and change their Numeric Format from "Length" to "Default". ( 3037311)

• Deleting a record with a date/time field as part of its primary key . You are unable to delete records from tables that have a date/time field as part of the primary key, such as the ehs_medical_mon_results table. There are no such errors when deleting records from the same table in Web Central views. (WC-2169)

• Deleting. hwr and hwo tables . It is not possible to delete records from Smart Client grid views that present these tables. As a work-around, delete the records from Web Central. (SMAR-596)

• Deleting . Bulk Editing . Currently there is no way of bulk deleting data from Smart Client. If you select all records and then hit Delete, only those records currently displayed on screen are deleted; all of the other records that are selected but not on screen remain. As a work-around, in View Definition Wizard, create a single panel interactive report for the table in question, choose only the primary key field(s) unless you need to add a restriction. In the preview pane, enable advanced editing, and add multipleSelectionEnabled=”true” in the panel, then insert a panel action with a command type deleteSeletedRows . Save Changes and preview the view and you can check all and delete right from the preview, without needing to save/publish it. (SMAR-17)
• Ribbon . The Smart Client ribbon is very small on high resolution monitors. (SMAR-503)
• Grid. Refresh when filtering. After you set and clear a filter, the grid does not correctly update record counts and refresh. As a workaround, run the Clear action on the menu ribbon. (SMAR-609)

• Replace Column . When there are more than two tables in the standard role attached to the Smart Client grid view, the command presents errors. (SMAR-528)

• Modified views cannot be saved as default view. Log in as a user that has the Security group SYS-VIEW-ALTER (such as AFMX), open a view, change the view, save, and make it the default view. Reload, and the default view will not reflect your changes. (SMAR-329)
• Explorer pane. Recent Views list . When you create new views and save them in the Explorer's list of recent views, you can save up to 8 views. When you save the ninth view, the system removes the newest view from the list. It should remove the oldest view from the list. (SMAR-907)

• Data Transfer. Dates deleted from the output file are not cleared in the database after transferring in the file with the changes made. (SMAR-671)

Smart Client Extension for AutoCAD known limitations

• Installer . The installer does not enable Smart Client Extensions for Revit and AutoCAD. This was found to occur on AutoCAD 2023 and Revit 2022. The workaround is to enable the Smart Client Extensions for AutoCAD or Revit by loading the Smart Client, accessing the Preferences command, and setting the CAD Application and AutoCAD Profile options. (AD-10759)

• Insert Asset . The Insert Asset logic doesn’t take into account the AssetTypeDetail.ParameterUnits value when inserting the asset. Therefore, in a drawing with Imperial/Architectural units, running the Insert Asset command on the RM layer inserts the asset in inches rather than feet. (AD-7470)

• Query Table . The Query Table command does not include fields that contribute to the primary key; for example, it does not show the Building Code and Floor Code values for rooms. (SMAR- 798)
• Highlighting commands
  • Unclosed polylines. If some areas don't highlight with solid highlights, they might be open not closed polylines. If so, close them. The AutoCAD solids don't fill unclosed-closed polylines. AutoCAD hatch patterns do, however. Notice that if you have multiple areas of one type (e.g. Office standard), having one unclosed polyline may cause others to also not have a solid fill (since Archibus hatches many of them in one go for efficiency's sake). ( 3030818 )
  • Hatch patterns. The Archibus-defined patterns (from the .pat file) are not being loaded into AutoCAD at the time of highlighting. Only the out-of-the-box AutoCAD patterns work as expected because the highlighting logic defaults to a SOLID hatch pattern if it can't find the pattern definition. (SMAR-902)
• Large floor plans. When dealing with very large floor plans (3,500 rooms on a single floor), commands like Catalog Layer and Highlight by Department do not give progress feedback, but function correctly.
• Asset Text Height . The Smart Client Extension ignores the atxt_ht_in and atxt_ht_cm in favor of the atxt_ht value, which is in inches. For metric drawings the SCE converts this to cm. (SMAR-189)
• Edit Data. Suite areas. If you use Edit Data on suite areas, and if you use Select Values to select an existing suite, the area in the form shows temporarily as 0. If you press OK, the correct area is recorded and appears correctly on subsequent invocations of the command. ( 3035340, 3034959 )
• Trial layers. Asset text . Asset text is left-justified instead of center-justified. (SMAR-492)
• Explorer window. Anchoring . When you open a drawing from within the Smart Client drawings list, the Explorer window should be positioned according to the settings made in the previous session; instead, it opens in the floating position and you must reset it. (SMAR-702)
• Drawing Publishing
  • AutoCAD Leader objects. EMF does not support arrows or text with the leaders. SVG supports only solid arrows. (3044919)
  • Secondary circulation areas as regions . As documented in https://www.archibus.net/ai/abizfiles/v23_help/archibus_help/user_en/archibus.htm#../Subsystems/webc/Content/web_user/space/concepts/open_plan.htm , you can draw accurate polylines for secondary circulation using AutoCAD REGIONS. Publishing these drawings may result in rooms being set incorrectly in front of or behind other rooms. In order for rooms within a secondary circulation region to be shown and highlighted in front of the secondary circulation space in a published drawing, they must be numbered higher than the secondary circulation space. (3051186)
  • XREF The XREF Layer does not publish when the TURNOFFALL* value is specified in the additional layers field. As a workaround, turn off layers individually and do not use the TURNOFFALL* feature to control XREF Layers. (SMAR-1001)
  • AFM_NET_LISP "Publish " command . Ignores the viewWindow attribute when the publishType is EMF and the generated file is published to extents. (SMAR-737) .
  • SVG. Background Color . If you set the Set the ColorMapping field to BLACK for AbPubBackground in the sample HQ database and publish, the black background does not appear to take effect. This is because there are multiple active rules in the database, and later results overwrite the earlier ones. To resolve this either (a) set the Active flag to No for all of the SVG files except for one; or, (b) specify a unique Rule Suffix (e.g. -bl, -reg, -eq) for each rule, except for the one that has a Color Mapping value so that different rules will produce different output files. (SMAR-417)
  • SVG. Hatches . Complex hatches, meaning that there are multiple polylines that are used as the boundaries for the hatch, do not publish to SVG; whereas hatches that do successfully publish are contained in a single polyline. You can separate the hatches using HATCHEDIT, and the publishing will work as expected. (SMAR-513)
  • Refreshing. Firefox. If your workstation uses Firefox and you load a drawing's enterprise graphics in Web Central or in the Smart Client, then republish that drawing's enterprise graphics, the change may not appear when you reload the view with the enterprise graphics. For performance reasons, some versions of Firefox do not immediately refresh the enterprise graphics files from their local cache even when the file has a later time stamp, as checking the time stamp involves an extra query to the server for each file. To view your changes, clear your cache or restart your browser. If you wish to see changes immediately without clearing your cache, you can change your browser cache settings to control the problem.
    1. In Firefox's menu, select Tools > Options.
    2. Select the Advanced tab, and then the Network tab.
    3. In the Offline Storage section, enter 0 for the MB of space used for the cache. (3024655 )

Smart Client Extension for Revit known limitations

• Installer . The installer does not enable Smart Client Extensions for Revit and AutoCAD. This was found to occur on AutoCAD 2023 and Revit 2022. The workaround is to enable the Smart Client Extensions for AutoCAD or Revit by loading the Smart Client, accessing the Preferences command, and setting the CAD Application and AutoCAD Profile options. (AD-10759)

• Uncatalog . With Revit 2022 running on Windows 11, you cannot select Asset Type on the Uncatalog form. (AD-10027)

• File names with special characters . When you publish a Revit file whose file name contains spaces and characters such as #+°$(), you may receive an error message when viewing the SVG file in Web Central. (WC-3132)

• Names of models and levels. Currently, the Smart Client Extension for Revit does not support model names or level names containing the '-' character. (AD-9418)

• Opening a model. Error message . Due to the way that Updater classes are implemented, Revit presents a message that you are missing a third-party updater. You can ignore this message. (SMAR-974).
• Number.
  • If you Number a room and then use the Smart Client to show the Room field "Perimeter ft”, the perimeter shows as 0. If you Data Edit or Data Edit Multiple, the number is corrected. (SMAR-285)
  • If the database does not contain enough information for the Number command to execute, it fails to number instead of providing feedback to the user about what database information is needed to successfully run the command. (SMAR-526)
• Deleting rooms. Revit does not notify Archibus when Revit deletes rooms. Currently, Archibus cannot uncatalog rooms on that event. Use the Synchronization / Uncatalog Records without Assets command to clear the Drawing Name and Id fields on these rooms in one step.
• Web Query. If the last primary key value for an asset is a single digit (e.g. if you query for room "1"), then the pop up dialog results are not restricted to that one record. This doesn't occur for two- and three-digit IDs (e.g. room "10" or "100"). ( 3035367, 3035366, 3034950, 3034414 )

• Publish Enterprise Graphics. Colors . Since Revit floor plans do not have color, colors for Enterprise Graphics generated from Revit can cause confusion, especially since the user does not have control over this. In a future release, Archibus will address this issue. (SMAR-988)

• Edit Data
  • Rooms . Some objects in linked models are not correctly picking up room codes of the rooms they are inside of. (SMAR-785)
  • Group Areas. For new groups, the Group Code will show as "1" until the record is actually saved. Thereafter, the proper autonumbered ID will show. ( 3034828 )
  • Suite Areas. If you use Edit Data on suite areas, and if you use Select Values to select an existing suite, the area in the form shows temporarily as 0. If you press OK, the correct area is recorded and appears correctly on subsequent invocations of the command. ( 3035340, 3034959 )
  • Long parameter values. If you have a parameter value (e.g. Name) mapped to an Archibus field (e.g. Option 1), and that parameter has an existing value longer than the field width in Archibus, then you will not be able to create a record using Edit Data. You can shorten the parameter value using the Revit Parameters dialog. Alternately, if you use the Archibus Catalog command, the command will find all of these conditions and allow you to rectify them individually or in groups. ( 3034793)

• Map Database Fields. This form is empty if there are no assets in the model of the specified asset type. (3034357)
• Copy / Paste. If you copy and paste furniture and equipment, you also copy and paste their Revit properties. Use the Archibus synchronization commands to find and resolve any duplicates. ( 3030989 )

Outlook Plugin known limitations

• Registry Entry to Keep Enabled. To ensure the Plugin cannot be disabled by users and will not be disabled automatically by Outlook, you must replace the following DWORD registry value (which is added by the standard installer)

  [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\x.0\Outlook\Resiliency\AddinList] "ArchibusOutlookPlugin"=dword:1

  with a string value.

  [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\x.0\Outlook\Resiliency\AddinList]
  "ArchibusOutlookPlugin"="1"

  This replacement can be implemented by customizing the Outlook Plugin MSI installer with a customization tool such as Master Packager. (AD-10391)

System Administration known limitations

• BMS Integration . The Technologies / Innovative Solutions / Integrations - BMS / Configure BMS Analysis (ab-iot-bms-configure-analysis.axvw) view has an "add new" option which is not functioning. (AD-7901)

• Security. LDAP. The result of using a distinguished name with a comma results in this error in archibus.log: "LDAP: error code 49 - Invalid Credentials". The solution is to change the bind user's "CN=" value to a name that does not contain a comma. (3037258)
• Security . SSO . In SSO mode, when the user name is incorrect, the user is redirected to the timeout page instead of the SSO error page. (WC-2027)

• Solution Templates. IofT . The Technologies / Innovative Solutions /Integrations - IoT / IoT Space Utilization solution template is not Oracle-compatible. (AD-8296)

• Solution Templates. Calendar Control . The Reservations Calendar example records multiple days for one-day events. (WC-3237)

• ConnectListener . When ConnectListener runs, it does not move the previous afm_conn_log entries to afm_conn_logh. ( AD-7003)

• Schema Change Wizard. The archibus.log fails to show correctly field and table name in the global dataset. This is only a logging issue. There is no functional error. ( 3033565 )

• Grid. API. Grid panels can display custom values calculated in Java Script code. An example can be seen in the following view. This example displays the custom Location field that is composed from Building, Floor, Room, and Location database fields. The example also includes a menu that allows the user to produce reports with the grid data. Due to Web Central technical implementation limitation, custom values formatted in Java Script code cannot be displayed in these reports. (3041685)
  • Path: Technologies / User Interface Add-Ins / Assemblies with Multiple Panels / Find-Manage with Categories
  • File: ab-products\solutions\assemblies\work-wizard\ab-ex-work-wizard.js
  • Function: updateLocations()
    
• Grid. API. When designing views with a grid panel, you cannot set specific grid column width in pixels. The grid automatically sets column widths according to the available space and the data displayed in each column. (3045398)
• Grid. API. The Clear Filter icon is not visible if the last grid column is hidden. To avoid the issue, add an empty last column. The condition does not affect any of the Archibus applications. (3040363)

Database known limitations

• Database Update Wizard. runDuw.sql script. The Database Update Wizard generates an SQL script called runDuw.sql. When writing this file, it does not replace macros with SQL. (AD-10595)

Mobile Framework known limitations

• Fail to log in again when reloading mobile client. iOS. If you log in, close mobile client, and then attempt to log in again, you will find that you cannot log in. The failure stems from being already logged into the OIDC connector and trying to reestablish a session. IOS has not been fully upgraded for service workers due to extra restrictions service workers have in IOS Safari. Therefore IOS still requires the connection checks. A workaround is to wait until the OIDC session is invalid/logged out, as well as not selecting "remember me" (for example in Okta) while on IOS. Not closing the app while there is a valid session will avoid this issue entirely. This is not an issue for Android. (AD-6517)

• Surveys. Measurement questions. Android . With the survey (questionnaire) features in both Maintenance and Compliance Surveys mobile apps, users can enter non-numeric values for Measurement questions. These values do not correctly upload when the mobile apps are synced. A future version will add validation so that users can input only numbers as the answer of Measurement type questions. (AD-4600)

Mobile App known limitations

• Compliance Surveys. Questionnaires. If a questionnaire requires a service request and the service request is created and then deleted, the questionnaire will still indicate the service request step is complete. (AD-9047)

• Maintenance. Resources . If you add resources, such as parts, tools, and costs, you will not see the new resource records in both Resource Details form. Thus, you might think the resource records were not added. After syncing, you will see that the resource record were successfully added. (AD-5908)

• Maintenance . uniqueidentifier Error . Due to Archibus resetting an application parameter for use with OnSite, users of the Maintenance mobile app will encounter the "uniqueidentifier property to be defined" error after completing a checklist or refreshing the screen. To resolve this, run System / Archibus Administrator - Application Configuration / Configure Application Parameters and reset the AbCommonResources. MobileSyncDataChangesOnlyTable s application parameter to: bl;eq;rm;rmpct;dv;dp;fl;em;pt_store_loc_pt . (AD-11666, AD-11679)

• Maintenance. Checklists. Android 11 . If you try to create a request from a work request's checklist, you receive a blank screen. This occurs only on Android 11. (AD-5863)
• Maintenance. Stopping Work . Supervisors cannot stop a work request that has a pending checklist. (AD-4883)
• Maintenance. Reopening a Checklist when Verifying It . If a supervisor reopens a checklist during the verify process, the work request correctly moves back to the Issued status. If this work request's checklist is still pending and the supervisor or craftsperson now selects multiple work requests to complete (including this one), you will find that you can complete this work request despite the fact that it has an open checklist. The issue does not occur when working from the My Work form because the form does not support multi-select action. (AD-4882)
• Maintenance. Confirmation. SLAs can contain Confirmation steps on the "Issued" and "Completed" statuses. Users who are assigned to these steps can perform the confirmation (Approve/Reject/Cancel) in the Maintenance Console, but this feature is not supported in the mobile Maintenance app. Confirmation steps work only on the "Requested" and "Assigned to Work Order" statuses on mobile. (AD-7267)
• Maintenance. Sync Issues .
  • When a user performs a Sync action on the mobile Maintenance app, any craftspersons hours data (such as Actual Hours or Overtime Hours) can be overwritten if those hours were entered in Web Central. (3045897)
  • When a requestor reports multiple maintenance requests of the same type from different locations and then syncs to upload all the requests at once, the mobile app does not consistently upload all the requests. To avoid this problem, sync after entering each request. (3048805) .

  • Part quantities are synced on the mobile Maintenance app only when you sync the background data. This affects mobile users who perform any of the following actions on the mobile maintenance application:
    o Estimate parts on a work request
    o Add purchased parts to inventory
    o Complete a work request that includes parts
    After you perform any of these actions and sync, the system will update the part quantities correctly in the database and they will appear correctly in Web Central; however, the mobile application will not show these new quantities. Also, any changes made by other mobile users or Web Central users to the part quantities will not be synced. The workaround is to go the Sync settings on the mobile application and click the button that says “Reset Background Data Sync Flag”. When you return to the Maintenance application, the background data will automatically sync, and the part quantities will be updated on the device. (3053237)
    

• Maintenance. Seeing Rejected Requests. Approvers can reject requests back to the requestor or step completer. However, mobile users cannot see or resubmit those rejected requests from the mobile application. This must be done from the Building Operations Console. (3048370)
• Maintenance. Photos. You can request maintenance from the Workplace Services Portal app and the Maintenance app, and you can update maintenance requests from the Maintenance app. However, the two apps store maintenance photos in different tables (wr and activity_log), which can cause problems when editing or deleting a photo. When you request maintenance using the Workplace Services Portal app and add a photo, and then access the corresponding work request using the Maintenance app, the photo will be shown. However, if later the photo is deleted by the Maintenance team from the work request (wr) record, the photo will not be deleted from the activity_log record, and vice versa. There are several alternative scenarios for adding, changing, or deleting photos which may cause this kind of issue. This issue will be fixed in a future release. (3047423)
• Workplace Portal. Chinese . If you enter a space after a Building Code value, you will encounter an error with Rooms / Locate Employee. (AD-5913)

Workplace Services known limitations

Space known limitations

• View and Print Floor Plan . If Room Category and Room Type have the same value, only value is displayed in the drawing. (AD-10178)

• Space Console. Bulk editing rooms . If you select from the floor plan more than 10 rooms and attempt to bulk-edit them, the form may not display all the fields and buttons making it difficult or impossible to edit the selected rooms. When editing rooms in bulk, edit fewer than 10 rooms at one time. (AD-2711)

• Space Console. Generate Ad Hoc PDF. Large Drawings . For large drawings, such as one with an SVG size of 5590K, the report may not generate. In these cases, increase the memory, such as increasing the Tomcat memory to 2048 M. (AD-2048)
• Space Console . Employees tab . Selecting Employees . If you have a list of employees that runs over multiple pages, when you select employees and then move to "Next" or "Previous" page, the selection will be cleared. As a workaround, you can first use the "Place Employee in Waiting Room" or "Unassign" action for the selected employees on the current page, and then move to a different page to select additional employees. (AD-2741)
• Space Console. Team Space . Organization Name field . When assigning associations to teams, you will see that the Associations tab includes the Organization Name field. This is validated by the Organizational Units (org) table. To create the values for the Organizational Units table so that they are available when completing the Organization Name field, you must use the Smart Client. Create a new view that holds the org table and use this view to define your organizational units. (3052882)
• Space Console. Plan Types. Using Plan Types on the Space Console affords the user the ability to personalize highlights, text labels, and printed legends to the deployment's needs, in addition to the pre-existing highlights and label options that exist on the Space Console's drop-down menus. The Add-In Manager defines Plan Type highlights and labels by creating or modifying view files and datasources that are logged in the active_plantypes table. However, to make changes or add legend datasources, in addition to defining those datasources in the view file that active_plantypes references, the Add-In manager must:
  1. Make an associated change in the same view file for a highlight datasource, and name it as the legend is named. For example, if the Add-In Manager makes a legend datasource named "ds_ab-sp-hl-rm-by-dp-name_rmLegend", they must also make an associated highlight datasource named "ds_ab-sp-hl-rm-by-dp-name_rmHighlight".
  2. In the PDF export AXVW file ab-sp-console-export-drawing-pdf.axvw , the Add-in Manager must also create a legend-type panel and refer to the new legend datasource. Following the same example, the panel's id must be named panel_ds_ab-sp-hl-rm-by-dp-name_rmLegend , and the datasource must equal ds_ab-sp-hl-rm-by-dp-name_rmLegend . The fields that the datasource defines and that should be visible in the legend must be defined in that panel. (3050005)
• Space Requests. Moves . If you change the From Location in a space request, use Space / Moves / Move Coordinator / Complete Group Moves to close the move, and check the rmpct record, you will see that the value for primary_em is still 0. It should change to 1 since user has changed the From Location from satellite location to primary location. The conditions for this situation are: workspace transactions are enabled, the SLA for Group Move calls for the service provider as Move Management and no approvers, and the application parameters are: InferRoomDepartments=0 and AssignUnallocatedSpace=ProrateFloor . (3043629)
• Moves. Action Questionnaires . If you add new Action Types (using the Space / Moves / Background Data / Define Action Types task), you cannot add questionnaires to these new action types using the Space / Moves / Background Data / Define Action Questionnaires task. ( 3028382 )

Maintenance known limitations

• Non-English Locales. Tagging in Comments . When you tag someone in a comment using OnSite or Web Central, the system generates an email; under a non-English locale, the strings in both email title and email body are not translated. Non-translated text includes: the string 'tagged you in work request' in both email title and email body, as well as all the strings for work request parameters in email body. (AD-9394)

• Time Zones . You will encounter the wrong time zone in work orders (11:57 AM instead of 1:57 PM) if you select the “Etc/GMT+1” value as the time zone using the Define Geographical Locations view. Instead, select a city-specific time zone such as "Europe/Paris timezone(UTC+1)". The “Etc/GMT+1” value will be removed in the future as it is not necessary. (AD-8802 )

• Maintenance Console. Japanese . Under a Japanese environment, the Maintenance Console's Comments are shifted to the right and do not properly align. (AD-10497)

• Maintenance Console. Equipment Documents . Only the Add, Update, and Delete actions for working with documents should be controlled by the user role. Currently, actions such as Show and Download are incorrectly controlled by user role. (AD-8299)

• Maintenance Console. Sorting . The first time that you sort the Maintenance Console's grid by a field it correctly sorts; if you sort by the same fields multiple times, the sort does not work and the arrow in the header row does not update correctly. (AD-7932)

• Craftsperson Sample Data . In the sample HQ project, there are many records in Craftspersons (cf) table that do not have email account; also many have duplicated email accounts like no-response@archibustgd.com. The key convention for the workflow is: cf.email=em.email=afm_users.email . These values must be unique. To fix this issue, just remove those records from the cf table for which emails are either empty or have duplicated value. Below are some situations where duplicated values can cause problems

  • Launch SLA console, dispatch to supervisor, click Select Value, you will see all employees instead of all cf.is_supervisor=1
  • Continue to add a estimation step, select employee to do estimation, you will see all employees instead of all cf.is_estimator=1
  • Launch the Maintenance Console, click any work request, click the Forward button, select supervisor, you will see all employees instead of all meeting the restriction: cf.is_supervisor=1. (AD-6744)
• Craftspersons. Notifications .For SLAs that are configured so craftspersons are to be notified when work is issued (notify craftsperson check-box), the craftsperson is not receiving notification when the work is issued. (AD-4960)

Assets known limitations

• Asset Lifecycle Console. Classification Filter . When you filter for a classification, in the Select Value list associated with the Classification filter, the Classifications tree expands automatically up to the second level. The returned classification results may be at lower levels, so you may need to manually expand the tree to see everything. Ideally, the Asset Lifecycle Console would automatically expand to the appropriate level; however, it expands only to the second level due to potential performance issues on larger inventories of assets. ( AD-10324 )

• Asset Disposal Console. Changing Building Status from Asset Disposal Console Causes Inconsistencies in REPM . The Asset Disposal Console updates the asset records for Buildings and Properties as well as inserts OT records to match when the asset is disposed of. REPM reports on Owned, Pipeline, and Disposed OT statuses for buildings, but ignores buildings with other ownership transaction statuses, or gives unexpected results in reports. The REPM Building Add/Edit Wizard does not have a way to modify the status of the bl record. Setting the transaction Status to Owner does not change the status of the building to Owned. Coordinate OT records with asset status in both REPM and Disposal Console. (APP-852)

• Define Classifications . Deleting Top Levels . In the Define Classification view ( ab-ca-def-class.axvw , which is available from the Business Process Owner process of Asset Management, Condition Assessment, and Environmental Sustainability Assessment), you cannot delete a top level. Instead, you must delete the top level by using Smart Client and deleting the record from the csi table. If you are not going to use a top-level classification hierarchy, it is advisable to delete all the child records (under the top level) before deleting the top level. (AD-6682)

• Classifications. Localization. Numeric ID (Automatic Lookup) . The Classifications ( csi ) and Classification Standards ( csi_std ) tables are not translatable. Therefore, in order to use the Automatic Lookups (Numeric IDs) feature for asset classifications, enable Automatic Lookups for them without afm_scmpref.preferences . Otherwise, Archibus will look for the translatable fields in the two tables, resulting in application errors. Also, the Asset Classification Description field ( csi.description ) and the field Classification Standard Description ( csi_std.description ) are not translatable. If enabling the Automatic Lookup for these fields, do not use the attribute displayType="translate" because the fields are not translatable. (APP-4286) ( AD-6683 ).

Real Property known limitations

Sustainability & Risk known limitations

Capital Projects known limitations

Connectors known limitations

• Reserved Words. Archibus does not support field names with reserved words. For example, adding the field "alter" to the table bl, causes the Archibus application server to fail to start when attempting to restart it. Therefore, the INBOUND use case of importing data into an Archibus table that has a field named with a reserved word is not supported. The OUTBOUND use case of exporting data to a remote system like BUILDER SMS that has a database field that uses a reserved word (ex. order) is supported. (APP-3975)(APP-4769)

• EDI Example . The example file provided for the EDI connector in the HQ project demonstrates Web Central’s ability to process EDI data formats, but only addresses the bill table. Since the example lacks a bill_lines connector definition and a bill connector association, it is not possible to fully load a complete utility bill using the EDI connector example. In the future, we plan to make a new example that is more realistic available for download. (3047882)

• Backslash Character . In some environments entering \\ in connector field parameters or connector parameters may result in the \\ being saved as \ . As a workaround, for a field enter \\\\ for \\ every time you save the field. For connector parameters, avoid use of \\ ; or, use \\\\ and fix configuration in post process. (3045250, 3047842)

• Saving . Saving a connector does not display the standard “Record Successfully Saved” banner. (3045250)

Extensions for BUILDER TM SMS known limitation

• Asset Attributes. Numeric Values. Separators. When entering numerical values for an asset attribute (ex. Quantity) do not enter a numeric separator such as a comma. If a comma is entered in the asset attribute value as a numeric separator, the connector framework will not know how to process the comma and the data transfer to BUILDER SMS will fail. (APP-5603)

• Outbound Connector. Condition Assessment Items . The master outbound connector SMS_ARCHIBUS_BUILDER_Inspect exports all condition assessment items for a given section with date assessed in the past 90 days or within the number of days from current date set in the application parameter AbCapitalPlanningCA-BUILDER_InspectionDate_NewerThan and not only the most recent condition assessment record for the that section and for that time interval. (APP- 4090)

• Inbound Connectors . Number of Buildings . Sites do not record number of buildings transferred in from BUILDER TM SMS for the specific site. (APP-2401)
• Inbound Connectors . Sections . Sections measured in pieces with quantity higher than 1 will not be split into multiple pieces of equipment when imported into Archibus. When transferring sections from BUILDER TM SMS measured in pieces and that have a quantity larger than one, Archibus does not create multiple pieces of equipment. It creates only one piece of equipment with the corresponding value for the quantity attribute. (APP-2138)

• Outbound Connectors . Organizations and Sites . For new organizations and new sites transferred from Archibus to BUILDER TM SMS, the OUTBOUND connectors do not set values to these BUILDER TM SMS fields:
  Organization.UpdateCosts
  Organization.UpdateCurves
  Organization.ORG_ACF
  Organization.ORG_SEISMICZONE
  Organization.ORG_CI
  Organization.ORG_FI
  Organization.ORG_PI
  Organization.ORG_FCI
  
  BUILDER TM SMS displays new organizations as new sites transferred from Archibus to BUILDER TM SMS, even without setting values to the above fields. BUILDER TM SMS users can enter the values for these fields using the BUILDER TM SMS interface. Running the OUTBOUND master connector a second time will not affect the values entered by BUILDER TM SMS users for these fields. (APP-3215)