Revision History for Archibus V.24.2

Included in this topic are known limitations and fixes to programs and applications.

Also see:

• What's New in Archibus V.24.2 for a description of enhancements and new features in Archibus mobile apps, business applications, platforms, and customization.

Note:. While the documentation provided with V.24.2 gives a complete overview of the V.24.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 an updated version of the latest help on an official DVD, please request a DVD from Customer Support.

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

Changes in Archibus V.24.2

• Archibus Web Central

• Environmental & Risk Management

Known Limitations of this version of:

• Archibus Help
• Archibus Cloud
• Mobile Framework

• Archibus Web Central
• System Administration and Technologies
• Archibus Smart Client
• Archibus Smart Client Extension for AutoCAD
• Archibus Smart Client Extension for Revit
• GIS
• Connectors

• Archibus Extensions for BUILDERTM SMS
• Archibus Extension for Lease Accounting

• Archibus Workplace
• Archibus mobile apps
• Real Estate Portfolio Management
• Capital Project Management
• Space Planning & Management
• Asset Management
• Building Operations Management
• Environmental & Risk Management
• Workplace Services
• Reservations Plugin for Microsoft Outlook

Changes in Archibus Web Central

• HTML Charts. Suffix. Charts now display "B" as the suffix for billions unit instead of "G", as in previous versions. (WC-3332)

Changes in Environmental & Risk Management

Energy Management

• Enter Bills. IE9. The following issue was fixed in V.24.1, but was not removed from the Known Limitations until this release. If you select a bill that does not yet have any bill line items added to it (or create a new bill) and add any line item to the bill, you will receive an error when you re-select the bill itself in the tree drill down. The work-around is to either select a bill that already has line items, or refresh the tree from the “Show” button in the filter before re-selecting the Bill after entering a line item. This is only an issue for IE9. (APP-5268)
• Configure Bill Processing. Excluded Bill Types. The following issue was fixed in V.24.1, but was not removed from the Known Limitations until this release. When the Configure Bill Processing view's "Check for monthly bills" is set to "Yes," users may select and save one or more selections for "Excluded bill types." However, upon re-opening the Select Value dialog for "Excluded bill types," the list will appear empty even though the previously saved selection is in the database. To modify an existing selection, one may choose the "X" to clear the Smart Search Console restriction, in which case the full list of available values will appear, albeit without the previous selection. Or, edit the field directly and type the value 'none', click Save; the selections will be deleted.(APP-5263)

Archibus Help known limitations

• Non-English V.24.2 help. For V.24.2, the online help has not yet been localized. When using a non-English version of Archibus V.24.2 and accessing the online help from the Archibus programs, you receive the localized version of V.24.1 online help that corresponds with your locale. When the translated V.24.2 help systems are available, they will be uploaded to the appropriate locale directory at https://www.archibus.net/ai/abizfiles/v24.2_help/archibus_help/user_<locale>/archibus.htm and will replace the localized V.24.1 help systems. (DOC-107)
• Trouble accessing topics. The online help systems located on archibus.net (https://www.archibus.net/ai/abizfiles/v24.1_help/archibus_help/user_en/archibus.htm and https://www.archibus.net/ai/abizfiles/v24.1_help/archibus_help/system/sysman.htm) are continually updated with late-breaking additions, clarifications, and fixes. After Archibus uploads a new version of the help systems, users might have trouble drilling down into the Table of Contents or accessing topics from the search results. Deleting the browser's cached information resolves this issue.
• Internet Explorer. Table of Contents. On IE9 in compatibility mode, the help system's Table of Contents properly aligns the icon with the text on long entries. However, if IE9 users turn off compatibility mode, the Table of Contents displays incorrectly.
• Internet Explorer. Searching. When you search and then choose a topic from the Search Results. the system correctly goes to the topic. However, if you now choose the IE Back arrow to return to the Search Results, the help system displays its home page. Choosing the Back arrow again brings you to the Search Results. This is not an issue for IE 11.(3039554)
• Internet Explorer 9. Process Navigator's Help command. On IE9, right-clicking on a Process Navigator role or process in Web Central does not call the corresponding help topic for this process or role. Instead, you receive the home page of the help system. You can then use the Contents, Index, or Search features to move to the appropriate topic. This is not an issue for other browsers. (3039160)
• Google Chrome v20. The search highlight will not show in the topic unless the help system is on a server. Also, if you run Web Central on Google Chrome v20, the Help window does not display correctly. Updating to Google Chrome v21 solves the problem. (3036825)
• Google Chrome. Navigation buttons. If you call Archibus Help from Web Central using the Help command or from the Process Navigator or a navigation page, the Back and Forward Chrome navigation buttons do not display; thus, as you jump to various topics, you cannot use the Back button to go to a previously-viewed topic. As a work-around, you can use the right-click Back and Forward commands. Or, instead of accessing the Help system from Web Central, create a bookmark for the help system's URL and use this bookmark to access Archibus Help. (3043685)
• Running Help Systems in browsers with debug settings turned on.You may encounter error messages when running Archibus Help and System Management Help if your browser is set to debug mode, such as IE users turning on Tools->Internet Options->Advanced->Settings->Browsing->Display a notification about every script error. If you clear these types of settings, the help systems will run without presenting error messages (3039524)

Archibus Cloud known limitations

• AFM-CAD user. License. For the sample CAD specialist user AFM-CAD, the "Use CAD/BIM License" option is set to "No". As a post-deployment manual step:
  1. Log in as ADMIN, and load the "Add and Edit Users" view.
  2. Click on AFM-CAD user, and change the "Use CAD/BIM License" option" to True.
  3. Flush cached accounts. (DB-431)
• Smart Client. Define Locations view. In Smart Client running on Archibus Cloud, selecting the Define Locations view presents an error message. As a workaround, select this view from the Cloud modules: Maintenance, Space, Assets, Reservations.(DB-399)
• Home Page Publishing. Cloud Partner Administrator. If you sign in as a cloud partner administrator (such as sample user AFM-BP), run the System Administration / Archibus System Administration / 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 Administration / Archibus System Administration / Add-In Manager / Publish Home Pages by Role to publish home pages after modifying them.(APP-6426)
• Reservations Cloud module. Reservation Reports bucket. On Edge and Firefox browsers, the Applications / Reservations / Reservation Reports bucket displays an extra empty page. The issue does not occur in Chrome.(APP-6588)

Mobile Framework known limitations

• Locations Services. Android. On Android, the Mobile Location Services work only when you are connected to a secured (https) Archibus domain. This is due to the facts that the Android Mobile client uses a WebView based on the Chromium browser engine and relies on the Chromium browser location services to obtain the location of the device, and the Chromium browser requires that the domain is secure in order to provide the Location service. (MOB-370)
• 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. (3045646)

• Localizing mobile apps. If you want to translate the mobile UI into your own language, such as Portuguese, you follow the same process as documented for Web Central but rename the file generated by the localization kit from lang_xx.js(where xx is a number like 01, 02 ...) to lang_lc.js (where lc is the locale code). For example, if you want to add a Portuguese locale of pt_PT, the localization kit will generate a file for the mobile device such as lang_01.js. This file should be renamed to lang_pt.js. Also note that it is not possible in mobile to have different UI translations for different regions of the same language (such as French Canadian or Spanish Mexican), although this is supported in Web Central. (3046373)

• Windows Mobile 8. Drawing Display. The Windows 8 browser is slow for SVG display and the available devices for Windows Mobile 8 are slower than those available for Apple iOS and Android. If your site uses drawings with Windows Mobile 8, change your publishing routines to publish the minimum information needed for field work. For instance, the SRL drawing published with building outlines and room outlines only performs adequately on a Nokia Windows Mobile 8 phone. The same SRL drawing with all wall lines, door lines, and plan lines is too slow to use. This condition is likely to change, as Windows Mobile 10 uses a more performance browser and Windows Mobile 10 will support phones and tablets with performance in the same class as those available for Apple iOS and Android. (3047583) (3047951)

• Windows phone HTC. Building labels on site maps. Site maps do not display building labels until the user taps the building on the site map. As a workaround, if you cannot see the labels on the map, use the list of the site's buildings. (3047979)

Web Central known limitations

• Google Maps. When opening a Web Central view configured to consume Google Maps data, (for example, the Standard Leaflet Map View > Simple Map - Google ab-leaflet-google-map.axvw), you may encounter the error message: "This page can't load Google Maps correctly." Google made some changes effective June 11, 2018, such that all Google Map API calls now require a Google Maps API key. Some changes will be necessary for clients who have implemented Google basemaps within the Standard Leaflet map control. Any Web Central views that use the Stand Leaflet map control Google basemaps option will require the following change to the Google Maps API reference in the corresponding view AXVW: <js url="//maps.google.com/maps/api/js?key=YOUR_API_KEY" />, where YOUR_API_KEY is your Google Maps API key. (WC-3008)

• MS Surface laptops with touch screens. Certain events on certain specialized forms (for example, dragging a reservation) work with the touch pad and with the mouse, but do not work with the touch screen on MS Surface Laptops. The behavior of the events differ between browsers (e.g. between Edge and Chrome). (APP-3310, APP-3312, WC-2494)

• Scroll by swiping. MS-Surface Pro Windows 10 with touch screen. Under both Edge and Chrome, you cannot scroll grid views vertically and horizontally by swiping. The workaround is to disable the custom scroller. To do so:
  
  Modify {WEB-INF/config/context/controls/view/controls-view.xml by setting:
  
  <property name="useScroller" value="false"/> and restarting the application server. (WC-2493)
• Fonts are difficult to read. Each version of Windows handles fonts slightly differently. If text looks odd and is difficult to read, do the following:
  
  1. In Windows Explorer, go to Control Panel / All Control Panel Items / Performance Information and Tools
  
  2. Click "Adjust Visual Effects."
  
  3. The "Performance Options" dialog appears. Ensure that the "Smooth edges of screen fonts" check box is checked.
  
  (In Chrome browsers, after applying the setting, you may need to clear cache, close, and reopen the browser in order for the changes to take effect. In Firefox, the changes are applied immediately.) (WC-2793)
• Hatch patterns. Defining. In the Set Highlight Pattern form, if you set a “true color” option for a hatch pattern, you can only set the color once, and cannot change it. The workaround is to edit the "true color" hatch pattern colors using Smart Client. (WC-2226)

• HTML Gantt Control. Filtering by specific dates does not work as it did in the Flash Gantt control. The control will not be filtered by dates. (DOC-92)

• HTML Chart Control. Axis. With more than one data axis in a chart, the control does not identify from which axis click events occur. (WC-2237 )

• HTML Chart Control. Export to Word. As part of V23.2, all Archibus views were updated to use the HTML Chart control instead of the Flash Chart control. However, the HTML Chart control does not offer the ability to export to Word, as does the Flash Chart control. As a work-around, you can take an image grab off the screen and paste it into Word. (APP-413)
• HTML Chart Control. Scrolling the Legend. Legend has to be scrolled, even though there is available space to display it without scrolling, in the Internet Explorer browser. (WC-1861)
• HTML Drawing Control. Markups. Internet Explorer. When working with drawings whose unit is other than Meter, you cannot resize a marker symbol by dragging. Also , clicking the symbol can double the size of the symbol. This applies to Internet Explorer only. (WC-2434)
• HTML Drawing Control. Drawing Load Progress Indicator. If you are loading a drawing in a Web Central view, you will notice that the view does not include the progress indicator (spinner) to inform you of the drawing load progress. This applies only when running Web Central on Chrome and IE. (WC-2742)
• HTML Drawing Control. Multiple Open Drawings. Visible Published Layers. If you open multiple drawings and these drawings do not have the same set of published layers, the drawings will show only the published layers that are common to all open drawings. (WC-2865)
• HTML Drawing Control. Drawings Published in Metric Units. Markers placed together to form a cluster cannot be viewed separately when zoomed in - they will always show as a cluster. (WC-2448)
• Select Value. Collapse window icon. Select Value windows cannot be collapsed. (3049201)
• Home Page Editor. New bucket not appearing. Internet Explorer 11. When you create a new bucket, save, and publish, the home page will not display your new bucket. You must take the additional steps of logging out, clearing the cache, and logging in again in order for the home page to display your new bucket. (WC-2787)
• Home Page Editor. Legacy Metrics. In the Home Page Editor, the user can select Legacy Metrics, which are not supported by home pages, due to different format than the Tracking Metrics. When working with the Home Page Editor, do not pick any of these Legacy Metrics: (WC-985)

  department_area_x_quarter
  department_area_x_month
  department_area_x_year
  em_capacity_x_bl_x_month
  occupancy_count_x_bl_x_quarter
  occupancy_count_x_bl_x_year
  occupancy_count_x_bl_x_month

• 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)
• Home pages. Localized. Long titles for processes. Some process titles in Asset Management, Enterprise Asset Management, and Telecom Asset Management Home Pages do not wrap up correctly for localized versions. For example, "Business Process Owner - Facilities", "Business Process Owner - Assets", and "Business Process Owner - IT Assets" do not wrap correctly. This is because there are two lines allotted for application titles. This issue will be addressed in a future release. (WC-3411)
• Accessibility Navigator. If you set the Navigation Method on the user profile menu to Accessibility Navigator, only an administrator can change the profile back to the other navigation methods: Dashboard or Process Navigator. (3053337)
• Accessibility Navigator - Grid. Smart Filter. On Internet Explorer versions 9 through 11, accessibility users cannot use the ENTER key to expand the grid's Smart Filter. This issue does not affect Internet Explorer 8, Firefox, or Chrome. (3053420)

• Tooltips. Internet Explorer 11. Field tooltip elements, displayed as small ? icons next to some fields, do not display tooltip text when the user hovers the mouse over the icon. The user can still click on the icon to see the tooltip text. This occurs only in IE11. (3050333)

• Data Transfer. Excel. When exporting decimal data to Excel, when Web Central user is in one locale and Excel is set to a different locale (i.e. when the decimal separator in one is a comma and in the other is a decimal point), review the rounding of the decimal data in the Excel file to verify that it is appropriate for your use. (3035375)
• Reports. Adobe Live Cycle PDF. The Adobe Live Cycle PDF output reuses the same file name by default, so users may need to clear their browser cache to see changes to the data or restrictions reflected in the report output. This issue does not apply to standard "PDF" output actions in Web Central, but only to the forms with custom layouts such as the OSHA forms produced by the EH&S application and Hazardous Waste Manifest documents from the Waste Management application. (3039687)
• Reports. Custom Colors. Add-in managers cannot configure custom colors for report totals. (WC-2046).

• Reports. DOC button. Some reports may give an error like the following when the DOC action button is used: "Unable to get property 'jobFinished' of undefined or null reference." Despite the error, the report still is produced successfully. (APP-5175)
• Dashboards and scroll bars. If you open from a home page a dashboard view that displays multiple frames, you may find that the scroll bars remain active if you move the mouse completely outside the panel. Click anywhere in the panel to deactivate the scroll bar. You may also find that when you move the mouse outside the panel, scrolling stops immediately or that the scroll bars disappear even though mouse button is pressed. Scrolling resumes if you move mouse back inside panel without releasing mouse button. (3043205)
• Dashboards. Long first-load time. On some application servers, such as Web Logic 8 and 10, we have observed that some large dashboards (e.g. the Move Scenario dashboard) take a long time to load (6 seconds). Archibus compiles view files to .jsp on first use so that the second load and all subsequent loads of the view are very fast. However, for some long dashboards on some application servers, the .jsp compilation takes multiple tries and produces several error in the archibus.log file. However, the process completes reliably and there is no error or service interruption to the user. The one observable effect of this issue is that large dashboards can take longer to load. (3032821)

• Tree Drill-downs. Firefox. Collapsing and expanding a tree control panel causes the tree control to be rebuilt, which undoes the user's selection of tree nodes. (3036779)
• Hierarchical Tree Drill-downs. Sybase. On Sybase, hierarchical trees in views like "View and Edit Organizational Units" or "Map Sites to Organizational Units" do not display all the hierarchical levels if the tables have pattern values that are larger than 126 characters. For example, in the above views, the tree uses a SELECT LIKE clause for org.hierarchy_ids, which on Sybase is limited to 126 characters. Thus, if using values for Organization Code, the hierarchical tree for organizational units will display only the first four levels because some values in org.hierarchy_ids are larger than 126 characters. This issue affects Sybase projects only. (WC-2406)

• Sybase Web Edition database engine. Connection limit.While using Web Central with Sybase Web Edition database engine, you might receive an error in the WEB-INF/archibus.log file stating that the database server connection limit was exceeded. The error message reads: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Database server connection limit exceeded at sybase.jdbc.sqlanywhere.IDriver.makeODBCConnection.
  To fix this issue you need to tweak the value of maxActive in the \Archibus\WEB-INF\config\context\compatibility\afm-config.xml file. To do so:
  1. In the afm-config.xml file, search for "Sybase-WebEdition" to find the attribute.
  2. Reduce the value for maxActive. The right value might be any value less than 10, except 0. The below example shows a value of 4.
     type="Sybase-WebEdition"
<connectionPool
maxActive="4"(3043397)

• User Profile. Chrome. If Chrome crashes or exhibits odd behavior, your Chrome user profile may be corrupted. See these instructions on how to reset your Chrome user profile: https://support.google.com/chrome/answer/142059
• Grid. Highlight ACAD Pattern (Swatch) fields. If working with a view in which you define highlight patterns (such as Space Planning & Management / Space Inventory & Performance / 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)

System Administration and Technologies known limitations

• Serraview-Archibus Integration. Connectors. FTP connections remain open, even after the data is processed. (APP-7260)
• Serraview-Archibus Integration. Story 2 is not supported in Oracle.(APP-5856)

• Database update scripts. V.24.1.002 and V.24.1.003. V.24.1ML customers who have already deployed V.24.1EN need to update their DB schema by running the scripts in \dt\24.1.002 and in \dt\24.1.003\. When using the V.24.1ML database, there is no need to do so. (APP-5925)

• Database update scripts. V.24.1.002. For V.24.1EN, you need to republish home pages after running the V.24.1.002 DUW scripts. This is not necessary for later releases because the database already contains the V.24.1.002 scripts. (APP-5059)
• Database update scripts. V.24.1.001. Running the update-database.duw script may give an error on some updates. If you get an error with "This record is locked by another user or program. ... Unable to execute statement." the cause might be a redundant update workflow rules statement in: ../dt / 24.1.001 / schema / sysadmin / gdpr / update-schema.duw. The solution is to comment out the last line in the above file by adding two hyphens ("--") at the beginning of the line. Then run the top-level update-database.duw again. (DB-327)

• Database update scripts. V.23.2. Oracle and SQL Server. To use the V.23.2 database update scripts on Microsoft SQL Server and Oracle, you must do the following:

  in \archibus\projects\users\public\dt\23.2-plus\sample-data\app-bldgops\common\update-sample-data.duw comment this line: ${run.script('%publicDataTransferDirectory%\23.2-plus\sample-data\app-bldgops\common\drop_WO_WR_triggers.sql')};

  See What's New in V.23.2 / Add-in Manager Features: Scripted Database Updates for information on the database update scripts. (DB-149)

• Schema database. System administration can be performed from any user that has one of the following roles assigned. The Schema database has users such as AFM and AI that have these roles. System administrators may also wish to set up a System Admin role that only has System Admin processes unlike the longer list of processes that the roles above have assigned. In a future release the schema.db will include System Admin-specific roles.(3042664)
  • 4 - PROCESS OWNER (ACP)
  • 4 - PROCESS OWNER
  • ACTIVITY LICENSEE

• Schema Change Wizard. Compare Tables. The Compare Tables step of the Schema Update Wizard cannot complete due to a security exception. As a workaround, you can temporarily disable the following settings in /WEB-INF/config/context/core/core-optional.xml, and restart the application server. After completing the wizard, please re-enable these settings.(WC-2295)
  
  <!-- <value>AFM_GROUPS</value> -->

<!-- <value>AFM_GROUPSFORROLES</value> -->

<!-- <value>AFM_ROLES</value> -->

<!-- <value>AFM_USERS</value> -->

• 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)
• Basic Rule Wizard. Linux and JBOSS EAP. On Linux and JBOSS EAP 6, Basic Rule Wizard cannot run basic rules. This issue has been verified to affect the following software configurations: Red Hat Enterprise Linux 6.1 x64, Java 1.7, JBOSSEAP 6.2 and Red Hat Enterprise Linux 6.1 x64, Java 1.7, JBOSS EAP 6.3. (3047117)
• Basic Rule Wizard. WebSphere. If you are running Web Central under WebSphere, basic rules may fail to execute. To resolve the issue, remove the following line from the basic rule templates: import org.apache.log4j.Logger;. The template files are under the schema\ab-core\system-administration\basic-rule-wizard\templates\ folder. (3049954)
• View Definition Wizard.Dashboards. The wizard fails if one of dashboard processes contains round brackets in the process name. (WC-2135).

