An idea on how to attack back at 'runaway' general tasks

[Mark Pyc]

G'day Tedde,
This is a new one on me! How many more tricks do you have up your sleeve?
The usage I liked was where in log-on exit you check if a user has newWorkitems and if so redirect them to the business workplace as theirstart transaction. This is much nicer than setting the businessworkplace as the standard log in transaction statically as it onlyapplies to those who have work to do.
Same exit I presume? How do you set the business workplace as the first screen?
Have fun,Mark
On 5/9/05, Tedde Taege <ttaege at nebraska.edu> wrote:> > At the urging of workflow gurus Mark P. & Mike P., I am posting an idea that> was included in my presentation at ASUG.   > > I have been burnt by general tasks that get sent into everyone's workflow> inbox.  Here is a way that lowers the exposure from a runaway general task> by checking for general tasks as each user logs into the system. > > In user exit EXIT_SAPLSUSF_001 - ZXUSRU01 (function group XUSR) which> executes at user login: > •        Retrieve work list for user  (function SWR_WL_CREATE) > •        Check agents assigned for work items (function RH_WI_AGENTS_GET) > •        Reserve general task work items to a specific ID (i.e. workflow> administrator) (function SAP_WAPI_RESERVE_WORKITEM) > •        Upon a successful reservation, notify workflow administration about> the work item > > Use caution with this exit because if you mess up here, then your users> might not able to log into the system. > > > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > >