Revision History for Archibus V.2022.02

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.
What's New in Archibus V.2022.02	Summary of major enhancements and new features in Archibus applications, mobile apps, platforms, and customization. Typically, items listed in the What's New are not repeated in this topic's "Changes in this Release" section.
Database Schema Revision History	List of database changes for V.2022.02

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

• Online Help
• Web Central
• Smart Client Extension for CAD
• Smart Client Extension for Revit
• Mobile Client and Mobile Apps
• OnSite mobile app
• Database
• 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
• 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

• Legacy Move Topics. In order to streamline the online help, a series of pre-24.1 topics describing legacy tasks for processing move orders has been removed from the online help. If you are using the legacy tasks and require documentation, see the V2022.01 topic: https://help.archibus.com/user_en_v2022.01/archibus.htm#../Subsystems/webc/Content/web_user/moves/concepts/legacy_tasks.htm (AD-10207)

Changes in Web Central

• WebSphere and WebLogic. Beginning with V.26.2, WebSphere and WebLogic are not supported for new customers. For existing customers, WebLogic was tested and is compatible with V.26.3, and WebSphere was tested and is compatible with V.26.2. (AD-4875, AD-5705)

• Reports Central. If you create a report that has a chart, and has a filter on a field that is not displayed in the chart (and therefore is not part of the chart datasource), the chart now correctly updates against the filter. (AD-5927)

• Document Management for Drawings. When editing WEB-INF\config\context\remoting\webservices-smartclient\webservices.xml to set up Web Central to use an FTP server to access drawings, you no longer need to reverse the user name and password entries so that the username entry contains the password and the password entry contains the user name. This issue did not impact SFTP or FTPS. (AD-7814)

Changes in Smart Client Extension for AutoCAD

• Supported Versions of AutoCAD. AutoCAD 2023 is supported. AutoCAD 2015, 2016, and 2017 are no longer supported.

• Line weights are now supported in publishing enterprise graphics. (AD-8566)

• Simple line types are now supported in publishing enterprise graphics. (AD-8565)

• Publishing Enterprise Graphics. Graphics were sometimes offset in the published enterprise graphics that are displayed in the Space Console’s PDF and DOCX formats. This is now fixed. (AD-8353)

• XREF. Some text contained in XREF files were offset in the Space Console’s PDF and DOCX formats. This is now fixed. (AD-8415)

Changes in Smart Client Extension for Revit

• Supported Versions of Revit. Revit 2023 is supported. Revit 2015, 2016, and 2017 are no longer supported.

• BIM Explorer. Can be refreshed by right clicking on the BIM Explorer tree view and then clicking on the ‘Reload ADT’ command. (AD-8443)

• Publish to Forge Publish to Forge from Revit is for trial purposes only. Enhanced support will be included with upcoming releases.. (AD-6971)

• Map Database Fields was not backwards compatible with pre 26.2 versions of the Web Central application. This is now fixed. (AD-8370)

• Map Database Fields. Some controls Map Database Fields form were chopped on hi-res monitors. This is now fixed. (AD-8392)

• Catalog. Certain conditions would display a ‘Duplicate Key’ error when selecting a category from the Catalog form. This is now fixed. (AD-9008)

Changes in Mobile Client and Mobile Apps

• Maintenance. The problem with not being able to create more than 25 work logs (WRCF records) for a single work request has been resolved. (AD-8706)

• Maintenance. Fixed several smaller UI issues for work requests and checklists.

• Compliance Surveys. Fixed a scrolling issue that was preventing some users to complete their questionnaires. (AD-8688)

• Assessments. Fixed several issues with questionnaires that were causing questions not to be displayed, or to be incorrectly displayed with the wrong assessment item so that the user could not complete the assessment. (AD-8540, AD-9222, AD-9221)

• Asset and Equipment Survey app. Cannot see task details after editing. If you select a survey, edit a task, and then navigate back, you will no longer find that the screen is empty. (AD-7272).

Changes in OnSite Mobile App

• Problem Type. In the Create Work Request form, the x icon in the Problem Type field now clears the value in the field. (ON-732)

• Non-image Documents. When the work request has non-image document added from Maintenance Console, the All Activity area no longer shows records with a blank body. (ON-624)

• URL Documents. If you enter a URL document in the Maintenance Console/Documents and Activity/Edit Document or Web Link form, OnSite now shows the URL in the Documents & Photos section of the Work Request Details page. (ON-623)

• Virtual Private Archibus (VPA). Users with VPA with settings can now sign in to OnSite. (ON-572)

