NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
7 replies Latest Post - 2014-04-01T07:14:33Z by BPMA
Pinned topic CoachDesginer XSL dojo Please Wait
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Has anyone built a processApp wide "loading, please wait" dojo nonmodal popup to lock the screen whenever coaches navigate on events?
Updated on 2012-12-17T22:16:43Z at 2012-12-17T22:16:43Z by SystemAdmin
laxmi87 2700051NG072 PostsACCEPTED ANSWER
Re: CoachDesginer XSL dojo Please Wait2012-09-22T07:09:57Z in response to JacobMEdelmanHi jacob,
kolban 10000004463315 PostsACCEPTED ANSWER
Re: CoachDesginer XSL dojo Please Wait2012-12-12T21:10:18Z in response to SystemAdminI created something similar just the other day for a project ... but it was for the BPM v8 Coach View technology. I found this awesome pre-made widget provided with the Dojo Toolkit:
NaveenBhardwaj08 270004SYTP55 Posts
Re: CoachDesginer XSL dojo Please Wait2012-12-13T16:58:04Z in response to NaveenBhardwaj08Hi Naveen,
Thanks for the response. I guess this was already tried out. It works fine when user has performed an action on the coach (like clicking on the submit button).
We are kind of facing an issue when the user actually clicks on the URL(coach exposed as URL) to open the submission form. It takes lot of time to load the coach and business wants a 'Page is loading' message for the wait period.
Re: CoachDesginer XSL dojo Please Wait2012-12-17T22:16:43Z in response to SystemAdminSo, if the problem is that when the user first runs the task you have a bunch of things the task needs to do to get to the point of rendering the first coach, then you have a few options.
- Evaluate the things you are doing before getting to the UI. Are they really things that have to be executed right when the user clicks the link, or are they items where "stale" data is not a concern. If stale data is not a concern, put those items in a system task and have it return the data that you then pass into the UI service, thus eliminating the wait.
- If you need "fresh" data, then think about creating your own utlitiy "Please Wait" screen. A utility service a while back that takes 3 arguments - the title, sub title, and details for display of a please wait. I used these as the Title, section name, and custom HTML of a coach that had a hidden button. I then had a JS that would click the hidden button. Put this as the first step in your task and then for each task you can have it display some meaningful context for the wait to the user like "Please Wait" "We are getting the details for your UI". "The HR process is loading the personell records and compenstation details from the HR database."