• 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 Administration / Archibus System Administration / 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. As an Add-In Manager, 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)

• Automatic ID Lookup. Translatable fields. Translatable lookup fields are supported in grids, reports, charts, and cross-tables, but are not supported in edit forms. If a translatable lookup field such as project.project_type is used in an edit form, and the user has a non-default locale, the form will fail to save data. This is because the user may enter or select a localized field value, which will not validate against the primary key of the lookup table. The solution is to use a description lookup field instead of a primary key lookup field.
  
  For example, to translate the project.project_type field:
  
  1. Remove the <root><lookup displayType="translate"/> </root> element from the projecttype.project_type field in the afm_flds table.
  
  2. Add the <root> <lookup/> </root> element, without the translatable attribute, to the projecttype.description field in the afm_flds table.
  
  Edit forms will then:
  
  

  • Display editable English value of the project.project_type field.
  • Save English value of the project.project_type field, which validates without errors.
  • Display read-only localized value of the projecttype.description field. (3054146, 3054148, 3054178)

Smart Client known limitations

• .Net 4.0 and TLS 1.2. .Net 4.0 does not support TLS 1.2. If you wish to use TLS 1.2 security protocol, you must install .Net 4.5 on your workstation, and then TLS 1.2 works per normal. If you use .Net 4.0, Archibus gives an "incorrect format of configuration file" error. (SMAR-501)
• Using V.21.1 Smart Client with V.21.2 and beyond If you have V.21.1 Smart Client, you cannot use it with the Sybase 12 Web Edition, support for which was only added in V.21.2. If you leave the Web Edition configuration in place, V.21.1 Smart Client users will get the "User ID and/or password" error. To remove the Web Edition configuration, edit \WebCentral\WEB-INF\config\context\compatibility\afm-config.xml and remove the entire <engine type="Sybase-WebEdition"></engine > element. Next, edit \WebCentral\WEB-INF\config\afm-projects.xml and remove any project definition that uses databaseEngineType="Sybase-WebEdition". Then V.21.1 Smart Client will sign into other databases per usual. (3045680)
• Installation. Installing Full Smart Client for Windows XP 64-bit can give a "Failed to complete installation" error and the installation does not complete. Archibus Inc. has found that installing AutoCAD first and then installing Smart Client might solves the issue. SmartClientOnly does not have this problem (3047460).
• Setup console. Disabled Start/Stop button. Microsoft SQL. If MS SQL service is started prior to installing Full installer, the system displays an error message, After all services start, the Start/Stop button in Setup Console is disabled. To resolve this issue, you need to set MsSqlExpress Installed="false" in the <InstallDir>/SmartClient.Common.dll.config file. The <InstallDir> directory is the Smart Client installation directory. (3050007)
• Setup console. SQL Express. If you use the Setup Console's Project tab to change the project to an SQL Express project and you set the database type to MS SQL Server and make other configuration changes as needed for your SQL environment, you will find that the program will not start. As a workaround, edit the afm-projects.xml file and specify the SQL Server Express project by changing database EngineType to "sqlServerExpress". Also change the three lines that say: <engine type="SqlServerExpress"> to <engine type="sqlServerExpress"> being sure to use a lowercase "s". (SMAR-924)