• Assign Equipment Actions. The app now follows the proper behavior for when Can Change Work Request? field is set Yes so that only appropriate users can assign, edit, or clear equipment on the Work Request details page; previously, any craftsperson could do this because the program ignored Can Change Work Request? setting. (ON-570)

• Work Requests without Work Orders. The following issue has been resolved. The correct behavior is: the app checks SLA after users enter all required request information and click the ‘Next’ button. If the SLA is not auto-approved or not auto work order, the “Self- assign” action is disabled.
  Original issue: When the application parameter WorkRequestsOnly = 0, (that is, the system should not automatically assign work requests to work orders in the background) but the SLA is not set to "Auto Work Order", the technician can still create the work request, add a work log, and complete the request. However, the supervisor will encounter an error when trying to close it. OnSite should not allow creating work requests for this case; instead, it should present a message saying the corresponding SLA does match with the WorkRequestOnly=0 setting. (ON-483)

Changes in Database

• See also Database Schema Revision History (System Management Help)

Changes in Workplace

• Accessibility Mode. In Accessibility Mode and with a screen reader active, it is now possible to select Start/End Date on the Calendar view when using keyboard actions .(AD-6101).

• Maintenance requests. No Matching SLA. Workplace now matches the Maintenance Console's behavior of reporting a problem for which If there is no matching SLA; if there is no matching SLA, you receive a message informing you that a work request cannot be created. Previously, Workplace created a work request in situations where there was no matching SLA. (AD-7472)

Desk Bookings

• Available Desks. Highlight. If the floor plan is highlighted with available desks to book, switching to List view (by using the bottom right of the floor plan) and back no longer removes the Available Spaces highlight from the floor plan. (AD-8052)

• Available Desks. Messages. We have improved the messages that the user receives when no desks are available to book. This occurs when all hotelable seats have been booked, or when EnforceFloorCapacityTarget is set to "Yes" and the floor has reached its maximum occupancy target. (AD-8097)

• Book Button. It is no longer possible to press the BOOK button several times when making a booking and thereby create multiples bookings. (AD-8122)

• Booking to be Near a Colleague. When you search for a room that is near a room booked by a colleague, you will no longer find that the marker for the colleague obscures the room on the floor plan that you wish to book. (AD-8056)

• Recommended Seats. Dismiss Message. We have improved the user interface and messaging for dismissing the recommended seat feature. (AD-7620)

• Floor List. Previously, if a floor had no available seats, the Workspace Booking screen did not include the floor in the list of floors for the building. Based on user feedback, the Workspace Booking screen now includes these floors in the floor list; this enables the user to load the floor plan if desired. A counter next to each floor lists the number of available seats on the floor; for floors at full capacity, no counter is listed. (AD-6195)

• AllowMultipleBookings. Two problems when AllowMultipleBookings is set to No are resolved. You could not create a booking for "Myself" after booking a room for a visitor. Also, multiple bookings (even for the same seat) can no longer be created using the “Recommendation” dialog. (AD-8970, AD-8961)

Meeting Room Reservations

• Room Type and Room Category Fields. If you have not completed the Room Type and Room Category fields for a reservable room, you will no longer encounter problems when trying to reserve the room. (AD-8230)

• VPA. The ApplyVpaRestrictions=false parameter now applies when creating a new reservation in Workplace.(AD-6935)

Changes in Space

• Space and Portfolio Planning Console. When there is no available area on a floor and the user has opted to hide unavailable areas, the stack plan now correctly hides the floor. Previously, the stack plan was displaying the floor with unavailable area. This resulted in the data points on the right not lining up with their representations in the stack plan. (AD-8152)

• Space Console

  • We enhanced the tree behavior to sustain the state of tree nodes after the commit. (AD-8604)

  • You can now export social distancing circles. (AD-4221)

  • If you promote a validated field to the Rooms table, the highlight will now use the corresponding highlight color defined for the validated field. Previously, the highlight indicated only whether or not the promoted field had a value. (AD-7365)

  • When you filter and then export toi XLS, the resulting spreadsheet's data is no longer obscured by a message stating a "restriction is in effect." (AD-7872)

Changes in Real Property

• Lease Console. Multi-Tab View. Previously, in the multi-tab view, when users scroll down within a tab to see all of the records the Control bar would disappear and users would need to scroll up to make it reappear. Likewise, a tab may display empty space where it had room to display additional records. These issues have been corrected. (AD-8659, AD-8658)

• Tenants Leases by Building. When you generate a paginated report, the view now correctly shows leases for which you are the tenant. Previously, the generated paginated report generated included all leases by building. (AD-2332)

Changes in Capital Projects

