Announcing the launch of FM:Interact bookME
We recently launched bookME, interactive digital signage that is placed outside of meeting rooms that gives employees the ability to reserve conference room space on the fly. bookME extends the functionality of FM:Interact’s industry leading Space Management solution to the entire organization by enabling employees to view room availability and reserve spaces with a user-friendly mobile interface. It was great to see the interest around bookME throughout the show firsthand.
Flexible Workspace for the Mobile Employee
Almost every conversation I had tied back into how mobile today’s employees are and how organizations are in need of a solution that will support today’s new approaches to working, including the requirements for flexible workspace, the ability to quickly support cross-functional teams and collaborative areas that break away from the traditional practice of one employee assigned to one workstation.
FM:Systems Space Reservation module supports these new ways of working and allows organizations to provide their employees with the flexibility of reserving as-needed space when they need it — whether it be reserving a workstation for the day, a meeting space with specific amenities, or walking up to and reserving a conference room on-the-fly for an ad-hoc meeting. The configurability of our product allows organizations to meet these rapidly changing demands and help them realize new business value — all while providing their employees with a flexible workplace…
[Admin: To see other related posts, use the FM:Systems tag or Mobile tag.]
We cannot assign resources using the Resource Manager.
The resource data needed to be sent to the Legacy Availability section applet correctly. Moving forward, several issues were fixed in the Legacy Availability section. One issue prohibited loading when there was resource data, while another issue caused the assignment of a resource to a task to fail and spin indefinitely.
[Admin: This post is related to the 01.27.16 post about being unable to access the TRIRIGA Gantt chart in Resource Manager.]
When you create a reservation, for example, a Location Reservation, some of the resources do not display on the Find Available Times tab of the reservation.
By default, only 50 rows display when the Find Available Times tab of the Availability section of a reservation is rendered. If there are too many results, a warning about exceeding the row size is displayed. Your administrator can change the maximum number of rows that display by changing the AVAILABILITY_SECTION_ROW_LIMIT property in TRIRIGAWEB.properties. As noted above, the default value is set to 50 rows. If set to 0, -1, or other invalid value, the default number will be used.
Warning: If the property is set too high, performance issues might occur when rendering. Large values might cause memory issues. It is recommended that you update the backing reserve queries to reduce results or design filters that keep the number of record results under this value. Any value above the max value of 500 will be set to 500.
This version of the Availability section replaces the Java applet-based Availability section. The Java applet-based Availability section is deprecated. Most browser vendors are no longer supporting Java applets. For details on support, see Java applet support.
The Availability section in IBM TRIRIGA display the availability of resources over a period of time. The Availability section is implemented in several locations in the as-shipped IBM TRIRIGA, for example, the Find Available Times tab in the Location Reservation form and Concierge form.
You can use the availability user interface to find and book available times for reservable resources such as rooms and equipment. The table contains resources and the chart displays free and busy times for the resources. The currently specified Start date/time and End date/time are displayed as well…
Since early 2016, most browser vendors no longer support the Netscape Plugin Application Programming Interface (NPAPI) architecture. Most Java applet plugins for web browsers rely on NPAPI to render Java applets.
Impact to IBM TRIRIGA applications
The end of NPAPI support prevents the Java applet-based TRIRIGA areas — such as the Gantt, Availability, and Stacking sections — from rendering in IBM TRIRIGA applications on certain browsers.
Areas of TRIRIGA impacted by changes in browser support
The following IBM TRIRIGA areas are impacted. Details on each area follow.
- Gantt section
- Availability section
- Availability Legacy section
- Stacking section
- Other Java applet-based TRIRIGA areas…
[Admin: This post is related to the 04.07.16 post about TRIRIGA compatibility with browsers, and the 07.16.15 post about removing NPAPI support from Chrome.]
Occasionally, we have IBM TRIRIGA customers who need clarification on the differences between General Availability fix packs and Limited Availability fixes. I want to share this information with you and state the best-practice guidelines here.
General Availability (GA) Fix Pack
A GA fix pack delivers product defect fixes that have undergone a full development release cycle and the most extensive QA testing of all maintenance releases…
Limited Availability (LA) Fix
An LA fix is an unofficial mechanism to deliver emergency fixes for severe product issues that cannot be delayed until the next regular maintenance delivery. An LA fix also goes by the name “one-off” or “one-off hotfix”, but they all mean a single APAR fix delivered directly to a customer from Support…
Best Practices for Fixes
It is perfectly acceptable to take an LA fix to address an issue when warranted. However, the risk associated with taking an LA fix should always be weighed against the perceived benefits. If at all possible, it is always best to wait for a fully tested GA fix pack. Also, if you do take an LA fix, it should only remain in place until a GA fix pack containing the needed fix is available. At that point, the GA fix pack should be applied.
Can someone point me to a full list or spreadsheet which lists the DB build numbers and their corresponding TRIRIGA platform versions? For example, I have the following list. Does anyone have a full list?
- 122594: TRIRIGA 184.108.40.206 Fix Pack
- 117182: TRIRIGA 220.127.116.11 Fix Pack
- 115341: TRIRIGA 3.3.2
- 103754: TRIRIGA 18.104.22.168 Fix Pack
- 110173: TRIRIGA 22.214.171.124 Limited Availability Fix Pack
- 103241: TRIRIGA 126.96.36.199
- 101076: TRIRIGA 188.8.131.52
- 92888: TRIRIGA 3.3.1
- 70886: TRIRIGA 184.108.40.206 Fix Pack
- 70563: TRIRIGA 220.127.116.11
- 70456: TRIRIGA 3.3 – 10.3
- 66963: TRIRIGA 3.2
- 62090: TRIRIGA 3.2 – 10.2
I don’t have a full list… But this list is comprehensive, only missing some older platform versions. TRIRIGA Build Numbers 26407 to 226817…
[Admin: This post is related to the 08.02.16 wiki page: Build Number, Release, and Dates (V.R.M).]