When using Clarity XML Open Gateway (XOG) to create or update a Financial Cost Plan, the application is processing the action slowly because it is invoking 'insta-slicing' multiple times resulting in slower XOG throughput. By design, The application should only 'insta-slice' data that is directly added as a 'manual' cell value through the application user interface. When the application is creating a cost plan using XOG or using the Cost Plan 'populate' feature, the slices are created or updated when the Time Slicing job is executed.
Steps to Reproduce:
- Pause the Time Slicing job for this example
- Create a 'manual' Cost Plan within a Project that has a Department OBS unit defined
- Manually 'add' one row to the Cost Plan - by design, manually added rows will have data automatically sliced
- Query the data to confirm slice records exist for manually added rows
- XOG out the Cost Plan
- Delete the detail row from the UI, confirm slice rows are gone by executing queries again
- With the Time Slicing job paused, XOG the Cost Plan back into the system
- Execute the queries again
Expected Result: No slice rows will exist in ODF_SSL_CST_DTL_UNITS as XOG should NOT automatically invoke 'insta-slicing'. The time slice job is responsible for slicing these rows.
Actual Result: Slice rows are populated, the XOG write action has invoked the 'insta-slicing' action.
None. Data is automatically sliced, the XOG write action will be slow, but this does not affect the data integrity.
Remember to resume the Time Slicing job.
Resolved in Clarity 13.2.0 Generic Patch. Reference TEC599354
Resolved in Clarity 13.3
Resolution to this issue prevents the 'insta-slicing' to occur for XOG write action.
Be sure to wait until the Time Slicing job completes after the success XOG write action to see the data sliced.