• Manage Condition Assessment Items. Create Service Request. This view has two changes pertaining to the Create Service Request command. The icon for "Create Service Request" is now labeled "Report Problem." Secondly, this view was previously checking for a license for the Service Desk application and not presenting the Create Service Request icon if the user did not have a license for Service Desk. The view no longer checks for the Service Desk license. (AD-8381)

• Manage Condition Assessment Items. Open in a New Tab.From the Navigator, if you selected the Projects / Condition Assessment / Assessment Manager / Manage Condition Assessment Items view and optrd to load it in a new tab, you would receive an error message. This has been resolved. (AD-3026)

Changes in Sustainability & Risk

• Flash Charts. The following Sustainability & Risk reports were using the Flash Chart control. They have been updated to use HTML charts. ab-energy-bill-prorate-column.axvw, ab-energy-bill-prorate-pie.axvw, ab-energy-bill-prorate.axvw, ab-energy-measure-and-verify.axvw, ab-gb-cert-dash.axvw, ab-gb-dash-cert-prj-compare-tabs.axvw, ab-gb-dash-cert-prj-compare.axvw, ab-gb-fp-dash.axvw, and ab-waste-rpt-amounts-by-cat1.axvw. (AD-8928)

• Define Utility Rates. A problem with an incorrect cost_unit when the user locale is not English has been corrected. (AD-7738)

Changes in Maintenance

• Maintenance Console. Completed Work. The Maintenance Console no longer displays completed work in the craftsperson's queue in the case that the work request has pending checklists and multiple craftspersons assigned; it is now removed from a craftsperson's queue when the craftsperson completes their work.(AD-8276)

• Maintenance Console. Per-Row Actions. In V2022.01, we removed the per-row action buttons for a work request. We have added this feature back by adding to each row an ellipses button that presents the appropriate actions. (AD-8193)

• Costs of Completed Work Requests. Totals in Wrong Cells. In the Costs of Completed Work Requests view (ab-ondemand-report-cost-tabs.axvw), the Accounts tab no longer presents totals in the wrong cells. (AD-7334)

• Search and Manage view. Now shows resources for archived Work Requests. (AD-8272)

Changes in Assets

• Equipment Systems Console

  • Removed incorrect reference to the 360 Viewer. (AD-8847)

  • Allow selecting equipment on the drawing viewer for floor plans published from Revit. (AD-5963)

• Asset Disposal Console. Enable Reports button in the “Evaluate Asset for Disposal” tab. (AD-7824)

• Asset Registration Console. Fixed generating floor plan PDF issues for the Asset Relationship Assignment tab. (AD-8062)

• Asset Lifecycle Console. On the Asset Registry tab, fixed showing duplicated asset records, caused by specific licensing check. (AD-7529)

• Foundations. If you sign in as a Foundations user (sample user AFM-FDN), you can now define and edit equipment standards using the new task “Define Equipment Standards.” This is available under the “Background Data & Reports” process. (AD-8251)

Changes in Workplace Services

Hoteling

• Overall Utilization by Building. This report now includes buildings that are not assigned to sites. (AD-7593)

• Define Amenities for Hotelable Rooms (ab-ht-rm-amenities.axvw) is now available as a task in the Reservations SaaS module. This view is used for defining fixed resources (amenities) to hotelable rooms. (AD-8786)

Reservations

• Outlook Plugin disabled. We have corrected a problem with Outlook disabling the Outlook Plugin because of a shutdown delay. (AD-9041)

• Outlook Plugin. We have corrected a problem with the Outlook Plugin log being written to %appdata%\ARCHIBUS\(null)\OutlookPlugin; the version number is now correctly included instead of "(null)". (AD-8640)

• From Address. Meetings with multiple attendees were being sent with the wrong "From" address, causing errors. This was an issue only in non-Exchange environments. (AD-8602)

• Reservations Calendar Console. Employee field. Automatic Lookup. If you add the automatic lookup feature to the em.name field, you can now reserve meeting rooms using the Reservations Calendar Console or Workplace. (AD-7767)

• Reservations Calendar Console. Calendar preview. The preview for reserved blocks no longer continues beyond when the Reservations would actually end. This was a display issue occurring before booking. Once the reservation was made, the correct dates were saved. (AD-5331)

• Reservations Calendar Console. Approval notifications. If the approval time expires, Archibus now correctly sends out notifications on time under these conditions: a room arrangement require an approval, the Action if Approval Time Expires option is set to Notify, and you specify a user to receive this notification. Previously, notifications were not sent out to this user until after the reservation was supposed to take place. (AD-6720)

