Revision History for Archibus V.2022.03

Included in this topic are fixes and changes to programs, modules, and applications, as well as known limitations.

You will also want to review these topics:

Topic	Description
Software Update for V.2022.02	Summary of the changes to correct security issues in V.2022.02. This software update was released shortly after the initial release of V.2022.02. These changes are included in V.2022.03.
What's New in Archibus V.2022.03	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.2022.03

Note:. While the documentation provided with V.2022.03 gives an overview of the V.2022.03 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 Archibus Technical 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.2022.03

Also see Software Update for V.2022.02, which has been incorporated into V.2022.03.

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

Known Limitations of this Version of:

• Archibus Help
• Archibus SaaS
• Mobile Framework
• Web Central
• Smart Client
• Smart Client Extension for AutoCAD
• Smart Client Extension for Revit
• Outlook Plugin
• System Administration
• Database
• OnSite mobile app
• Mobile apps
• Workplace
• Workplace Services
• Space
• Maintenance
• Assets
• Leases
• Real Property
• Sustainability & Risk
• Archibus Extension for Lease Accounting
• Connectors
• Archibus Extensions for BUILDERTM SMS

Changes in Online Help

• BIRT. We have removed all BIRT topics from User Help and System Help. If you have developed custom views that use BIRT and you require the BIRT topics, see the V.2022.02 online help, which is available as links from the User Help home page. (AD-9589)

• Exchange. The topics in the following section of System Management Help were updated to reflect the software changes made in V2022.01. https://help.archibus.com/system/sysman.htm#outlook_plugin/exchange_res_overview.htm

• Esri. The Esri topics in System Management Help were completely revamped. https://help.archibus.com/system/sysman.htm#gis/esri/oveview.htm (AD-9973)

Changes in Web Central

• Document Management. File Types. For security reasons, we have changed documentManagement file types in afm-config.xml. We now support uploading the following file types: docx, xlsx, mpp, pdf, jpeg. jpg. We have removed support for: doc, xls, dwg, dwf, txt, gif, bmp, png, mp4, zip, xml, htm, html. If you have uploaded documents whose types are now not supported, those documents remain as is; however, you cannot add additional files of those types. (AD-9523, AD-9967, AD-10156, AD-10301, AD-1044)

• BIRT. Due to BIRT 4.8.0 having a high-level security issue that requires Java 11 to resolve, we have removed all BIRT-related files. (AD-9575)

• Automatic Lookup. We have resolved an inconsistent behavior when automatic lookup is enabled. (AD-8345, AD-8348)

• Notification Log View. The ab-notifications-log.axvw view now can show OnSite push notifications by selecting the AbOnSiteMobile application. The view has been renamed from "Email Notification Log" to "Notification Log." (AD-8940, AD-8925, AD-8197)

• Mail. Added mail.send.rate and mail.send.rateUnit to mail.properties to limit the rate at which Web Central sends emails without attachments to an SMTP service. Also added mail.host.sslProtocols parameter to mail.properties. (AD-9582, AD-10170, AD-3887)

• Timeout. Fixed a problem with TimeOutView not redirecting properly. (AD-9383)

• Document Fields. If you check in documents that have uses spaces in their file names, Archibus no longer replaces each space with the "+" character. (AD-9421)

• Translation. Improvements to a few translations, including the Log in button in Japanese. (AD-10421)

• Data Event Listeners. Addressed issue in data event listeners listening to changes to leases. (AD-10291)

• Data Event Log. Addressed error when clicking on SqlExecuted events in Data Events Log. (AD-9269)

• Console Views. Improved consistency of Check All function when selecting multiple items. (AD-7949)

• User Interface. Aesthetic improvements to spacing and titling of message dialogs. (AD-3845)

• Bar Charts. Addressed “_.map Object is not a function” error when clicking on bar charts. (AD-9763)

• Drawing Control. Addressed multiple executions when clearing highlights. (AD-9404)

• Drawing Control. Resolved problem with floor plans zooming in unexpectedly on some devices. (AD-7512)

• Tabs. Addressed error in tab logic depending on a previous tab, where there isn’t one. (AD-9509)

• Localization. Enable all localization languages by default. (AD-9408)

• Security. Addressed a variety of injection, library, and cross-site scripting issues. (AD-9836, AD-9674, AD-7844, AD-9306, AD-9319, AD-9321, AD-9335, AD-9337, AD-9399, AD-8757)

