Revision History for Archibus V.26.2

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
What's New in Archibus V.26.2	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.26.2
V.26.1 Update Revision History	These V.26.1 fixes are included in V.26.2.
V.26.2 Update Revision History	Archibus V.26.2 included a software update after the initial release.

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

User Help: https://www.archibus.net/ai/abizfiles/v26.2_help/archibus_help/user_en/archibus.htm

System Management Help: https://www.archibus.net/ai/abizfiles/v26.2_help/archibus_help/system/sysman.htm

Changes in Archibus V.26.2

• Online Help
• Web Central
• Smart Client Extensions for CAD and Revit
• Mobile Client
• Database
• System Management
• Mobile Apps
• Workplace
• Real Property
• Space
• Maintenance
• Assets
• Workplace Services
• Capital Project Management

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
• Mobile apps
• Workplace
• Space
• Maintenance
• Assets
• Workplace Services
• Leases
• Real Property
• Capital Projects
• Sustainability & Risk
• Archibus Extensions for BUILDERTM SMS
• Archibus Extension for Lease Accounting
• Connectors

Changes in Online Help

• Installing Help Locally. This was a change to V26.1; it is repeated in this topic for those who might have missed the original announcement. Previously, users who wanted to install Archibus Online Help locally (rather than access it from https://www.archibus.net/ai/abizfiles/v26.1_help/archibus_help/user_en/archibus.htm) would deploy it from the archbus_help.war file. We have changed the war file to three zip files holding Archibus User Help (English), Archibus User Help (Localized), and System Management Help. These zip files can be downloaded from the Software Downloads section of Eptura Allbound (https://eptura.allbound.com/my-dashboard/) or obtained from Archibus Professional Services. See https://www.archibus.net/ai/abizfiles/v26.1_help/archibus_help/system/Content/J2EE/install_help_systems.htm. (AD-6108)

• Archibus SaaS. The term "full software offering" representing a deployment housed hosted locally or by partners has been standardized to "Archibus non-SaaS" or "non-SaaS." This is a result of Archibus SaaS now offering almost all business solutions, as well as the Developer Portal. Similarly, the Help system's Table of Contents has been reorganized and Archibus Essential SaaS modules are now housed within their domains on the Table of Contents. (AD-6225)

• WebLogic and WebSphere. Since V.26.2 and beyond does not support these application servers for new customers, the help topics for these application servers have been removed from System Management Help. Existing customers using these application servers can consult Customer Support for this material. (AD-6829)

Changes in Web Central

• Home pages. The hovertip.js library has been replaced; we advise that you re-publish your home pages for all roles.(AD-6245)

• WebSphere and WebLogic application servers. Archibus V.26.2 and beyond does not support the WebLogic and WebSphere application servers for new customers. (AD-6829)

• Reports Central. Currency and multi-units are now implemented yet for Reports Central. The filter now converts units; you no longer need to adjust the comparison numbers by required factor. (AD-5807)

• Security updates. Multiple third-party libraries updated to latest and most safe versions.

• REST APIs. Support for relative operations (AND/OR) in filter parameters (AD-6224). Also, now correctly accepts dates and times formatted in ISO 8061 format and parses them. (AD-4502)

• Forms. Until V.26.2, form fieldsets always displayed labels to the left of fields. V26.2 can display labels on top of fields. (AD-6352)

• Grid. Fixed V.25 bug: Category Grid v3 was querying data for each category twice if categoryCollapsed=false. (AD-6229)

• Floor plan. Redline Text tool correctly increases or decreases text size for the next Text redline. Text display is improved. (APP-7467)

• Core: Fixed V.25 bug in which you could not configure symbolic link for the projects/users folder. (AD-6361)

• Eclipse. New Eclipse distribution.

• Default Home page. A problem with the By Building location granularity on the default home page has been resolved. (AD-6009)

Changes in Smart Client Extensions for AutoCAD and Revit

Smart Client Extensions for AutoCAD and Revit

• Fix: Slow connections may cause publishing enterprise graphics to timeout. A new CloseTimeoutSeconds smartclient.common.dll.config parameter has been added to help alleviate this timeout condition. (AD-5368)

Smart Client Extension for Revit

• Enhancement: Revit parameter mapping to Archibus standards is now supported. Mapping is now more granular down to the Category and Family level. (AD-5471)

• Fix: Certain Revit models would publish room labels outside of the floor. (AD-5753)

Smart Client Extension for AutoCAD

• Enhancement: Improved appearance of Asset labels in the Space Console. Will honor the Text height, position, and orientation as exists in the AutoCAD drawing. (AD-5887)

• Fix: Color override for publishing enterprise graphics. (AD-4061)

• Fix: Some ellipses that were published to EMF would not be rendered properly (AD-6239)

• Fix: Some DWG files that were created by a non-AutoCAD application would create visual defects in the published SVG file. (AD-6344)

Changes in Mobile Client

• Mobile Client 4.0. Mobile Client 4.0 removes reliance on Google AppCache. This fixes some user experience issues such as: being able to load the apps screen, being able to go back to the apps screen. This also aligns with Google's plans to stop supporting AppCache beginning in October 2021 (AD-5816)

• Archibus Logo. iPhone 6s. Resolved: After installing the mobile client and then checking it in the mobile screen, you will notice that the Archibus logo is missing from the mobile client icon. Also, the logo shows and hides after you open and close the client. This is happening on an iPhone 6s plus with iOS v14.4. (AD-5893)

Changes in Database

See also Database Schema Revision History (System Management Help)

• Room Amenities table. The DUW changes the structure of the Room Amenities table (rm_amenity), keeping the data records. In order to do so, it creates resource standards (resource_std records) from the amenity types (rm_amenity.amenity_type). Administrators may want to review the newly created resource standard. (AD-6092)

• Database Update Wizard. Workflow Rules. The following issue is resolved: The DUW may fail if certain scheduled workflow rules are running at the same time as the update process. To prevent these failures, use this process:
  1. Set core.runScheduledRules=false in WEB-INF\config\core.properties.
  2. Start the application server.
  3. Run the Database Update Wizard.
  4. Set core.runScheduledRules=true.
  5. Restart the application server. (AD-3908)

Changes in System Management

• Edit Data Dictionary. Fixed: PDF and XLS buttons that did not work in Edit Data Dictionary view. (AD-6115)

• Installation: 26.2 WAR file includes sample HQ drawings and enterprise graphics files under the projects/hq folder. In production deployments, these files should be removed.

Changes in Mobile Apps

• Assessments app. The Project Name is no longer blank and displays the correct value. (AD-5651)

• Maintenance app

  • Easier to scroll in the Problem Type screen. (AD-6094)

  • Fixed scrolling Work Requests for Issued work requests. (AD-6044)

  • Maintenance mobile app. A problem when scrolling in the Create Work Request / Problem Type pop-up has been resolved. (AD-6094)

Changes in Workplace

• Booking desks with status "Do not use" are now not available for booking today or in the future. (AD-5343)

• Unsubmitted and unscheduled Work Requests are no longer shown as Scheduled by the visual progress indicator. (AD-5439)

• VPA irregularities corrected. (AD-2602)

• Corrections to Spanish translation of UI components. (AD-6070)

• When running Workplace on a phone in portrait mode, you can now access the Book a Working Space button. (AD-6237)

• Improvements to label size when zooming. (AD-6091)

• A problem with space that is available in the future not being reservable has been resolved. (AD-5742)

• A URL in the form of "/workplace/?action=servicerequest&eq_id=" was not working with SSO. This has been resolved. (AD-5974)

Changes in Space

• Space Console. Query Search. If the search string contains “AND”, such as “R AND D”, the search now returns the correct results. Also, Division/Department query search for accent characters, such as française, or été, now returns results. also, the special character, “-”, is now supported. (AD-5206, AD-5337, AD-5964)

• Space Console. Query Search. Employee search. Oracle. Employee search now supports the case-insensitive search. (AD-5949)

• Space Console. Selection indicator. In the Detail panel's tree node or record row selection, the Space Console now highlights in yellow the selected item, similar tp the behavior of selecting floors. (AD-6052)

• Space Console. Border highlights. Previously, after changing highlights or labels you would find that the highlight borders disappeared, but the rooms remain selected. This has been corrected such that the borders shown around selected rooms are maintained. (AD-5970)

• Space Console. Employee moves. Previously, if you move an employee and committed, the floor plan did not re-load. This has been corrected. (AD-6616)

• Space Console. Waiting Room. We have clarified the text on the Waiting Room's Commit dialog. Also, we have improved the waiting room behavior such that when the employee is placed in the waiting room from the Employee panel’s "Place to Waiting Room" action, the corresponding employee label is removed from the room on the floor plan. (AD-6199, AD-5488)

• Define Locations

  • Building Spec label issues (AD-6233)

  • Edit Building form does not save changes to the values of the fields in the "Other Fields" group (AD-6141)

  • Saving new building does not refresh grid (AD-5987)

• Move views

  • Automatic Lookup problems resolved. (AD-1288)

  • Workspace Transaction start date (mpct.date_start) is kept in sync with move date(mo.date_to_perform) during the move process. (AD-784)

• Move Console

  • Messages now point to the Move Console instead of obsolete ab-mo-examine-form.axvw, which no longer exists in the product. (AD-5008)

  • Group Move that include a New Hire are now able to be issued. (AD-5332)

  • Group move problem when workspace transactions enabled is corrected. (AD-5544)

Changes in Real Property

• Lease Portfolio Console. Add Option form now warns and prevents the lease administrator from entering duplicated options for the lease. (AD-5002)

• Lease Portfolio Console. Fixed Data Transfer errors when adding new leases (AD-4749)

• Missing Translation. The "More Reports" divider task under the Cost Reports process of the Leases module (AbCloudLeases. Reports Costs More Reports) is no longer missing a translation in the database. It is no longer necessary to run update-translation.duw from the 26.1.005 dt folder to obtain the translation. (AD-5915)

Changes in Maintenance

• Maintenance Console.

  • Performance . Enhancements include initial loading, refreshing, expanding a group, opening the work request details, opening the schedule popup. (AD-6019)

  • Add Parts. When users typed their parts instead of selecting from the form, the system would not warn if the parts were not available. We have made UI enhancements to address this issue and to present a warning message. (AD-4861)

  • No longer allows conflicting statuses on a work request. (AD-5787)

• SLA. Duplicate email. For SLAs that included notifications on the Complete and all the On Hold statuses, duplicate emails were issued. This has been corrected. (AD-6615)

• Labor Scheduler. Problems with the work team filter have been resolved. (AD-5184)

• Manage Service Level Agreements. A problem with SLAs that had multiple problem types has been corrected. (AD-6075)

• Notifications. Problems with formatting of notifications have been corrected. (AD-6170)

• Messaging. Messaging and UI improved for cases when users have selected more parts are selected than are available in inventory. (AD-4861)

Changes in Assets

• Define Equipment Standards view. Highlight Pattern-Acad field. The view now includes this field. This enables Asset Managers and Maintenance Managers to set a specific highlight color to each equipment standard, to be used for floor plan highlights or in the View Equipment Plan report. (AD-6142)

• Telecom Console. Connecting an item to itself. The following issue was fixed in V.23.2, but erroneously remained in the Known Limitations list until now: In the Telecom Console, do not link a piece of equipment or its port, jack (faceplate or jack code) or patch panel (panel code or panel port code) to itself. Doing so results in the Archibus Web Central page locking and the Archibus web server entering into an infinite loop of querying for the next step in the connection chain.(APP-4704)

Changes in Workplace Services

• Hoteling. Bookings for a Date Range report. Resolved: In the report's Bookings grid, the horizontal scroll may not work if you display too many columns. Keep the number of columns to a minimum resolves this. (AD-3300)
• Hoteling. Room Status. Rooms with a Room Status of "Do Not Use" are not available for bookings today or in the future. Previously, these rooms were available for future bookings. (AD-5343)
• Reservations Calendar Console. View Employee Schedules. O365 Exchange. Resolved: When running with O365 Exchange, you might experience inconsistent behavior with the View Employee Schedules feature of the Reservations Calendar Console. For example, you might the schedule for a second booking does not display immediately, or the attendee schedule displays only once the room is reloaded or the environment is restarted. Note that this does not occur with Exchange 2016. (AD-3040)

• Reservations Calendar Console. Smart Search grid filters. Corrected Smart Search grid filters for time fields which were not working. (AD-4039)

• Reservations Calendar Console. Comment field. Fixed the issue of losing content of Comments field when editing reservation.(AD-6310)

Changes in Capital Project Management

• View Work Packages Scorecard . Oracle. The ab-proj-work-packages-scorecard.axvw view no longer produces a workflow error when clicking the cells in the dashboard. (AD-6119)

• Project Management. Project creation.. A problem with creating new projects using the ab-project-edit.axvw view when the environment is not configured to send email has been corrected. (AD-6178)

Changes in Sustainability & Risk

• Extended Questionnaires. Editing Section Details Hides Answer Options. Resolved: If you add a new section type with answer options (Single/Multiple/YesNo/PassFail), save the section, add and save a question, and then edit the section, you will find that the answer options do not display for editing. Workaround: If you select Back and select the Section's In-line Edit option again, the Answer Options do display and can be edited. (AD-5736)

• Define Compliance Questionnaires. Lookup Fields. When defining a lookup field question, you will now see that the form has red asterisks for the "Lookup Table" and "Lookup Field" fields to remind you that these fields must be completed.(AD-6263).

• Track Incident Witness. Automatic Lookups. An error when opening the Track Incident Witness view if Automatic Lookups was enabled has been resolved. (AD-6375)

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)
• 26.2 Features. The 26.2 features have not yet been updated in the corresponding help topics. The help will continually be updated with this material. (AD-5462)

Archibus SaaS known limitations

• Home Page Publishing. Cloud Partner Administrator. If you sign in as a cloud partner administrator (such as sample user AFM-BP), run the System / Cloud 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)
• Mobile security groups and schema database. System administrators need to add the %MOB security groups to the afm_groups table in a blank schema database. (AD-7147)

Web Central known limitations

• Reports Central

  • Although you can choose to filter on a time field (in the afm_fields table, the Data Type is "Time"), the generated chart does not reflect this filter. (AD-5919)

  • 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 does not update against the filter and you receive a workflow rule error message. (AD-5927)

  • It is not possible to add a chart to a report if the filter for one of the columns is set to 'is not blank' or 'is blank' (for example, a report on the Work Requests table where the filter is Building Code is not blank). This action will present the "Workflow rule failed" error message. The workaround is to use a different type of filter (ex. Building Code is any of a list of values), or remove the filter.(AD-6642)

  • When creating reports from SQL views (such as All Work Requests) and using a filter on a validated field (for example, Building Code), you will find that the Select Value list is not available. You will need to type your value instead of selecting it from a list; for example, you must type "HQ" for the Building Code field. (AD-6606)

  • On the chart, date fields are displayed formatted as timestamps. (AD-6415)

• 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 new V.25.1 user interface, 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)
• 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