• Reservations Calendar Console. Editing meetings. The following issue is resolved: Create a new meeting and select a room that has other scheduled meetings during the current week. Next, in the My Reservations tab, locate this meeting to edit it. The Calendar Console shows the reserved room in the room list, and the edited meeting is shown in red in the calendar. However, you might also need to see the other existing meetings in case that you want to change the times; the Calendar Console does not show these other existing meetings. (APP-6518) (AD-5827)

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

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

• Document fields. If you check in documents that have uses spaces in their file names, Archibus will replace each space with the "+" character. You can avoid this by renaming the documents before checking them in. (AD-9421)

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

• Automatic Lookup. We are investigating inconsistent behavior when automatic lookup is enabled. (AD-8345, AD-8348),

• 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: (AD-2292)
  
  font-family: "Open Sans";
  
  with this line:
  
  font-family: "Open Sans", Arial;
  
  
• 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.

• Extended Questionnaires. Error Message for Mixed Section. 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)

• 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

• Configure Application Parameters for CAD and BIM. From Smart Client, the "Configure Application Parameters for CAD and BIM" task is not set to load as Web Central view. You can correct this by using the Database Update Wizard to run a script in the /webapp/projects/users/public/dt/v2022.02.003, which sets the Task Type to "WEB URL." (AD-9381)

• 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

• 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

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

System Administration known limitations

• Security. BIRT. BIRT 4.8.0 has security vulnerabilities with a Severity of High. For a secure environment, you can remove BIRT. For details, see https://help.archibus.com/system/sysman.htm#BIRT/BIRT_Overview.htm (AD-9575)

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

• ICS and Time Zones. The 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)

• Database Update Wizard. Version-to-Version Database Update Scripts in SQL Format. When you generate sql for csv files, you may experience that the scripts do not properly separate statements.(AD-6177)

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

• BIRT reports. Pie Charts and Bar Charts. You cannot load datasource reports with pie and bar charts inside of Web Central; meaning that you cannot use VPA or pooled database connections with BIRT and pie charts or bar charts. (WC-2321)

• GDPR. Workflow rules. Workflow rules for GDPR need to be activated by running the script \dt\24.1.004\schema\sysadmin\gdpr\update-schema.duw (DB-361) (DB-362) (DB-366)
• GDPR. Filter. Name and Email fields. Sybase. The System / Archibus Administrator - User and Security / GDPR Personal Information view displays a filter console containing the fields 'Name' and 'Email'. On a Sybase database, entering more than 125 characters in one of these two filter fields will result in an error. On all other databases, these fields are set to accept up to 128 characters. (APP-4792)
• 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)

• Automatic ID Lookup. Sample department data. Those wishing to convert the sample HQ department names to numeric codes to illustrate the use of this feature should use the Basic Rule Wizard to execute this file: \schema\ab-products\common\resources\basic-rules\BasicRules_GenerateIds.java
• Automatic ID Lookup. Pkey fields.If a System Administrator enables Automatic ID Lookup (LookupID), then they should remove any primary key (Pkey) fields from the <translatable> section of afm_scmpref.preferences. Lookups do not work properly for translatable primary key fields. (APP-1500)

Database known limitations

• Database Update Wizard. Script Calls Previous Version. The v2022.02.002 script calls the localization files from the v2022.01.001 folder. This affects the following situation: if a new user purchases V2022.02, and if they want to develop their system based on schema database, and if they are using European language, they will see the non-translated English strings of 2022.02. The fix is to correct the paths in \dt\v2022.02.002\translation\update-translation-template-singlebyte.duw by replacing “v2022.01.001“ with “v2022.02.002“, and then execute the duw script. (AD-9931)

• Database Update Wizard. Additional Script. A script in the /webapp/projects/users/public/dt/v2022.02.003 folder corrects the "Configure Application Parameters for CAD and BIM" task in Smart Client to load as a Web Central view by setting the Task Type to "WEB URL." This folder also 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)

• v2022.01.001 scripts. If you attempt to run the V.2022.01.001 DUW update scripts twice, the import will fail. The issue is that the connector with connector ID “connect_dp_em” was updated and then deleted in the v2022.01.001 script folder. The workaround is to create a connector with this ID before rerunning the script. You can run the below statement in the Database Update Wizard’s preview text box, or you can create the connector through the Configure Connectors view. As long as the record exists before the script is run, the script will not fail when it is run more than one time. (AD-8621)

  insert into afm.afm_connector (connector_id) values ('connect_dp_em');

OnSite mobile app known limitations

• VPA. 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. In future releases, we will improve the messaging regarding this situation. (ON-973)

• Requestor section. Message icon. Android. In some versions of Android phones, clicking on the message icon does not work and the message form does not open. This is due to a bug in React Native, for which we opened a support case. (ON-525)

