I have an issue where it is not possible for non-Admin users to trigger the Create state transition through our OSLC interface. Instead, we get the following error:
2017-06-27 13:08:10.301 UTC ERROR [com.tririga.platform.integration.oslc.OslcRequestDispatcherImpl](Default Executor-thread-34280) Failed to read message: null
2017-06-27 13:08:10.301 UTC ERROR [com.tririga.platform.integration.oslc.OslcRequestDispatcherImpl](Default Executor-thread-34280) Exception in OSLC call: com.tririga.platform.integration.oslc.OslcException. message=java.lang.ClassCastException: com.tririga.platform.metadata.domain.BoStateTransitionId incompatible with com.tririga.platform.metadata.domain.gui.GuiStateTransitionMetadata
The fact that I am able to create and associate the record using an Admin user says to me that this is related to permissions, but I’ve made sure that the user has full security access for both the BO/form it is trying to create, the BO/form that it is attaching it to, and all other BOs/forms that are associated to it, and it still gives me the error above.
When I open the created record that my Admin user created, it looks to be correct. But when I open the one that the non-Admin user tried to create, it shows an empty record. None of the fields are saved in a null state, which of course is because it didn’t get created, the Create state transition was not triggered. Any idea of what is causing this issue? And how to resolve it?
[Admin: To see other related posts, use the OSLC tag.]
I am experiencing an error with a smart section that was working just a week ago. This smart section exists across various environments, but is now causing an error in the development environment. I have experimented with the following:
- Removing the smart section causes record to show properly.
- Association and reverse association are both set properly.
- Removing all fields from the smart section causes the record to show properly, but adding any one field results in an error again.
- I can move the smart section to another tab and the rest of the record shows properly, until I click on the tab with the smart section.
- I have already tried object migrating the business object and form from an environment that works.
In the server log, this is error that shows:
440 ERROR [com.tririga.platform.error.ErrorHandler](WebContainer : 16) Report handled exception: com.tririga.platform.gui.rendering.GuiRenderingException: Could not render Gui Component: GuiTabMetadataImpl[Name=triGeneral,ID=14,GUI=GuiMetadataImpl[Name=tdbREProjectAuction,ID=10048479]] for record: SmartObjectImpl[ID=SmartObjectId[ID=47510356,Business Object ID=10002876],Business Object=BoImpl[name=triREProject,id=10002876,module=ModuleImpl[name=triProject,id=19]]][MID-3549400938]...
[Admin: This post is related to the 05.25.17 post about a GUI rendering issue. To see other related posts, use the Smart Section tag.]
We can’t export the graphic floor map to PDF from TRIRIGA. The system is “hanging” and not exporting. This is only happening with some drawings and only occurs when using Layer 0 from the Xref file ( xrefdwg | 0 ). If all other layers are off and a layer zero from any Xref is displayed on the graphics section, even if empty, the export will fail to complete.
The export graphic was throwing a malformed XML exception. The root cause was that there was a “1 = 1” element that got pulled in from the layout of an attached Xref onto layer 0 on that Xref. It turns out that, for any text element that contains any equals sign, the process of sending the SVG from the client to server using a Dojo API to post via a hidden input element, resulted in extra double quotes getting sent, and causing the SVG XML to be malformed.
We resolved this by pre-processing the SVG sent to the server to remove these extra double quotes, before sending it to the SVG converter. Moving forward, the export graphic will now successfully export a graphics section that includes text that contains any equals sign. Text that contains both double quotes and equals in it, will get the double quotes removed for technical reasons.
[Admin: To see other related posts, use the Xref tag or SVG tag.]
We are seeing an issue where a floor plan is not getting loaded for a particular building. We see a lot of errors in the server logs, but cannot make anything out of it. Can anyone advise what could be the issue here? The error is as follows:
2017-05-25 15:05:53,509 ERROR [com.tririga.platform.error.ErrorHandler]([ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)') Report handled exception: com.tririga.platform.gui.rendering .GuiRenderingException: Could not render Gui Component...
[Admin: To see other related posts, use the Graphics tag.]
I am getting a strange error when I am trying to deploy to TRIRIGA with the WebSphere Application Server (WAS). TRIRIGA doesn’t come up and throws an exception. Interestingly, when I point a Liberty application on the same DB2 database, it works well. I have confirmed with my network team that this is not a network connectivity issue. Here are the error logs:
Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: DB2 SQL Error: SQLCODE=-805, SQLSTATE=51002, SQLERRMC=NULLIDR1.SYSSH200 0X5359534C564C3031, DRIVER=4.18.60 DSRA0010E: SQL State = 51002, Error Code = -805...
Have you checked to see that both the Liberty server and the WAS server are actually using the exact same version of the DB2 driver (db2jcc4.jar)?
[Admin: To see other related posts, use the DB2 tag or JDBC tag.]
If a query section exists in a record, that query section has a “Find” and “Remove”. If that query has a “Group By” in it, the “Remove” will issue a MID error (even though the removal actually takes place) if filter criteria are applied before clicking “Remove”.
The problem does not occur if no filter criteria are applied before clicking “Remove”, or if the query associated with the query section does not have a “Group By”. This problem was seen in multiple releases including TRIRIGA 220.127.116.11 and 18.104.22.168.
We needed to change the submit of the page method to “Get” for non-state-changing actions like “Refresh” or “Clear Filter”. The “De-Associate” action on the “Group By” report no longer throws any exception after applying a filter to the query.
If you add a single quote to a query name and click “Where Used”, it causes errors. I suspect this is due to the SQL generated, as it would require an extra single quote to pass the string correctly. If you add another single quote, to ‘escape’ the character, it will work correctly. This is an amendment to the SQL query that is generated when clicking “Where Used”. Additional logic is required where it searches for a single quote and then if it finds one, it adds it to the SQL generated.
We needed to update the SQL call to allow for a single quote in the parameter. Moving forward, the issue is resolved where the “Where Used” tab throws an exception if the report has single quote (‘) in the name.