Hi all,
We have a process where there are three actions. The first and the third actions are created from normal Web Dynpro applications. The second action is created from a callable object of type Background Execution. We need to assign the first and the third actions to two different users (which they can open from their UWL). The third action will reach its corresponding user only when the background callable object (second action) is completed. The problem we are facing is that GP requires us to assign a user (or role) to the background callable object action too. Due to this, this action is also going to a user's UWL (although on clicking on it, we just see a message that "The next activity is not yet available: try again later using the Refresh button").
We do not want the background callable object action to go into anyone's UWL. According to our understanding, this should be the logical behavior of this type of callable object. Can anyone provide any clue?
Thanks in advance.
Bye
Ankur