You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Advanced Sort isn't taken into account, at least for the React demo. Siebel doesn't run anything on the presentation model for the applet being sorted for advanced sort, so this makes no trigger in change of state. In order to get it working with the React Demo (a modded version), I put a PR on the sort applet to trigger a change to a global flag to make React know the data changed.
So in BindEvents for the PR:
$(fullAppletId).find("[title='Sort Order:OK']").on("click", function(){
SiebReact.sorted = true;
});
Advanced Sort isn't taken into account, at least for the React demo. Siebel doesn't run anything on the presentation model for the applet being sorted for advanced sort, so this makes no trigger in change of state. In order to get it working with the React Demo (a modded version), I put a PR on the sort applet to trigger a change to a global flag to make React know the data changed.
So in BindEvents for the PR:
$(fullAppletId).find("[title='Sort Order:OK']").on("click", function(){
SiebReact.sorted = true;
});
In React component:
if(SiebReact && SiebReact.sorted){
SiebReact.sorted = false;
SiebReact.refreshList();
}
Our implementation relies heavily on advanced sort, since the users actually use that for sorting instead of clicking columns on Siebel.
Is it possible for Nexus to know the advanced sort has been triggered by a user and somehow trigger a callback since Siebel doesn't?
The text was updated successfully, but these errors were encountered: