Revision History for Archibus V.2023.02

Included in this topic are fixes and changes to programs, modules, and applications that may be of interest. The topic also contains known limitations.

You will also want to review these topics:

Topic	Description
What's New in Archibus V.2023.02	Summary of major enhancements and new features in Archibus applications, mobile apps, platforms, and customization. Typically, items listed in the What's New are not repeated in this topic's "Changes in this Release" section.
Database Schema Revision History	List of database changes for V.2023.02.
Usage Notes	Documents issues you should be aware of, but are not known limitations. If you encounter an unexpected behavior that is not listed below as a known limitation, check the Usage Notes.

Note:. While the documentation provided with V.2023.02 gives an overview of the V.2023.02 functionality, Archibus continues to add documentation on feature details and usage notes. Should you want the most recent available information, please check the version of the help that is available online at the links below. If you are at a secure site with policy restrictions governing Internet access, and you wish to receive an updated version of the latest help, please contact Customer Support.

User Help: https://help.archibus.com/user_en/archibus.htm

System Management Help: https://help.archibus.com/system/sysman.htm

Changes in Archibus V.2023.02

• Online Help
• Archibus Saas Foundations
• Web Central
• Workplace
• Smart Client, Smart Client Extensions for CAD and Revit
• Mobile Framework and Mobile Apps
• OnSite Configuration
• Database
• Platform
• Assets
• Space
• Maintenance
• Risk
• 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 BUILDERTM SMS

Changes in Online Help

• Allbound URL. The URL for Allbound (the Partner Portal with links to files, events, webinars, and more) has changed from https://archibusserraview.allbound.com to https://eptura.allbound.com/. References to Allbound in User Help and System Management Help have been updated to reflect the new URL. If you attempt to access the previous URL, you will automatically be redirected to the new Eptura-based URL. (DOC-3235)

• Sybase Topics. Since V.25.2, Sybase has been available only for demonstration and training, and has not been tested for production deployment. In V.2023.02 System Management Help, we have removed the Sybase topics. If you use Sybase as a testing environment, you can consult the Sybase topics in archived V.2023.01 System Management Help. (DOC-3137)

• Client/Server Topics. Beginning with V.25.1, Windows Client/Server compatibility has not been supported, although the features supporting Client/Server compatibility remained in Web Central and Smart Client. Users who wanted to work with the Client/Server compatibility features, used a pre-V.25.1 version of Archibus. Given that Client/Server compatibility has not supported for several releases, we have removed the Client/Server topics from the System Management Help. If you need the Client/Server topics, consult archived V.2023.01 System Management Help. (DOC-3138)

• Single User and Small Workgroup Deployment Topics. Since these deployments have not been available for some time, we have removed the topics from System Management Help. If you require them, consult the archived V.2023.01 System Management Help. (DOC-3001)

• Upgrading Personalized Views to the V.21.1 User Interface. This section has been removed from System Management Help. If you require these topics, please consult the archived V.2023.01 online help.

• Crystal Reports. We have removed these topics from System Management Help. If you require these topics, please consult the archived V.2023.01 online help.

Changes in Archibus SaaS / Foundations

• Archibus Geospatial Extensions for Esri. The Foundations package now includes the Archibus Geospatial Extensions for Esri. In future releases, this license will be enabled as part of Foundations. In the meantime, contact Archibus Customer Support if you need this license activated. (DOC-3225)

Changes in Web Central

BIM Viewer

• Buildings Drop-dwon Menu. With the addition of the Projects List for accessing all projects, the BIM Viewer's Buildings drop-down list now presents only those buildings cataloged in Archibus. (AD-13327)

• Autodesk Platform Services SDK. We have upgraded the BIM Viewer to Autodesk Platform Services SDK v7.86.0 . Refer to Autodesk Platform Services change log to see the benefits of upgrading to v7.86.0 at https://aps.autodesk.com/en/docs/viewer/v7/change_history/changelog_v7/(AD-12725)

• Equipment Systems. The System tree now enables you to easily move assets to different systems or within the same system by dragging and dropping them into the correct position within the system. This is the same behavior as found in the Equipment Systems Console. (AD-12881)

• Nested Families. Supports locating and highlighting nested families. (AD-11499)

• Export. You can now export the list of Assets to XLS. (AD-11612)

• Additional Highlights. We have added additional highlights for rooms, including: Room Standard, Super Categories, Status, Available and Hotelable, Not Surveyed. (AD-11758)

• Catalog BIM Models. Minor UX enhancements and layout fixes. (AD-12420)

