Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.2.0.GA, EE-3.3.0.GA_P05
-
Fix Version/s: 4.3, EE-3.3.0.GA_P06
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ace
-
Support Case References:Support Case 14298:- https://icesoft.my.salesforce.com/5000g00001rKtID?srPos=0&srKp=500
Description
Currently the event triggered from the ajax listener does not keep track of the location in the source list and the new location in the destination list (like old event.getOld.... and event.getNew... from other components).
The user must instead do the following:-
If you need the indexes, you could read the request parameter 'formId:listId_reorderings' and parse the value, which contain an array of arrays of two elements, where the first element is the source and the second element is the destination. So, for a single reordering it looks like this:c[[2,3]]. ......, not very developer friendly in this case.
The user must instead do the following:-
If you need the indexes, you could read the request parameter 'formId:listId_reorderings' and parse the value, which contain an array of arrays of two elements, where the first element is the source and the second element is the destination. So, for a single reordering it looks like this:c[[2,3]]. ......, not very developer friendly in this case.
r52385: added ListMigrateEvent and ListMoveEvent for the ace:list migrate and move events, respectively, containing the indexes involved in the operation
r52386: backported to the EE 3.3 maintenance branch
Note that because certain operations involve multiple reorderings or migrations, these records are included in a list of MoveRecord and MigrationRecord objects, defined as inner classes in the event classes, respectively.