TRIRIGA OSLC API's - BULK PROCESSING OF PRIMARY BUSINESS OBJECT RECORDS

IBM TRIRIGA Application/Platform OSLC defect:

In current OSLC framework of Tririga, attempting to push multiple records—such as cost center entries, profit centers, and personnel records—in a single payload while posting multiple records is failing. When these records are sent from the client code i.e. source system, the OSLC post processes each record individually. Due to the limitation in the existing Tririga OSLC framework, which doesn't support bulk processing of records, the session history table is being accessed multiple times.  Reason behind multiple hit, authentication process for each individual record is creating a new session each time a record was posted to TRIRIGA. As a result, both the security log and the `session_history` table in TRIRIGA were being hit for every single record while submitting payload which has bulk data to post.This has resulted in the table size increasing to approximately 99 GB over six months, negatively impacting database performance. The Cargill IT team is seeking a solution from IBM to enable the pushing of primary business object records in a single payload from the client code system to Tririga using the OSLC framework.

We can see OSLC payload syntax for bulk processing of associated records is available but missing for primary business object. Customer IT team is looking IBM to enhance the platform to enable bulk processing for primary business object records via. OSLC REST API.