- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
First thing I would do is see if you get the same delay in a un-customized Workspace. This will tell if there is something to look for in your customization or not. Also, the version and SP level you are using may be helpful to know.
Next, ensure you have the latest fixes for whichever SP you are on. Note that the workspace source provided in a patch/SP stays in the patch/SP folder, it doesn't overwrite the original install folder source, so make sure your customization is on the updated source.
My guess is that the task is being pushed the client (workspace) but isn't being shown, either due to your customization or on older source, because of a missing refresh. The tasklist is bound to a dataprovider from a LiveCycle DataService. But very hard to determine why the refresh isn't occuring.
Another way to prove if the task is making it to you customized workspace is to use the Charles Web Debugging Proxy product to trace your http session. It understands the AMF protocol used by Workspace and LiveCycle DataServices. Look in the workspace-server/messagebroker/amfpooling messages at the time you expect the task to be pushed down from the server and you should see the task in one of the responses.
Views
Replies
Total Likes