• Zooming. We have improved the zooming features. (AD-12486)

• Performance. When working with Autodesk Construction Cloud repositories that have a very large set of models (ex. over 50), you will find that the errors about exceeding data limits have been resolved.

• Filter. Group by Systems. Previously if you filtered to a building by choosing the Building button and then grouped by systems, you would see systems in all the buildings. Group by systems now reflects the filter. (AD-12319)

• Unresponsive Highlights. The highlights in the BIM Viewer became unresponsive after six minutes of working with the same building or six minutes of inactivity. This was because the datasource became unresponsive. This has been corrected and you no longer need to reload the view and then set the highlights again. (AD-12120)

• Equipment Labels. After you loaded a floor from the Levels drop-down and turned on the Equipment labels, the BIM Viewer displayed the labels for all the equipment in the building instead of just the labels for the equipment on the floor being visualized. This has been corrected. (AD-12488)

• Asset Selection when Switching Floors. Previously, if you selected in the Asset list equipment on multiple floors and then loaded a new floor plan, the assets on the new floor plan were not highlighted. We have corrected this so that the assets on the newly-loaded floor plan are highlighted. (AD-12487)

Interface

• Addressed error when submitting a license file using Set up License for Clustered Deployment
• Addressed issue where icons on grids would become disabled after a refresh
• Addressed issue in legends where the value contains a dash or the legend contains a large number of entries
• Addressed errors when attempting to run Basic Rule Wizard
• Certain characters which are encoded in HTML are now displayed correctly in grids
• Ensured Edit Drawing Publishing Rules display all SVG and EMF publishing rules
• Improved message when deleting records succeeds
• Make display of date in Database Revision view consistent in Oracle
• Remove obsolete items from View Program Information and License Usage
• Visual improvements to Navigator menu and branding

Export

• Addressed error generating a Paginated Report with no restriction
• Addressed error exporting to Excel where a restriction could cover data. (DOC- 2749, AD-11606)
• Addressed error exporting to Excel from Report Central
• Addressed error exporting to Excel from the Space Console with a restriction

Changes in Workplace

• Service Requests. Request Types with Questions. Displaying User Responses. The following issue has been resolved: If you make a request in Workplace for a Request Type that has questions and also has a Problem Type, the user's responses to the questions do not display in the Workplace Services / Service Desk / Client / View Service Requests task; the responses are correctly recorded as XML in the activity_log.act_quest field.  Requests for Request Types that do not have a value for Problem Type do successfully display the user response. (AD-12927)

• UX. "Meeting Reservation" changed to "Meeting Space Booking."  Based on user feedback, we have changed titles, buttons, and message text that contains "Meeting Reservation" to "Meeting Space Booking." (AD-13340)

• Workspace Booking. Search for Employee. Previously, if you searched for an employee near whom you wanted to book a space and there was no available space on the employee's floor, you were redirected to another floor with space with no explanation. Now, in this situation, you land on the same floor as the searched employee and there’s an a message that there are no available seats on this floor. (AD-12901)

• Workspace Bookings. Booking Multiple Seats. Floor Capacity Target. The following issue has been resolved: When the application is set up such that AbSpaceHotelling-AllowMultipleBookings is set to Yes and AbSpaceHotelling-EnforceFloorCapacityTarget is set to Yes, when users encounter a room with more than 1 seat available, they have the option to book multiple seats in their own name. However, users can book up to the total number of available seats in this room, even if it exceeds the Floor Capacity Target set for this floor. They will be able to proceed with the booking and exceed the Floor Capacity Target. The next person who tries to book on the floor, however, will be prevented from making any further bookings. (AD-7498).

• Accessibility Mode. Pre-block and Post-block Times. Workplace now displays a message that pre- and post-block times are considered in the search for meeting rooms: ”Available times are automatically adjusted to meet the following requirements..." (AD-11661)

• Accessibility Mode. On the floor plan view, we have improved the meeting room and workspace availability messages that display when the user hovers over a room. These messages adhere to accessibility standards. (AD-11284)

• Accessibility Mode. Service Catalog. If Accessibility Mode was enabled, the /archibus/schema/ab-products/essential/workplace/index.html?action=servicecatalog URL displayed the pre-V2022.02 Service Catalog view and did not display the Dashboard, as is the behavior for V2022.02 and beyond without Accessibility Mode. This was resolved in V.2023.01 but not listed in the V.2023.01 revision history. (AD-8901)