• 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)
• Highlighting commands. 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. SWF and EMF do not support arrows or text with the leaders. SVG-- only solid arrows are supported. (3044919)
• Drawing Publishing. 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)
• Drawing Publishing. 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)
• Drawing Publishing. AFM_NET_LISP "Publish" command ignores the viewWindow attribute when the publishType is EMF and the generated file is published to extents. (SMAR-737).
• Drawing Publishing. 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)
• Drawing Publishing. 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)
• Drawing Publishing. 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

• Map Database Fields. Map Database Fields displays an error when saving with a non-English Revit Category. (AD-6721)

• 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)
• Number. 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 command. Is intended to work on rooms, furniture, and equipment; but does not provide additional information for other asset types, such as gross, group or suite areas. For these elements, use the Edit Data dialog to display all relevant properties. Also, 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. Visibility. While the Extension does filter for visibility, in some cases, invisible lines -- such as walls that are visible but hidden by a floor element -- show in any case. The very first entity in a Revit model or AutoCAD drawing is not published to the SWF file. This condition is typically only noticeable in very small test drawings. (3035308, 3034839)

• Publish Enterprise Graphics. Colors. Since Revit floor plan don't 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 and 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)
• Edit Data. Rooms. Some objects in linked models are not correctly picking up room codes of the rooms they are inside of. (SMAR-785)