• Drawing List. Document Management for Drawings. The Drawing List is sluggish for large (thousands) of record drawing lists. Most large teams prefer to use virtual-private Archibus to divide the drawing list by area of responsibility.

• 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 or Client/Server.(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)

• High-DPI Display. Explorer. On a high-DPI display, you may see small and cut-off text in the Explorer. (SMAR-210)

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

• Data Transfer. Chinese user name. If you sign in to Smart Client with a user name in Chinese characters, Smart Client's data transfer feature does not work in Jetty. Tomcat works fine. (SMAR-663)
• Data Transfer. Linux. Java 1.6. If you encounter errors using Data Transfer when running Linux with Java 1.6, upgrade to Java 1.7. (3045880)

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)
• Highlighting commands. Hatch patterns. Scale. Hatch highlights do not scale correctly for Metric drawings. Depending on the hatch pattern used and the DB scale used for hatch patterns, the asset symbol will either appear to be not highlighted, or completely filled with the color of the hatch pattern. As a workaround, uncheck the "Apply DB Scale" option in the Highlight Settings form and enter a very small value (such as 0.1) in the "Default Scale" field. This will enable the hatch pattern to appear. (SMAR-800)
• 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 SCE, like the Win Client/Server Overlay, 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)

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

• Lighting Fixtures. Although they are listed as a Revit Category in Archibus, you cannot catalog or publish them from any view or floor, even after adding them to afm_bim_familes. (SMAR-998)

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

