Problem refreshing UI after document deletion
Hi,
i'm trying to implement a permanent deletion feature : I created a document type that lists the deleted documents for a given user, so that he can permanently delete the selected ones.
Everything runs fine … for the first deletion
It seems that the previsously selected documents are still cached somewhere in the UI (my “permanently delete” button is enabled although selection is empty), so that if i try to delete a second batch of docs, i get a “No such document” error.
I tried to use the Seam.Refresh operation, but it doesn't seem to work.
Any idea ?
 |
pibou Bouvret
Member (8.9K) 4 7 10 |
05/03/2012 ( History) |
Actually we're missing a 'Clear Selection' operation, a bit like 'Clear Clipboard' works.
The code of your operation would look like that:
@OperationMethod
public void run() {
OperationHelper.getDocumentListManager().resetWorkingList(
DocumentsListsManager.CURRENT_DOCUMENT_SELECTION);
}
This will empty the current selection. The refresh UI operation only invalidates queries cache.
 |
Laurent Doguin
Member (6.6K) 2 5 5 |
05/10/2012 ( History) |
For my second problem ("validate button"), i created a "refresh" automation chain that does what i do in the UI :
Navigate to the Parent document
refresh
Go back
Seems dirty … but it works.
the 'Clear Selection' operation works fine : I can select documents after a deletion, nevertheless i still have to refresh the list with my “refresh” automation chain.
|
pibou Bouvret
Member (8.9K) 4 7 10 |
06/04/2012 ( History) |
thx
What's the point of the "Refresh" action since it seems it does not refresh anything ?