Defining a step as a Background task

[Todd Walter]

A task cannot be a background task unless the method is defined as a
non-dialog method.  If you are using a standard SAP method you cannot change
this.  If it is a custom method, go to the BOR, double click on the method
and uncheck the 'Dialog' attribute.  To answer your second question, tasks
should be activated using transports instead of directly in the target
system.
 
Todd
 
>From: SMITH Elizabeth IS_Dept <Elizabeth.Smith at lai.ie>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Defining a step as a Background task
>Date: Mon, 22 Jan 2001 12:59:00 -0000
>
>Version 3.1H
>
>I'v defined a new task for inclusion in an existing Workflow. I want the
>task to run in the background but when I go into change task the Background
>Processing checkbox is 'greyed out' and I cannot check it.  Am I missing
>something basic?
>
>Also , initially when I transported the modified WF from our development
>server to our test server I found that the new step was not being executed.
>I then activated the WF in our test server. Now I've got a message in my
>inbox from the step (because it is not defined as a backgrounfd step - see
>first question above). My question here is is it correct procedure to
>activate the WF in the test server?
>
>Elizabeth Smith
>LAI
>
>
>Visit our Web Site:   www.lufthansa-airmotive.com
>
>                       *******************
>This email and any files transmitted with it are confidential and
>intended solely for the use of the individual or entity to whom they
>are addressed. If you have received this email in error please notify
>the sender.
>                        *******************
 
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com