• Number of Buildings. Added a common property that counts the number of buildings. (AD-9860)

• Filters. Address issue using an apostrophe character in a filter console. (AD-9878)

• Extended Questionnaires. Error Message for Mixed Section. The following issue is resolved: Adding one single choice question to the Mixed Section using the "..." button of this section and then adding a Date question by using the "Add Question" button (at the top of the tab) presents an error message. As a workaround, add the Date question using the ‘…' button of the mixed section, rather than the Add Question button. (AD-4868)

• Navigator. System Administration / CAD and BIM Manager process. This process has two new tasks: Connect BIM Viewer to Autodesk, Catalog BIM Model. (AD-10334, AD-10338)

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

• Setup Console. De-supported. It is not longer part of the Smart Client installer (AD-10321)

• Smart Client Extensions for Revit and AutoCAD. Improved UI visibility on high resolution monitors.

• Smart Client Extension for Revit

  • Clear Archibus Data from Model is a new command under the Synchronization drop-down. Detaches the Revit model from Archibus completely and removes all Archibus data from the model. (AD-8473)

  • Map Database form. Using the Refresh button no longer closes the form, improving the usability when mapping parameters to fields. (AD-8455)

  • Cataloging Assets. Fixed issue that was preventing cataloging assets other than equipment (AD-9482)

  • Sign in to Project . An "object reference" error was corrected. (AD-9419)

Changes in Mobile Client and Mobile Apps

• Mobile Client 3.0. Google Play. Mobile Client 3.0 is no longer available on Google Play. Only Mobile Client 4.0. is available.

• Mobile Client. Fixed issues with launching the camera on Android versions 10, 11, and 12 (AD-10309)

• Compliance Surveys. Syncing. If the auditor has a long list of survey tasks and syncs a complete survey, they no longer see that some incomplete survey tasks disappear. (AD-7194)

• Compliance Surveys. Truncated Text. The text for a Yes/No or Multiple Choice question is now correctly displayed and is not truncated on your mobile device; you no longer need to edit the question and change the Display Format from Short to Long. (AD-6407)

• Assessments. Improved the visibility of completed items. (AD-9221)

• Asset Surveys. Added the ability to scan room barcode. (AD-7363)

• Maintenance. Work Log time error is corrected. (AD-8976)

Changes in OnSite Mobile App

• Tagging all users in comments. You can now tag any user, not just those that are in the Employees (em) or Craftspersons (cf) tables, when making a comment. This is handy for when other users (such as guests, or visitors) make requests; these users now show in the selection list for the tagging action. (ON-1038)

• Create Request. Add Photos. When a technician creates a request using OnSite, they can now add photos to the request. (ON-1033)

• Closing a Work Requests Generated from a Checklist. The following issue is resolved and applying the database script is no longer necessary: if you have to generate a new work request as an action for completing a checklist, you will encounter problems when trying to close this work request. The /webapp/projects/users/public/dt/v2022.02.003 folder contains a correction for OnSite pertaining to closing work requests that were generated as a follow-up action to a checklist question. Database administrators can apply the scripts as desired. (AD-9381, ON-971)

• Work Request List. Updating. Previous work request data was persisting in the cache and displaying in the work request list. This is no longer an issue and you do not need to pull to refresh on My Work in order to get the updated requests. (ON-733)

• Requestor section. Message icon. Android. In some versions of Android phones, clicking on the message icon did not work and the message form did not open. This was due to a bug in React Native, but is now resolved. (ON-525)

• VPA. We have improved the messaging regarding the following situation: if multiple craftspersons assigned to the same work request do not have the same VPA and if one craftsperson creates a work request from a checklist, the other craftsperson will not be able to access the work request. (ON-973)

Changes in Database

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

Changes in System

• BIRT. For security reasons, we removed BIRT report views from the product, but we omitted this change from upgrade scripts. Any views using BIRT or in the BIRT Pick-and-Place Reports process will not function, and we recommend removing them from the Navigator. (AD-9812)

• ICS and Time Zones. Resolved. The following issue is resolved: ical4j jar is used to resolve timezone information. For example, it will try to open http://tzurl.org/zoneinfo/America/New_York which is a URL referenced by the America/New_York.ics file in the jar. The response to an HTTP request to this URL will be an HTTP 302 redirect to https://static.tzurl.org/zoneinfo/America/New_York.ics which is the actual file containing timezone information.
  
  We’ve observed some implementations of java.net.URLConnection to not redirect, causing this redirect message to be processed as timezone data. This manifests as exceptions when trying to use or resolve a timezone.
  
  The workaround is to disable the feature for updating timezone data and use the information in the jar. To do this, add a text file named ical4j.properties to the root of the java classpath with the following content:
  
  net.fortuna.ical4j.timezone.update.enabled=false (AD-9432)

• Assign Processes to Roles or Users task. SaaS. This task has been updated with the following three changes to restrict access for client and partner administrators in a SaaS environment:

  • Users assigned to role 4 - CLIENT ADMINISTRATOR (ACP) are now limited from seeing Roles and Users that have the following Roles:
    
    4 - SYSTEM ADMINISTRATOR
    
    SYSTEM ADMINISTRATOR
    
    SYSTEM ADMINISTRATOR (ACP)
    
    ARCHIBUS ADMINISTRATOR
    
    4 - PARTNER ADMINISTRATOR (ACP)
    
    4 - CLIENT ADMINISTRATOR (ACP)

  • Users assigned to role 4 - PARTNER ADMINISTRATOR (ACP) are now limited from seeing Roles and Users that have the following Roles:
    
    4 - SYSTEM ADMINISTRATOR
    
    SYSTEM ADMINISTRATOR
    
    SYSTEM ADMINISTRATOR (ACP)
    
    ARCHIBUS ADMINISTRATOR
    
    4 - PARTNER ADMINISTRATOR (ACP)

  • Users assigned to either of these two roles cannot assign Roles or Users to System Administration processes. They can still see existing assigned processes and also unassign processes from Roles or Users that they have access to.
    4 - CLIENT ADMINISTRATOR (ACP)
    4 - PARTNER ADMINISTRATOR (ACP) (AD-7128)

Changes in Workplace

General

• Desktop. Open in App Button. On certain laptops with trackpads and without a mouse plugged in, Workplace formerly displayed the Open in App button, which should have been displayed only in the Workplace mobile app. (AD-9349)

• Service Catalog. Locations. When you select a location for the service request using the map and then switch to the Locations by Room Type tab, you will find that the Room Types are now listed. (AD-9009).

• QR Codes. Signing In. When you access Workplace by scanning a QR code on a meeting room, workspace, or equipment, you might not be logged into Workplace or have the Workplace mobile app on your phone. Previously, this would result in the request being created for user GUEST, and the item did not appear on your User Dashboard. To avoid this situation, Workplace now prompts you to sign in when scanning a QR code. (AD-9684)

• Maintenance Requests. Screens Displaying Request Number. For maintenance requests, the screens in Workplace that indicate a request number (such as User Dashboard / My Requests or Request Details) now show the Work Request Code (wr_id) instead of the service request number. (AD-9376)

Meeting Room Reservations

• Accessibility Mode. Fixed several UI issues for meeting room reservations on both Desktop and mobile. (AD-9555)

Desk Bookings

• Guest users. Users signed in as GUEST are now required to indicate an employee or visitor when they create a workspace booking. Guest users can no longer choose "For Myself"; instead, Workplace moves them to the “Workspace Booking: Occupants List Selection” page where they select a visitor or guest. With this change, the occupant of the booking is now captured. (AD-9018)

• Booking for Others. User Interface. We have improved the UI so that a Workplace user can more easily create a workspace booking for themselves or others and reserve space that works for any size party. (AD-10087)

• QR Codes. Resolved. Attempting to book a room that was previously booked (but is now available) using the QR code results in the room not being available. Occupiers can use the QR code to check into their booking. Also, QR code users have trouble checking into a room. For example, if the room capacity is two or more and if there is only one booking on the room, the Check-In button is not visible to QR code users. (AD-8284)

• Search for Room Type and Employee. Resolved. If you search for a room based on room type and then search for a person's location, the filter should be reset to reflect both the room type and the employee; instead, the last selected filter (in this case, employee) clears the previous filter (in this case, Room Type). (AD-9465)

• Confirmation Check-in Message. Resolved. If a booking requires that you check in, when you book the room you receive a message reminding you to check in. On an iPhone running the Workplace mobile app or browser, the check-in confirmation message is truncated. (AD-9568)