GIS known limitations

• Standard map views. Zooming the map hides controls (IE only). In some map panels, using mouse wheel to zoom out hides the panel title bar and controls. For example, if you place the mouse pointer inside the map and zoom out using the scroll wheel, the panel title bar disappears, along with all the necessary controls on the title bar. If you zoom in with the scroll wheel, the title bar reappears. The issue does not happen if you zoom using the + and - buttons on the map. (3045585)

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 won’t display the standard “Record Successfully Saved” banner.(3045250

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)

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

Archibus Workplace known limitations

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

• Reservations. 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-6853)
• Reservation requests. Time parameters. The meeting scheduler does not honor the application parameters for AbWorkplaceReservations.TimelineStartTime and TimelineEndTime. It always goes from 8am to 9pm. It also does not prevent the user from booking a room outside the times set by the Room Arrangement Start and End Times. If the user attempts to reserve a room outside of these times, they get an error "Room is not available." (DOC-97)
• Reservation requests. Multiple room configurations. 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 floorplan. (APP-5485)
• Reservation requests. New Visitor. Oracle. 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 building 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. (APP-5194)
• Reservation requests. Workspace requests. Add Visitor The Add Visitor sequence does not allow selection of all departments at the site. (APP-5835)
• 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)
• Reservation requests. Conference room kiosk. You should not be able to cancel reservations from the Conference room kiosk. (APP-5892)
• Requestor photos. The QR scan Room page Request list shows requestor photos that do not match the requestors. (APP-5884)
• Required fields. In Workplace forms, fields that must be completed are not clearly marked. (APP-5840)
• Move Requests. Turning off Move features using parameters. When setting parameters for the EssentialSuite application, you will notice that there is no application parameter for turning off the move features in Archibus Workplace, as there are application parameters for disabling other aspects of Workplace. Thus, if you are using Workplace with Archibus non-SaaS, and you do not have the Enterprise Move Management application, you will not be able to manage move requests generated in Workplace. (APP-5636)
• 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-5162)
• Move requests. Description field. After creating a Move Request, the Request appears on Workplace, but with an empty description field. (APP-4842)

Mobile App known limitations

• 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)
• 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 Web Central Building Operations 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).