• 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. Previous work request data persist in the cache and displays in the work request list. You must pull to refresh on My Work in order to get the updated requests. (ON-733) 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)

• Closing a Work Requests Generated from a Checklist. If you have 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)

Mobile App known limitations

• Compliance Surveys. Syncing. If the auditor has a long list of survey tasks and syncs a complete survey, they might see that some incomplete survey tasks disappear. As a workaround, reset the filter in the Survey Tasks view and sync the app again. (AD-7194)

• Compliance Surveys. Truncated Text. If the text for a Yes/No or Multiple Choice question is not displayed or is truncated on your mobile device, you can edit the question and change the Display Format from 'Short' to 'Long'.(AD-6407)

• 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

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

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

• 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 not listed. (AD-9009).

• 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 without Accessibility Mode. (AD-8901)

• Desk Bookings

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

  • Confirmation Check-in Message. 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)

  • Search for Room Type and Employee. 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)

  • Multiple Bookings for the Same Room. 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)

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

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

  • Cancel. Workspace Booking Summary Page. 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)

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

  • Web Browser. UI. Meeting Room Reservations. 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)

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

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

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

  • Hiding the Create A Service Request Button. 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).

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

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

  • 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

Hoteling known limitations

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

Service Desk known limitations

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

• 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. Catering and Other Resources. When you edit a reservation with catering, if you change the selected room to another room in the same building, an error message states that the catering is not available under the new conditions; however, the catering is, in fact, still available. The catering is canceled, but you can manually add it again. Similarly, if you added limited or unique resources to the reservation and then changed the room, those resources are also canceled; however, the system creates them again under a new resource reservation id. (AD-9651)

• Reservations Calendar Console. Multiple Room Arrangements. If you have defined multiple arrangements with different time frames for a particular room, the room arrangements are available for you to choose from the drop-down list when creating a reservation. However, you will find that when reserve a room with a particular arrangement, the times might not reflect the times assigned to the arrangement. This also occurs when making a reservation from Workplace. (AD-9233)

• 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

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

• Space Console. Deselecting a room. In the following sequence, the selected room will remain selected despite using the Clear button to deselect it:
  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. Bulk editing rooms. If you select from the floor plan more than 10 rooms and attempt to bulk-edit them, the form may not display all the fields and buttons making it difficult or impossible to edit the selected rooms. When editing rooms in bulk, edit fewer than 10 rooms at one time. (AD-2711)

• Space Console. Generate Ad Hoc PDF. Large Drawings. For large drawings, such as one with an SVG size of 5590K, the report may not generate. In these cases, increase the memory, such as increasing the Tomcat memory to 2048 M. (AD-2048)
• Space Console. Employees tab. Selecting Employees. If you have a list of employees that runs over multiple pages, when you select employees and then move to "Next" or "Previous" page, the selection will be cleared. As a workaround, you can first use the "Place Employee in Waiting Room" or "Unassign" action for the selected employees on the current page, and then move to a different page to select additional employees. (AD-2741)
• Space Console. Team Space. Organization Name field. When assigning associations to teams, you will see that the Associations tab includes the Organization Name field. This is validated by the Organizational Units (org) table. To create the values for the Organizational Units table so that they are available when completing the Organization Name field, you must use the Smart Client. Create a new view that holds the org table and use this view to define your organizational units. (3052882)
• Space Console. VPA. If a user has VPA set for division or department, the user can still update an employee's location to be a room that does not belong to the division or department VPA. This can be done by:
  • Using the Space Console to drag and drop the employee to the new room.
  • Using Define Employee or Edit Employee to update the employee's building, floor, room (note that this can only be done by directly inputting the location, as the select-values list of rooms will obey VPA).

  If the user does update the employee location to a new room that does not belong to the same division or department as is set by VPA, the location change will not create a workspace transaction, and therefore the employee's change will not be recorded in history.

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

• Labor Scheduler: Some work requests are not shown when multiple are assigned to single craftsperson in single day. (AD-8076)

• 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. Email Notifications. Attached Documents. 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)
  

• 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

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

• 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

Portfolio known limitations

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

Forecasting known limitations

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

Strategic Financial Analysis known limitations

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

Sustainability & Risk known limitations

Compliance known limitations

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

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

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

Hazard Abatement known limitations

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

Waste known limitations

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

Energy known limitations

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

Green Building known limitations

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

Capital Projects known limitations

Projects known limitations

• Approve Bids. Under certain circumstances, you are unable to approve a bid using the Capital Projects / Projects / Procure /Approve Bids task; clicking the Approve button on this view has no action. We are researching this issue to determine the circumstances that result in this issue. (AD-9138)

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