• Multiple Bookings for the Same Room. Resolved. If you have the AllowMultipleBookings parameter set to No, you make a booking, and then select Workspaces again; the recommendation shows the same room you just booked, the current date, and the option to book the room. You can go ahead and successfully book the room a second time despite the setting of the AllowMultipleBookings parameter. (AD-9283)

• Cancel. Workspace Booking Summary Page. Resolved. Select Cancel while on the Workspace Booking Summary page, and you move to the People & Places view, instead of the Dashboard landing page. (AD-9017)

Workplace Mobile App

• Hiding the Create A Service Request Button. Resolved. Setting the SelfServiceCreateRequest and KioskCreateRequest application parameters to 0 and scanning a QR code for a Room or Equipment should hide the “Create A Service Request” button; however, the button does show. (AD-8746).

• Web Browser. UI. Meeting Room Reservations. Resolved. If you reserve a meeting room and proceed to the “Meeting Booking: Name and Attendees” page, you will find that the top of the Select Employee page or Select Department pages are cut off. (AD-8598)

• Cancel Button. Resolved. On vertical tablets and phones, some form fields are not as high as other fields, creating an unbalanced look and resulting in the Cancel icon not correctly fitting. (AD-8054)

• Calendar Icon. Resolved. The calendar icon is not clickable/tappable; only the date box is clickable/tappable, which opens both the calendar dropdown and the keyboard at the same time. The keyboard blocks the calendar, making the view hard to work with. (AD-9478, AD-9479)

• Create a Request form. No longer has extra white space. (AD-8864)

• Confirmation booking pop-up. Text no longer displays outside of the pop-up. (AD-9553)

• Truncated text. When Workplace was running on Pixel 4 (chrome and app) and iPhone 12 (safari and app), several screens were truncating text. This has been resolved. (AD-8337)

Changes in Space

• Space Console. Deselecting a room. Previously, in the following sequence, the selected room would remain selected despite using the Clear button to deselect it. This is no longer an issue.
  1)In the floor plan, click on a room to select it.
  2)Highlight by a property such as Division.
  3)Invoke the Highlight form again and choose Clear Highlight to remove the highlight.
  4)On the floor plan, click Clear to deselect the room. Notice that it remains selected.
  To resolve this issue, invoke the highlight again and clear it; the room will become unselected. (AD-9368)

• Space Console. Performance. We made some performance enhancements to the Employee panel. (AD-9417)

• Space Console. Workplace Utilization report. The Space Console now launches Workplace Utilization report. (AD-10102)

• Define Buildings and Floors View (Foundations). Deleting buildings from the ab-ess-def-bl-fl.axvw view no longer takes an unreasonable amount of time. (AD-8091)

• Space Console. PDF. The Generate Ad Hoc PDF Report has been renamed to Export to PDF.

Changes in Real Property

• Global Portfolio Dashboard. Oracle. Chinese. When running this view with a Chinese local and Oracle database, the KPI session is no longer missing from the upper left corner. (AD-9403)

• Chargeback Cost Wizard. The Chargeback Cost Wizard's log file was showing a workflow rule error. This error is no longer generated. (AD-9530)

• Rent Roll Report. Filter. We have made the filter collapsible so that users can see more data in the report's grid.  (AD-8830)

Changes in Capital Projects

• Approve Bids. Under certain circumstances, you were unable to approve a bid using the Capital Projects / Projects / Procure /Approve Bids task; clicking the Approve button on this view had no action. This has been corrected. (AD-9138)

Changes in Sustainability & Risk

• Compliance. A problem with creating a work request using the Complete Questionnaire form has been resolved. (AD-10142)

Changes in Maintenance

• Maintenance Console. Group By. Collapsing. In order to improve performance, the Maintenance Console now collapses the groups when grouping is by Craftsperson or Work Order. This occurs regardless of the value of the AbBldgOpsOnDemandWork-BldgOpsConsoleExpandOnOpen application parameter. Other groupings follow the parameter setting. (AD-10380)

• Maintenance Console. Email Notifications. Attached Documents. The following issue has been resolved: If in the Manage Service Desk Steps task, you select the Work Request Issued notification step and attach documents, you will find that for work requests using this SLA step, attachments are not included in the email notification. (AD-7758)

• Labor Scheduler.Overlapping Scheduled Work. Previously, overlapping scheduled work was not shown when the view was set to show individual craftspersons. This has been corrected. (AD-8032)