• Maintenance app. Syncing part quantities. Part quantities are synced on the mobile Maintenance application 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 Web Central's 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 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 & Occupancy Survey app. Redlines on iOS 7.0.3. The redline feature does not work in the Space & Occupancy Survey App on Apple iOS 7.0.3. The solution is to upgrade to 7.0.4 or later. (3045485)
• 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. Please 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)

Real Estate Portfolio Management 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)

Capital Project Management known limitations

• Capital Budgeting. Cross Tables. The Capital Project Management / Capital Budgeting / Budget / View Budget by Program Type view cannot display cross-tables when auto-lookup is enabled for the program.program_type field. If you encounter this issue, please contact Customer Support for suggestions. (WC-2176).

• Project Management. Export to XLS. The Capital Project Management / Project Management / Manage / Management Console (ab-proj-mng.axvw) When you export to XLS, the column totals appear in the wrong column; they are shifted one column to the left. For example, the Project Budget total appears under the Project Status column. (APP-1890)

Space Planning & Management known limitations

Space Inventory & Performance known limitations

• Define Rooms. Room Code field. Sybase schema database. If you edit the Room Code field and save your changes, the change does not save and you generate an sql exception in the archibus.log file. This issue happens only when using the Sybase schema database. This issue does not exist in MSSQL and Oracle schema databases, and does not exist in Sybase 10 HQ database. (APP-5601)
• Space Requests. Move Management. If you change the From Location in a space request, use Move Management / Enterprise Move Management / 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)
• Space Console. Export to XLS. When you export organizations or room categories to XLS, in the spreadsheet the values of the owner records are shifted one cell to the left. For example, the Division Legend value appears in the Division Room Count cell. (APP-6753)
• Space Console. Team Space. Export Employees. In the Space Console, you can export the contents of the Employees tab to DOCX or XLSX format. One of the fields that can be displayed and exported is the Teams list. This is a comma-separated list of teams to which each employee has rooms assigned. When you export the Employees data and you include this column, the column will be blank. (3053431)
• 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. Moving employees. When making employee assignments, if you move an employee to one room, and then decide to move the employee again to a different room, the first room will remain highlighted. The pending assignment is correct, but the room highlight for the first room will not re-set to indicate that no move is occurring in that room.(3041300)
• Space Console. VPA. If a user has VPA set for division/department, the user can still update an employee's location to be a room that does not belong to the division/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/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 Chargeback known limitations

• Chargeback calculation. If workspace transaction records contain an end date before the start date, they will be incorrectly accounted for in the chargeback calculation. (3033209)

Enterprise Move Management known limitations

• Move Console. Refresh. When you change the status of a move when working in the Move Details pane and you return to the Move List, the status is not updated and the move is listed in its original group. You must click Filter for the list to refresh. This differs from the behavior when you change a status using the buttons on the Move List. In this case, the Move List is automatically updated any you don't need to take any action. (APP-4895).

• Group moves. Employee and Team assignments. When a group move project contains employee and team assignments, and there are conflicts among the assignments such that a room is involved in both a team and employee move, the system does not handle the conflict well. (APP-2496)

• Move Scenarios. Plan Move Scenario tab. WebSphere. On the Process Navigator, choose Enterprise Move Management / Move Scenario Planner / Develop Move Scenarios. Create a new scenario or choose a scenario to edit. When you move to the Plan Move Scenario tab, the program presents an error message. Subsequently, you can access this tab without a problem. (3027142)

• Move Scenarios. Placing employees by dragging. If the Gross Area layer is on in layout scenario drawings, you may experience that you cannot drag employees to rooms for placement. To drag and drop employees that are part of the move onto layout scenarios, open the layer selector and make sure that the Gross Area layer is unchecked. (WC-3081)

• Action questionnaires. If you add new Action Types (using the Enterprise Move Management / Business Process Owner / Define Action Types task), you cannot add questionnaires to these action types using the Enterprise Move Management / Business Process Owner / Define Action Questionnaires task. (3028382)

Asset Management known limitations

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)

Asset Management known limitations

• Purchase Price. Visibility. The Asset Management and Enterprise Asset Management applications 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.

• Asset Lifecycle Console. Asset Registry tab. If you have newer depreciation reports that do not cover all the equipment in your inventory, then it is possible that the Asset Registry tab of the Asset Lifecycle Console will not load appropriately because the asset depreciation query cannot find depreciation values in the latest depreciation report for all equipment. The workaround is to make sure that all equipment is covered in the latest depreciation report. In a later release, the depreciation query will handle the case of not all the equipment being covered in the latest depreciation report. (APP-6819)

Enterprise Asset Management known limitations

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

• 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)
• 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)
• 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)
• Purchase Price. Visibility. The Asset Management and Enterprise Asset Management applications 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.

Telecom Asset Management known limitations

• Connecting an item to itself. 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)
• Connecting equipment using Chrome browser version 52.0.2743.116 m. Using this version of Chrome, you will encounter no response when attempting to connect two equipment assets. Connecting correctly works on Chrome version 55.0.2883.87 m. Please upgrade to Chrome 55.0.2883.87 m if you encounter this issue. (WC-1558)

• Queries and traces. Multiple drawings are not supported for queries and graphical traces. (APP-216)

Building Operations known limitations

