We recently upgraded to TRIRIGA Platform 3.5.3 and we are still in Application 10.3. We have a custom cstWorkTask form and it has 133 form actions. In the “Shop Foreman” security group, we want to give access to over 125 form actions.
But it looks like there is a limit where you can only set 119 form actions. Because as soon as you select the 120th form action, the spinning wheel appears and never completes. We have tried clicking the “Select All” check box, but as soon as you click that, the spinning wheel appears and never completes. If we remove a couple of actions from the 119 already selected, then it lets you check two more without the spinning wheel. Is there any setting that controls how many form actions can be set in the security group? Or is this a known issue?
[Admin: To see other related posts, use the Security Manager tag.]
We are using IdP-initiated SAML, and we access TRIRIGA via a link that looks something like this: http://idpprovider/applications/Tririga. Can we pass this link in FRONT_END_SERVER in TRIRIGAWEB.properties so that users can click on the link that they get in a work task email, and they can be redirected to TRIRIGA?
SAML does not support basic authentication for non-browser clients. This is a SAML limitation. See the following APAR IV88274 link.
[Admin: For convenience, here are the meanings of the acronyms: Identity Provider (IdP), Security Assertion Markup Language (SAML).]
[Admin: This post is related to the 08.18.16 post about lack of support for non-browser clients. To see other related posts, use the SAML tag.]
Is there a size limitation on multi-record smart sections? We have more than 70,000 users. So the group member list could be huge. The Group Member section of the security group doesn’t show all of the users that belong to this group. Is this a known issue?
This is a limitation of the platform and smart sections. The performance of a smart section will slow down when you have that many records in the section. Customers have worked around this limitation by hiding the smart section, and showing a query in its place. You can then have the query section actions perform the add and remove of members from the hidden smart section…
After upgrading to TRIRIGA 3.5.2, we are facing an issue on editable queries, where the locator fields are not populating after selecting a value from the popup query. Also, it logs out after we select a value, click “OK”, and refresh. Has someone faced the same issue? Or is it a known issue?
This issue is resolved in the 22.214.171.124 Fix Pack and is now available on Fix Central. The readme file for 126.96.36.199 can be found here.
Are there any known limitations with pie charts in the TRIRIGA Report Manager?
We created a chart, but the available data meant it should show 100% for a single status value. However, the report just says “No data to display”. Expanding the filter to bring in more records meant that we had multiple status values to display and the chart displayed correctly. Is there a limitation on a pie chart so that if the result set is 100% in one grouping, it doesn’t display anything?
This is a known issue covered in APAR IV95291. You can subscribe to the APAR for updates on the fix.
Disclaimer: TRIRIGA encourages using the latest platform release when installing new TRIRIGA databases. This ensures that you have the latest platform with fixes to known issues. However, if you need to stay at 3.4.2.x and are installing on Microsoft SQL Server, review the following as you might encounter collation issues.
New database install, single-byte
There is a known issue with a TRIRIGA 3.4.2 and SQL Server new install where the single-byte option is ignored during the installation process and the resulting TRIRIGA database will be MBCS with a Latin1_General_CS_AS collation. If a single-byte environment is absolutely necessary, we suggest using TRIRIGA 3.5 where the issue has been resolved.
New database install, multibyte, non-English collation
There is a known issue with a TRIRIGA 3.4.2 and SQL Server new install where the multibyte option is selected with a collation other than English/Latin1_General_CS_AS. The chosen collation is used when building and populating the database, but the ENVIRONMENT_PROPERTIES value for “db.mbcs.mssql.collation” is not set correctly and can cause issues when new text fields and new business objects are created and populated. You can possibly get a collation conflict exception. (Note that for English collation, there is no issue since the “db.mbcs.mssql.collation” is set correctly.) We suggest you make the following changes to ENVIRONMENT_PROPERTIES…
[Admin: This post is related to the 06.29.16 post about installing TRIRIGA 3.4.2 or 3.5.0 on a non-US English database.]
We recently upgraded to TRIRIGA Platform 188.8.131.52. But Internet Explorer has an issue with some of the floor graphics, where the export to PDF is not showing the labels. Meanwhile, the export to PDF for the same floor is showing the labels in the Chrome browser with no issues.
This is a known issue and has been reported to Microsoft. It is a limitation with Internet Explorer (and Edge). The bug has been reported here. Text elements with x,y attributes 214749 or over resolve at -214748.3648. We cannot do anything to fix it on our end, but there are some workarounds:
- (a) Use another browser to export.
- (b) Move the drawings closer to the origin and republish it. The text elements need to be inside of +/- 214749 to avoid this issue.