The support for secondary methods is discussed in Note 882731. The note states that support begins in release NW04 SPS15 and NW04s SP05 for backends from 6.20+.
For those of you are are new to secondary methods, here are the basics of what you should know:
- Secondary methods are part of Business Workflow.
- They enable you to execute an additional method to the task method.
- There are three types of secondary methods:
- Amodal – executes at the same time as the task.
- Before work item execution – executes before the task.
- After work item execution- executes after the task.
Secondary methods are accessed by selecting the “Methods” tab from your workflow task.
Notice the types of secondary methods, and notice I am using an Amodal secondary method.
My workflow task is the basic user decision. The secondary method is to display a material.
Now notice how this appears in UWL at runtime.
The task in UWL is the “basic decision” task. The secondary method is displayed in the details of the task as “Required Reading”.
At this point I can execute the “Required Reading” which launches the secondary method, or I can execute the decision to complete the task.
So, what do you think? Please do a reply once you give secondary methods will UWL a try. The current limitation is that you can only use the amodal type of secondary methods. The before and after secondary methods should work if you are only using ITS to launch the task. In my example I was using the SAPGui to launch the task and the before/after secondary methods did not work. So, at least for now, you should try it with the amodal secondary method.
Give this a try in 2007!!