• SSO. If you closed the browser without fully signing out, you were not able to sign in again until either the Web Central session expired, or a hard refresh was performed in the browser. This has been resolved in most circumstances; the Known Limitations lists an exception when using tablets. (AD-12162, AD-12870)

• Logging. Workplace logging now reports if the landing page (index.html) has been cached. This can be valuable for troubleshooting. Consult the log by using F12 to enable Developer Tools and then click on the Console tab. (AD-13163)

• Employees Tagged in Comments. In order to display comments in which employees have been tagged, Workplace now consults the following fields in Comments: em.name, em.em_id, and the em.name_first and em.name_last combination. This resolves a problem in which some employees, such as sample employee Allison Abernathy, were not seeing comments in which they were tagged. (AD-12491)

• Employee Details popup, When AbEssentialFacility-SelfServiceSearch was set to 0, the Workspace Booking screen was incorrectly showing employee details about the employees who had booked spaces on the floor plan you are viewing. We have corrected this so that Workplace does not show employee details with this setting. (AD-12586)

• VPA. A problem with floor plans not loading under some VPA conditions has been corrected. (AD-13149)

• Localized. The calendar is now fully translated in a custom language. (AD-13028)

Workplace Mobile App

• Floor Selection. Accessibility Mode. The floor selector buttons were replaced with drop-down lists. In both modes, Workplace now uses floor selector buttons. (AD-9844)

Changes in OnSite Configuration

The OnSite mobile app is not updated as part of V.2023.02. However, we did make changes to the Manage Configurations for OnSite task. These pertain to OnSite V6.

• In the Workflow tab, you can now specify what fields the craftsperson must enter when completing their work. (AD-13512)

• In the Display Options tab, you can now specify additional fields, such as Other Costs, that can be hidden from the OnSite display. (AD-13511)

• In the General tab, there are new option for specifying Timer-related configurations. (AD-12692)

• In the Notifications tab, users with a locale of Chinese now receive an informational message: “Technicians might not see the notifications on their mobile device. They need to access the OnSite Notifications tab to view all of them.” This is required because Chinese users will not receive notifications from Push Service hosted by Google, due to the ban on Google in China. (AD-10430)

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

General Smart Client, Extension for AutoCAD, and Extension for Revit

• Security. Multiple security issues addressed

• SSO. A problem with SSO not compatible with AWS ALB (Application Load Balancer) with sticky sessions has been resolved. (AD-12579)

• Sign out: Resolved a problem with licenses not being released in SSO environments. (AD-12925)

• Publish: Publishing would fail and display an error message stating "Access to path… denied" if the path was not configured properly in Web Central. This has been resolved. (AD-12713)

Smart Client

• Main screen: Corrected a problem with the displayed text was tiny on high-DPI monitors. (AD-12815)

Smart Client Extension for AutoCAD

• Publishing. We have corrected a problem with drawings using mm units not publishing some blocks to the published floor plan. (AD-12490)

• AutoCAD supported versions. Support added for AutoCAD 2024. (AD-12669)

• Insert Asset. The following issue has been resolved: 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)

Smart Client Extension for Revit

• Map Database Fields. Would not work with certain models This has been corrected. (AD-13493)

• Infer. Equipment option not available for instance elements when they were first added to the model. This has been corrected. (AD-11248)

• Publish. Rooms would be missing from an exported DOCX and PDF exports from the Space Console for some models This has been corrected.(AD-12452)

• Publishing. An error when publishing 2D if the Smart Client Locale is set to French has been resolved. (AD-11893)

Changes in Database

• See the following topic in System Management Help: Database Schema Revision History.

Changes in Platform

Security

• Improved access restriction to assigned views.
• Logging out while user has jobs running now always logs the user out.
• Added warning in log to set APP_ENCRYPTION_PASSWORD if using default.
• The workflow rule flushCachedUserRoles is now a privileged operation restricted to administrators.
• Opting out of usage analytics will correctly disable all analytics.
• Hardening against unauthorized path traversal.
• Hardening against session fixation.
• Hardening against External Entity Inject (XXE) attacks.
• Updated 60 java libraries; removed four redundant libraries; added three libraries to support new features
• Increased minimum Java version to Java 11.

Logging

• Added slf4j provider to ensure complete logging.

Back End

• Accommodate viewName ending in axvw when referencing a data source.
• Changed default project to FirstActiveProject generally.
• More consistent and persistent data source resolution and caching, but the core.preloadFileIndex is ignored (always true).

• Data source caching was improved at the cost of start-up time and configuration.

• Support for parameterized queries in cross table views.

Other

• New Eclipse environment

Changes in Mobile Framework and Mobile Apps