• Building Operations Report Console. Charts. Internet Explorer. When you load the Building Operations Report Console report in Internet Explorer and set the properties for a chart, it does not present a chart. (APP-5767)
• Define Craftsperson Variances. Manage Craftsperson Shifts. Internet Explorer.You cannot select multiple date cells to create time blocks when working with IE. This was tested on IE 11.125, update version 11.0.49. (APP-3697)
• PM Planner. Locations procedures. You cannot generate work orders for PM Procedures that have a Procedure Type of Location. As a work-around, run the Building Operations / Preventive Maintenance / Maintenance Manager / Generate PM Work Orders task. (APP-5155)
• PM Planner. Costs. MS SQL. When running under MS SQL, the PM Planner cannot show costs if you group by trade. (APP-5049)
• Labor Scheduler. Internet Explorer. When using the Labor Scheduler on Internet Explorer, you will find that when you try to drag and drop a work request to the craftsperson's calendar, the system will prevent the user form dropping the work request box onto the background color blocks indicating regular schedules and variances. As a workaround, you can drop to the white space below the background color. (APP-2452) Also, when using the Labor Scheduler in IE, you will find that when you mouse over a schedule block, the schedule type does not show. (APP-2857) Also, when running on IE, you cannot drag a scheduled assignment from one craftsperson to another craftsperson. (APP-3690).
• On Demand Work. Licensing Issue. A "not licensed" error can occur on a few of the older-style On Demand Work views for users with only On Demand Work licensed. The affected views are “Create Maintenance Service Request,” “View Un-Submitted Service Requests,” “Review Approved Service Requests,” and “Define Parts Inventory.” If you see a “view is not licensed at your site” error when accessing any of these views, you can contact Customer Support for a solution to this issue. (3054339)

Environmental & Risk Management known limitations

Emergency Preparedness known limitations

• View Emergency Contacts by Building. Paginated Report button. In the Emergency Response and Recovery Teams / View Emergency Contacts by Building (ab-em-contactsxbl.axvw) view, the DOCX button on the Emergency Contacts Details panel does not generate a paginated report and presents an error message. (APP-5465)

Clean Building 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. Document/Photo. If a questionnaire form includes document/photo question, the questionnaire response form in Web Central will not count completion of the document fields in its estimated % complete, and may indicate some % complete for a blank form. (APP-2538)

• Extended Questionnaires. Document/Photo. The Web Central questionnaire form 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. A questionnaire designer should take this into account when designing forms. 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. (APP-2426)

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

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

• Management reports. Generating Word documents. Several reports in the Management Reports process have a "DOC" button by which users can export the panel's contents to a DOCX file. The application generates the file, but first pops up an error message on screen and leaves the report panel unresponsive until the user refreshes the report. This occurs in the following reports: (APP-5070)

  • Environmental & Risk Management / Compliance Management / Management Reports / Compliance Level and Priority (ab-comp-rpt-req-lvl-priority.axvw)
  • Environmental & Risk Management / Compliance Management / Management Reports / Compliance Level and Requirement Type (ab-comp-rpt-req-lvl-type.axvw)
  • Environmental & Risk Management / Compliance Management / Management Reports / Compliance Level and Program (ab-comp-rpt-req-lvl-prg.axvw)
  • Environmental & Risk Management / Compliance Management / Management Reports / Compliance Level and Regulation (ab-comp-rpt-req-lvl-reg.axvw)
  • Environmental & Risk Management / Compliance Management / Management Reports / Expired License-Permit Count (ab-comp-rpt-req-expired.axvw)

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

• Configure Bill Processing. Oracle. Users are unable to remove all values from the "Excluded bill types" field using the select value dialogue because the "Save" action button is disabled after clearing the values. The workaround is to edit the field directly and type the value 'none', then click Save; the selections are deleted. (APP-5264)

• Review and Approve Bills. Oracle. When no bills have previously been sent for approval when starting with an empty schema database in Oracle, you receive an unclear error message. This is an unlikely situation and relatively benign issue, though the error message "An application error occurred" is not very helpful and could cause more concern than warranted. The message will be updated in a future release, but the behavior is legitimate. Please send at least one bill for approval or directly archive at least one bill upon initial implementation of a blank schema in Oracle before attempting to open the Review and Approve Bills task. (APP-5265)
• Cash Flow report. Multicurrency. When multicurrency features are enabled, archived bills are not shown in the Cash Flow report. Scheduled cost transaction records that the Energy Management application creates when archiving energy bills are visible in the Cash Flow report only if the Archibus Multicurrency features are not enabled. (APP-5266)
• 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)

Workplace Services known limitations

Reservations known limitations

• Calendar Console. Exchange integration.
  • All-day events are not properly shown. In some situations, they are duplicated. In other situations, they are not shown as occupied times for attendees in the Calendar view. (APP-6220)

  • The Calendar Console does not retrieve attendee availability from Exchange when you add attendees in the Monthly and Scheduler views. (APP-6799)

• Calendar Console. Pre-meeting and post-meeting block times.
  • The Console allows you to create back-to-back meetings that overlap pre-meeting and post-meeting block times. (APP-6728)

  • The Scheduler does not display a reservation's pre-block and post-block times. (APP-6779)

• Calendar Console. Recurring reservations.
  • The timeline does not always correctly display recurring patterns; although the timeline might not display these reservations correctly, the Console does correctly save these meeting dates. (APP-6651)

  • There is a display issue when selecting the time period for recurring meetings. For example, define a daily recurrence pattern that starts today and ends after 3 occurrences. Select a room and select a time period. The Calendar Console should automatically populate the timeline with the selected time period starting today, for 3 days. (APP-6798)

• 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)
  • The Scheduler doesn't validate against the earliest and latest time for the selected room arrangement until trying to confirm the meeting. (APP-6740)
• Calendar Console. Continuous meetings.
  • You can create single continuous meetings, but recurring continuous meetings are not supported. (APP-6322)
  • The My Reservations tab disables the Edit option for continuous meetings. As workaround if users need to apply any changes they can cancel the meeting and create it again. (APP-6565)
  • 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)

  • If you click on a past date of a continuous reservation to see its details, the Console presents the details but also presents a message box on top of the details informing you that you cannot select a past date. This message box is not necessary because you were simply examining the details of a past date. (APP-6789)