• Edit Data and 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)

• Edit Data and 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)
• 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

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

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

• 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)
• Solution Templates. Calendar control. The Reservations Calendar example records multiple days for one-day events. (WC-3237)
• 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)

Mobile App known limitations

• Workplace Portal app. Photos. You can add photos to various types of service requests (copy, maintenance, move, space, furniture). However, when you save the request and the system syncs, the system does not save the photos as documents. Thus, when you click on the request after saving, click the Document button, and check the Document form, you will find that there is no image. (3047424)
• Space Book app. Space Survey Form. Space Survey Form does not automatically save data. red lined images or documents entered by auditors. Auditors can save changes only by tapping on the Complete button. Note that this behavior does not apply to the Space & Occupancy mobile app. (MOB-551)
• Hazardous Materials app. If you add new material and then examine the highlighted floor plan, the highlight will not include the room for which you just entered material until you sync. (3047744)
• Compliance Surveys app. 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. (MOB-548)

• Compliance Surveys app. 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 app. 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 app. Loading records. iOS. From the My Work screen, if you have more than 25 records to load and want to use the Load More button, you may find that you cannot access this button. This happens with only some HQ sample users, and does not happen on Android. (AD-5892)
• Maintenance app. Changing the problem type. When a craftsperson's Can Change Work Request field is set to Yes, they receive an error if they try to change the value of a work request's Problem Type field from the mobile app. As a workaround, create a new work request with the desired problem type. (AD-5865)
• Maintenance app. 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 app. Stopping work. Supervisors cannot stop a work request that has a pending checklist. (AD-4883)
• Maintenance app. 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 app. 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.(3049202)
• Maintenance app. 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 app. Upgrading. If you are upgrading from a pre-21.3 version and you have existing service requests or work requests that do not have a Building Code value, then you will encounter a problem. A workaround is to edit the records from Smart Client or SQL and provide a value for the Site Code and Building Code fields. (3045895)
• Maintenance app. 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 app. 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 known limitations