• There were no updates to the Sencha mobile apps and mobile framework in V.2023.02.

Changes in Assets

• Equipment Standards. In the Define Equipment Standards view, the left-side panel displays additional fields. This will help you more easily identify the equipment standard to be modified. (AD-13810)

• Archibus Asset Families task. We have added a new Background Data task for defining records in the Archibus Asset Families. This table provides the values for the new Asset Family field in the Equipment Standards table. (AD-12941)

• Define Asset Attribute Standards task. We have added this task to the Assets / Background Data - Assets process for Archibus SaaS. Non-SaaS users can find this task under Enterprise Asset Management / Background Data - Assets; in Non-SaaS deployments, this task is not available under Assets / Background Data - Assets, but will be in a future release. (AD-14097, AD-12912)

Changes in Space

• Highlight Occupiable Vacant Rooms. Previously, the Paginated Report button produced a report that included floor plans for all floors with vacant occupible rooms. This has been corrected to include only the floor plan displayed in the report. (AD-12220)

• Space & Portfolio Planning Console. We have corrected an issue when exporting data. (AD-9297)

• Space. Console. Export. We upgraded the aspose words library, which fixed issues with PDF and SVG export. (AD-11950, AD-12712)

• Space Console. Legend. We have resolved a problem with legends when the division by which you are highlighting contains a dash character. (AD-12338)

Changes in Maintenance

• Maintenance Console. Locale. Dates, such as Date to Perform, are now formatted per user locale. Likewise, days of the week are now translated and display in the user’s locale. (AD-11895, AD-13112)

• Maintenance Console. Bulk Update. Craftspersons. When you perform a bulk update of work requests, you can now make craftsperson assignments using the Add Work Logs button. (AD-11102)

• Craftsperson Availability. Filter. Previously, the Primary Trade Required filter was not working properly. This has been corrected. (AD-11178)

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

• Labor Scheduler: Multiple work requests were incorrectly listed under the same time slot. This has been corrected. (AD-13039)

Changes in Risk

• Emergency Preparedness. View Egress and Occupancy Plans. This view (ab-egress-occ-plans.axvw) now correctly includes employee names, as it had in the past. (AD-11841)

• Compliance. Operational Reports. Permits and Licenses. (ab-comp-rpt-permit.axvw) Previously, the filter in this view was not working. This has been corrected. (AD-12361)

Changes in Workplace Services

Reservations

• Define Room Arrangements. Groups Allowed to Approve. Previously, Groups Allowed to Approve field was limited to only Groups assigned the non-SaaS AbWorkplaceReservations application Approve process. It now includes theAbCloudWorkplaceServices process. (AD-8977)

• Recurring Conference Call Reservations. Canceling. If you canceled one reservation of a series of recurring reservations and entered a comment, the comment was applied to all remaining reservations that have the same res_conference value as the canceled reservation. This has been corrected. (AD-11054)

• Reports. Filters. For several reports, we fixed the filters that were not properly functioning. (AD-13158, AD-13160, AD-13229).

• Exchange Integration. New Application Parameter. To support meetings created by Exchange users that don’t exist in Archibus, the calendar monitoring now maps unknown email addresses to a ‘dummy’ user via a new application parameter: AbWorkplaceReservations.ExternalBookingEmployeeId. (AD-12335)

• Exchange Integration. Private Flag. Previously, the private flag was not propagated to Exchange and comments for private meetings were still visible. This has been corrected. (AD-12868)

• Reservations Plugin for Outlook. Recurring Reservation. A problem with the reservation failing when you create a recurring reservation with an exact date has been resolved. (AD-12689)

• Reservations Plugin for Outlook. SSO. We have improved SSO experience so that the Outlook user does not access the Web Central application. After a single login, the user accesses the Archibus Room Finder in Outlook. (AD-12918)

Hoteling.

• Workplace Utilization. We have improved the filter and added a chart to this view. (AD-12512)

Service Desk

• Move Requests. Email notification. When a move is requested and Request Type is SERVICE DESK - INDIVIDUAL MOVE, we now prevent a move notification email from going out to the department contact, if department contact is the same as the requestor. This change reduces the number of duplicate messages sent. (AD-13083)

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)

• Navigator for AFM-MOD Sample User. If you sign in to the HQ sample project as AFM-MOD, you will notice that the Navigator groups modules into domains (including the Archibus SaaS domain) so that the Navigator presents four levels. Having some modules grouped under the Archibus SaaS domain may be confusing if you are demonstrating or learning the product. This change is a result of the Healthcare module being added to the Navigator and the Navigator now exceeding 13 modules. This can be resolved by removing a module that you do not need. (AD-12985)

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)

