The following objects are core objects in TRIRIGA Application Platform functionality and any modifications to these objects are not supported by TRIRIGA.
Any TRIRIGA-shipped Business Objects belonging to the following Modules should not be modified. Care should also be taken in modifying any Forms, Queries and Workflows belonging to the following Modules as platform functionality can be affected. (There may be other objects not included in this list.)
[Admin: To see other related posts, use the Best Practices tag.]
In TRIRIGA 10.5.1, if you navigate to Home > Projects, and have the “Projects – Projects Landing Page – Default” portal in place, the primary locations for any projects you have listed in the “My Active Projects” portal section are flagged in the “My Project Locations” portal section.
But in TRIRIGA 10.5.2, this does not happen. No project locations appear with a flag in the “My Project Locations” portal section. There appears to be a problem introduced between 10.5.1 and 10.5.2 due to a reverse association filter being removed.
The “Location – Navigation – GIS – Buildings, Structures, and Retail Locations – Project Manager Query” was configured with an incorrect forward association string, that prevented capital project locations from displaying on a GIS map. Moving forward, the Advanced tab > Geography Module > triCity Business Object association filter had its forward association string updated to “Geography Contains” from “Geography Belongs To”.
[Admin: To see other related posts, use the GIS tag.]
When you change the basemap after the map is initially rendered, this causes the map to maximize and show the entire extent, instead of the original location that is centered on the building.
When you zoom into a Esri map with one pin, the record is fully zoomed in. The issue was that the max zoom level being used when a map initially zooms to a pin is too extreme, and not usable. Moving forward, we resolved an EsriJS issue where the initial zoom for GIS maps containing one pin was too extreme. The initial zoom has been scaled back to a more usable level.
The GIS section height could be expanded since there is a lot of white space at the bottom of the screen.
The issue is that about a quarter of an inch of white space was appearing at the bottom of the GIS map. This fix drastically reduces the amount of white space at the bottom of the map. In doing this, this fix also needed to specially handle a scroll bar that was appearing on Firefox due to the reduced white space. A scroll bar is only needed on the map when the Show Options tab or Show Table tab are being shown. We now programmatically set the scroll bar to either “auto” or “hidden” when those tabs are toggled.
I have configured Esri connector in our TRIRIGA instance using the following URL:
/html/en/default/rest/EsriJS?map=Default – Location – Associated to Current Record&level=5
We have found that the GIS map initially displays but at the lowest zoom level. Essentially, the map is not responding to the Level parameter. Does anyone have any experience with this?
[Admin: This post is related to the 02.04.15 post about GIS documentation, and the 01.21.15 post about GIS functionality.]
When upgrading to TRIRIGA 3.5.2, an error related to importing EsriJS system objects may appear in the server.log:
2016-12-21 15:05:39,826 INFO
[com.tririga.util.startup.upgrade.systemobject.EsriJSOMUpgrade](server.startup : 1) Unable to import EsriJS System Objects, required application dependencies are most likely missing...
If this happens, the following error may appear in the ObjectMigration.log as well:
2016-12-21 15:05:39,825 ERROR [com.tririga.platform.om.service.AbstractOMObjectImportService] [\TRIRIGA GIS Widget View Mode] group 1) Group Import failed - com.tririga.platform.versioning.recorddata.RecordDataVersioningException: Snapshot is not enabled for the Business Object Group, in the Module Group...
This problem appears to be the result of the 3.5.2 upgrade script, that enables snapshot functionality on the Group business object, running after the upgrade script that loads EsriJS components, during the initial 3.5.2 app server startup. The EsriJS upgrade has a Group that it is trying to import, and this is causing Group snapshot functionality to fail, since the necessary snapshot changes have not yet been applied to the Group business object.
HearUSA, the recognized leader in hearing care, has selected Tango’s Strategic Store Lifecycle Management Solution to support plans to explore new market opportunities and develop strategies for the United States and international markets, as well as support their future growth across the entire real estate and store development lifecycle. HearUSA purchased Tango’s Predictive Analytics, Market Planning & Site Selection, and Geospatial Location Platform products…
Tango’s Total Solution is unique in an industry that typically offers software that only addresses a portion of the real estate lifecycle. By bringing together Predictive Analytics, Retail GIS and Store Development Execution in a single, seamless offering, Tango helps organizations like HearUSA avoid the information silos that inevitably occur with disjointed solutions which often result in decisions being made with inaccurate and incomplete information. Tango enables retailers to make informed decisions, drawing on critical data from all areas of the lifecycle…