In TRIRIGA 10.5.2, the following issues have been seen:
- (1) When capital leases start and end in the middle of a Semi-Annual, Annual, Quarterly, or Monthly payment period, the first and last period amortization in the fiscal line item (FLI) is not prorated correctly. As a result, the Day 1 right of use (ROU) is incorrect.
- (2) Massive amounts are appearing in the Capital/Finance Schedule. The Interest Expense, Change in Liability Value, P&L Book Expense, Liability Value, and Net Equity fields are displaying massive amounts, like in the quintillions, even though the total rent is $240K.
We needed to fix the partial payment issue for the current and new lease accounting standards. Moving forward, we fixed an issue that when capital leases start and end in the middle of a Monthly, Quarterly, Semi-Annually, Annually payment period, the first and last period amortization in the FLI is not prorated.
[Admin: To see other related posts, use the Payments tag.]
When publishing a drawing with Xrefs, the display state of the Xref layers is not carried over to the graphics section. Meanwhile, the base drawing layers do maintain their state when published. A couple related things:
- 1. If there are no existing or active layer configurations, the default behavior seems to be that the base layers will be displayed as they were in the drawing at the time of publishing. Meanwhile, the Xref layers will all be displayed regardless of their display state at the time of publishing. Is this the intended functionality?
- 2. There does not seem to be a way to save the graphics section display of layers. When you open the graphics section, it is displayed based on the state of the last publishing. (I’ll be looking into this further and will likely open a separate L3 request. There should be a way to save the graphics section display.)
We resolved this issue by removing the code that removes the Xref layers. Now, the Xref layer states and colors, based on the main drawing, are retained when publishing a drawing. Moving forward, the Xref layer display states and colors are correctly retained when publishing to the graphics section.
[Admin: To see other related posts, use the Xref tag.]
When a report is executed from “My Reports”, the title is shown as the header, even though we have changed the REPORT_HEADER_COLUMN property to “Name” in the TRIRIGAWEB.properties.
We needed to remove the REPORT_HEADER_COLUMN property since it is no longer being used. It was used in the out-of-support TRIRIGA 2.7.x platforms and older. Moving forward, the deprecated REPORT_HEADER_COLUMN property has been removed from the TRIRIGAWEB.properties file since it has not been used since the TRIRIGA 2.7.x platform releases.
[Admin: To see other related posts, use the TRIRIGAWEB.properties tag.]
With TRIRIGA 126.96.36.199 and BIRT 4.3.1 on Windows Server 2012 R2, we see that the “Export Report” option in a BIRT report defaults to “PostScript”, whereas in the current TRIRIGA 188.8.131.52 production version, it is defaulted to “Excel”. We want this export report option to be defaulted to “Excel” in TRIRIGA 184.108.40.206 as well. Only after upgrading from 220.127.116.11 to 18.104.22.168, we are seeing this change.
The BIRT engine did not sort the export options by default. Moving forward, the list of format options when exporting a BIRT report are now in alphabetical order, with the default being Excel XLS.
[Admin: To see other related posts, use the Export tag or BIRT tag.]
When a “Finance” (or “Capital”) lease is modified, the new ROU asset balance should be calculated in the same way as future accounting “Operating” lease modifications, that is, the amount of change in the liability balance is added to (or subtracted from) the prior-period ROU asset balance immediately preceding the modification.
Note that this calculation should mirror the calculations that were implemented in TRIRIGA 10.5.2 for future “Operating” lease modifications. Currently, we see that the asset balance is set equal to the re-measured liability balance upon a modification.
Moving forward, when a “Finance” (or “Capital”) lease is modified, the new right-of-use (ROU) asset balance is now calculated correctly. The amount of change in the liability balance is added to (or subtracted from) the prior-period right-of-use (ROU) asset balance immediately preceding the modification.
[Admin: To see other related posts, use the ROU tag.]
For TRIRIGA 10.5.2/3.5.2 OOB, there is an issue with the “Initial Liability Carryover” (ILC) field. In both operating leases and capital leases, when a value is entered in this field, the right of use (ROU) asset in the future accounting schedules is not reduced at Day 1 (against lease liability (LL) and initial direct costs (IDC)).
- What should happen: Day 1 ROU = Day 1 LL + IDC – Initial Liability Carryover.
- What is happening now: Day 1 ROU = Day 1 LL + IDC. (No ILC is applied.)
The balance in this ILC field should get pulled into the Day 1 ROU asset balance, and it currently does not. If this field is functioning per OOB, then we need to fix it. It is critical that the transition to the new accounting standards is calculated correctly.
The initial carryover balance (ICB) was not applied to new accounting schedules. Moving forward, if leases are created on or after the look-back period, the initial carryover balance will now be applied to operating leases and finance/capital leases.
[Admin: To see other related posts, use the ROU tag.]
Panels that didn’t have vertical scrolling in-frame now have vertical scroll bars. That is, they are not presenting the whole information within the visible area as before. Frames and portal sections are not sized correctly and some clickable areas might not work until some other action is performed. This is a change in behavior from TRIRIGA 3.5.1 to 3.5.2 when this behavior could be observed for customized forms.
Internet Explorer does not correctly calculate the new height of the content internal to the portal. We needed to rework the logic to resize to the actual content size. Moving forward, an issue that caused an extra scroll bar to appear when rendering a record in the portal has been resolved.
[Admin: To see other related posts, use the Portal tag.]