• 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

• Accessibility Mode. Workspace Bookings. In Accessibility Mode, Workplace conveys that a room is unavailable when, in fact, it is available for booking. (AD-13569)

• Localized New V.2023.02 Strings. With a non-English locale, new V.2023.02 user interface elements will appear in English while the rest of the user interface will appear in the user's selected locale. When the localized strings become available, we will post them on Allbound. (AD-13591)

• Search. When focus is on the filter panel, it should remain on the panel until the user tabs. Instead, when the search is completed, focus shifts automatically to the floor plan. (AD-13716)

• Sign in. SSO. If you have set up Web Central for request header SSO in Web Central and enabled UseSingleSessionForConcurrentUsers in security.properties, if you attempt to access [WEB CENTRAL URL]/archibus/workplace/ directly, you are not able to log in. You must first access Web Central and then load Workplace from there. Similarly, if you load Workplace, copy the URL, close the browser without signing out, open a new browser and paste the URL, you will not be able to log in. (AD-11342, AD-12854)

• 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)

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

• Tablet. iPad pro/Safari. SSO If you start Workplace in a Safari browser and without signing out, you close the web browser window fully and then reopen the web browser window and attempt to navigate to Workplace again, you will not be able to start Workplace. To work around the issue, clear the browser cache and reopen the browser. Or, open the browser, close the Workplace tab which is stuck, open a new tab and enter a Web Central or Workplace URL. This was tested on iOS 16.2. (AD-12878)

• Tablet. iPad pro/Safari. The header is truncated, and on some pages cuts off buttons. This occurs in both landscape and portrait modes. (AD-13718)

• Tablet. Android. Next button. The Next button does not display for several Service Request types when you are running the Workplace mobile app on a tablet. (AD-12544)

• Tablet. Android. Create Request. Next Button. If you run the Workplace mobile app on an Android tablet, you will find that if the selected request type presents a questionnaire for you to answer as part of entering the request, Workplace will not display a Next button and you cannot continue with the request. (AD-12848)

Desk Bookings (Hotelable Rooms)

• Team Restriction. When the “team” restriction is defined, and the space selected for booking is assigned to a specific team, the occupants selection list should be restricted to that team. Instead, the occupant list is not restricted to the team. (AD-11906)

Meeting Room Reservations

• Meeting Times. When you enter time in your search for meeting rooms, and click Book from the list of available rooms, the specified time is not highlighted in the time slider or entered in the start time/duration selectors. (AD-13581)

• Self-booking. QR Codes. When self-booking a meeting room is not permitted (SelfServiceBookMeetingSpace = 0, KioskBookMeetingSpace = 0), you will find that after scanning the QR code label, the Book button is displayed. It should be hidden based on the parameter settings. (AD-9683)

• Multiple Room Configurations. In Workplace, we assume that only one configuration and one room arrangement has been defined for a room. If you create multiple room configurations with the Reservations application, the configurations will appear in Workplace, but there is no distinguishing information about the configurations and the user will not know which space they are reserving. There will also appear to be a discrepancy between the available room count and the number of rooms shown on the floor plan. (AD-835, APP-5194, APP-5845)
• Recurrence Pattern. Workspace reservations do not show recurrence patterns in the details view. You can only delete a single occurrence at a time. AD-835)
• Time Slots. Meeting space requests do not honor the value of the parameter in AbWorkplaceReservations-MinutesTimeUnit. You can only select time intervals in 30-minute blocks. (AD-7010)

Workplace Mobile App

• Service Request. Uploading Both Images and Documents. Due to device and application permissions, it is not possible to upload both camera images and other file types from the device in the same service request. (AD-13309, AD-13928)

• Scrolling and extra spaces. There are improper empty spaces above the header and below the footer. There are two redundant scroll bars that appear when it is impossible to scroll up or scroll down. (AD-13929)

• QR scan. Android Tablet. When applied in a mobile browser, the URL generated by a room correctly takes the user to the Room booking view. However, in the Workplace Mobile app running on an Android tablet, the URL generated by the room QR scan incorrectly takes you to Workplace Dashboard view. (AD-13986)

• QR Codes. The Home button is not available after scanning a QR code, and from QR Code page, it is difficult to navigate to the login screen. (AD-9659, AD-9681)

• Signing in. Android. Mobile Client version. You cannot log in if you are not using Mobile Client 4.0. As a workaround, upgrade to Mobile Client 4.0. (AD-6801)