• 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)
  • When editing conference calls and choosing the "only this location" option, you might find that the reserved room is not shown in the room list. (APP-6430)
• Calendar Console. Scheduler.
  • In the Scheduler, the list of rooms cannot be sorted in the same ways it can be sorted in other formats. (APP-6739)
  • The Scheduler lets you select occupied times, proceed to the confirmation, and add details; it alerts you to the conflict only when you try to save the meeting. (APP-6734)
  • For rooms whose room configs have multiple arrangements, changing the format to Scheduler does not update the room list. (APP-6791)

• Calendar Console. Editing meetings. Editing meetings is severely limited when External Visitors Allowed set to No. (APP-6692)
• Calendar Console. Showing all scheduled meetings when editing. 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. (APP-6518)

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

• Calendar Console. Changing the date selection. When you select a date on the calendar and use the View Employee Schedule button to see employee meetings, the Console correctly displays this information. However, if you now change the calendar dates, the employee schedules are not updated; instead, you see only the schedules for the dates you originally set in the filter. This can be misleading because you might think that the attendees are free this week since no meeting are shown for them. (APP-6219)
• Calendar Console. Selecting rooms with click and drag. While it is possible to click and drag on the time slots for rooms, doing so doesn't select that room. To actually select the room, you must make the extra effort to click the room. This behavior is throughout all views of the Calendar Console. (APP-6658)

• Calendar Console. Number of attendees not recorded. Create a single reservation with attendees. access the Calendar Console, select the reserved room, click on the reservation in the timeline. The reservation shows that # of Attendees in Room is 0. (APP-6801)

• Calendar Console. End Date omitted. Several tooltips and views omit Date End; they have Date and Time Start, but only Time End. For example, the Date End is missing from the Room Reservations Details form, and the Reservation Details section of the Room Reservations form (accessed by selecting a date on the calendar). (APP-6632)
• 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 Reservation. Sign-in name includes a slash. When running the Create New Room Reservation (ab-rr-add-room-reservation.axvw) view, if you sign in as a user whose Employee Code field includes a backslash character, the system cannot create the reservation. (WC-2667)
• Create Reservation. Timeline. Microsoft Surface. When working with Create Room Reservation, Create Resource Reservation, and Create Conference Call Reservation, you cannot drag with touch input a reservation on the timeline. Timeline drag-and-drop supports only mouse events. (APP-3312)
• Create Reservation. Exchange integration. All-day events. All-day events sometimes show duplicated. In other situations, they are not shown as occupied times for attendees. (APP-6220)
• Exchange integration. Outlook 2010. Time zones. In some situations using Exchange Integration, when creating a recurring reservation from Web Central, attendees using Outlook 2010 can receive the meeting invitation in plain text. The time zone information is then displayed in the meeting invitation body instead of in the when field. The cause of this issue is yet to be determined. Reinstalling Outlook or resetting the Outlook profile could resolve the issue. (APP-2340)

• ICS invitations sent when no relevant changes. When the Reservations application is configured to send ICS invitations, the application will send new ICS invitations each time a reservation is updated, regardless of whether any relevant changes have been applied. For example, if you add resources to a reservation, the application will send new ICS invitations even though resources are not listed in the ICS invitations. (APP-2363)

• Confirm reservations. Email. In the Confirm Reservation screen, the Requestor’s Email (reserve.email) is used by the Outlook Plugin and for Exchange integration. The non-integration sending of emails retrieves the email address from the Employees table. For this reason, reserve.email should be equal to the requested_by employee email. If you change the default email presented in the form, by entering a different email than the employee’s email, the Plugin and Exchange use the new value, but the .ics invitations will continue to use the em.email value. For reservations created via the Plugin, the Plugin fills in the user_requested_by and user_requested_for fields based on the reserve.email field. (3015233)
• 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.
• Time zones. Editing conference calls. The time zone of the meeting in Outlook is not modified when you update a recurring meeting from Web Central. This means that the time zone in which the meeting is displayed in Outlook can be different from the following in Web Central. However, in both cases the reservations do remain in sync with the meeting. (3045844)
  • the time zone you chose for the conference call in
  • the local time zone of the room you chose for non-conference call

Reservations Plugin for Microsoft Outlook known limitations

• Notification of cancellation from Web Central.When you create a recurring conference call reservation from the Plugin, and some reservations are canceled from Web Central, you do not receive a notification of this cancellation if you open the meeting again from the Plugin. The system notifies you when you open the canceled date from Plugin as "only this date"; but if you open the entire series (from any date), you do not receive the required warning message. (OLKPLGN-12)
• Meetings created in Web Central cannot be updated via Outlook without the Outlook Plugin. When the meeting organizer uses Outlook to change a meeting originally created in Web Central, and the Archibus Outlook Plugin is not installed on his machine, the Exchange Listener will not update the reservation in Web Central. The meeting organizer receives a Meeting Decline message from the resource account to indicate the reservation was not updated. As a workaround, the meeting organizer can change his meeting via OWA or via Web Central. This issue does not occur if the meeting organizer has the Outlook Plugin installed. (APP-2346)

• Non Exchange integration. Canceled Location not removed from the meeting email body.When using ICS for a recurring reservation, once an occurrence is moved to a different date, any change to the recurring reservation is sent as separate updates for each individual occurrence instead of as a series update. Such a change won’t be visible when opening the entire series on your calendar. It will only be visible when opening the individual occurrences. For example, suppose you change the date for one of the occurrences of a recurring conference call reservation and later remove a room from the recurring reservation; after importing all ICS files to your calendar, this update is applied to each occurrence but the body of the meeting series still shows the removed room. (APP-2131)