• Labor Scheduler. VPA. The Labor Scheduler view no longer presents an error message when VPA is active. (AD-9998)

• Labor Scheduler. Missing Work Requests. Previously, some work requests were not shown when multiple were assigned to single craftsperson in single day. This has been resolved. (AD-8076)

• Work Requests. Tagging all Users in Comments. You can now tag any user, not just those that are in the Employees (em) or Craftspersons (cf) tables, when making a comment. This is handy for when other users (such as guests, or visitors) make requests; these users now show in the selection list for the tagging action. (AD-9515)

• Define PM Procedures, Steps, and Resources. UI Change for Checklists. The tree now shows the Checklist Name instead of the Checklist ID. This change will help users more easily locate checklists because they can see the descriptive checklist name. (AD-9353)

• Maintenance Survey Report. Multiple Response Questions. For multiple response questions, the report was showing the answers as code values rather than the text that mapped to the codes, resulting in the fact that the report was not useful unless the reader had memorized the corresponding text value for each code. This has been corrected. (AD-8792)

Changes in Assets

• Equipment Systems Console: If auto-lookup is enabled, selecting the View Full Equipment Profile icon in the Equipment detail panel produces no longer an error. (AD-8345)

• Asset Lifecycle Console. Classification Code Filter. Fixed searching by classification name. (AD-9816)

• All Asset Consoles. Smart Search Filter. Fixed Asset Status filter to work for all asset types, not just buildings. (AD-9667)

Changes in Workplace Services

Service Desk

• Service Console. Firefox. The following components of the Service Console did not work on the Firefox browser: Search button, column sorting, Smart Search filter, folding the request tree for each status. This has been resolved. (AD-9570)

Reservations

• Reservations Calendar Console. Catering and Other Resources. Previously, when you edited a reservation with catering, if you changed the selected room to another room in the same building, an error message would state that the catering is not available under the new conditions; however, the catering was, in fact, still available. The catering was canceled, but you could manually add it again. Similarly, if you added limited or unique resources to the reservation and then changed the room, those resources were also canceled; however, the system created them again under a new resource reservation id. This is no longer an issue. (AD-9651)

• Reservations Calendar Console. Multiple Room Arrangements. Previously, if you had defined multiple arrangements with different time frames for a particular room, the room arrangements were available for you to choose from the drop-down list when creating a reservation. However, you would find that when reserving a room with a particular arrangement, the times might not reflect the times assigned to the arrangement. This also occurred when making a reservation from Workplace. This is no longer an issue. (AD-9233)

• Reservations Calendar Console. Yearly Recurrence Pattern. A problem with yearly recurrence selection yielding an error has been corrected. (AD-10502)

• Reservations Calendar Console. Changing Rooms. Room calendar monitoring sometimes canceled a reservation when changing rooms. This has been corrected. (AD-9653)

• Outlook Plugin. We updated the Smart Client DLLs in the Outlook Plugin. (AD-9592)

Hoteling

• Desk Bookings. When the department's approving manager is not required to approve bookings and SendEmailtoOccupiers is enabled, the notification will now send upon booking creation, and it will be a consolidated notification for recurring bookings. In the case that the department's approving manager is required to approve bookings, then the notifications will wait for individual approvals, with individual notifications sent at that time. (AD-9250)

• Workplace Utilization Report. Highlighting the floor plan no longer produces inconsistent results. (AD-9513)

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

• SAML SSO . Customers using SAML SSO using Shibboleth SP and request-header Spring security config, who also wish to use REST APIs and/or the OnSite mobile app, will need to provision a second instance of WebCentral to support REST APIs, as the request-header Spring security config breaks JWT token authentication

• User AFM-MOD. Navigator missing some Risk applications. When you sign in as sample user AFM-MOD, you should access all applications licensed for SaaS. However, the Emergency Preparedness, Sustainability Assessment, Health & Safety, Hazard Abatement, Hazardous Materials, Waste, and Green Building modules are missing from the Navigator. If you need to see these modules when signed in as AFM-MOD, you can assign them and unassign some others. In the future, the Navigator will be able to display all modules assigned to AFM-MOD at one time. (AD-6967)

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

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)

Web Central known limitations

• 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. Sample Data. In the sample HQ project, building HQ loads as a floor plan instead of a model. This occurs because in our Forge account, we have a CAD drawing that is linked to building HQ. This will be corrected in the future. (AD-9585)