• Select Occupants for Workspace Booking. If you try to book six or more staff for working space, the UI cannot correctly display you selected employees. (AD-8599)

Web Central known limitations

• Localized New V.2023.02 Strings. With a non-English locale, new V.2023.02 Web Central and Workplace user interface elements will appear in English while the rest of the user interface will appear in the user's selected locale. The localized strings will be available in the future. (AD-13591)

• BIM Viewer.

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

  • Blank Worksheets. For some Revit 2022 models, the new feature “Sheets & Views” may display the worksheets as blank. This is an issue with the Autodesk Platform Services API that we could not fix on our side and we are waiting for Autodesk to fix. (AD-10801)

• 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)

• 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)

• 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)

• 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)
• 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

• 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)

• IofT. Oracle. The Technologies / Innovative Solutions /Integrations - IoT / IoT Space Utilization view 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.MobileSyncDataChangesOnlyTables 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

Service Desk known limitations

• Manage Request Types. Non-English Locale. When using the Service Desk / Service Desk Manager / Manage Request Types view (ab-create-activitytype-tabs.axvw) to edit request types that have been translated into other locales, the request type does not appear correctly in Service Desk Manager edit form. (AD-2813)

Reservations known limitations

• Archibus Extension for Exchange Integration. Reservation with No Subject. If you create a reservation with no subject, the message stays in the user's calendar and the reservation cannot be found in Archibus; the reservation errors out in the log because the subject is empty. (AD-13528)

• Reservations Calendar Console. Attendees in Room. Does not correctly set the “Attendees in Room” field value when creating meetings; there is no way for a user to manually edit this value. (AD-4856)
• Reservations Calendar Console. Double-byte Characters and Comments Field. The Calendar Console presents an error message when you attempt to confirm a reservation whose comment includes double-byte characters and is larger than 4000 characters. As a workaround, enter smaller comments when a comment includes double-byte characters. (AD-436)
• Reservations Calendar Console. Recurring Reservations for Monthly Meetings. The timeline does not always correctly display recurring patterns for monthly meetings. For example, if you created a reservation for the first Monday of the month, the Reservations Calendar Console might show all Mondays in the month. Although the timeline might not display these reservations correctly, the Console does correctly save these meeting dates and the summary text reflects the proper date. (APP-6651)(AD-1028)
• Reservations Calendar Console. Room Configurations. For situations in which multiple reservations exist at the same time in the same room, but for different room configurations, the calendar displays only one reservation. (APP-6561)
• Reservations Calendar Console. Continuous Meetings. The system does not prompt you resolve continuous meetings that have conflicts; when it encounters this situation, the system generates a workflow rule error. (APP-6535)
• Reservations Calendar Console. Conference Calls.
  • If you create a conference call and you select several buildings in order to select rooms in several buildings; and if many of the rooms in one building are reservable, all of the rooms for this building are shown, and reservable rooms from other buildings are not displayed. This can make hard to select rooms from different buildings. The TimelineMaxRoomsPerBuilding application parameter does not control this.(APP-6214)
  • You cannot edit the date and time of a conference call reservation. (APP-6613)
• Reservations Calendar Console. Changing Room Selection.Time not Recorded. If you select a room, select a time, add some resources, and select another room; you will find that the designated time does not persist to the second room. (APP-6800)
• Reservations Calendar Console. Application Parameters. The TimelineStartTime and TimelineEndTime parameters work only with one-hour increments. If you enter times such as 9:30 and 17:30 in the parameters, the Calendar Console does not consider them. (APP-6698)
• Create Resource Reservation. Reservation Timeline. Microsoft Surface. You cannot drag with touch input a reservation on the timeline. Timeline drag-and-drop supports only mouse events. (APP-3312)
• Outlook Plugin. My Reservations. When the Outlook Plugin displays the My Reservations, the popup is opened without the option to edit any of the reservations showed, so users cannot add resources. The Add Reservation button is also disabled. (AD-4846)
• Google Calendar Integration. When you have configured the application for "no integration" with Exchange, the .ics files that are generated to be imported into Outlook, Google Calendar, or any other calendar app, sometimes do not correctly update the Google Calendar application. Specifically, there can be a problem with the file content related to the meeting identifiers created by the application. These meeting identifiers are not always unique. If you create a new calendar, instead of importing an existing one, the creation of meetings seems to work correctly for single and recurring reservations, but updates and cancellations don’t always work as expected.

Space known limitations

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

