table.removeRecord() destoys the coachView.context on any nested Coach Views

Gary Joy

February 25, 2020 at 8:48 am #5688

I’m using the UI Toolkit (8.6.0.0) in IBM BPM.

I’m using the Table Coach View and inside the Coach View (i.e. for each row) I am using a Custom Coach View of my own.

When a row is removed from the Table (either using the out-the-box remove or by calling table.removeRecord(rowIndex);) the “context” of all my Custom Coach Views (i.e. all rows, not just the one being deleted) is destroyed.

I can see this by doing something like table.ui.get("MyCoachView[1]") just before and just after table.removeRecord(rowIndex);.

This causes problems for me down the line e.g. in the custom validation I have added to my Custom Coach View.

I have a feeling that this is a bug that may be fixed in a newer version but I would be really grateful if there’s some kind of fix/workaround I can apply in the meantime.

Thanks!

SPARK Support

February 25, 2020 at 10:01 am #5695

Hi Gary,

I have experienced this same issue.  A PMR should be opened with IBM for them to support a fix or work around:

https://www.ibm.com/support/home/

However, I have worded around this issue by adding a Boolean to the list.  Set the Boolean to true when deleting a record and simply hide the div for the row.  Then delete the record server side in the Process.

I should point out that I have only observed this issue when the Table contains nested objects such as a Data control or another Table.

Feel free to reach out to our Sales Team if you would be interested in getting more information about an Expert Services agreement from Salient Process.

Regards,

Stephen P.

Gary Joy

February 25, 2020 at 12:02 pm #5696

Thanks Stephen!

I always consider PMRs a bit of a last resort but that’s probably where I am on this one now…

I did consider a workaround along those lines. It would need to be a bit smarter because each row is unique and they could re-add the deleted row. I was worried that by the time I had written all the code necessary to make it work I could build a custom coach view that encapsulated the table behaviour as well as the row behaviour.

I appreciate your quick response and I remain a big fan of the Spark Toolkits.

🙂

 

SPARK Support

February 26, 2020 at 12:13 pm #5702

Hi Gary,

If the user readds a deleted row, you could use some logic to simple display the TR div again and set the Boolean to false.  But yes, this would be some complex custom logic.

Regards,

Stephen P.

Gary Joy

February 27, 2020 at 1:58 am #5705

As you indicated, the problem is limited to situations where the Table contains nested Tables (or similar). I reworked the solution to avoid this and everything is good now. 🙂

SPARK Support

February 27, 2020 at 7:17 am #5708

Hi Gary,

Good to hear.

Regards,

Stephen P.