Fix Readme
Abstract
This document lists APARs that are fixed in IBM® Maximo® Real Estate and Facilities 9.1.0.
On 24 June 2025, IBM released IBM® Maximo® Real Estate and Facilities 9.1.
Content
APAR and Known Issue Fixes
| APAR | Application Name | Description |
|---|---|---|
| IJ46421 | Platform | The Security Manager and Data Integrator labels on the Tools page are now translated for French users in the latest language pack. (Tri-88316-IJ46421) |
| IJ47559 | Platform | The internationalization (i18n) process has now been applied to Smart Section Actions (ADDED, DELETED). As a result, Smart Section Actions are now displayed in French when the French user language is selected. (Tri-91483-IJ47559) |
| IJ34288 | Platform | If you clear the "Title Bar" checkbox for a section in the Form Builder, that section’s title bar are hidden in the form. When a user collapses a form section, any adjacent sections with hidden headers also collapse automatically. This behavior occurs regardless of whether the Enhanced Report Renderer is enabled or disabled. This functionality is consistent and is working as designed. (Tri-74356-IJ34288) |
| IJ40998 | Platform | The report filter must use the user's date format while retrieving data for reports. (Tri-79898-IJ40998) |
| IJ44006 | Platform | When you remove a user's Group and License audit details, they are still visible in the user profile even after running the Platform Maintenance or Cleanup Agent. Note: For Maximo Real Estate and Facilities environments, user licenses can only be updated through the Maximo Application Suite. As a result, auditing for user licenses will not be available. This update only affects future changes and does not impact past records. You will not be able to retrieve audit details for past events, but changes going forward will be accurately reflected. (Tri-80860-IJ44006) |
| IJ44518 | Platform | On the Graphics tab, when you click the check boxes for layers that are displayed after clicking the Layers icon, the selected layers load immediately. (Tri-86111-IJ44518) |
| IJ48766 | Platform | Improvements have been made to XSS filtering and onChange workflows. (Tri-94265-IJ48766) |
| IJ48867 | Platform | When you click the "Where used" button for any workflow with a single apostrophe (') included in the name, no error message will now be displayed. (Tri-93710-IJ48867) |
| IJ49521 | Platform | The Classification-Lease Asset Class is now translated correctly. (Tri-95275-IJ49521) |
| IJ49691 | Platform | The Report Manager now features a ""Work In Progress"" status for queries that have design changes but are not yet ready to be published as the report's runtime version. Additionally, a ""Publish"" button has been introduced. Any changes saved to queries will remain in the ""Work In Progress"" state until the Publish button is clicked. After the report is published, it becomes the official runtime version. (Tri-95099-IJ49691) |
| IJ50099 | Platform | The Gantt DateTime picker for Planned Start and Planned End dates now displays the saved date and time of a record, rather than the current date and time. (Tri-95863-IJ50099) |
| IJ50216 | Platform | For reservations that span for more than a month, My Calendar now renders reservation properly. (Tri-97816-IJ50340) |
| IJ50335 | Platform | The Issue action is now correctly translated in the latest language pack. (Tri-97781-IJ50335) |
| IJ50583 | Platform | Resolved an issue with the Object Migration Platform REST API operation, createPackageByDate, where objects were not being added to the Object Migration package. (Tri-98273-IJ50583) |
| IJ50961 | Platform | In the Report Manager, Business Objects (BOs) are displayed in the same order as defined in the report template, sorted by Module. The tooltip shows the BO label according to this Module order. (Tri-98542-IJ50961) |
| IJ51080 | Platform | You can now use underscore ( _ ) in the variable names of the formula picker in workflows without getting formula parse exception. (Tri-98659-IJ51080) |
| IJ51297 | Platform | The Query API now correctly handles Memory Exceeded Exceptions with appropriate responses. (Tri-99015-IJ51297) |
| IJ51788 | Platform | Resolved an issue where integration with Esri ArcGIS resulted in authentication failures on secured layers and base maps. (Tri-99579-IJ51788) |
| IJ51818 | Platform | When you create a sparse column with the Database Table Manager, the original collation remains unchanged. (Tri-99633-IJ51818) |
| IJ51981 | Platform | The OSLC response now displays the date for date fields. (Tri-99903-IJ51981) |
| IJ52145 | Platform | For form custom tabs, such as GIS and 3D Model, the tab height is now responsive and is no longer defaulted to a hardcoded value. (Tri-100293-IJ52145) |
| IJ52190 | Platform | List type validation is added for file inbound in the integration object. (Tri-100263-IJ52190) |
| IJ52316 | Platform | Home is now translated correctly in Japanese. (Tri-IJ52316-100291) |
| IJ52355 | Platform | For Spanish users, the 'City' and 'Address' labels are now translated. (Tri-100302-IJ52355) |
| IJ52520 | Platform | In the Integration Object user interface to establish record associations with linked business object, there should be alert box "No mappings found for the selected Business Object as it is associated with a linked business object." restricting user to map. (Tri-100394-IJ52520) |
| IJ52553 | Platform | Truncate workflow instances are being properly cleaned up across all database types. (Tri-100413-IJ52553) |
| IJ52621 | Platform | The report history table has been modified to support reports with longer run times and users with larger spec_id values. (Tri-100566-IJ52621) |
| IJ52713 | Platform | The queries that are associated with the hierarchy reports will now be displayed in the Associate Query section if the report name contains double quotes in it. (Tri-100662-IJ52713) |
| IJ52759 | Platform | Logging has been added to the AppServer startup logic to indicate which objects have changes that trigger the PlatformPasswordAdmin upgrade to re-import at startup. These changes will be recorded in the server.log file. Workflow comparisons have also been improved in the environments where the ordering of workflow task mapping fields was causing false positive comparison differences. (Tri-IJ52759-100564) |
| IJ52828 | Platform | Removed extra tab at the last empty column of the outbound text file. (Tri-100711-IJ52828) |
| IJ52862 | Platform | The editable queries will now sum the data from the associated object fields and render properly in the legacy renderer. (Tri-100767-IJ52862) |
| IJ52870 | Platform | In the Space Assessment Perceptive app, the issue causing errors when selecting buildings with a forward slash ("/") in their names has been resolved, ensuring smooth and seamless operation. (Tri-100771; 100900 -IJ52870) |
| IJ52872 | Platform | The query runtime filter now correctly applies the filter when there is a date in the range filter column. (Tri-IJ52872-100789) |
| IJ52873 | Platform | The notification message content is now visible in facilities records. (Tri-100773-IJ52873) |
| IJ53003 | Platform | The placeholders for Date Type column filters and Range filters are displaying the filter operator correctly in reports.(Tri-IJ53003-100982) |
| IJ53020 | Platform | On the Graphics tab, space and floor records with large spec_Id values are now highlighted. (Tri-100998-IJ53020) |
| IJ53021 | Platform | When you create an Excel template for a Data Load Set for Building Equipment application, the Food Service Equipment Spec are not displayed. (Tri-101033-IJ53021) |
| IJ53051 | Platform | The issue with the date range filter has been resolved. The fix provides enhanced flexibility, enabling the filter to function independently with both the "Before" and "After" operators. (Tri-IJ53051-101091) |
| IJ53080 | Platform | Resolved an issue where the inline loading spinner (processing wheel icon) on enhanced query rendering grids would not disappear when double quotes were used in the query filter. (Tri-92820-IJ53080) |
| IJ53083 | Platform | The values in the currency fields are now displayed properly based on the rounding rule set either in the Data Modeler or in the Unit of Measure (UOM) values. (Tri-101148-IJ53083) |
| IJ53089 | Platform | The Revision list is now be accessible in Data Modeler and Form Builder for users who were unable to access it. (Tri-101168-IJ53089) |
| IJ53113 | Platform | OAuth related warnings are no longer logged during sever startup. (Tri-101229-IJ53113) |
| IJ53127 | Platform | List field values are now saved correctly even if the saved value is from a non-English user. (Tri-101258-IJ53127) |
| IJ53374 | Platform | Resolved an issue in the Enhanced Report Rendering mode where when the "Prompt Before Query" option was enabled, unnecessary data was being fetched during the initial report load. Additionally, also resolved the issue related to proper visibility of the loading icon and "No Rows" overlays. (Tri-101618-IJ53374) |
| IJ53405 | Platform | A session history issue has been resolved where duplicate sessions were recorded for a single user after the session was manually terminated. This mostly occurred when a single user had multiple active sessions and one of those sessions was terminated manually. (Tri-101620-IJ53405) |
| IJ53425 | Platform | Fixed form settings for rowspan and colspan when Enhanced Render Mode is on. (Tri-101637-IJ53425) |
| IJ53455 | Platform | Models can now be uploaded with the latest Autodesk endpoints. (Tri-101674-IJ53455) |
| IJ53475 | Platform | The values for hours, minutes, seconds, and AM/PM are visible and properly aligned with the colons in the 'Time' field popup. (Tri-101675-IJ53475) |
| IJ53514 | Platform | The filter options for the number-type field are now accurately displayed in the report filter modal. (Tri-101691-IJ53514) |
| IJ53543 IJ53330 | Platform | A retrieve records task that has large number of records and special characters no longer throws an exception or displays an attention message. The task now completes successfully and retrieves the correct data. (Tri-101710-IJ53543; Tri-101514-IJ53330) |
| IJ53652 | Platform | Resolved the display issue that caused boolean fields to be displayed distant from their corresponding labels. (Tri-101812-IJ53652) |
| IJ53659 | Platform | For reports with summary columns enabled, number fields that use currency UOM now display correct values for users who use the Euro currency. (Tri-IJ53659-101836) |
| IJ53745 | Platform | The dropdown list picker for a field is now properly aligned with the field. (Tri-101896-IJ53745) |
| IJ53781 | Platform | Resolved an issue that affected the ordering of the results by the triRecordIdSY column in queries. Additionally, the results returned from the Greatest/Least record when using the triRecordIdSY column in the Retrieve Task in workflow have also been corrected. (Tri-101891-IJ53781) |
| IJ53783 | Platform | For a DB2 instance, no SQL syntax errors are displayed in the Instana tool while accessing the Administrator Console.(Tri-101903-IJ53783) |
| IJ53861 | Platform | Resolved an issue that prevented changes to the portal title bar background color from being applied correctly. (Tri-101957-IJ53861) |
| IJ53996 | Platform | When the resolution or size of the Currency Conversion form is reduced, the search button now remains fixed and visible while the rest of the content becomes scrollable. (Tri-IJ53996-101985) |
| IJ54001 | Platform | On the Columns tab, in the Display Columns section, the hover text is now display properly. (Tri-100065-IJ54001) |
| IJ54085 | Platform | Security Manager settings for the triPlatformPerformanceAnalyzer or triPlatformObjectLabelManager tools now allow non-admin users to access the Performance Analyzer or the Object Label Manager. (Tri-102021-IJ54085) |
| IJ54105 | Platform | Security checks in the Performance Analyzer have been improved. (Tri-102050-IJ54105) |
| IJ54209 | Platform | The export reports function is now working correctly for non-English users. (Tri-102094-IJ54209) |
| Platform | When viewing user records, previous licenses for existing TRIRIGA users are displayed until a user sync occurs from Maximo Application Suite. This includes user records with previous licenses that were imported via Object Migration. Although these previous licenses do not affect the functionality of Maximo Real Estate and Facilities, they can serve as a reference when deciding which license to apply to a user when creating their account in Maximo Application Suite. After a user sync is performed from Maximo Application Suite, the old licenses are removed and replaced with the one specified in Maximo Application Suite. (MASREF-855) | |
| Platform | The following settings have been removed from the TRIRIGAWEB.properties file: - ALTERNATE_RESOURCE_DIRECTORY - ALTERNATE_INDEX_HTML - LOGIN_PAGE_RESOURCE_LIST The DEFAULT_TITLE setting in TRIRIGAWEB.properties no longer affects the title of the login screen. Maximo Application Suite now manages all controls over login pages, providing a centralized and streamlined experience. (MASREF-1008) | |
| Platform | The SSO_SINGLE_SIGN_OUT_REDIRECT_URL setting has been removed from the TRIRIGAWEB.properties file. When users log out, are now redirected to the Maximo Application Suite log-out page. (MASREF-1014) | |
| Platform | The USERNAME_CASE_SENSITIVE setting in TRIRIGAWEB.properties has been removed. To align with Maximo Application Suite User IDs, only case insensitive User IDs are now supported. This means that User IDs are no longer distinguished by case. The username field on People and My Profile records is now labeled as User ID. If your TRIRIGA environment was previously configured for case sensitivity, you might have multiple users with the same username but with different cases. This can cause issues with the Maximo Application Suite user sync process. Review your user records to ensure that there are no duplicate User IDs with different cases. Update any duplicate records to use a unique User ID to avoid sync failures. (MASREF-1007) | |
| Platform | Users can now adjust the refresh value on the Performance Monitor page of the Administrator Console, even after it has been set once. (Tri-101944) | |
| Platform | For IBM Db2, the schema value defaults to the database username in capital letters. You cannot specify your own schema. (MASREF-1199) | |
| Platform | Non-admin users with valid permissions can now add discussions for a given document. (Tri-101436) | |
| Platform | The Retire action will now be available in the document record for a user with admin permissions. (Tri-88378) | |
| Platform | Fixed an issue causing errors when uploading a document immediately after performing a cut, copy, or paste action. (Tri-101124) | |
| Platform | The tooltip text for the icon that is used to open and close the left pane in Document Manager now displays properly and get translated for non-English users. (Tri-101018) | |
| Platform | Handled an issue where assigning user or group permissions to a document resulted in the original uploader losing administrator access. (Tri-99738) | |
| Platform | Handled an exception that occurred when an admin user attempted to add a discussion thread to a document after clearing the global cache. (Tri-101575) | |
| Platform | When a drawing is deleted, there is now an option to delete the associated .dxf file from content manager. (Tri-101551) | |
| Platform | When a drawing is deleted, its attachment status is affected as follows: • If the drawing was attached using the default application, it becomes detached. • If the drawing was attached using a non-default application, it is deleted without any changes to its attachment status. No error message is displayed to the user, but an error is recorded in the platform log file. (Tri-101499) | |
| Platform | Setting non-working hours now correctly uses the time zone of the space when creating a 'Non-working hours' meeting. (Tri-99598) | |
| Platform | The duplicate Update Working Hours issue is now fixed. (Tri-102201-IJ54645) | |
| Platform | Resolved an issue where Update Working Hours failed if a space had existing recurring meetings. (Tri-102057) | |
| Platform | For the triMSOAuth Business Object (BO), the "Modified By" field is now correctly set. (Tri-98700) | |
| Platform | In the Create Scripts section of Exchange Integration Manager, a new command is added to the create new mailbox that can be used only when the space name starts with numbers. (Tri-99476) | |
| Platform | Added locationUri field to be inline with Microsoft graph to triExchangeLocation. (Tri-102013) | |
| Platform | The WF Agent Info tab now refreshes after an action to ensure that the latest action is used. (Tri-101478) | |
| Platform | Enhanced GraphReadCalendarEvent Custom Task to filter the records based on the event type. (Tri-101272) | |
| Platform | Users no longer encounter an exception when deleting a user or group from the WF Agents Info tab of the Admin console, even when no user or group is selected. (Tri-96374) | |
| Platform | A "200 OK" response is now received after calling | |
| Platform | User can now add multiple instances of an agent without any issues. (Tri-100500) | |
| Platform | In the Database Query tool, users no longer encounter a MID error when they click "Delete Query" without selecting any query. (Tri-86771) | |
| Platform | Additional Information column data for forms and workflows no longer displays the tag. (Tri-100633) | |
| Platform | An exception is no longer thrown in a large spec_id environment when adding a record to the Forms tab in the Form Builder. (Tri-101200) | |
| Platform | Users can now add external reports inside the Form Builder query section without any issues. (Tri-101250) | |
| Platform | Users might see some CSS issues in some forms. If any CSS issues are observed, perform the following steps to correct the custom.css file: 1. Stop the pod. 2. Run the following three queries for the installation Database: DELETE FROM ENVIRONMENT_PROPERTIES WHERE PROPERTY LIKE '%triPlatformRecordUpgrade%'; DELETE FROM ENVIRONMENT_PROPERTIES WHERE ENVIRONMENT = 'platform.class.upgrade' AND PROPERTY = 'lastRun'; UPDATE ENVIRONMENT_PROPERTIES SET VALUE = '1' WHERE PROPERTY LIKE 'db.build.number'; 3. Delete the pod. The pod restarts with the updated values. (Tri-102152) | |
| Platform | The image field now displays correctly when row span settings are changed. (Tri-102096) | |
| Platform | You must now download Maximo Real Estate and Facilities language packs from Passport Advantage. Delta exports for language packs can now use only the /home/default/userfiles reference directory as their comparison reference. Facilities language packs must be downloaded from Passport Advantage. (Tri-61896) | |
| Platform | Text is correctly translated in the Norwegian language. (Tri-99921) | |
| Platform | The Arabic translation for "Page size" is now correctly displayed in on the Print Options panel in the Gantt section. (Tri-48571) | |
| Platform | "Loading, please wait..." message in License Matrix is now translated as per logged in user language. (Tri-99985) | |
| Platform | Users do not now encounter a MID error when trying to save a blank lock message in the admin console. (Tri-90233) | |
| Platform | Tooltip text for the Collapse icon of the open and close actions under Globalization Manager now display "Open' and 'Close' labels instead of 'Undefined'. (Tri-101016) | |
| Platform | Users can now export queries with file names that have special characters. (Tri-90624) | |
| Platform | A new property, ENABLE_SQL_WILDCARD, has been added to the TRIRIGAWEB.properties file with a default value of Y. This property controls how SQL wildcard characters % and _ are handled in query filters for Reports and Queries. When set to Y (default), % and _ function as SQL wildcards. When set to N, these characters are treated as literal values rather than wildcards. This setting allows greater flexibility in controlling query behavior based on your requirement. (Tri-101213) | |
| Platform | The tooltip texts for the Collapse icon of the open and close actions in Lists are now translated for non-English users. (Tri-101021) | |
| Platform | In License Viewer, the tooltip text for the icon that opens and closes the left pane displays properly and is translated for non-English users. (Tri-100001) | |
| Platform | The 'OK' button label is correctly translated for Arabic language users in Report Manager when attempting to copy, share, or delete a report without selecting one. (Tri-99990) | |
| Platform | The empty state icon in the Primary Location Graphic section of the Employee form is now positioned at the center of the section. (Tri-102079) | |
| Platform | The CACHE_LOAD_SIZE_FOR_ORACLE property is only visible under Administrator Console for Oracle environment and not for DB2 and MSSQL. (Tri-99746) | |
| Platform | You must review the header values in TRIRIGAWEB.properties. These properties have been tested and customers are encouraged to use these either through the application server (through TRIRIGAWEB.properties or through their web servers). These are the default header values tested in TRIRIGAWEB.properties to restrict clickjacking and to increase additional security layers. Note that these properties will replace the similar key value pairs if they were already present, or were added externally: - X-Frame-Options: SAMEORIGIN - Content-Security-Policy: frame-ancestors 'self' *.office.com; - Strict-Transport-Security: max-age=63072000; includeSubDomains; preload - X-Content-Type-Options: nosniff - X-XSS-Protection: 1; mode=block - Cache-Control: no-cache, no-store, must-revalidate. (Tri-102187) | |
| Platform | Removed unnecessary warning messages that were displayed while importing a non-dynamic list with Object Migration. (Tri-96859) | |
| Platform | The User Session Timeout in Minutes property in Administrator Console is set to 30 minutes by default for clean and upgraded environments. (Tri-101337) | |
| Platform | The Integration Object for File Outbound query look up requires the published details of the query to process the records successfully. (Tri-101728) | |
| Platform | Handled an exception message inside the Job Scheduler module. (Tri-81082) | |
| Platform | License names are displayed in alphabetical order on the Summary tab of License Viewer. (Tri-100324) | |
| Platform | Fixed an issue with the LicenseTypeUpgrade class, which was incorrectly running on every application startup. (Tri-100999) | |
| Platform | Fixed an issue with UX datasource license calculations where a user had no access but was allowed Read Only access to the datasource. (Tri-101431) | |
| Platform | Locale and time zone support might differ across applications. Not all applications support these preferences and instead use application-specific settings for locale and time zone. (MASREF-797) | |
| Platform | On the Reports page, in the My Reports tab, the Close option has been added to the menus in My Bookmarks. (Tri-97556) | |
| Platform | The screen reader focus now moves to the 'Add to bookmark' dialog on the Reports page. (Tri-100818) | |
| Platform | The screen reader focus now moves to the two sub-menus within the "My Bookmarks" section. (Tri-100833) | |
| Platform | When you attempt to add a bookmark without a name, a warning message is now displayed. (Tri-99767) | |
| Platform | The issue was appearing on each click action when the page is getting reset to 1. Made changes to correct the issue. The result display on Forms with URL selected on tabs is now working correctly. (Tri-101908) | |
| Platform | Resolved filter issues in Object Label Manager. (Tri-96016) | |
| Platform | Introduced a new param excludeObjectLabelOwners in the following OM API endpoint to enable users to package all the objects modified after the given date with the excludeObjectLabelOwners condition: /createPackageByDate?packageName={packageName}&packageDescription={packageDescription}&dateInMillis={dateInMillis}&includeDependents={includeDependents}&excludeObjectLabelOwners={excludeObjectLabelOwners} (Tri-101834) | |
| Platform | The following six new OM API endpoints have been introduced: • The endpoint /addRecordDataToPackage/{packageId}?recordId={recordId} adds record data to a package using the provided record ID and package ID. • The endpoint /addAssociatedRecordDataToPackage/{packageId}?recordId={recordId} adds associated record data to a package using the parent record ID and package ID. • The endpoint /addRecordsFromQueryResultsToPackage/{packageId}?queryId={queryId} adds records from query results to a package using a valid package ID and query ID. • The endpoint /addRecordsFromNamedQueryResultsToPackage/{packageId}?queryName={queryName}&moduleName={moduleName}&boName={boName} adds records from named query results to a package using a valid package ID and query details. • The endpoint /addRunOnImportWorkflowToPackage/{packageId}?workflowName={workflowName}&moduleName={moduleName}&boName={boName} adds workflow into a package by using the workflow name and package ID provided. • The endpoint /addRunOnImportWorkflowToPackage?packageName={packageName}&workflowName={workflowName}&moduleName={moduleName}&boName={boName} adds workflow into a package by using the workflow name and package name provided. (Tri-Tri-97323; 101375) | |
| Platform | Setting: httpheader.Content-Security-Policy=frame-ancestors 'self' *.office.com *.office365.com in the TRIRIGAWEB.properties file allows the Room Search Add-in to open in office365.com. (Tri-100884) | |
| Platform | Hierarchy cache is no longer flushed when clearing the Object Metadata cache. (Tri-101432) | |
| Platform | The default value of the PERFORMANCE_ANALYZER_MAX_FILE_SIZE_IN_MB property has been increased to 110 MB. (Tri-101954) | |
| Platform | The positions of menus that open when you click the menu buttons are now fixed. (Tri-102149) | |
| Platform | The scrolling issue for Notification Message Content in the Notification window is fixed. (Tri-102023) | |
| Platform | The issue that allowed creating draft Lease records without a mandatory "Commencement Date" is fixed. Users cannot create, save, or close a record unless all date and date-time fields have valid values. (Tri-85335) | |
| Platform | A pop-up message will now be displayed when an incorrect date is selected for a date field. (Tri-100929) | |
| Platform | The image added using the editor inside the report scheduler page is now populated in the received email. (Tri-101181) | |
| Platform | Enhanced test for Exchange Test Error by filtering out HTML elements from it. (Tri-100634) | |
| Platform | Workflow Future agent now properly processes events on records with large record IDs or where the user record ID is large. This includes when processing a Lease that has a large record ID. (Tri-102205-IJ54730) | |
| Platform | The Project Budget records can now be created and issued successfully for large project record IDs. (Tri-101857) | |
| Platform | Uploading a document by using the Attach Format File Task in a workflow no longer throws an exception if the record ID is large. (Tri-101475) | |
| Platform | Security groups can now be successfully created for users with large Spec IDs. (Tri-101144) | |
| Platform | The process of adding a user to a group has been enhanced for better performance, even when dealing with large groups containing numerous users. (Tri-99612) | |
| Platform | Editing of security groups will be successfully saved for users with large spec IDs. (Tri-101333) | |
| Platform | When 'Use Uploaded File' is selected in the Integration Object record, the 'Test File Access' button will be disabled and will remain in its current position. (Tri-99881) | |
| Platform | Users with a large spec_id will now be able to publish the forms. (Tri-101329) | |
| Platform | Property definition for the REBUILD_HIERARCHIES_ON_CACHE_REFRESH property has been updated to explain how it works when cleanup agent runs under Administrator Console. (Tri-100016) | |
| Platform | When the Maximo Real Estate and Facilities system is locked using the Lock System feature on the System Info page of the Administrator Console, the Administrator Console can still be accessed by adding html/en/default/admin to the end of the Maximo Real Estate and Facilities base URL. Note: Administrator Console access does not work if the URL includes adminMainFrameSet1.jsp?. (MAS-794) | |
| Platform | The user can now schedule reports that have names of less than 3 characters. (Tri-86781) | |
| Platform | User actions and changes will be tracked on all pages of the Maximo Real Estate and Facilities Administrator Console, except for the Admin Summary and Build Number pages. (MASR-2513) | |
| Platform | The invalid values in the Association list have now been removed. (Tri-100123) | |
| Platform | The report execution history is now tracked for BIRT reports loaded using the portal sections. (Tri-101327) | |
| Platform | The message for invalid precision inside the report manager is now updated. (Tri-99169) | |
| Platform | Fixed the issue where a blank report name was not showing the proper error message. (Tri-101231) | |
| Platform | Users can switch tabs without any issues when a valid value is entered inside a system filter with an IN operator. (Tri-101236) | |
| Platform | In System Reports, the Business Objects (BOs) are displayed as BO labels in an alphabetical order in each module. Also, the tooltips display the BO labels instead of BO names. (Tri-101185) | |
| Platform | Accessibility for screen reader users has been improved on the Reports page. When you use the screen reader software and use the actions such as "Copy", "Delete", "Copy as Community Report", or "Share Report", the screen reader now clearly announces the opening of the associated alert window. This improvement provides a clearer user experience when interacting with reports by using assistive technology. (Tri-93086) | |
| Platform | In the Display Column section, modification of the Report Label is correctly reflected during the report runtime. (Tri-100893) | |
| Platform | In rare cases, certain reports may experience an unintentional status change to "Work In Progress". This can occur due to issues such as BoField label changes, invalid BoSections, or BoFields that were introduced during the process flow but not properly reflected in the report tables. (Tri-102095) | |
| Platform | Updated the null values in the sequence fields of the related reports with the appropriate sequence numbers, ensuring they follow the correct order based on the related report IDs. (Tri-101914) | |
| Platform | Implemented logic to bypass invalid boFields during the object comparison process and applied corrections to the column sequence accordingly. (Tri -101481) | |
| Platform | Related reports now consistently use the published data of the report in the report designer and during runtime. (Tri-101684) | |
| Platform | The display sequence changes for related reports is tracked during the revision comparison process. (Tri-101399) | |
| Platform | Creating a copy of a report updates the 'Modified By' value with the details of the currently logged-in user on the General and Revisions tabs. (Tri-101173) | |
| Platform | The Child Details column is available for all the reports that were previously valid hierarchy reports, regardless of the current report type. (Tri-101387) | |
| Platform | On the Advanced tab of reports, in the Actions form, the Secondary Action checkbox is now displayed properly in the Firefox browser. (Tri-101495) | |
| Platform | The Object Label details on the General tab will align with the most recent Object Label information on the Revisions tab. (Tri-101699) | |
| Platform | The change in the state of a record will be included in the revision comparison only when the report is editable. (Tri-101477) | |
| Platform | Related reports with a blank or null header value will be handled and treated as having an empty value. (Tri-101681) | |
| Platform | Comparing revisions in the report manager will no longer show a false positive difference because the valid order and group-by column details are no longer being removed. (Tri -101919) | |
| Platform | The report names containing '<' and '>' symbols are displayed correctly without being interpreted as HTML tags in the 'Name' column of the Related Reports tab. (Tri-102062) | |
| Platform | You can securely authenticate Connector for Business Application (CBA) requests in Maximo Real Estate and Facilities by adding authentication headers “Username” and “Password” and their corresponding values to the CBA request. (MASREF-1088) | |
| Platform | The 'Use single sheet' checkbox on the export report window dialog box will be if the property - BIRT_XLSX_DISABLE_REPEATED_HEADERS is set to true. (Tri-100690) | |
| Platform | BIRT now supports display parameters in a report. (Tri-60636) | |
| Platform | Fixed an issue with the ODT export where parameter values were not displayed properly. (Tri-81292) | |
| Platform | Resolved an issue where the toolbar failed to display when a BIRT report was queued. (Tri-100930) | |
| Platform | Fixed an issue where users were logged out when BIRT report requests were cancelled. (Tri-99425) | |
| Platform | Fixed an issue where parameter values were populated as null instead of default values when a BIRT report was run from an app server. (Tri-101132) | |
| Platform | PPT has been removed from the available BIRT export options. Users must use the alternative format: PPTX. (Tri-65797) | |
| Platform | BIRT now supports exporting images through Spudsoft Excel (.xls). (Tri-81290) | |
| Platform | Fixed an issue where the file name did not populate correctly when exporting a BIRT report as a CSV using the Extract Data option from an offloaded report. (Tri-101131) | |
| Platform | BIRT now supports single page export for Excel (.xlsx) format. (Tri-94698) | |
| Platform | BIRT now supports single page export for Spudsoft Excel (.xls) format. (Tri-101241) | |
| Platform | The BIRT queuing window user experience is now enhanced. (Tri-100940) | |
| Platform | BIRT now exports master page information for XLSX export type. | |
| Platform | The BIRT engine and viewer is now upgraded to 4.16.0 version. (Tri-100335) | |
| Platform | BIRT now supports creating password protected XLSX and XLS files. (Tri-101232) | |
| Platform | Fixed an issue where the Bookmark button disappeared after running an external report. (Tri-101984) | |
| Platform | The user will now see the following message when attempting to export data without selecting any columns: "No column is selected. Please select at least one column for export." (Tri-101186) | |
| Platform | Fixed an issue where canceling the processing of a BIRT report would log out users. (Tri-99425) | |
| Platform | A minimum password length requirement of 6 characters has been added to the password protection functionality for exported XLSX BIRT reports. (MASREF-795) | |
| Platform | The POI library was upgraded. (Tri-102153) | |
| Platform | In the Work In Progress state of a report, the Object Label on the General tab is set to ObjectLabelPending. (Tri-101698) | |
| Platform | Comparing revisions in the Report Manager will no longer display a false positive difference on secondary section names in the column details. (Tri-101476) | |
| Platform | Empty or null association type values are now consistently displayed as "-" across the query design to ensure uniformity. (Tri-102102) | |
| Platform | The intermittent issue in Report Manager has been fixed. Previously, clicking the "Clear Filter" button on the My Reports tab would incorrectly display the error message "Not able to retrieve My Report." Similarly, clicking the System Reports tab would display "Not able to retrieve System Report." (Tri-93416; 101028) | |
| Platform | Implemented bypass logic to skip the unintended report data difference caused by the incorrect sequence data in the display, order, and filter columns for certain system reports. (Tri-101293) | |
| Platform | Users will be able to filter reports by using the '\' escape character in the Report Manager. (Tri-100969) | |
| Platform | Resolved an issue where certain click streams allowed two queries in the same module to have the same name. Now, two queries in the same module cannot have the same name, queries within the same module must have unique names. (Tri-101279) | |
| Platform | The Created By field of a report is no longer modified during OM import and consistently displays the expected value. (Tri-101685) | |
| Platform | The creation of report revisions is now prevented along with an alert for duplicate names within the same module. (Tri-101344) | |
| Platform | Modified the tooltip for the Modified Date column in the Object Label Manager. Now, hovering the date in the Modified Date column will display the date instead of milliseconds. (Tri-101368) | |
| Platform | Nested interactive controls in the "Add Bookmark" and "My Bookmarks" sections are now hidden. (Tri-98734) | |
| Platform | The warning "Web Message Does Not Exist" displayed in the server.log file is now resolved. (Tri-101546) | |
| Platform | The range operator has been updated to produce accurate and reliable results when used in summary reports. (Tri-100995) | |
| Platform | Resolved the issue with column width adjustment that occurred when you switched operators in date-type fields within the filter modal. (Tri-101167) | |
| Platform | This fix ensures that the last column in the grid flexes correctly, with the minWidth value applied to prevent the column from shrinking below its defined minimum size. (Tri-101305) | |
| Platform | Resolved the issue of interactive controls being nested for the side navigation component when the accessibility mode is enable in your profile. When running in Accessibility Mode, you'll no longer be able to right-click on nested side navigation items or access browser context menu options, such as Open in New Window or Open in New Tab. (Tri-100760) | |
| Platform | The filter criteria bar is now correctly displayed after clearing the prompt message, and this fix applies to all report types when a filter input is present. (Tri-101657) | |
| Platform | The "IN" and "NOT-IN" operators for query reports are now functioning correctly for number fields. (Tri-101706) | |
| Platform | The default column widths for the dateTime filters are set at 318px for range operators and 172px for all other operators. (Tri-101261) | |
| Platform | If queries running through enhanced report rendering grids run into an out-of-memory issue, an error message is now displayed to notify the user. (Tri-100786) | |
| Platform | The calendar icon has been removed from the DateTime filter input in queries. You can now enter date, time, period, and timezone directly. (Tri-101265) | |
| Platform | The Community reports will be displayed in the Report Manager by using the latest published data from the version table. (Tri-99136) | |
| Platform | A new column called "Report Status" has been added to both the My Reports and System Reports sections in the Report Manager. This column indicates whether a report is "Work In Progress" or "Published". (Tri-99137) | |
| Platform | You can now run any version of a report by clicking the Run Report play button on the Revisions tab. (Tri-99532; 97416) | |
| Platform | All runtime queries will use the latest published data from the revision tables to render reports. (Tri-97274) | |
| Platform | Users have the ability to run any metric report version by clicking the Run Report Play button available on the Revisions tab. (Tri-100233) | |
| Platform | The design-time version of a metric report is rendered when the metric report is run from the report template by clicking the “Run Report” button. (Tri-100232) | |
| Platform | Report status is displayed in the title bar of the report: • Published versions of the report shows the ""Published"" status. • Saved and design-time version of the report shows the ""Work In Progress"" status. (Tri-97272) | |
| Platform | The design-time version of a report will be available in the Revisions tab of the report template. A revision is marked with a “-“ symbol and the status is indicated as “Work In Progress“ in a different color and can be compared with any other version to track the changes. (Tri-97271) | |
| Platform | The design-time version of a report will be rendered when the report is run from the report template by clicking the “Run Report” button. (Tri-98562) | |
| Platform | All Metric Runtime Queries will display the metric report based on the most recent published data available in the revision tables. (Tri-100231) | |
| Platform | The "Modified By" and "Modified Date" details on the General tab will align with the most recent modified information on the Revisions tab. (Tri-101388) | |
| Platform | Update logic has been added to correct sequence data in the display, order, and filter columns in the database for specific system reports. This logic is triggered when the Save or Apply Revision operation is performed. (Tri-101469) | |
| Platform | Report Manager can render hierarchy reports with the versioning concept and can run any version of the hierarchy report by clicking the ""Run Report Play"" button on the Revisions tab. (Tri-99313) | |
| Platform | The "Publish" button is enabled only for reports that are in the "Work In Progress" state. (Tri-101175) | |
| Platform | Introduced a new Publish button. When you publish the reports, the ""Show As Community Report"" and ""Report Security Access"" actions are activated and displayed in the Report Manager. (Tri-97269) | |
| Platform | Report Manager can render the hierarchy reports with versioning concept and can run any version of the hierarchy reports by clicking the Run Report Play button on the Revisions tab. (Tri-99312) | |
| Platform | The Report Manager has been enhanced with a new "Publish" button, replacing the existing "Save & Close" button. (Tri-97268) | |
| Platform | A new column has been introduced on the Revision tab of valid Hierarchy Reports to display the relevant child details. (Tri-100241) | |
| Platform | The Object Migration export and import operations for queries will use the most recent published details. (Tri-97275) | |
| Platform | The Object Migration import suspends work-in-progress queries before importing the exported data. (Tri-100877) | |
| Platform | All runtime queries, regardless of whether they are rendered using the enhanced renderer or classic renderer, display the latest published version of the report data from the revision tables. (Tri-98546) | |
| Platform | The report name must be unique within the same module. To ensure this, the system checks for duplicate report names using the design-time data. This validation prevents the creation of multiple reports with the same name. (Tri-100984) | |
| Platform | A new "Copy All Display Columns" button has been added to the User Filter Columns section on the Report Filters tab. This button allows you to automatically add all display columns as user filters. (Tri-99998) | |
| Platform | All the runtime queries will render reports from the most recently published version data in the revision tables. (Tri-97270) | |
| Platform | Resolved issues with Metric Report results and fixed a null pointer exception (NPE) that occurred when saving settings. (Tri-101355) | |
| Platform | The report's 'Tag' and 'Precision' values will now be included in the comparison process. Changes to these fields will be accurately tracked and reflected in revision comparisons. (Tri-101212) | |
| Platform | Changes to the Metric Report will now take effect immediately, without requiring a global cache clear. (Tri-99334) | |
| Platform | The report header containing < and > symbols is now displayed correctly in the 'Header' column of the Related Reports tab, without being interpreted as HTML tags. (MASREF-788) | |
| Platform | Focus now works correctly inside the bookmark popup window. When the user presses "Enter" while the focus is on the Cancel button, the focus moves to the next available item. (Tri-93277) | |
| Platform | There is now enhanced TRIRIGA security on SQL Injection. (Tri-102016) | |
| Platform | Cloud login custom configurations now support OAuth providers that require a proof key for code exchange. (Tri-100902) | |
| Platform | The Apache POI library is upgraded. (Tri-98304; 102101) | |
| Platform | Enhanced security for Cross Site Scripting (XSS). (Tri-100456; 101970; Tri-101829; 101996; 101997) | |
| Platform | A new CSV_INJECTION_EXCLUDE_LIST setting has been added to TRIRIGAWEB.properties, which ensures that records can no longer be created with special characters at the start of their name. (Tri-100558) | |
| Platform | When you create reports, ensure that report names only use acceptable characters as defined in TRIRIGAWEB.properties. (Tri-100429) | |
| Platform | The org.eclipse.core.runtime jar is now upgraded and the org.eclipse.pde jar was removed. (Tri-98361) | |
| Platform | Loggers has replaced references of e.printStackTrace() with logging. (Tri-99432) | |
| Platform | The Axis jar file has been updated to a newer version. (Tri-100474) | |
| Platform | The Eclipse jetty-http.jar file has been upgraded. (Tri-100696) | |
| Platform | Enhanced security by supporting request rate limiting. (Tri-99563) | |
| Platform | The Apache Commons Codec JAR dependency has been removed from the BIRT SpudSoft emitter. (Tri-100636) | |
| Platform | Upgraded the gwt-servlet-jakarta.jar file. (Tri-101918) | |
| Platform | The TinyMCE rich text editor has been upgraded. (Tri-99342) | |
| Platform | Spring has been upgraded. (Tri-99959; 100753) | |
| Platform | A false positive security issue that was logged while logging in by using cloud login is now corrected. (Tri-100921) | |
| Platform | WebSphere Liberty has been updated. (Tri-101197) | |
| Platform | Security enhancements have been made on the WSDL layer. (Tri-101589) | |
| Platform | Security enhancements were made to mitigate Reflected Cross Site Scripting (XSS) attacks. (Tri-100386; 100085) | |
| Platform | Security enhancements have been implemented on the platform for MS Project. (Tri-100888) | |
| Platform | The Minimist library has been upgraded to the latest version. (Tri-97990) | |
| Platform | Canvg dependency has been removed. (Tri-101939) | |
| Platform | Enhanced the security by preventing XXE injection through OSCRE XML file import. (Tri-100467) | |
| Platform | On applying the Java filter the system now effectively blocks unauthorized objects from being loaded, reducing the risk of insecure deserialization attacks while ensuring the application continues to function as expected. (Tri-102045) | |
| Platform | Permission changes in admin console now take effect immediately without needing to log in again. (Tri-100454) | |
| Platform | The workflow text export will now include the object labels. (Tri-90106) | |
| Platform | Validation rules have been applied to all required fields within the forms. (Tri-101377) | |
| Platform | TCP timestamps have now been disabled. Reference: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_for_real_time/8/html/optimizing_rhel_8_for_real_time_for_low_latency_operation/assembly_reducing-tcp-performance-spikes_optimizing-rhel8-for-real-time-for-low-latency-operation#proc_turning-off-tcp-timestamps_assembly_reducing-tcp-performance-spikes (Tri-100809) | |
| Platform | The user entered details are now persisted for Rich Text Editor Style in Style Manager. (Tri-99610) | |
| Platform | When you click Export in Style Manager, no errors related to streams are now displayed in logs. (Tri-101119) | |
| Platform | The FACILITIESADMIN user will always default to the BASE license during the IBM Maximo Application Suite sync process, regardless of the license selected when creating or updating the user. Please note that a valid license must be selected; it cannot be left blank, and it cannot be set to "No Access", or the sync will not occur with IBM Maximo Real Estate and Facilities. (MASREF-805) | |
| Platform | IBM Security Verify is now a supported provider for Cloud Login. (Tri-100913) | |
| Platform | Themes now correctly load even if the server does not have a theme labeled "triAssets001". (Tri-100879) | |
| Platform | The scroll bar will remain aligned with the form based on the currently active element.(Tri-95941) | |
| Platform | Updated the appropriate warning message in case of mapping into Live Link section field. (Tri-101603) | |
| Platform | In Workflow Builder, the tooltip text for the collapse icon, which is used for open and close actions, now displays "Open' and 'Close' labels instead of 'Undefined'. (Tri-101017) | |
| Platform | Resolved a character encoding issue in the "Where Used" section of Workflow Builder.(Tri-102083) | |
| Platform | The Drawing Info panel now displays details about linked files for drawings that include external references. (Tri-101863) | |
| Perceptive Application | For Occupancy by Organization assignment with the "people" policy, the calculation of supply, demand, and stack count has been updated to align with the Stacking app. Supply is now based on the space’s capacity, while demand reflects the number of assigned seats. (Tri-102092) | |
| Perceptive Application | Resolved an error that occurred when a floor had exactly two spaces with Work Point set to true. (Tri-102035) | |
| Perceptive Application | An issue that allowed duplicate scenario names to be created has been fixed. (Tri-101840) | |
| Perceptive Application | Many dialogs now correctly set keyboard focus to the primary or secondary button when opened. (Tri-101409) | |
| Perceptive Application | Users can now add contact roles to the 'Floor Scenario' under the 'Contacts' tab. (Tri-101376) | |
| Perceptive Application | When opening a stack plan from the Dynamic Space Planning statistics table, Stack plans can now be selected with a single mouse click. (Tri-100476) | |
| Perceptive Application | The loading indicator is now properly canceled when Dynamic Space Planning is opened for a floor that does not have an attached drawing. (Tri-100475) | |
| Perceptive Application | Removed people are no longer stored with the scenario. They are now determined each time a scenario is opened by comparing the assignments in the scenario against current baseline assignments. (Tri-100245) | |
| Perceptive Application | Resolved an issue with staging people where individuals removed in the baseline and later re-added in a scenario were not handled correctly. (Tri-99758) | |
| Perceptive Application | The issue related to the missing triSpace - UX - Drawing Manager - Space Lookup query has now been resolved. (Tri-100162) | |
| Perceptive Application | When using Occupancy by Organization and the policy is based on people, any individuals assigned to a floor but not associated with an organization are automatically grouped into an artificial organization called ""Unassigned."" This "Unassigned" group is treated like a regular organization within DSP. In DSP: • "Unassigned" appears in the Occupancy Org legend. • Spaces are color-coded to reflect unassigned individuals. • A stack bar segment and stack filter option exist for "Unassigned." • The ""Remove People by Organization"" feature includes "Unassigned" as a selectable option. However, the "Unassigned" organization exists only within DSP. It is not included in staged data and is ignored during staged organization updates. As a result: • There may be discrepancies between the stack bar and the statistics table in stacking and DSP. • DSP will display a mismatch warning when opened on floors with unassigned individuals. (Tri-102159) | |
| Perceptive Application | The filter tooltips now include a Select button that selects the spaces associated with the filter item. (Tri-102118) | |
| Perceptive Application | A Space List panel has been added, displaying all the spaces on the floor. (Tri-102088) | |
| Perceptive Application | Improvements have been made to enhance the responsiveness of dropping people pins on large floor plans. Users will notice the following: • Pin placement on the floor plan is now more responsive. • Space color updates based on assigned people may occur shortly after the pin is placed. • Legend updates may be slightly delayed following pin assignment. • The statistics table and stack bar may also update with a slight delay after a pin is placed. (Tri-101086) | |
| Perceptive Application | Dynamic Space Planning can now load newly created stack plans that have not been modified or saved. (Tri-100460) | |
| Perceptive Application | The stack bar tooltip on the Dynamic Space Planning floor plan now displays space class colors in the Spaces tab. (Tri-100080) | |
| Perceptive Application | The occupancy organization of selected spaces can now be copied to their corresponding charge-to organization. (Tri-99791) | |
| Perceptive Application | Drag-and-drop of people now correctly accounts for updated space capacity changes. (Tri-99756) | |
| Perceptive Application | The charge-to organization of selected spaces can now be copied to their corresponding occupancy organization. (Tri-99754) | |
| Perceptive Application | The PDF export legend now supports both count and area columns. (Tri-99732) | |
| Perceptive Application | The "Show By" and "Filter By" entries now include tooltips displaying the count and area for each item. (Tri-99701) | |
| Perceptive Application | The Distance Factor tool now displays both the count and the total area of available spaces. (Tri-99686) | |
| Perceptive Application | There is now a dialog to show the current (edited) state of a space. (Tri-99685) | |
| Perceptive Application | All Drawing Manager functions are now incorporated into Dynamic Space Planning, which is included with the Maximo Real Estate and Facilities 9.1 application. However, Drawing Manager remains available as a standalone application and is included with the Maximo Real Estate and Facilities 9.1 Platform. (Tri-99535) | |
| Perceptive Application | The Remove People by Organization table now displays the number of people to be removed. (Tri-99238) | |
| Perceptive Application | The Graphics React application now runs correctly using npm start. (Tri-99600) | |
| Perceptive Application | The version of the Autodesk Platform Services viewer used by Maximo Real Estate and Facilities is no longer compatible with Firefox. (Tri-101214) | |
| Perceptive Application | If records are closed when either Drawing Manager, Stacking, or Dynamic Space Planning use the in-line options to display TRIRIGA records, the frame must be closed manually. (Tri-100831) | |
| Perceptive Application | On SQL Server, when using the legacy stack planning app, it may be necessary to close and reopen the application for a newly created stack plan to display properly. (Tri-101505) | |
| IJ53766 | Lease Accounting | Issue: In the ""Process Payments,"" ""Void Payments,"" and ""Process AR Receipts"" forms, clicking the 'Find' action automatically retrieves all Payment Line Items (PLIs) without allowing the user to filter results. This can lead to long processing times and inefficiency. Fix: The ""Prompt Before Query"" setting has been enabled for all PLI 'Find' queries and their associated reports. This change prompts users to apply filters before executing the query, significantly improving performance and usability. Additional Enhancements: • On the Generate Lease Invoice form: • A new parameter, ""Lease Primary Location Geography"", has been added to the General tab. This parameter serves as a filter in the ""Find Real Estate Lease"" query and is now included as an additional column in the master query. • In the AR Leases section: • A new action, ""Get Contracts,"" is introduced to retrieve Accounts Receivable (AR) Leases based on the ""Due Before"" and ""Primary Location Geography"" parameters (for Real Estate leases). • Enhanced filtering capabilities have been added to ""Find"" actions for both Real Estate Lease and Asset Lease, allowing users to refine results using the ""Due Before"" and ""Lease Primary Location Geography"" fields (for Real Estate leases). • Security Access: The following security groups now have access to the newly added actions: 'Find Asset Lease', 'Find Real Estate Lease', and 'Get Contracts' within the 'AR Lease' section of the Generate Lease Invoice form: • TRIRIGA RE Contract Manager • TRIRIGA RE Contract Manager - Fundamentals • TRIRIGA Lease Accountant • TRIRIGA Lease Accountant - Fundamentals • TRIRIGA Local Lease Accountant (Tri-101893-IJ53766) |
| IJ51017 | Lease Accounting | Issue: For IFRS standard leases, applying the Index Adjustment Calculator causes the IAS 17 accounting schedule (old standard) to be recalculated. Fix: The application has been updated so that the IAS 17 accounting schedule (old standard) will no longer be recalculated for IFRS standard leases when the Index Adjustment Calculator is applied. (Tri-98763-IJ51017) |
| IJ51082 | Lease Accounting | Issue: In the Local Reporting tab of the financial schedule, the Net Asset Value was not reducing to zero after applying multiple Index Adjustment Calculators. Fix: The Net Asset Value now correctly reduces to zero after issuing multiple Index Adjustment Calculators. Additionally, for the Non-Rent Index Calculator, application no longer displays the Recalculate Accounting Schedule action, as non-rent adjustments do not impact the accounting schedule and recalculation is not required for non-rent payments. (Tri-98661-IJ51082) |
| IJ51326 | Lease Accounting | Issue: When a lease with a Tenant Improvement Incentive payment schedule before the commencement date is modified within the first period, the re-calculated accounting schedule did not include the Tenant Incentive in the Current Asset Value. Fix: The Tenant Incentive is now correctly included in the Current Asset Value after recalculating the accounting schedule. (Tri-99065-IJ51326) |
| IJ51395 | Lease Accounting | Issue: Performing a Data Revise triggered unnecessary re-calculation of the lease term length and short-term leases. Fix: The lease term length and short-term leases are no longer recalculated during a Data Revise. (Tri-99106-IJ51395) |
| IJ51754 | Lease Accounting | Issue: The workflow “triAssetLease - DELETE FROM MGR” was being triggered by the triCreateDraft action. Fix: The “triAssetLease - DELETE FROM MGR” workflow will now be triggered only by the “WF DELETE FROM MGR” action. (Tri-99562-IJ51754) |
| IJ51771 | Lease Accounting | Issue: After upgrading the application to version 11.4 or higher, payment breakdown items were not being created for payment line items that had been previously adjusted retroactively. This was due to the absence of a temporary field needed to capture the retroactive adjustment amount. Fix: A new field, triTempRetroactiveAdjustNU, has been added to the System tab of the Payment Line Item form to capture the retroactive adjustment amount. Payment breakdown items are now correctly generated based on this amount. (Tri-99570-IJ51771) |
| IJ51817 | Lease Accounting | Issue: When creating a Tenant Improvement Incentive (TI) payment schedule for an Income Sublease, the Accounting Type was incorrectly reverting to Accounts Receivable (AR), even when the user selected Accounts Payable (AP). Fix: The system now correctly assigns the Accounting Type on TI payment schedule based on the lease type. (Tri-99621-IJ51817) |
| IJ51913 | Lease Accounting | Issue: During the Data Revise process, the associated Temporary History lease was expected to be deleted, but it remained in the system. Fix: The system now correctly deletes the Temporary History lease when performing a Data Revise. For existing leases with multiple Temporary History leases, a patch helper workflow has been provided to address the issue. Workflow Name: triPatchHelper - triCalculate - 11.7 - Remove Data Revise Temp History From Contract (Tri-99736-IJ51913) |
| IJ52073 | Lease Accounting | Issue: The REPaymentFact ETL job previously encountered issues when processing items with 700 characters in the triContractNameTX field. Fix: The ETL job now successfully processes items with up to 700 characters in the triContractNameTX field. (Tri-99977-IJ52073) |
| IJ52125 | Lease Accounting | Issue: The ""Estimated Economic Life of Asset (Months)"" field was accepting decimal values, but those decimals were not being considered in the calculation of the ""Estimated Economic Life of Asset End Date."" Fix: A new field, ""Estimated Economic Life of Asset (Days),"" has been introduced. Users can now enter the number of days, and the ""Estimated Economic Life of Asset End Date"" will be accurately calculated based on both the ""Months"" and ""Days"" fields. (Tri-100032-IJ52125) |
| IJ52170 | Lease Accounting | Issue: When running the ROUA Roll Forward Report on an existing lease with a cutover Contract Summary Balance, the Opening Gross ROU Asset Balance and Opening Accumulated Amortization columns were showing as zero. Fix:The Opening Gross ROU Asset Balance and Opening Accumulated Amortization columns are now correctly calculated for both Functional and Reporting currencies. This fix also resolves the same issue observed in the Liability Roll Forward Report. Note: If the reports were previously run, select ""Force Recalculate"" on the Roll Forward reports and process it to apply the correction. (Tri-100167-IJ52170) |
| IJ52257 | Lease Accounting | Issue: When making a second retroactive adjustment to a payment schedule on the same day to update the description with the same amount, the retro payment line item that had been created by the first adjustment has been removed. Fix: The application retains the retro payment line item if a user makes the multiple payment adjustments on the same day without changing the adjustment amount. (Tri-100238-IJ52257) |
| IJ52356 | Lease Accounting | Issue: When the Base Lease Expiration date and the Accounting End date are updated on a Real Estate lease with a renewal option set to 'likely term' and exercised, and the updated Base Lease Expiration date extends beyond the Likely Term End date of the exercised term, the Likely Expiration Date on the lease does not align with the updated Base Lease Expiration date. This leads to the incorrect generation of operating schedules. Fix:The following changes have been made in this release: 1. The Likely Expiration Date on the lease record will now update from the Likely Term End date of the Likely Term option, but only if the Likely Term option is active. 2. If the Likely Term option is exercised and the Base Lease Expiration Date is greater than the Likely Term End date, the Likely Expiration Date will update from the Base Lease Expiration Date. Otherwise, it will update from the Likely Term End date of the Likely Term option. 3. If the Likely Term option is retired, expired, or terminated, the Likely Expiration Date will always update from the Base Lease Expiration Date. Note that for adoption cases, the same logic will apply. Additionally, when the user clears the option from the current lease: 1. If the lease has no history without the Likely Term option, the Likely Expiration Date on the current lease will update with the Base Lease Expiration Date. 2. If there is a history without the Likely Term option, and the Base Lease Expiration Date on the current lease is greater than the Likely Expiration Date in the history, the Likely Expiration Date on the current lease will update with the Base Lease Expiration Date. 3. If there is a history without the Likely Term option, and the history's Likely Expiration Date is greater than the Base Lease Expiration Date on the current lease, the Likely Expiration Date on the current lease will update with the history's Likely Expiration Date. (Tri-100298-IJ52356) |
| IJ52410 | Lease Accounting | Issue: When a user performs the retro payment adjustment with partial dates on the payment schedule, the catch-up amount is incorrectly calculated. Fix: The catch-up amount is correctly calculated if a user performs the retro payment adjustment with partial dates on the payment schedule. A catch-up payment line item is generated with the correct amount. (Tri-100377-IJ52410) |
| IJ52594 | Lease Accounting | Issue: The Closing Net Asset from Schedule columns for both the functional currency and reporting currency were showing zero when the Net Asset Value (Lease Currency) field on the Lease Summary Balance (LSB) was populated. Fix: These columns now correctly display values and no longer show zero when the Net Asset Value (Lease Currency) is populated on the LSB. To ensure FX rates are properly updated from the cutover LSB to both the current lease and the temporary history lease, execute the following patch helper workflow using the string: ""MREF 9.1 - UpdateFXRate"" Workflow Name: triPatchHelper - triCalculate - MREF 9.1 - UpdateFXRate - Update Currency Conversion Rates on Lease (Tri-100534-IJ52594) |
| IJ52794 | Lease Accounting | Issue: In the Option Master Disclosure Report, when the Option Effective Date is earlier than the Period As Of date selected in the Contract Disclosure Report, the ""Months to Effective Date (From As Of Date)"" field was displaying negative values. Fix: The report logic has been updated so that when the Option Effective Date precedes the Period As Of date, the ""Months to Effective Date (From As Of Date)"" field will now display zero instead of a negative value. (Tri-100608-IJ52794) |
| IJ52914 | Lease Accounting | Issue: When an index adjustment was issued, the modified lease was incorrectly changing from long-term to short-term. Fix: This issue has been resolved. After an index adjustment is applied, a long-term lease now correctly remains classified as long-term. (Tri-100853-IJ52914) |
| IJ53042 | Lease Accounting | Issue: Leases with a status of ""Revision"" were excluded from the Lease Disclosure and Roll Forward reports. Fix: Leases with statuses ""Revision In Progress,"" ""Revision Accounting In Review,"" and ""Revision In Progress Returned"" are now included in the report results, provided they have a contract summary balance for the periods specified in the report parameters. (Tri-101059-IJ53042) |
| IJ53068 | Lease Accounting | Issue: The Revision Number column was not displayed in the Modification History of Asset Lease section on the History tab of Asset Lease. Fix: The Revision Number column is now included in the Modification History of Asset Lease section on the History tab of Asset Lease. (Tri-101101-IJ53068) |
| IJ53069 | Lease Accounting | Issue: When terminating a lease in the mid-month for non-rent payments and the lease does not have the fiscal line items, the 'Payment for Partial Period' field was not appearing on the Contract Termination form. Fix: User can now see the option to prorate the payments while terminating the non-rent payment leases (Tri-101120-IJ53069) |
| IJ53088 | Lease Accounting | Issue: For leases created prior to version 11.1, where the lease currency and functional currency are the same, modifying the lease did not update the blended rate to 1. Instead, it was incorrectly calculated using an invalid rate. Fix: The blended rate is now correctly updated to 1 when the lease and functional currencies are the same. (Tri-101153-IJ53088) |
| IJ53091 | Lease Accounting | Issue: For IFRS leases, when a reasonably certain option existed on an active lease, and the lease term was reduced during a modification while making the option reasonably uncertain, the application was considering it as a reduction in lease term scenario. Fix: The application will no longer consider the above scenario as a modification that decreases/reduction in the lease term.(Tri-101161-IJ53091) |
| IJ53149 | Lease Accounting | Issue: When a user performs multiple modifications in the same period and the previous modification had the gain/loss generated is getting cleared in the next modification in that same period. Fix: The application will no longer clear the gain/loss in cases of modifications in the same period and will now include the gain/loss in the current accounting calculations. (Tri-100943-IJ53149) |
| IJ53362 | Lease Accounting | Issue: When executing the ""Weighted Average Remaining Lease Term and Discount Rate Report"" application version prior to 11.1 on Platform 5.0 with a DB2 database, an error occurs: java.lang.ArrayIndexOutOfBoundsException at java.math.BigDecimal. Fix: This report is no longer included by default in application versions after 11.1. For guidance on resolving this issue, refer to https://www.ibm.com/support/pages/node/7184853. (Tri-101608-IJ53362) |
| IJ53537 | Lease Accounting | Issue: The new blended rate is calculated incorrectly after a lease modification. Fix: After the cutover Lease Summary Balance (LSB) is created for each lease, the following patch helper workflow must be executed to update the FX rates from the cutover LSB back to both the current lease and its temporary history lease. To trigger the update, use the string: ""MREF 9.1 - UpdateFXRate"" Workflow Name: triPatchHelper - triCalculate - MREF 9.1 - UpdateFXRate - Update Currency Conversion Rates on Lease (Tri-101709-IJ53537) |
| IJ53786 | Lease Accounting | Issue: On the Generate Payment Schedule page, when a user selects an Expense Cost Code using the ‘Find’ action, it automatically runs a query to fetch all active cost codes. This process takes time when there are many cost code records. Additionally, the hierarchy for the cost code is not shown, so users may select the wrong cost code due to the missing information. Fix: The ""Prompt Before Query"" option is enabled for all types of Cost Code ""Find"" queries and their related reports. This allows users to apply a filter first. Additionally, the ""Hierarchy Level"" column is added to all Cost Code ""Find"" queries.(Tri-101898-IJ53786) |
| IJ53787 | Lease Accounting | Issue: The Lease Manager query currently lacks the Address column, making it difficult to identify the exact location of a lease. Similarly, the Process Payment form is missing the Country column, which makes it unclear which record the payment was created for. Fix: • The Address column has been added to the Lease Manager query and all associated reports. • A new field, Lease Primary Location Geography, has been introduced in the Parameters section of the Process Payment form. This filter applies only to Real Estate Leases and has also been added to the Process Payments Manager query and its related reports. Enhancements: • Separate ""Find"" actions have been introduced for: • Real Estate Lease PLIs • Asset Lease PLIs • SBITA Contract PLIs These are available in the Payment Line Items section of the Process Payments form. • When users input values in the Parameters section, both the ""Get Payments"" action and all ""Find""actions in the Payment Line Items section will filter results accordingly. If a parameter is left blank, that specific filter will be ignored. • The newly added ""Find"" actions in the Payment Line Items section are now accessible to the following security groups: • TRIRIGA Contract Manager • TRIRIGA RE Contract Manager • TRIRIGA RE Contract Manager - Fundamentals • TRIRIGA Lease Accountant • TRIRIGA Lease Accountant - Fundamentals • TRIRIGA Local Lease Accountant • Additionally, parameter values will now be captured in the history record when a Process Payments record is revised. (Tri-101894-IJ53787) |
| IJ53855 | Lease Accounting | Issue: On the Owned Property (Fee) Agreement form, when a user performs a Non-Lease Accounting Amendment revision, the Contract Locations section becomes non-editable. If a data revise or amendment is later performed, the section remains non-editable. Fix: The Owned Property (Fee) Agreement form will now allow only data revise and amendment revisions. The Non-Lease Accounting Amendment is not applicable to this form. The History tab will display both the REContract Revision and Owned Property (Fee) Agreement Revision records in the Amendment History query section. Any new revision will now create an Owned Property (Fee) Agreement Revision record. As part of the fix, the following changes have been made: 1. When performing a data revise, the Critical Dates and Payment Schedule sections will become read-only. 2. When performing an amendment, the Critical Dates, Contract Locations, and Payment Schedule sections will remain editable. (Tri--101920-IJ53855) |
| IJ53856 | Lease Accounting | Issue: When a user performs an amendment on an Owned Property (Fee) Agreement without any payment schedules added, an attention message related to accounting end date validations is displayed. Fix: The attention message no longer appears. Accounting end date validations are now skipped during the amendment revision of an Owned Property (Fee) Agreement. (Tri-101921-IJ53856) |
| IJ53992 | Lease Accounting | Issue: The label ""Lease Journal Entry Setup Template"" was renamed to ""Contract Journal Entry Setup Template. However, the 'Linked Form' field and publish name in all out-of-the-box (OOTB) Calculation Inputs records linked to the updated templates still reflect the outdated values. This mismatch is resulting in the creation of duplicate calculation variables during the upgrade process. Fix: The Linked Form and publish name of OOTB triJournalEntryCalculationVariable records associated with the Contract Journal Entry Setup Templates have been updated to match the new naming convention. To ensure consistency moving forward, the patch helper workflow will automatically update the Linked Form and publish name of triJournalEntryCalculationVariable records linked to both the Contract Journal Entry Setup Templates and Contract Journal Entry Setup, if any outdated values remain. Additionally, the ""triLinkedForm"" list must be manually updated: • In the parent list, select ""Journal Entry Setup"" • Remove the outdated entry: ""Lease Journal Entry Setup"" • Add the updated entries: ""Contract Journal Entry Setup"" and ""Contract Journal Entry Setup Template"" (Tri-101979-IJ53992) |
| IJ54050 | Lease Accounting | Issue: Payment schedules that are unchecked for ""Include in Amortization Schedules"" are still being considered for generating the accounting schedules. Fix: The application now only considers payment schedules that are checked for ""Include in Amortization Schedule"" when generating accounting schedules. (Tri-102011-IJ54050). |
| IJ54097 | Lease Accounting | Issue: When terminating a lease with a termination penalty and the lease currency is other than US Dollars, the Termination Fee journal entry displayed an incorrect amount. This occurred due to an unintended currency conversion from the lease currency to USD (but only when a conversion rate was available). Fix: The Termination Fee journal entry now reflects the correct amount in the lease’s original currency, without unintended currency conversion. (Tri-101737-IJ54097) |
| IJ54200 | Lease Accounting | Issue: When multiple cutover Contract Summary Balance records are uploaded for a lease and their System Record IDs are not in chronological order, the Balance Sheet Account values in the first Automated Period LSB (generated during month-end journal entry processing) are incorrect. Fix: The “A.” fields of the Balance Sheet Accounts in the first Automated Period LSB are now correctly populated using the corresponding account values from the previous period’s Contract Summary Balance record. To correct all Automated Contract Summary Balance records generated during month-end journal entry processing, run the following patch helper workflow using the string ""MREF 9.1 - FixAutomatedLSB"": Workflow Name: triPatchHelper - triCalculate - MREF 9.1 - FixAutomatedLSB - Batch Process Leases (Tri-102068-IJ54200) |
| IJ54210 | Lease Accounting | Issue: When a lease is revised using the 'Date Revise' change type, and a contract revision is performed after activation using the 'Non-Lease Accounting Amendment' change type, the available lease clauses cannot be edited. Fix: The application now allows users to edit lease clauses during a contract revision using the 'Non-Lease Accounting Amendment' change type. (Tri-102093-IJ54210) |
| IJ54504 | Lease Accounting | Issue: The Contract Summary Balance was not being generated because the fiscal period dates became inconsistent. This occurred when the ""Correct fiscal period start and end dates to system server time zone (milliseconds)"" button was clicked in Application Settings without first setting the System Format field on the first fiscal year. Fix: The issue has been resolved. Now, even if the System Format field on the first fiscal year is left blank, the fiscal period dates are correctly updated when the correction button is clicked in the Application Settings. As a result, the Contract Summary Balance can now be successfully created using the Data Utility. (Tri-102174-IJ54504) |
| Lease Accounting | Issue: While uploading documents in bulk, the lease accountant user was unable to remove documents from the duplicate documents section. Fix: The duplicate documents can now be removed using the 'Remove' section action. (Tri-100205) | |
| Lease Accounting | Issue: For the Contract Admin user, the Bulk Upload Documents form was set to read-only. Fix: The Contract Admin user can now bulk upload documents across multiple leases. (Tri-100204) | |
| Lease Accounting | Issue: When impairment is performed during the same period as the previous modification, the accrued liability was incorrectly calculated on the accounting schedule. Fix: When the modification occurs in the same period and the current modification is an impairment, the accrued liability is correctly calculated on the accounting schedule. (Tri-101015) | |
| Lease Accounting | Issue: When copying a lease, the fields ""Est. Economic Life of Asset (Months)"", ""Est. Economic Life of Asset (Days)"", and ""Est. Economic Life of Asset End Date"" were not carried over to the new record. Fix: The data in these fields are now correctly copied during the lease copy process. (Tri-99224) | |
| Lease Accounting | Issue: When GAAP Impairment was performed on an IFRS lease with the Local Reporting tab, the current impairment was not correctly mapped as a GAAP Impairment on the helper record, leading to incorrect accrued liability calculations. Fix: The application now accurately maps the current impairment scenario as a GAAP Impairment on the helper record, ensuring correct calculation of accrued liability. (Tri-101356) | |
| Lease Accounting | Issue: The following BIRT reports were returning no data when executed: - triAssetLease - BIRT - AR RE Contract Payment Details for Asset Lease - triRealEstateContract - BIRT - AR RE Contract Payment Details Fix: These BIRT reports now return data as expected when executed. (Tri-101484) | |
| Lease Accounting | Issue: When a Purchase Option was exercised on a contract: 1. The Base Lease Expiration Date, Accounting End Date, and Likely Term Expiration Date were not being updated to reflect the Likely Purchase Execute Date of the Purchase Option. 2. Users were still able to manually modify the Base Lease Expiration Date after the Purchase Option had been exercised. Fix: Upon exercising a Purchase Option on Contract: 1. The Base Lease Expiration Date, Accounting End Date, and Likely Term Expiration Date are now automatically updated to match the Likely Purchase Execute Date. 2. If a user attempts to manually change the base lease expiration date after the Purchase Option is exercised, an attention message will now appear: ""The base lease expiration date cannot be changed because the purchase option is exercised"". (Tri-100715) | |
| Lease Accounting | Issue: While performing a Payment Adjustment on a Real Estate Lease, the server logs were showing the error: ""triRevisionDateDA named field does not exist for triRealEstateContract business objects."" Fix: The triRevisionDateDA field has now been added to the triRealEstateContract business object to resolve the issue. (Tri-100048) | |
| Lease Accounting | Issue: The ""Find Template"" action appears duplicated in the Options section of the Real Estate and Asset Lease templates. Fix: After creating a draft for Real Estate and Asset Lease templates, only a single ""Find Template"" action will be displayed, in accordance with the lease accounting standards. (Tri-100087) | |
| Lease Accounting | Issue: In the Recalculate NPV attention message for the Treatment section, the word ""Treatment"" was incorrectly spelled as ""Treatement"" on the lease record. Fix: The spelling error has been corrected. The system will now display the word ""Treatment"" correctly in the Recalculate NPV attention message on the lease record. (Tri-99941) | |
| Lease Accounting | Issue: For Accounts Receivable (AR) leases with Accounts Payable (AP) Tenant Improvement Incentive payment schedules that begin after the lease commencement date, the Incentive Amount field was not being populated in the Incentive Schedule After Lease Commencement section when generating accounting schedules. Fix: The application has been updated so that when generating accounting schedules, the Incentive Amount field is now correctly populated in the Tenant Improvement Incentive After Commencement section on the Accounting tab for AR leases with AP Tenant Incentive Payment schedules that start after the commencement date. (Tri -101988) | |
| Lease Accounting | Issue: For GAAP leases with local reporting enabled, when the lease classification is changed from Operating to Finance or vice versa, the system incorrectly generates journal entries associated with the Modification trigger subtype in the Journal Entries Event Setup. However, it should generate entries under the Reclassification trigger subtype. Fix: The issue has been resolved so that, for GAAP leases with local reporting enabled, changing the lease classification between Operating and Finance now correctly generates journal entries under the Reclassification trigger subtype, as intended. (Tri-101461) | |
| Lease Accounting | Issue: In the lease history records, the Estimated Economic Life of Asset End Date field was incorrectly being populated based on the lease modification effective date. Fix: The calculation logic has been updated. For modified leases, the Estimated Economic Life of Asset End Date will now be derived from the original accounting start date. For initial lease history records, it will continue to be calculated from the lease commencement date. (Tri-101765) | |
| Lease Accounting | Issue: On the history lease amortization summary record, all fiscal line items were being associated, which led to incorrect calculations for the Total Tax Expenses field in the schedule summary section. Fix: If the lease is amended, it will associate only the fiscal line items from the modification effective period to the amortization summary record of the history lease. (Tri-100063) | |
| Lease Accounting | Issue: When the full-period payment schedule is adjusted with partial period dates, and the newly created payment schedule with partial period that is adjusted further for future with the full period duration, the application calculates the catchup amount for the future full-period duration. Fix: The application no longer calculates the catch-up amount for the payment schedule that contains the partial amount, and it is adjusted with future full-period duration. (Tri-100978) | |
| Lease Accounting | Issue: In the Update Payment Instruction functionality, the payment instruction end date was being mapped incorrectly. Fix: The payment instruction end date is now correctly mapped.(Tri-99957-IJ52072) | |
| Lease Accounting | Issue: When an active payment line item due on the current date is part of a payment schedule that was retroactively adjusted, the application incorrectly included it in the retro catch-up amount, and the new adjustment amount was being applied to it. Fix: If an active payment line item due on the current date is part of a retroactive adjustment, it will be excluded from the retro catch-up amount. Instead, the new adjusted amount is applied directly to that line item. (Tri -100197) | |
| Lease Accounting | Issue: When Initial Direct Costs (IDC) and/or prepayment are added or updated alongside a Tenant Improvement Incentive before or after adjustment during a modification, the current asset value calculation did not include the updated IDC and prepayment amounts. Fix: The current asset value calculation now correctly includes the added or adjusted IDC and prepayment values. (Tri-101777) | |
| Lease Accounting | Issue: When a lease is impaired in the first period and that period is a partial period, the loss was being calculated incorrectly in this scenario. In GAAP leases, this also resulted in the Accrued Liability column not reducing to zero by the end of the lease term. Fix: The loss is now calculated accurately in the accounting schedules. For GAAP leases, the Accrued Liability correctly reduces to zero at the end of the lease term. (Tri-101881). | |
| Lease Accounting | Issue: Upon lease termination, the gain/loss amount was incorrectly included in the accrual calculation. Fix: Accruals for terminated leases are now calculated excluding any gain or loss amounts. (Tri-98203) | |
| Lease Accounting | Issue: When an impairment was performed in the same period as a prior modification, the gain/loss was incorrectly calculated in the next period instead of the modification's effective period. Fix: The gain/loss is now accurately calculated within the modification effective period. (Tri-100630) | |
| Lease Accounting | Issue: When a user clears the ""Likely Term Option"" from the current lease, and the base lease expiration date of the current lease is greater than the ""Likely Expiration Date"" from the lease history, the current ""Likely Expiration Date"" gets updated to the base lease expiration date. Additionally, the following attention message is displayed: ""The Likely Expiration Date is mapped from the latest history lease without a likely term option associated with the lease. The Accounting End Date is not updated; you must manually update the end date if required."" Fix: When a user clears the ""Likely Term Option"" from the current lease: 1. If no history exists without the ""Likely Term Option"", the current lease's ""Likely Expiration Date"" will be updated with its base lease expiration date. 2. If history exists without the ""Likely Term Option"", and the current lease's base lease expiration date is greater than the history's ""Likely Expiration Date"", the current lease's ""Likely Expiration Date"" will be updated with the current base lease expiration date. 3. If history exists without the ""Likely Term Option"", and the history's ""Likely Expiration Date"" is greater than the current base lease expiration date, then the ""Likely Expiration Date"" on the current lease will be updated with the history's ""Likely Expiration Date"". Additionally, the attention message will now be shown only when the ""Likely Expiration Date"" is updated from history. (Tri-100317) | |
| Lease Accounting | Issue: The ""Create Payment Instruction"" action was available to users while updating payment instructions, even when the lease was in draft state. Fix: The ""Create Payment Instruction"" action is now disabled for users when the lease is in draft state. (Tri-101381) | |
| Lease Accounting | Issue: When a lease with multiple clauses linked to a single payment schedule is copied, the copied lease generates separate payment schedules for each clause. Fix: When copying a lease that includes clauses or options with associated payment schedules, the payment schedules will now be copied only at the lease level, not at the clause or option level. Additionally, if clauses or options with payment schedules are copied separately, their associated payment schedules will no longer be copied with them. (Tri-86317) | |
| Lease Accounting | Issue: When an index lease is amended and the existing Index clause is updated with an additional payment schedule, the Draft Index Adjustment Calculators continue to display outdated information. Fix: The outdated Draft Index Adjustment Calculators will be deleted, and new ones will be created with the updated information. (Tri-100004) | |
| Lease Accounting | Issue: When copying a Lease record that included an option marked as Likely Term, the Likely Term checkbox was not retained on the copied option in the new lease record. Fix: This issue has been resolved. The Likely Term checkbox is properly retained when a lease with a Likely Term option is copied to a new record. (Tri-100316) | |
| Lease Accounting | Issue: After executing a non-lease accounting amendment on a Real Estate Lease, the Modification Effective Date was being cleared from the Accounting and Local Reporting tabs. Fix: This issue has been resolved. When a non-lease accounting amendment is performed on a Real Estate Lease, Asset Lease, or SBITA, the Modification Effective Date will remain intact on the Accounting and Local Reporting tabs. (Tri-100303) | |
| Lease Accounting | Issue: When adjusting lease payment schedules that include partial future dates, the application was incorrectly calculating the amount for the adjusted future-dated payment line item. Fix: The application now accurately calculates the payment amounts for future-dated payment line items during partial future date payment schedule adjustments. (Tri-101922) | |
| Lease Accounting | Issue: When users adjusted multiple retroactive payments within a partial period, the catch-up amount was being calculated incorrectly. Fix: The application now accurately calculates the catch-up amount when multiple retroactive payments are adjusted within a partial period. A catch-up payment line item is generated with the correct amount. (Tri-100720) | |
| Lease Accounting | Issue: When adjusting a payment for a partial last period, the catch-up amount was being calculated incorrectly. Fix: The application now correctly calculates the catch-up amount for partial last period adjustments, and generates a catch-up payment line item with the accurate amount. (Tri-100697) | |
| Lease Accounting | Issue: When performing a payment adjustment using the ""update only payment line items"" action, the system was incorrectly updating the catch-up payment line items created for retroactive adjustments with new amounts. Fix: The system has been updated so that catch-up payment line items created for retroactive adjustments will no longer be updated when users perform adjustments with the ""update only payment line items"" action. (Tri-100535) | |
| Lease Accounting | Issue: When users performed multiple retroactive payment adjustments with partial dates on the payment schedule, the system created partial payment line items with past due dates, leading to unintended additional payments. Fix: The adjustment amount is now accurately calculated for the partial period, and a catch-up payment line item is generated with the correct amount and appropriate date. (Tri-100533) | |
| Lease Accounting | Issue: After applying the 11.4 lease post process patch-helper for existing leases, the payment breakdown items were created without a parent Payment Line Item (PLI) record ID. However, when you adjust a retroactive payment on any lease that contained these payment breakdown items without a parent PLI record ID, the adjustment considers all the payment breakdown items without a parent PLI record ID from the entire system during that retroactive adjustment period and incorrectly maps the parent PLI record ID on the payment breakdown items. Fix: The application no longer permits mapping the parent PLI record ID on payment breakdown items that are generated after applying the patch for existing leases for the payment breakdown type as payment adjustments. (Tri-100463) | |
| Lease Accounting | Issue: For IFRS leases with GAAP Local Reporting operating schedules, when a second lease amendment is performed within the same period as a previous amendment, specifically involving an update to the rental prepayment payment schedule, the Net Asset Value and Net Equity columns were not reducing to zero in the GAAP Local Operating Schedule. Fix: The issue has been resolved. Now, when a rental prepayment payment schedule is created or adjusted on the lease, the Net Asset Value and Net Equity columns correctly reduce to zero by the end of the GAAP Local Reporting Operating Schedule. To properly adjust a rental prepayment amount, use one of the following recommended approaches: Option 1: • Use the “Update or Split Payment Schedules” option to modify the rental prepayment amount on the payment schedule. • Then, use the “Update Only Payment Line Items” option, selecting the rental prepayment schedule to update the corresponding payment line item. Option 2: • Remove the existing rental prepayment payment schedule. • Create a new rental prepayment payment schedule with the desired amount and ensure the “Include in Rental Prepayment” field is checked. (Tri-99569) | |
| Lease Accounting | Issue: When performing an impairment on a lease with a non-standard calendar, the Amortization amount was not calculated correctly, resulting in the Net Asset Value not reducing to zero. Fix: The Amortization amount is now correctly calculated for leases with non-standard calendars during impairment, and the Net Asset Value properly reduces to zero. (Tri-99316) | |
| Lease Accounting | Issue: For an IFRS lease with GAAP Local Reporting operating schedules, when a second amendment is made within the same period as a prior amendment and the Initial Direct Cost field is updated on the Accounting tab, the Net Asset Value and Net Equity columns on the GAAP Local Operating Schedule do not reduce to zero as expected. Fix: The issue has been resolved. Now, when the Initial Direct Cost is updated on the lease, the Net Asset Value and Net Equity columns correctly reduce to zero at the end of the GAAP Local Reporting Operating Schedule. (Tri-102080) | |
| Lease Accounting | Issue: When a payment adjustment is performed on ""Other"" frequency payment schedules to update tax rates, the updated tax rates are not being applied to the adjusted payment schedules. Fix: To properly update tax rates on existing ""Other"" frequency payment schedules, users must complete both of the following steps: 1. Remove or void the existing ""Other"" frequency payment schedule, ensuring the associated payment line item is deleted from the lease. 2.Create a new ""Other"" frequency payment schedule and enter the updated tax rates. (Tri-100042) | |
| Lease Accounting | Issue: The Subscription-Based IT Arrangements form includes the ""Est. Economic Life of Asset (Months)"" and ""Est. Economic Life of Asset End Date"" fields, which are visible under the Accounting tab in the Other Information section. Fix: The ""Est. Economic Life of Asset (Months)"" and ""Est. Economic Life of Asset End Date"" fields have been removed, as they are not required for Subscription-Based IT Arrangements.(Tri-101627) | |
| Lease Accounting | Issue: On an active Subscription-Based IT Arrangement record, the 'Copy & Link to Lease' action had incorrect configurations, preventing the record from being copied. Fix: The configuration has been corrected, so the record is now properly copied and linked to the parent record.(Tri-100406) | |
| Lease Accounting | Issue: When making a second retroactive adjustment to a payment schedule on the same day to update the tax adjustment with the same amount, the retro payment line item that had been created by the first adjustment has been removed. Fix: The application retains the retro payment line item if a user makes multiple payment adjustments on the same day and modifies the tax without changing its overall percentage with the same adjustment amount. (Tri-100239) | |
| Lease Accounting | Issue: When users dismissed a Lease Notification, it remained in the Sent status due to a typo in the triContractNotification business object on the Dismiss state transition attribute for the Status field . Fix: The typo in the state transition attribute for Status field has been corrected from ""Dissmissed"" to ""Dismissed."" As a result, dismissed Lease Notifications now correctly transition to the Dismissed state. (Tri-101105) | |
| Lease Accounting | Issue: When a user performs an amendment on an Owned Property (Fee) Agreement created under the application standard GASB, an attention message appears regarding short-term lease validations. Fix: The attention message no longer appears. The short-term lease validations are skipped during the Owned Property (Fee) Agreement amendment revision. (Tri-101967) | |
| Lease Accounting | Issue: The Reports tab was incorrectly displayed on the Contract Disclosure Report form. Fix: The Reports tab is no longer shown on the Contract Disclosure Report form. (Tri-100970) | |
| Lease Accounting | Issue: When creating a reference only smart section with field-to-field mappings, an error of field mapping is shown in the server log. Fix: The field-to-field mappings are now removed in the workflows for reference only smart section. (Tri-100105) | |
| Connector for BIM | The BIM Connector now supports both Revit 2025 and Revit 2026. (Tri-98398) | |
| Connector for BIM | Revit Integrator now supports TLS 1.3. (MASREF-951) | |
| Connector for BIM | In the BIM Connector, on the Maximo Real Estate and Facilities environment, publishing a 3D model results in a [Method Not Found] error. As a workaround, publishing is performed through Maximo Real Estate and Facilities BIM Model Management. (MASREF-886) | |
| IJ52768 | CAD Integrator/Publisher | Smart Attach now successfully handles large spec_Id values. (Tri-100671-IJ52768) |
| IJ52911 | CAD Integrator/Publisher | The Smart attach search filter will now filter queries based on name. (Tri-100991-IJ52911) |
| CAD Integrator/Publisher | Smart Attach now functions correctly with large spec_Id values. (Tri-100549) | |
| CAD Integrator/Publisher | The [Find Object] menu now functions correctly with SPEC_ID values longer than 9 digits. (Tri-100613) | |
| CAD Integrator/Publisher | CI now functions correctly with large spec_Id values. (Tri-100620) | |
| CAD Integrator/Publisher | The Guava library has been updated. (Tri-99151) | |
| CAD Integrator/Publisher | Spring has been upgraded. (Tri-99960) | |
| CAD Integrator/Publisher | The POI library has been upgraded. (Tri-99150) | |
| CAD Integrator/Publisher | CAD Integrator now includes support for TLS 1.3. (Tri-99565) | |
| CAD Integrator/Publisher | A new log file has been added to track publish, upload, and detach actions in CAD. (MASR-2732) | |
| CAD Integrator/Publisher | The "updated_by" and "updated_date" columns in the CAD_DRAWING table are now updated when a user attaches a drawing to an existing floor plan. (MASR-2731) | |
| CAD Integrator/Publisher | Silent install properties have been updated to version 9.1. (Tri-100555) | |
| IJ51250 | Application | Issue: JEs run with OutOfMemory due to unnecessary t_triRecipient records in memory Fix: The Recipient record is de-associated from the Notification Content after the notification is sent. The patch helper de-associates all recipient records that are associated with 'TRIRIGA002', triApproval001, and 'TRIRIGA001' notification contents. (Tri-98855-IJ51250) |
| IJ51408 | Application | Issue: Workflow different from text export and workflow export getting corrupted Fix: The workflow text export now includes all workflow tasks from the 'triMoveRequest - Synchronous - Revise Record' workflow. (Tri-99138-IJ51408) |
| IJ51449 | Application | Issue: Incorrect spelling and having extra space on the workflow Name Fix: The workflow name has been corrected for the following workflows: PMEvent - Synchronous - Create Scheduled Events and Create Project or Tasks triContract - Synchronous - Create Prepayment Fiscal Line Item triPaymentSchedule - Synchronous - Create Tax Rate Record triRequest - Synchronous - Create Project or Tasks after Approval triRequest - Synchronous - Create Tasks for each Asset triRequest - Synchronous - Create Tasks for each BuildingSystemItems triRequest - Synchronous - Create Tasks for each Location triRequest - Synchronous - Create Tasks for each triDeferredLineItem triRequest - triFinalApprovalHidden - Create Project or Tasks triServicePlan - Synchronous - Create Wizard triInspectionRequest - Synchornous - On Submit Call Permanent Save. New Workflows: PMEvent - Synchronous - Create Scheduled Events and Create Project or Task triContract - Synchronous - Create Prepayment Fiscal Line Items triPaymentSchedule - Synchronous - Create Tax Rate Records triRequest - Synchronous - Create Project or Tasks after Approvals triRequest - Synchronous - Create Tasks for each Assets triRequest - Synchronous - Create Tasks for each BuildingSystemItem triRequest - Synchronous - Create Tasks for each Locations triRequest - Synchronous - Create Tasks for each triDeferredLineItems triRequest - triFinalApprovalHidden - Create Project or Task triServicePlan - Synchronous - Create Wizards triInspectionRequest - Synchronous - On Submit Call Permanent Save (Tri-99206-IJ-51449) |
| IJ51722 | Application | Issue: Recorded By person on the Facilities Project record is mapped by the employee's Name instead of Record Name Fix: The 'Recorded By' field in the Facilities Project record is now mapped correctly. (Tri-99527-IJ51722) |
| IJ51900 | Application | Issue: Parent and Child related workflows keep getting executed in a loop when removing a Capital Project child Fix: Child Project is now either added or removed after saving the parent Capital Project. (Tri-99727-IJ51900) |
| IJ51948 | Application | Issue: The accessible text for the “Log off” button doesn’t match the rest of the application. Fix: The Accessible text for the log off button is now ""Log Off"" instead of ""Sign Out"". (Tri-99771-IJ51948) |
| IJ51950 | Application | Issue: ARIA tooltip node does not have an accessible name. Fix: An accessibility issue was fixed where the ARIA tooltip node did not have an accessible name. (Tri-99784-IJ51950) |
| IJ51951 | Application | Issue: Implement a button to skip navigation on all reserve pages Fix: Implemented 'Skip to content' button to directly jump to main content by skipping repetitive elements. (Tri-99783-IJ51951) |
| IJ51975 | Application | Issue: Worktasks can be updated by only an associated supervisor Fix: Fixed an issue in the Work Planner App where supervisors could edit or delete tasks that were owned by people outside their workgroup. Supervisors can now see all tasks that belong to people that they supervise, but can edit or delete only the tasks that belong to people in their workgroup. (Tri-99865-IJ51975) |
| IJ52109 | Application | Issue: Additional Tasks are incorrectly created by PM Schedules when adding additional assets to a Job Plan. Fix: When additional assets are added to the Job plan, tasks are now created as per the service rule present on the PM schedule record. (Tri-100002-IJ52109) |
| IJ52151 | Application | Issue: Performance issue and workflow fix for the Project Search SAM Records (Organization Tree) workflow Fix: Performance has been improved for the SAM Proximity Search for Project. (Tri-100061-IJ52151) |
| IJ52572 | Application | Issue: Teams meeting link is getting truncated [PDM 11.5.2 defect 100543] Fix: An issue was fixed where long meeting links were truncated by increasing the length of the URL field. (Tri-100444-IJ52572) |
| IJ52581 | Application | Issue: Triblock-tabs not showing space between tab name & number badge. Fix: An issue was fixed where a space was not shown between the tab name and the number badge when using triblock-tabs. (Tri-100445-IJ52581) |
| IJ52709 | Application | Issue: Error message on amending Meter Service Allocation Fix: On saving Meter Service Allocation created for Asset, The Attention Message for Duplicate Allocation displays only if there is an existing Meter Service Allocation record for the current Asset and Service Location added on current Meter Service Allocation. (Tri-100501-IJ52709) |
| IJ52844 | Application | Issue: Reserve app allows booking rooms beyond their cutoff time Fix: Users could create recurring reservations beyond the room's Reserve Cut-Off Duration. Users now receive a warning message when attempting to create a recurring reservation that is beyond the cut-off duration. (Tri-100756-IJ52844) |
| IJ53092 | Application | Issue: Application- Question regarding trailing spaces on triNoteType list Fix: An extra space was removed from the end of the ""Conversation"" list value in triNoteType List. To update the triNoteType List and existing records. You must manually fix the triNoteType list, and run a patch helper to update the database records as follows: 1. Edit the triNoteType List, manually remove the ""Conversation "" list value with the extra space, and add a ""Conversation"" list value with no extra space. 2. Run the ""triPatchHelper - triCalculate - 11.7 - Update Comment Type on Comments Records"" patch helper to update any existing ""Comment"" records that have a ""Conversation"" list value in the ""Comment Type"" field to remove the extra space. (Tri-101179-IJ53092) |
| IJ53135 | Application | Issue: Not authorize page display while loading the event detail page Fix: The Perceptive Reserve event detail page displays a loading spinner with a blank page background while loading the event. (Tri-101276-IJ53135) |
| IJ53328 | Application | Issue: System Expires Warranty on the Expiration Notice Day not on Expiration Date. Fix: The warranty expires on the expiration date as the expiration event is now started correctly on the expiration date. (Tri-101525-IJ53328) |
| IJ53368 | Application | Issue: WF change from synchronous to asynchronous causes more documents to be removed than desired. Fix: Added a new section 'Assets and Specifications' Application Settings. This section now has 'Don’t update the image on assets from specifications.' and 'Keep manually added documents when asset specifications are updated.' checkboxes. If 'Don’t update the image on assets from specifications'. is checked, then the system does not update the image from the specification. If 'Keep manually added documents when asset specifications are updated.' is checked, when the user changes the specification on an asset, the system adds documents from the new specification to the asset. The system removes only the documents which were added from the old specification to the asset, it does not remove documents which are manually added by the user to the asset. (Tri-101574-IJ53368) |
| IJ53437 | Application | Issue: PO Invoice line item values are not calculated correctly Fix: When a PO is imported to a PO Invoice, line items are imported from the PO to the Invoice using Line Item Summary, and Previous Invoiced values are populated from the Line Item Summary to the Invoiced Total section on the Line Item. When the invoice is retried, the line item summary is recalculated to exclude the retired invoice from the invoiced value on the line item summary. Invoiced values are also populated correctly on line items when importing a PO on a PO Invoice. (Tri-101645-IJ53437) |
| IJ53454 | Application | Issue: Location Field Character Limit in Reservation Definition is Insufficient for Multi-Room Reservations Fix: The size of the 'triLocationTX' field in the 'triReservationDefinition' business object is increased to 1000 characters. (Tri-101659-IJ53454) |
| IJ53597 | Application | Issue: Error Re-Open Task [PDM 11.6.1 Defect 101909 ] Fix: Now, when you re-open the service request created through the UX application, the error message is not displayed. (Tri-101775-IJ53597) |
| IJ53603 | Application | Issue: Incorrect Planned date on Purchase Order record - In Recurring Reservation Fix: In the case of a recurring reservation with a food order, the purchase order record planned start date is now mapped as per the occurrence of series reservation. (Tri-101780-IJ53603) |
| IJ53807 | Application | Issue: App Reserve Room - Highlight floorplan Fix: When drawing units are set to millimeters, and after attaching and publishing the drawing, selecting the room on the floorplan triggers the room highlight. (TRI-101907-IJ53807) |
| IJ54268 | Application | Issue: Outlook Room Search Add-In app not working when legacy Exchange online tokens disabled. Fix: Microsoft has deprecated legacy Exchange Online tokens and is turning them off for Microsoft 365 tenants, starting on February 17th, 2025. This fix is a solution to the deprecated legacy Exchange online token, the fix requires customer to create a Microsoft Azure app registration and a TRIRIGA OAuth profile. In the Azure App Registrations, Click ""New Registration"", In the new registration, make sure to select ""Multitenant"" for the supported account type. And under the Redirect URI, please select ""Single-page application (SPA)"", and for the redirect URI field, put [your TRIRIGA domain]/p/web/outlook/roomSearch. Once created, under Overview, copy the Application (client) ID. We will need this client ID later in the TRIRIGA OAuth profile form. In TRIRIGA, visit Tools > System Setup > Integration > OAuth Settings. In the OAuth Settings page, click ""add"" at the top right corner. a new OAuth profile form will be opened. In the OAuth profile form, you can give any name (i.e Outlook Add-in), select Microsoft as the OAuth Provider, and User delegate as the Access Type. For the OAuth Application Key field, please paste the copied client ID from the Azure app registration. And for the OAuth Redirect URL field, please put [your TRIRIGA domain]/p/web/outlook/roomSearch. (Tri-102121-IJ54268) |
| IJ54646 | Application | Issue: Stack overflow errors due to triServiceWakeUp workflow event in 11.6 application version. Fix: When users create a reservation with no end date, the reservation instances are created as per the service wakeup duration present on the application setting under the reserve tab. (MASREF-868-IJ54646) |
| Application | Issue: Some BIRT reports show an error when ran - Invalid expression to retrieve value in presentation Fix: The following BIRT reports no longer show the ""Invalid expression to retrieve value in presentation"" error when the reports have no data: - Space Class Summary by Geography - Lease Critical Dates Report - Energy Opportunity Summary Report (Tri-99546) | |
| Application | Issue: Validate/add/modify shipping time zone records Fix: The following time zone is added in timezone classification: ""(GMT +6:30) Yangon [Asia/Rangoon]"". (Tri-96696) | |
| Application | Issue: The currency field should be blank, when a new Facility project create. Fix: The currency field is set to blank when a new Facility project is created. (Tri-101306) | |
| Application | Issue: ""The email is missing for the current user profile. Specify an email address"" text is not translated for all languages, while login into UX application with email id in my profile page. Fix: ""The email is missing for the current user profile. Specify an email address."" text is now translated. (Tri-100013) | |
| Application | Issue: SQLException value too large for column triNameTX while importing the pl.zip language pack. Fix: Field size of triNameTX from the triPropertyClass business object is now increased to 700 characters. (Tri-101702) | |
| Application | Issue: IndoorMap - image (png) files do not render Fix: All the corrupted (.png) Image files are replaced with new Image files. (MASREF-435) | |
| Application | Issue: The Indoor Maps App alignment is not proper on Mobile devices. Fix: On mobile devices, ""Key rooms"" and ""Restrooms"" text are now aligned correctly. Also, the search and back buttons are added. (Tri-101563) | |
| Application | Issue: Refactor the current locateMap Fix: There is no change in navigating to locateMap. Previously, the locateMap was loaded as separate application, but now the locateMap page is integrated within locate app. To access locateMap, navigate to the locate application and then find location that has the map setup. If you want to directly access the locateMap using a URL, use the following URL instead: [domain]/p/web/locate?homeApp=workplaceServices&overrideBuildingId=147343433#!/esri/buildingId/147343433/floorId/147347672. (Tri-98418) | |
| Application | Issue: Zooming and scaling is disabled for Locate Fix: An accessibility issue was fixed where zooming and scaling was not enabled. Zooming and scaling can be now enabled or disabled by using input arguments. (Tri-99638) | |
| Application | Issue: Contract Notifications records are not generating correctly for Insurance in the Insurance Notifications section. Also, the Event Start Date for the Insurance Expiration type contract notification is not the same as the Insurance Expiration date. Therefore, the contract administrator is not getting notified correctly for the insurance expiration date and insurance expiration notification date. Fix: Now, the contract administrator is correctly notified for the Insurance Expiration Date and the Insurance Expiration Notification Date. (TRI-101491) | |
| Application | Issue: Option+F9 function key combinations don't seem to work on my Mac in Room reservation description page. Fix: When editing a description, note that, by default on MacOS, you must hold the Function (Fn) key while pressing a function key. (Tri-98259) | |
| Application | Ìssue: People records are going for approval when activated even though the approval requirement is retired Fix: When a People record is activated, it is no longer sent for approval if the related approval requirement is retired. (MASREF-332) | |
| Application | Issue: [Request Centre]: When creating a survey, adding the survey recipients does not display the record in the list. Fix: The 'General Evaluation Request' and 'Reservation Survey Request' records now display the added recipients in the 'Survey Recipient' section. (MASREF-327) | |
| Application | Issue: UX Applications - Fix Polymer V3 SVG duplicated IDs Fix: Enhance `tri-bundler`, and introduce a new flag, `--unique-svg-ids`. The flag is optional, and when it is used, the script assigns unique IDs to all UX Polymer Maximo Application Suite Real Estate and Facility SVG icon elements in the bundled file. Visit `tri-bunlder` npm site for more information https://www.npmjs.com/package/@tririga/tri-bundler. (MASREF-726) | |
| Application | Issue: Exchange login can fail on multi-homed servers Fix: An issue with multi-homed servers (more than one URL) was fixed where the Microsoft login failed but no reason was given. When the Oauth redirect URL does not match the application base URL, an error message is now shown. (Tri-86757) | |
| Application | Issue: Timezone should persist when creating meeting reservation Fix: An issue was fixed where the user timezone was incorrectly displayed when a user created a reservation without a room in a different timezone. The selected timezone is now displayed in the meeting summary page. (Tri-92883) | |
| Application | Issue: ""Select "" text is not translated, while selecting 24 hours event calendar in Room reservation Fix: The AM/PM label is now translated when reserving a 24 hour meeting. (Tri-100025) | |
| Application | Issue: Fix Application Reports with All Module and All Associations - All Modules except Lease Module Fix: Association filters on queries with All Modules and All Associations are fixed across the application in all modules except the Lease Module. (Tri-92857) | |
| Application | Issue: Availability View section is not working on Reservable Inventory tab of Inventory Manager process form. Fix: Availability View section on Reservable Inventory tab of Inventory Manager Process Form is working now. (Tri-101538) | |
| Application | Issue: Default value of Exchange Retry Duration in Reservation Setting page is 4 hours which is too high. Fix: The Default value of the Exchange Retry Duration field, which is present on the application setting record under the Reservation setting tab is now set to 10 mins. (Tri-101664) | |
| Application | Issue: Fix 'Model And View Metadata: triRoomReservation' so it can be included in the OM Fix: An issue was fixed in order to include the ""triRoomReservation"" Model and View Metadata in the OM package. A new Application Metadata record ""triAppReservationList"" has been added, with the AppName selected as ""triRoomReservation"". This ensures that the Model and View Metadata is included in the OM Package. (Tri-101134) | |
| Application | Issue: When creating series reservation with multiple rooms with check in enabled and auto cancellation, after check expired and recheck button appears , only one room is getting strikethrough and duplicate entries are displayed for the 1st occurance in Agenda page. Fix: When creating a series reservation with multiple rooms that have the same check-in and auto cancellation time, the reservation does not create a duplicate entry in My Calendar. (Tri-101245) | |
| Application | Issue: UX-Room-Reservation: Platform error messages are not visible to the end user. Fix: When Microsoft authentication fails, a Microsoft Exchange authentication failed modal displays the actual error message. (Tri-86764) | |
| Application | Issue: Once user edits the reservation by clicking on Edit reservation button after clicking on recheck room, the room is not getting displayed in agenda view or event details page. Fix: In the auto cancellation scenario, a check-in expires and the room is auto canceled. Now, when editing a reservation, users can select the same room with a different time. (Tri-101303) | |
| Application | Issue: The room result counter section is hidden when floorplan in the viewport that does not have any available spaces Fix: The toolbar below the floorplan was not shown when users click ""Search this area"" and there is no space in that area. The room results counter section is now displayed. (Tri-100712) | |
| Application | Issue: UX Reserve - use platform api to get OAuth profiles instead of using Query Fix: When creating oauth profile for development users must not set a domain filter. Also, the access type in oauth settings must be User Delegate. (TRI-97691) | |
| Application | Issue: ""Recheck"" button is not showing in Room hold expire 30 mins popup message in Room reservation application Fix: An issue was fixed where the Recheck button was not displayed on the 30 mins room hold notification. (Tri-101578) | |
| Application | Issue: Certain fields in UX reserve app does not work in a single click. Need to click twice to make it work. Fix: An issue was fixed where some options needed a second click to work. The Attendees, Rooms, Find available rooms, Online meeting, Catering, and Equipment options now work with a single click. (Tri-101332) | |
| Application | Issue: Application Settings: Remove the attention message displayed for Integrate Perceptive Reserve App with Exchange? Field Fix: An issue was fixed where you were unable to save the Application Settings record when the ""Integrate Perceptive Reserve App with Exchange?"" checkbox was selected but no value was provided for the ""Perceptive Reserve App OAuth Profile"" or ""Exchange URL"" fields. (Tri-100414) | |
| Application | Issue: Microsoft authentication for the UX Reserve app is failing without any detailed error when another Microsoft account is already signed in to the browser. Fix: You cannot log in to Microsoft Outlook in the the Reserve app when another user is already logged in to Microsoft. Previously, the Microsoft login would fail without an error message, but now an error message is displayed to explain why the login failed (Tri-99894) | |
| Application | Issue: For some spaces (particularly big ones), floorplan is not showing the nearby available spaces first Fix: Fixed an issue where the search radius for finding nearby spaces for colleague reservations was too large, causing distant spaces to be included in the results. Now spaces closer to colleagues are fetched first. (Tri-99580) | |
| Application | Issue: User should be able to see all the spaces in that selecting building, while clicking on clear action in select room page. Fix: An issue was fixed where the search filter was not reset when you clicked the Clear button in search results for a selected building and floor. Now all available rooms are shown when you click Clear. (Tri-98055) | |
| Application | Issue: UX app is showing only one Purchase Order when the catering order having multiple purchase orders Fix: When a user adds catering items from different vendor menus, separate purchase orders are now generated for each vendor. Purchase order details, such as the delivery date, vendor name and purchase order ID for each vendor, are displayed in collapsible sections. Also menu items are displayed. (Tri-83558) | |
| Application | Issue: After create and review the reservation, in the review page not able to open the added catering and equipment orders. Fix: Catering and equipment details can be viewed in cost summary page before creating a reservation in UX Room Reservation app (Tri-82514) | |
| Application | Issue: Cannot copy or click on email from Unavailable (i) button popup Fix: The Mailto window can now copy the text when users open the unavailable room details modal. (MASREF-320) | |
| Application | Issue: Favorite Rooms/Spaces are not showing Fix: View Switcher is hidden when there is no selected building and list view is displayed instead of Floorplan view. (MASREF-324) | |
| Application | Issue: Should show a skeleton when data is being loaded Fix: The skeleton loader was only visible during the initial load on event details page. Now, the skeleton is displayed for Attendees and Description fields. (MASREF-479) | |
| Application | Issue: View Switcher should not be rendered when showing favorite rooms Fix: ViewSwitcher is now hidden when there is no selected building and list view is displayed instead of Floorplan view. (MASREF-340) | |
| Application | Issue: Room details not showing when clicked from Continue combo button Fix: Previously, the app navigated to Agenda page when trying to check room details of the selected room from the ""Continue"" button. Now, when clicking the ""Continue"" button the app now shows the room details in a modal. (MASREF-318) | |
| Application | Issue: UX Reserve]: When user directly navigates to Workspace page from meeting space rooms page, the workspace page directly loads the floorplan even if no location is selected Fix: Previously, when users navigated directly to the Workspace page from the Meeting Room > Rooms > Find Available Rooms flow, the workspace page incorrectly displayed the floorplan even when no location was selected. Now, the workspace page correctly validates the location selection. If no location is selected, it displays a “No workspace found” message instead of loading an incorrect floorplan. (MASREF-325) | |
| Application | Issue: [UX Reserve] [Globalization] [Czech, Brazilian Portuguese , French and Spanish] Alignment issue on meeting room and workspace in agenda page Fix: Meeting room and workspace text alignment is now working for the Czech, Brazilian Portuguese, French, and Spanish languages. (MASREF-254) | |
| Application | Issue: Zooming and scaling is disabled for Service request Fix: An accessibility issue was fixed where zooming and scaling was not enabled. Zooming and scaling can be now enabled or disabled by using input arguments. (Tri-99636) | |
| Application | Issue: Space details are (people and Assets details) not removing in ""Assessment Details"", when removing in Space Assessment record. Fix: Space details (people and Assets details) header panels are removed from ""Assessment Details"" Tab when no Space Assessment record is available. (Tri-101070) | |
| Application | Issue: Sort function for tasks and people not working on Work Planner UX app. Fix: Sorting functionality is now working for tasks and people. (MASREF-779) | |
| Application | Issue: Service manager security group is not having permission to add materials and parts in WTS UX App Fix: Users with the following roles: - TRIRIGA External Service Provider Security Group - TRIRIGA Service Manager Security Group - TRIRIGA Service Manager - Fundamentals Security Group - TRIRIGA Service Technician Security Group +[@[ Release note summary]]- TRIRIGA Service Technician - Fundamentals Security Group Were getting the error ""You do not have permission to perform the action."" when performing any of below actions: 1. Post a comment 2. Add Parts 3. Add Materials 4. Start or Stop timer 5. Add Time Entry These users can now perform these actions without error. (Tri-101595) | |
| Application | Issue: Direct Work Task and Work Task Services URLs not working Fix: An issue was fixed in the Work Task and Work Task Services apps where where users were unable to log back into the app after logging out. Users are now redirected to the login page when they sign out of the app. (Tri-98964) | |
| Application | Issue: Zooming and scaling is disabled for WorkTaskServices Fix: Zooming and scaling can be enabled or disabled using input arguments. (Tri-99637) | |
| Application | Issue: When creating a reference only smart section with field-to-field mappings, an error of field mapping is shown in the server log. Fix: The field-to-field mappings are now removed in the workflows for reference only smart section. (Tri-100105) | |
| Application | Issue: Reservations are not showing in workplaceServices application [PDM 11.6.1 Defect 101383] Fix: Fixed an issue where ""This Month's Reservations"" were not displayed on the Workplace Services page. (Tri-100974) | |
| Application | Issue: Zooming and scaling is disabled for Workplace services Fix: An accessibility issue was fixed where zooming and scaling was not enabled. Zooming and scaling can be now enabled or disabled by using input arguments. (Tri-99635) | |
| Application | Issue: UX perceptive app IRS accessibility issues 9.1 Fix: Upgraded Workplace Services and Service Request applications from polymer 1 to polymer 3 version. And also fixed accessibility issues which are listed when running the IBM Accessibility Checker Tool for Workplace Services, Service Request, Locate and Meeting/Workspace Reservation applications. (MASREF-737) | |
| Application | Issue: Select your building from map view (Reserve, WPS) Fix: Users can now search for and select the building from the map view. (Tri-100727) | |
| Application | Issue: Calculated fields - Loss factor and CAF fields Fix: The 'Loss Factor (LF)' and 'Common Area Factor (CAF)' calculated fields are added to the Area Measurement Tab on the Property, Buildings and Floor forms. Loss Factor (LF) = (Rentable Area – Usable Area) / Rentable Area Common Area Factor (CAF) = (Rentable Area – Usable Area) / Usable Area These fields are calculated for existing records when the user saves the records. Upgrade customers that want to calculate these new fields for existing records automatically must execute Patch Helper workflow with string 'Calculate LF and CAF for Location'. The patch calculates 'Loss Factor (LF)' and 'Common Area Factor (CAF)' fields on existing Property, Building, and Floor records for which 'Rentable Area' is not zero. (MASREF-262) | |
| Application | A navigation option to launch DSP from the main menu has been added. (Tri-99601) | |
| Application | Issue: Reserve Accessibility - make list view the default when a user has the Enable Accessibility Mode option enabled in their profile Fix: 1. List View is the default mode if user enables Accessibility Mode in My Profile. 2. If the user enables Accessibility Mode in My Profile, they can now search for spaces near a colleague’s reservation on the entire floor directly from the List View by clicking the 'Check More' button. This provides an accessible alternative to searching through the Floorplan View, which is a visual interface. (Tri-97982) | |
| Application | Issue: [OnCloud and Hybrid] When turn on the 'show private rooms' button in filter, the conditional message to reserve a private room should be displayed Fix: You can now see the room and owner details for a private room by clicking on the information icon. The owner details are displayed only if the owner has consented to display their details. (Tri-80927) | |
| Application | Issue: Reserve: Web Conference (Teams Meeting) Integration Fix: Implemented web conference integration with Teams Meeting. The changes made to event description from Outlook are now synced correctly with the Reserve app. (MASREF-331) | |
| Application | Issue: Enhance tri-vulcanize to handle basicAuth Fix: tri-vulcanize version 1.1.2 now supports basic authentication. (Tri-98953). | |
| Application | Issue: Reserve and Workplace Services (WPS) - improved default location handling Fix:Workplace Services remembers the last building reserved by user from UX Room Reservation app. This building will be automatically selected in WPS next time if theuser does not have a Primary Building or the app does not detect a location through location services. (MASREF-244) | |
| Application | Issue: Network URL field is too short Fix: If your Esri URLs are longer than 150 characters, you must manually increase the field size for the triEsriPortalUrlTX or triEsriPortalUrl fields. Tri-100072) | |
| Application | Issue: Asset marked as lost is added to the reserve work task. Fix: Assets marked as lost are not considered for reservation. (Tri-101498) | |
| Platform | The SNMP business process agent is no longer included. (MASREF-1785) | |
| IJ51865 | Platform | Resolved an issue where a database mismatch occurred during the platform upgrade. (Tri-99665-IJ51865) |
| Platform | Install log messages are now more descriptive. (Tri-100000). | |
| IJ52996 | Platform | To improve performance, you can use the STATIC_CLIENT_RESOURCE_CACHE_CONTROL_VALUE and STATIC_CLIENT_RESOURCE_LIST properties to allow static resources that do not contain sensitive customer data to be cached rather than downloaded each time the resource is requested. (Tri-101133; Tri-100972-IJ52996) |
| Platform | After you upgrade to Maximo Real Estate and Facilities, some reports, documents, and queries become obsolete because they apply only to TRIRIGA license data that exists before the upgrade. After the upgrade, you convert TRIRIGA licenses to Maximo Real Estate and Facilities licenses, which are administered in Maximo Application Suite Administration. After you have completed any needed license audits on TRIRIGA licenses, you can manually delete the obsolete TRIRIGA external reports, documents and queries. For more information, see https://www.ibm.com/docs/SSRHPA_cd/appsuite/upgrade_tririga_to_mref/c_post_remove_tririga_licence_reports.html. (MASREF-1087) |
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8mgJ000000029tQAA","label":"Maximo Application Suite-\u003EMAS Applications-\u003EReal Estate and Facilities"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1.0"}]
Was this topic helpful?
Document Information
Modified date:
20 January 2026
UID
ibm17237639