Is there any way we can specify the sequence of resource attributes to appear in the JSON-formatted Get query output? We are looking for a pre-defined set of ordered resource attributes to appear in the OSLC Get query output.
You should be able to use the oslc.orderBy parameter to define the ordering of results. If you are talking about the default ordering without that parameter, then I think the query definition of the query capability should define the ordering.
[Admin: To see other related posts, use the JSON tag or OSLC tag.]
Since TRIRIGA is new territory for a lot of you out there, and I have already received various queries about this, let’s take a brief look at the correct sequence to create a new TRIRIGA classification as follows:
- 1. Create a new BO within the Classification module, and add other fields, if needed.
- 2. Set up the Publish Name (BO Mapping). Tip: For classifications, you use the Name field as the lone field in the Publish Name to prevent entering duplicate classification entries. The Name field is in the Record Information section when you click Find in the BO Mapping tool.
- 3. Save the BO.
- 4. Create an association between the new BO and itself by using Is Parent Of. This action creates an Include. Note: Create this association from within the Data Modeler, not within the Association Manager. Also, when creating Includes, ensure that the Parent BO is in the Revision in Progress state before you create the association. Otherwise, the Include is not created properly.
- 5. Publish the BO.
- 6. Revise the Classification BO.
- 7. Create an association between the Classification BO and the new BO that was created in Step 1 using Is Parent Of. This action creates an Include.
- 8. Publish the Classification BO.
- 9. Copy the triClassification form and assign the new form to the BO that was created in Step 1. Add at least the Name field to the form.
- 10. Change the label of the new form to match the label of the new BO.
- 11. In the State Family, click Find to import the other states and transitions.
- 12. In the Includes/Forms tab, add the newly created form to the Includes list. (Add it to itself.)
- 13. Publish the form.
- 14. Revise the triClassification form.
- 15. In the Includes/Forms tab, add the newly created form to the Includes list.
- 16. Publish the triClassification form.
Thus far, we have the Classification definition metadata and no Classification records exist yet. In order to create records, follow the last 2 steps as follows:
- 17. From the Classification Hierarchy Master detail view, create the local parent for the new Classification as a child of the Hierarchy root record.
- 18. Create the actual new Classification records under the local root for the new Classification.
[Admin: To see other related posts, use the Classifications tag.]
We’re unable to perform a Sync Full of CAD drawings if there are any people assigned to the spaces. Here’s the ci.log error:
ERROR [com.tririga.ci.sync.SyncServiceImpl](pool-1-thread-2) Sync failed.
com.tririga.ci.error.CiRuntimeException: com.tririga.ci.remote.shared.error.CiSharedException: Attach associated object could not find the association to use.
The CAD hierarchy for the custom configuration is not mapped correctly for triSubSpace. Custom business objects and forms were created for all property hierarchy items. But the existing triSubSpace CAD hierarchy node for triSubSpace was not changed. It still references “Space Mapping”, instead of “cstSpace Mapping”. This means both space mappings are part of the application definition (which have different forms). This was causing the Sync Full to fail. Updating the triSubSpace hierarchy node to point to the cstSpaceMapping will resolve this error.
[Admin: This post is related to the 09.12.16 post about a Sync failure in CI, and the 08.05.16 post about a Sync Full error in CI.]
[Admin: As a side note, with the 3.5.1 introduction of object labels and revisions, you’re not required in 3.5.1 or later to use the classic “cst” naming convention any more. For reference, here are the new naming convention best practices.]
In the TRIRIGA 3.5 platform release, a new feature was added allowing you to track the performance and monitor who runs queries and reports in Report Builder. A flag can be set on the report definition that will track who has run the report, and the time it took to retrieve the information from the database.
To enable report run history, open the report in the Report Manager and click “Track History” on the General tab. Note that enabling this tracking causes just a slight overhead, but it should still be used with caution. Once enabled, you will need to let your users use the system for a while, so that some data can be saved. Once a few days goes by, you can then start to analyze what is happening in your system…
- Which reports have run the longest overall?
- Of the reports that have run, which have the average longest runtime?
- For the users in the system, who runs the most reports?
- Of the users in the system, who have run the longest reports?
TRIRIGA Web Services (WSDL) are not working on WebSphere 8.5.5 with TRIRIGA 3.4.2. The error “IncompatibleClassChangeError” is reported. The full error message is as follows:
Caused by: java.lang.IncompatibleClassChangeError:
TRIRIGA 3.4.2 uses the Apache Neethi 3.0.2 jar to support the web services associated with the Connector for Business Applications (CBA). However, it seems that WebSphere 126.96.36.199 uses an earlier version of Neethi internally via [WebSphere root]\AppServer\plugins\org.apache.axis2.jar. The two versions of Neethi don’t particularly care for each other and result in an “IncompatibleClassChangeError” problem… Without the TRIRIGA 3.4.2 Neethi, web services do not work. Without the org.apache.axis2.jar, the WebSphere Admin Console (and probably some other things) do not work…
CAD Integrator users who attempt to login via the CAD Integrator menu are getting an error indicating that there is no valid application definition. You see an entry in the server log like this: “No valid standard application definitions were found.”
This means the CAD application definitions or one of their components needs to be modified to account for changes in the underlying forms that the application definitions reference. You will need to review the server.log file and ci.log file to identify the missing component(s)…
The most common cause of this problem is the result of changes within the objects that are referenced by the application definitions. For example, if the triFloor form has been modified to include a new field.
[Admin: This post is related to the 01.29.16 post about getting an error that no valid CI application definitions exist.]
If I understand correctly, there isn’t a way out-of-the-box to attach a drawing to a floor record that is a child of a structure. It appears the OOB application definition does not include a CAD mapping to do this. I see an RFE suggesting this.
My question is, has anyone looked at doing this themselves without waiting for an RFE to work its way through the process? If so, what is involved and is it advisable? Our use case is that we have many smaller utility-shed-type buildings that we do not want to include in our real estate rollup reports, but we need to track square footage at a local level. So we are thinking of using the structure form for all of these small buildings.
[Admin: This post is related to the 04.05.16 post about attaching drawings to floors under structures.]