• Report Central. Charts. In order to see more of the chart, you might attempt to resize the grid panel and find that you cannot resize it. In this case, you can hide the filter, and then scroll the region to see the entire chart. (AD-9149)

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

  should be replaced by 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)

• afm_ptasks table. Missing Translation for "Configure Application Parameters for CAD and BIM" task. This task is not translated. You can enter it yourself in the afm_ptasks table using these values: (AD-10583)
  

  • Chinese: 为 CAD 和 BIM 配置应用参数

  • Dutch: Toepassingsparameters configureren voor CAD en BIM

  • French: Configurer les paramètres d’application pour la CAO et le BIM

  • German: Anwendungsparameter für CAD und BIM konfigurieren

  • Italian: Configurare parametri applicazione per CAD e BIM

  • Spanish: Configurar parámetros de aplicación para CAD y BIM

• afm_ptasks table. Missing Chinese Translation for "Define Owner's Requirements with Building Occupant task. This task is not translated for Chinese. You can enter it yourself in the afm_ptasks table using this value: 定义业主大厦占用率要求: (AD-10582)

OnSite mobile app known limitations

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

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

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

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

• UI Issues

  • On the Calendar view, team member names lack proper spacing, and names and titles are obscured by the calendar grid. (AD-10424)

  • The People and Places view has truncated text. (AD-9578)

  • Comment text does not wrap properly. (AD-10444)

• Check In. New visitors. In the Calendar view, under Workspaces Booked for Others, there is no Check In button for visitors. (AD-10536)

• Comments. On the Requests details page, it is possible to click on the Comments, not enter anything, and save. Saving an empty comment should not be possible. (AD-10439)

• Comments. It is possible for a user to edit or delete comment created by another user. (AD-10434)

• 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 ncorrect or missing data. (AD-10440)

• Tablet. Mobile browser. Meeting Space Booking Time. The following behavior was observed with Samsung Galaxy Tab A with Android 11 in portrait view: the navigation buttons cover the Time selection fields. As a workaround, turning the device to Landscape orientation and you can select values for the two fields. Returning to Portrait orientation allows the user to continue with navigation. (AD-10617)

• iPad Pro.

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

  • Application Freezes. If you are in the process of using Workplace and close the device screen, Workplace freezes and you cannot continue your operation upon your return. (AD-9469)

• Desk Bookings

  • Teams. With HotelBookingRestrictions set for Team, not all team members are shown when booking a desk. Only the names of the logged-in user and one team member are listed, the names of the other team members are not listed, nor are they found when searching for them. (AD-10674)

  • Highlighted available seats. From the Workspace Booking page, all available, hotelable workspaces are not highlighted on the floor plan. (AD-10099)

  • Department and Room Type filter. If you choose a Department filter first and then a Room Type filter, in that order, then the drawing will not show available seats. You can remove the Department filter to see available seats. (AD-10343)

  • Visitor. When you make a workspace booking for a new Visitor, the Visitor Department is not saved. (AD-9016)

  • Rooms without Room Categories. The Create and Review Bookings view may show fewer rooms available for a building than a user might expect IF rooms have been flagged as bookable but do not have a Room Category associated with them. Since hotelable rooms should be in occupiable space, and since Room Categories are required to indicate occupiable space, those users who are defining hotelable rooms will want to check that all rooms defined as hotelable include a Room Category value. In a future release the Define Hotelable Rooms view might be updated to enforce that requirement. (AD-4915)

• Booking Multiple Seats. Floor Capacity Target. 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).

• Meeting Room Reservations

  • Self-booking. QR Codes. When the 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)

  • Unavailable rooms. On the Meeting Space Booking page, a room that is completely booked on the selected date is not showing as unavailable. The room should be greyed out on the floor plan and hidden from the List view. (AD-10379)

  • Fully Occupied Rooms. Accessibility Mode.In Accessibility mode, Workplace does not correctly handle fully occupied meeting room for a specific date. (AD-10452)
  • 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

  • Skip to Available Rooms redundant message. When you access the Meeting Space Booking page, you receive the "Skip to Available Rooms" message, which is not necessary. (AD-10264)

  • Meeting Room Reservations.Today not shown. If you book a meeting room daily beginning today and then create a booking of the same meeting room for a weekly recurrence pattern with a date frame which includes some days of the previous booking, the result will not list today and will not show the proper duration. (AD-10115)

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

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

  • Meeting Reservation. You cannot change Start Time or Duration from the selected value to note; you can change only to other available Start times or Durations. As a workaround, click Cancel and start over. (AD-9554)

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

  • Icon and Title. On iPhones and iPads, the main page listing all your apps has the wrong icon and title for the Workplace app. (AD-8653)

  • Header and Footer. On iPhone 12, the header of the application is cut so that you cannot access buttons located at the top of the screen, such as "My Account" or "Cancel" buttons. (AD-7459)

  • Blank Areas. We are working on problems of extra blank areas appearing in various screens of the Workplace mobile app. (AD-8258).

  • Searching. Dismiss Keyboard. If you search and then dismiss the keyboard, the screen area that the keyboard occupied remains blank. (AD-8227, AD-8006)

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

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

