There's a couple of different ways you can do this.
You can configure your application so that the approve/reject operations are sent as a batch. In this scenario, you would take the individual approve/reject operation menuitem and make it of type Delete Listview Row/Delete Key Collection (what its named depends on what release you are using). This marks the row as having been deleted, and thus it will be removed from the listview when you go back to it. Then, put a Submit Workflow menuitem on the listview screen and have it do a Parent Update. This will then, asynchronously, send to the server a request to go through the listview and, for each row, visible or not, invoke the corresponding operation on each row, depending on what the state of that row is ("add", "update", or "delete"). In this case, you'll have mapped the "delete" state to your approve/reject operation.
In the other scenario, you want the approve/reject operations to be invoked right away, as online request (necessitating an active connection to the server). To support this, you'll want to write custom code to mark the current message value collection's state as "delete", which will be a cue to the listview not to display it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.