How long can a password be in IBM TRIRIGA?
There is no maximum password length imposed by the out-of-the-box TRIRIGA system. The encrypted password length is 500 characters. However, that encrypted length translates to about 125 characters.
[To see other related posts, use the Password tag.]
I’m seeing issues within report results, where if the user profile language is in US English, the results are of one type, but if the user profile language is in German, it is showing some other data. The record while checked is the same for both cases. While opening and checking the record, the ID and name of the record varies from what it showed as a result in the report. While investigating, what we observed is that these fields are marked as “Localizable” in Data Modeler. What is the use and impact of the “Localizable” field property? Any suggestions?
Here is a PDF link to the 3.5.3 Globalization (Localization) user guide. Also, perhaps this technote on localized database storage will help provide some insight.
[Admin: The same question is also posted in the main Application Platform forum. To see other related posts, use the Localization tag or Language tag.]
When running queries against records within the application, expected record results are not displayed. Why do queries that are expected to display data show nothing at all?
Within the application, we have a variety of different settings that can restrict a user’s access to record data. The user’s Security Group can restrict access to records at the module and BO level, but each use case is slightly different.
Within every user-facing record, on the System tab, there are fields for System Organization, System Location and System Geography. These values operate in conjunction with similar fields on the Security Group and the User’s People record to allow and restrict access to records.
The key is that as soon as the user is given a defined Organization, Location, and Geography, the fields on the System tab of their People record are populated. Once that happens, each record they create will be seeded with that information as well. So far, all is well and good, but those users who lack similar settings are now unable to see those newly created records, unless their System fields are the same as or located at a higher point in the hierarchy.
Another area to consider is the Security Group settings for Organization and Geography. If a user has no values set on their People record, the application can still restrict access by using the Security Group values. This can cause a problem as the Organization and Geography Security is defaulted to null in the as-shipped application. This essentially gives the security code no starting point for determining access and will not display records.
To recap, if the record data does not align with the data in the user’s People record, or the data in the user’s Security Group, the record will not be displayed. As mentioned, there are a couple of things to look for. As an Admin user, compare the user’s record data with the record that should be displayed, and correct any misaligned data. Also, in the Security Group, set the Organization and Geography to the root of each hierarchy by default. For additional details, please review the following TRIRIGA wiki article: Security Overview.
We manage properties globally so some of our locations are measured in Imperial and some are in Metric. What is the best way to manage this type of scenario so that our drawing and graphics section labels are not incorrectly sized when they are viewed from other global geographies?
The best way to address this situation is to have 2 sets of labels for your drawings, and 2 sets of labels for your TRIRIGA graphics section. You will need to adjust the height of the label elements to work for both situations. We are considering an enhancement to automatically scale according to the drawing units.
[Admin: To see other related posts, use the Graphics tag or the Labels tag.]
Why doesn’t the picker show up in a smart section when doing an edit map?
The business object is not mapped correctly. If the “Map From” object is not correct for the smart section that you are trying to map to, the picker will not display in the smart section. If the smart section displays information about a people record that uses the triPeople business object, then the “Map From” BO must be of the type “triPeople”.
[Admin: To see other related posts, use the Smart Section tag.]
If you attempt to revise a project from the Schedule tab, where the Gantt chart is visible, your session is expired and you receive an invalid session error. The issue was observed in Internet Explorer and Chrome, but not in Firefox.
An analysis from a Fiddler trace shows that when revising the project in Chrome, this POST to GanttDataUpload.jsp seems to kill the session. In Firefox, for whatever reason, this POST doesn’t occur, and the state transition is successful. To confirm that this is the scenario you are experiencing, use the following technote to run a Fiddler trace and check for the same GanttDataUpload.jsp call: IBM TRIRIGA using Fiddler for tracing web browser traffic.
As a temporary fix, use Firefox. When the record is in a read-only state, no Save action should be called on the Gantt. Moving forward, we resolved the session-kill issue when the user performs a Revise action on a project in the Schedule tab.
[Admin: This post is related to the 08.18.15 post about using Fiddler to trace TRIRIGA web traffic. To see other related posts, use the Gantt tag or Fiddler tag.]
Sometimes when using TRIRIGA CAD Integrator “Smart Attach”, some of the spaces are not being uploaded. There were 3D shapes around some spaces. There were values greater than 0 on z= dimension.
TRIRIGA does not support 3D polylines. You may have shapes with a value greater than zero on the z= dimension. You can find these using the AutoCAD PLIST command. To resolve this issue, it is necessary to use the AutoCAD “Flatten” command to force all polylines to be 2-dimensional. Other things to check: (1) The polylines are closed, (2) The shape and labels are on the layer you are selecting during the Smart Attach process, (3) The label is within the polyline boundary.
[Admin: To see other related posts, use the Smart Attach tag.]