• Reservations Calendar Console. Room Arrangement. If you edit a reservation and change the room arrangement, you receive an error message. Workaround: Instead of clicking on the room row, and then changing the arrangement as a second step, click first on the arrangement selection without first selecting the room, this way, you can select any arrangement. (AD-10233)

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

  • With an Oracle database, loading the building list takes over a minute to load. This is much longer than loading in other environments. (AD-10426)

  • 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. Export Drawing to PDF. Drawing Units of mm. If you are using mm as units in your drawing, when you try to export to PDF, you will likely run out of memory. To resolve this, you can increase the java heap, or use meters or centimeters as units. (AD-8717)
• 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

• Chinese Locale. Tagging in Comments. When you tag someone in a comment using OnSite or WebCentral, the system generates an email; under a Chinese 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. 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 can be prevented from using the Report Problem button. This is a result of the Report Problem button calling a second view that is not listed in a process that is assigned to the user's role. To resolve this issue, add ab-bldgops-console-wr-create.axvw to the afm_ptasks process assigned to this user role. (AD-8377)

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

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

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)
• Export Energy Star Data. This report generates an xls report instead of xlsx format. Customers using it can re enable the xls file in the configuration. (AD-10362)

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)

Archibus Extension for Lease Accounting known limitations

The following limitations will be corrected in a future release or update.

• Lease Classification Wizard. Amortization Schedule not Updated. If you change the recurrence period of a lease from monthly to yearly after working through the Step 1 and Step 2 tabs and before approving, the amortization schedule does not reflect the period change. As a workaround, you can use the BasicRules_ClearLeaseClassification.java rule to clear the classification, and then re-classify the lease.(APP-3701)

• Lease Classification Wizard. Remaining Life Question. If you change your response to the question “Does lease term exceed 75% asset’s remaining life?” from Yes to No, the Wizard does not update the Lease Classification to "Operating" until you restart the Wizard. (APP-3795)

• Lease Classification Wizard. Fair Market Value Field. If you change the Fair Market Value field in Step 2 to a value that would result in changing the Lease Classification to "Operating," the Wizard does not update the classification to Operating until after you restart the Wizard. (APP-3808)
• Lease Classification Wizard. Short-term Leases. Short-term leases and leases beneath the capitalization threshold currently are not classified with the FASB/IASB Classification status of Executory Contracts. As such they end up with amortization records and there is no option to approve them. (APP-3802)
• Lease Classification Wizard. Information Buttons. Some of the Wizard's "i" buttons (such as Residual Value, Rate Implicit in Lease, and Depreciation Period) are missing explanations. (APP-3402)
• Generate Subledger Entries for Leases. At Payment Date for Fiscal Period Field. The entry for "At Payment Date for Fiscal Period"can appear out of sequence depending on if the payment date is at the beginning or the end of the period. (APP-3759)
• Lease Classification Analysis Console. Lease Payment and Initial Lease Liability Out of Date. The Lease Classification Analysis Console and Lease Classification Details form are presenting values for Lease Payment and Initial Lease Liability that are out of date and do not reflect the classification. The views are obtaining these values from fields in the Leases table (ls.lease_payments and ls.initial_lease_liability), which are not updated by the classification process. The views should be consulting the Amortization Schedule table. (APP-3853)
• Quantitative Disclosure Report. Previous Years. The report only shows data for years 2017 and 2018. If you want to see data for other years you must modify the Start Date and End Date values in \schema\ab-products\rplm\ls-admin\fasb\reports\ab-rplm-fasb-quantitative-disclosures.js. (APP-3796)

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)