• Space Console. Highlights. Highlights that combine Teams and Divisions or Teams and Departments do not work in v2023.02. We will be working on this for v2023.03. (AD-14040)

• Space Console. Export to DOCX or Excel. Currently the Export feature is not exporting all records listed in the tabs (Room Categories, Employees, Rooms, and so on) to XLS or DOCX. tab. For Excel, you can export only 100 records; for DOCX, the amount varies. As a work-around, export from other views. (AD-13752, AD-13368)

• Space Console. Export What You See. If you select multiple floor plans to display, only the first displayed floor plan is exported. All visible floor plans should export. (AD-12658)

• Space Console. Search by Team. If you select Show Teams in View Settings, use the Advanced Search form to search for a team, floor plans that have assigned teams do not show. However, you can load these floor plans if you select them from the floor list. (AD-12821)

• Space Console. Search. Default Layers. If you search for a floor using the Smart Search Bar and load the floor plan, the default layers correctly display. However, if you choose another floor plan from the search results, the not all the default layers display on the second floor plan. (AD-9538)

• 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. 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)

• 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)

• 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)

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. Inventory of Asset Systems report. Oracle only. The Inventory of Asset Systems report (available from the Reports button on the Asset Relationship Analysis tab) presents a workflow rule error if you are running on Oracle. (AD-14128)

• Asset Disposal Console. Changing Building Status from Asset Disposal Console Causes Inconsistencies in Real Estate. 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 Real Estate domain's 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 Real Estate 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).

Enterprise Assets known limitations

• Project Proposal Console. Baseline cost of a Billion Monetary Units or Greater. If you enter a baseline cost for an individual required asset that is a billion monetary units or greater, you get an error that the value entered exceeds the maximum storage unit for the field. This is because the value for the baseline cost in the sb_items table is defined as numeric (9,1). However, the value you entered displays correctly in the grid and in the statistical summary because the value in the eq_req_items table is defined as numeric (16,2). This error occurs only in the rare case that the cost of an individual asset is a billion monetary units or greater. (3052851)

• Project Proposal Console. Selected Period Fields not Displaying. The default selection is to display Baseline and Period 1. If you add other period fields but then want to return to the default setting and find that the Console is not displaying your selection, clear your browser cache. (APP-1601)
• Manage Reference Documents. This task enables you to associate a document with a Building Use, Property Type, and Furniture Standard. However, there is currently no way to view documents added for these items. It also enables you to associate a document with projects of different types. Currently, you are able to view documents for only projects that have the Scenario type. You are, however, able to view documents added for work request Problem Types, PM procedures, and action items that are associated with a Proposed project. (3050281)

Asset Portal known limitations

• View Equipment Plan. If you have a lot of asset symbols on the floor plan, they may not display the Equipment Code as asset text and may not be correctly filled with color. (3028852)

Real Property known limitations

Forecasting known limitations

• Portfolio Forecasting Wizard. Calculations. If the user units are different from the project units, when you calculate the area on the floor for an allocation event by multiplying headcount by average area per employee, the result can be off by a factor of 10.76. (3052105)

Strategic Financial Analysis known limitations

• Financial Analysis Console. VPA. The console does not load if the user has a VPA that is not compatible with the console restriction. Please see Adding VPA to the Financial Analysis Console  for details on creating a VPA for this console. (3053673)

Sustainability & Risk known limitations

Compliance known limitations

• Extended Questionnaires. Service Requests from Mobile. Although the ability to create service requests from questionnaires was added to the Compliance Surveys mobile app, it has not yet been implemented in the Web Central Compliance application. Therefore, if a mobile questionnaire respondent provides details for a follow-up Service Request actions for any question in a questionnaire, then the respondent should take care to fully submit the questionnaire via the mobile app; they should not edit or submit via the Web Central questionnaire edit form because the Web Central edit form might not preserve the request details or set the status of the request as expected via the mobile app. (APP-4250)

• Extended Questionnaires. Assigned to Events. View my Events Calendar. The "View My Events Calendar" task for Compliance Program Coordinators does not provide a link from events details to answer or review any questionnaires that might be attached to assigned events. The workaround is for Program Coordinators to use one of the other "My... Events" tasks to access assigned questionnaires. (APP-1667)
• Extended Questionnaires. Question Tree. Nodes without Child Records. In the Define Compliance Questionnaire view, when you examine a question that has multiple choice answers, you will see that the Question Tree does not indicate that a node has no child content. When a node has no children, it still displays the triangle-shaped icon for expanding and collapsing, giving the impression that there are child records. After you click the node, the triangle disappears until refresh. (WC-2386)

• Contracts and Compliance Programs with Cost Records. Deleting. You must first delete all assigned cost records associated with a contract or program or requirement or term before you can delete the coordinating record. (APP-2276)

Hazard Abatement known limitations

• Homogeneous Areas not Highlighted. The application does not currently highlight all rooms identified as containing portions of homogeneous areas when there are no assessments directly associated with those rooms. (APP-5240)

Waste known limitations

• Hazardous Waste Accumulation Report. The application stores and displays the hazardous waste accumulation volume limit application parameter value in units of US Gallons. Users must take care to convert any other volume limit parameter into gallons if they adjust the application parameter controlling this. In any case, the application does automatically and correctly convert the accumulated waste quantity to compare against this standard, no matter what units the waste had been recorded in. (APP-5470)
• Waste Container Labels. The application generates formatted label documents for selected waste records. The web pop-up dialogue that shows the results of the document creation has a bug limiting the display of outputted documents to 4 records. However, the application does still produce label documents for all the selected records as distinct files, named according to the waste record id number and saved to the .../WebCentral/schema/per-site/pdf-forms/[username] folder. (APP-5241)

Energy known limitations

• Prorating bills. Duplicate Bills. If you happen to enter duplicate bills for the same building and vendor with overlapping dates of service, and then attempt to auto-generate prorated bills, the application may encounter a duplicate primary key error when trying to generate one or more of the bill records. This is because the resulting time periods will be the same, and the proration action will fail. (APP-5242, AD-924)
• Configure Bill Processing. Excluded Bill Types. Archived Bills. The Configure Bill Processing view allows users to choose to exclude certain bill types from the application's rules requiring bills to be archived in contiguous, ordered, monthly series. However, if an unusual situation occurs wherein a vendor account's utility bill type should change after some bills have already been archived, then the application will ignore a request to exclude the new bill type for new incoming bills for that vendor account. A work-around is to exclude both the old and new utility bill types from the monthly bill test. (APP-1855)
• Process BAS Data View. The Web Central core does not yet support grid indexes on dates fields or on calculated fields. For example, if you create an index on a date field having the value 2014-01-01, the value first shows as ‘2 – All.’ If you click the ‘2’ option, the value changes to ‘20’; click the ‘20’ and it's transformed to ‘201’; click the ‘201’ and it’s transformed to ‘2014’; click again, and it’s transformed to ‘2014….’ This issue appears in the right “Clean num” panel in Energy Management's Process BAS Data view. (WC-3108)
• View Prorated and Aggregated Bills. In rare cases, when the sum of aggregated bills exceeds a value 1000000 in the chosen display units, the application will present an alert message stating that the value of the calculated field exceeds the field's maximum. In this view, the user may safely dismiss this message and proceed to view the bill record. (APP-5270)

Green Building known limitations

• Fuel Density. Tree Panel. The Green Building / Background Data - Carbon footprint / Fuel Density task has a tree panel that manages two different levels of information. The tree panel does not display the second level. As a workaround, you can enter data so that both levels are shown, and then remove the data. (AD-1618)

Capital Projects known limitations

Projects known limitations

• Projects. Importing from Microsoft Project. From the Projects / Execute / Procure task / Import tab you can import an *.xml file from Microsoft Project. Depending on your version of Microsoft Project, you may need to choose to “Open as a new project." Otherwise, you may encounter errors with the predecessors values if you decide to append the data or merge the data. (3011985)

• Project Template. VPA. With VPA active, if you use the Projects / Set Up / Define Template Projects task to create a new project and enter a Project Type and Title, you will find that the process fails and a template project is not created. As a work-around, add NULL to the Site VPA list; this allows a Project record to be generated. (AD-8105)

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 BUILDERTM 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 BUILDERTM 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 BUILDERTM 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 BUILDERTM SMS, the OUTBOUND connectors do not set values to these BUILDERTM SMS fields:
  
  Organization.UpdateCosts
  
  Organization.UpdateCurves
  
  Organization.ORG_ACF
  
  Organization.ORG_SEISMICZONE
  
  Organization.ORG_CI
  
  Organization.ORG_FI
  
  Organization.ORG_PI
  
  Organization.ORG_FCI
  
  
  
  BUILDERTM SMS displays new organizations as new sites transferred from Archibus to BUILDERTM SMS, even without setting values to the above fields. BUILDERTM SMS users can enter the values for these fields using the BUILDERTM SMS interface. Running the OUTBOUND master connector a second time will not affect the values entered by BUILDERTM SMS users for these fields. (APP-3215)