• Camera

  • On some Android devices, when you capture a photo for a request, the camera cannot be switched to rear-facing mode when it is set to front-facing by default. (APP-7373)

  • Photos captured by camera on some devices are not displayed in the Request Details view in Workplace. However, the stored photos are still viewable by the supervisor in the Maintenance Console and Service Console. (APP-7414)

• QR scans. If in security.properties, you set security.restrictLoadingOfUnassignedViews=true, you will not be able to use the QR code scanning features to access Workplace. (APP-6039)

• Workspace bookings. 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 may be updated to enforce that requirement. (AD-4915)

• Workspace bookings. Requests. Add Visitor The Add Visitor sequence does not allow selection of all departments at the site. (APP-5835)
• Workspace bookings. Availability highlight. When switching from the floor plan to the Room List and back to the floor plan when Department Highlight is checked , you will notice that the room availability highlights do not display and the floor plan highlights only the departments. (AD-6565)
• Reservations and Workspace bookings. Buildings without Floor Plans. For both Meeting Space reservations and Working Space reservations, there is a toggle between the floor plan and list view. If you define rooms as reservable meeting spaces or hotelable working spaces, then the list view should show the available spaces in list or card format, even if no floor plans are uploaded for the building. However, if the building is missing floor plans, the list view erroneously shows no results. (APP-6852)
• Reservation requests. 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)
• Reservation requests. 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)
• Reservation requests. Oracle. New Visitor. When running under Oracle on the sample HQ project, if you reserve meeting space, add attendees, select New Visitor, and enter a name, the system does not save your entry. This is a result of a problem with the auto-number sequencing in the Oracle HQ sample database in the Visitors table, and affects demonstration only on Oracle. It does not affect new projects you create. To prevent this error, re-run the Sample Data DUW script on Oracle.(APP-5848
• Reservation requests. Meeting organizer. When choosing a Meeting Organizer, you will find that only employees with a permanent seat assignment at the site are shown as options. (APP-5834)
• Reservation requests. Recurrence pattern. Workspace reservations do not show recurrence pattern in the details view. You can only delete a single occurrence at a time. AD-835)
• Requests. Show More button. If Workplace is displaying all requests, it still presents the Show More button. The Count value next to the Show More links are not accurate (APP-5755)
• Requestor photos. The QR scan Room page Request list shows requestor photos that do not match the requestors. (APP-5884)
• Move Requests. Add new employee. Department list. When a department manager uses the Add Employee button (accessed from the Department List "Edit" icon), the system creates a Move Request for the new employee. Users might expect the employee to appear in the department list at this time since they have specified a department. However, the specified department is stored only in the move request. Once the move is approved, the system will update the Employee record with the department and the new employee to appear in Workplace's department employee list. (APP-4655)
• Move requests. Description field. After you create a Move Request, the request appears on Workplace, but with an empty description field. (APP-4842)

Space known limitations

• Space Console. Export Floor Plans in Floors list to PDF. The "Export Floor Plans in Floors list to PDF" option is exporting all floor plans in the project. A workaround is to use Quick Search to locate the floor plan then export it. (AD-6703)

• Space Console. Duplicate Entries on Legends. Under the following conditions, you can receive duplicate entries on the Legends menu (such as two entries for Vacant): filter on a criteria, load a floor plan, and access the Legend menu; the Legend shows the item by which the floor plan is highlighted. Next, move to the floors list and click on a floor. When you return to the legend, you will see that it now presents duplicate entries. (AD-3510)

