Upgrade

Mark Pyc mark.pyc at gmail.com
Wed Aug 31 09:02:08 EDT 2005


Are the responsible agents hardcoded or expressions or via Rules?

On 8/31/05, Maes Steven <Steven.Maes at luminus.be> wrote:
> Hi Mark,
> 
> Thx for your reaction.
> 
> 1. This happens with all the steps of the workflow. Even when this step
> is a subworkflow. => it happens with several workflows. I haven't tested
> all the workflows yet since we are in the beginning of out testing
> phase.
> 
> 2. The possible agents are linked to the task. I can see this in the
> organisational structure and in the agent assignment of the standard
> task it self. (Additional data -> agent assignment -> maintain)
> 
> 3. The responsible agents are set as well (the org unit where the agents
> belong to)
> 
> 4. In the workflow log I can see the possible agents, but there are no
> selected agents.
> 
> 5. When executing SWI2_ADM1 and then the redo rule button, I can see the
> selected agents in the workflow log.
> 
> Very weird indeed ...
> 
> I can follow your thinking with the authorisation part. Thing is that I
> have executed the workflow myself.
> 
> 
> Steven
> 
> -----Oorspronkelijk bericht-----
> Van: Mark Pyc [mailto:mark.pyc at gmail.com]
> Verzonden: woensdag 31 augustus 2005 13:44
> Aan: SAP Workflow Users' Group
> Onderwerp: Re: Upgrade
> 
> G'day Steven,
> 
> Can you be a bit more specific about the agent resolution situation?
> 
> Some terminology clarification first:
> * Possible Agents are those linked to the task.
> * Responsible Agents are those returned by a Rule or expression
> * Excluded Agents are those listed as such at the step.
> * Selected Agents is the Intersection of Possible and Responsible
> minus Excluded. These are the people who can see the Workitem in their
> inbox.
> 
> >From your explanation it sounds as though initial pass of the Workflow
> sees the Rule return Responsible agents who are not Possible. The lack
> of intersection is what leads to the Workitem without agents.
> 
> When you reevaluate the rule a different set of agents who are
> possible are returned.
> 
> Sounds weird.
> 
> Does this only happen for 1 step in 1 Workflow and the rest of your
> flows are going fine?
> 
> Where is this step relative to the rest of the Workflow? Is the
> previous step a dialog step - this means that the agent determination
> happens under the executing users authorizations. When you
> re-evalutate the determination would happen using yours.
> 
> Have fun,
> Mark
> 
> 
> 
> On 8/31/05, Maes Steven <Steven.Maes at luminus.be> wrote:
> > Hello,
> >
> >
> > We are doing an upgrade from 4.64 to 4.72.
> >
> > For a workflow, the agent assignment is not working anymore. When
> > executing the WF, the step finds the possible agents, but no agents
> that
> > can execute the work item. We have clicked, double-clicked and even
> > triple-clicked in swu_obuf and swus and on the "generate index" in the
> > agent assignment in the task... no way it works. Strangely when we do
> > transaction SWI2_ADM1 "work items without agents" and press the new
> 4.72
> > icon "execute agent rules" which runs the REDUROLE-function, the
> agents
> > are found !!!!
> >
> > My guess is that there is some memory problem or some parameter
> missing
> > due to the upgrade.
> >
> > Anyone who encountered this or has a logical explanation ??
> >
> >
> >
> > Thx,
> >
> > Steven
> >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>



More information about the SAP-WUG mailing list