nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

re ordering of replicant on Delete replicant event

mansirastogi

Hi

In our project we have a requirement to provide explicit re-order functionality for the replicants. In this functionality we have provided a text box and a re-order button, user will enter the number in the text box and click on the re-order button, the replicant will move to that location.

On first opening a form, this re-order text box should be pre-populated with the order of replicant.
this re-order text box should also reflect the correct repliant index if user has used OOTB buttons for moving, adding and deleting replicant.

We are able to achieve most of this functionality, by using the events and javascript.

Only Delete part is left where are stuck.

If user clicks on the delete button of the replicant, that replicant should be deleted and all the replicant should show the correct order (replicant index) in the re-order text box.

Teamsite site version : 6.7.1, Solaris 10

I am wondering if any one has done it before.

Thanks
Mansi

Find more posts tagged with

Comments

ravio

Couldn't you make a call to another function onReplicantDelete and return from the event handler function.
Set a small amount of timeout (enough for allowing the event handler to return) in the called function and then go about doing the reindexing.

Maybe there are some more elegant ways of doing it, but thats the first thing that came to my mind

Hope that helps

Cheers

scrollwopagebreak.rptdesign

mansirastogi

Thanks

But method called onReplicantDelete event will be called before the delete event is fired. I want something that can be called after delete event is fired.

thanks
Mansi

Adam Stoller

Thanks

But method called onReplicantDelete event will be called before the delete event is fired. I want something that can be called after delete event is fired.

thanks
Mansi

Since the event handler is passed the item instance being deleted - you can easily parse the index number from that, and traverse all children of the replicant beyond it and decrement their ordering-number so that when the delete is completed the numbers should be correct.