• 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 action types using the Space / Moves / Background Data / Define Action Questionnaires task. (3028382)

Maintenance known limitations

• Problem Type Change. Updating Due Date. When you change the problem type of a work request to a problem type that is governed by a different SLA, the work request keeps the due date from the original SLA instead of clearing the due date or resetting it based upon the new problem type. (AD-5881)

• Craftsperson sample data. There are many records in Craftspersons (cf) table of the sample HQ project which do not have email account, and also many have duplicated email account 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 and click the Forward button, select supervisor, you will see all employees instead of all cf.is_supervisor=1 (AD-6744)

Assets known limitations

• Manage Equipment and Standards. Does not show Equipment records without associated Equipment Standard; likewise, it does not show new Equipment Standard records without associated Equipment records. The recommended best-practice is to assign equipment standard when creating equipment. (AD-4653).

• Purchase Price. Visibility. Ownership Transactions.The consoles display the Property and the Building Purchase Price from the Ownership Transaction (ot) table. If you have entered the purchase price data directly into the Properties or Buildings table, you will need to create an ot record in order for the value to display in the Asset Management and Enterprise Asset Management consoles. For steps to do so, see the "Entering Ownership Information" section of the topic Enter Information for Buildings, Structures, or Land.

• Equipment Systems Console. Queries and Traces. Multiple drawings are not supported. (APP-216)
• 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. (APP-4187)

• 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) (APP-4192).

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)

Workplace Services known limitations

Reservations known limitations

• Reservations Calendar Console: Scheduler does not display reservations. When you create a meeting for a configuration with multiple arrangements and select arrangement that is not the default, you will encounter an error and the Scheduler will not display your reservation . (AD-5871)

• 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. Slight time inaccuracy when extending or decreasing a meeting time. When working with Chrome when zoomed to a non-100% value, you may find that if you enter a meeting time and then change it by a small increment, such as 10 minutes, the new time is not accurate. For example, if you change a meeting end time from 9:00 to 8:50, the meeting may register as ending at 8:51. This is due to an issue with the use of jQuery version 3. This is not an issue when running on the Firefox or Edge browsers. (APP-6981)
• 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. Editing meetings.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)
• 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)
• My Reservations. Outlook Plugin. 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)
• 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)
• 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.

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)
• Determine Ordering of Service Level Agreements. If you group PM or corrective maintenance SLAs, the "Determine Ordering of Service Level Agreements" view should display these grouped SLAs on a single line; the Grouping field (helpdesk_sla_request.grouping) should be set to the same value so that they can be edited and managed together. This behavior is described in https://www.archibus.net/ai/abizfiles/v25.1_help/archibus_help/user_en/archibus.htm#../Subsystems/webc/Content/fim/on_demand/sla_grouping.htm. However, the items are not listed on one line. (AD-1998, AD-4253, APP-3774)

Real Property known limitations

Portfolio 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

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)

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)

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)

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

Capital Projects known limitations

Condition Assessment known limitations

• Manage Condition Assessment Items. Open in a new tab.From the Navigator, if you select the Projects / Condition Assessment / Assessment Manager / Manage Condition Assessment Items view and opt to load it in a new tab, you will receive an error message. As a workaround, do not open it in a new tab and it will properly load. (AD-3026)

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)
• View Projects Map. In the Project Map, in order to see action items by room, you must associate your action items with a room in the Extension for AutoCAD and then publish the asset data to enterprise graphics. To display action items in the Projects Map:

1. Start the Extension and open the Archibus project and drawing for the action items you wish to display in the Projects Map.
2. Use the Set Asset Layer command to change the current layer to activity_log / Action Items.
3. Draw a polyline inside the room asset symbol for the action item. For example, draw a rectangular polyline inside the boundaries of room 107 to associate the action item with that room.
4. Select the Archibus Attach to Record command and select the polyline you just created.
5. In the Attach to Record dialog, select the Action Item you wish to display in the Projects Map and click OK.
6. Repeat steps 3 through 5 for each room and action item you wish to map.
7. Save the drawing and run Publish Enterprise Graphics
8. Copy the enterprise graphics to your project (e.g. to \projects\hq\enterprise-graphics\).

Extensions for BUILDERTM SMS known limitations

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

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)