Workflow logically deleted instead of invoking default rule

[Dale Davis]

Thanks Jocelyn:
 
I found the note and  just referenced it in my OSS message which I had
created yesterday morning. This is now the second message I have opened
related to the rule resolution behavior in 6.20. The first was created at
the start of the month but is still being worked on. Hopefully they can fix
the code for this problem so that it checks for a default rule before it
sets the workflow to error status since I would prefer not to change the
WFLOW.ROLE flag.
 
Perhaps that  flag is the source of the error  for my other message where
the returned notification agent from the rule is being erroneously checked
against the background agent for the  task. Maybe the code doesn't consider
the workitem type or the agent type in the check? I will have a look.
Thanks for the feedback.
 
 
Regards
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow/Webflow  PP Consultant - SAP Practice
 
IBM Business Consulting Services
Phone: 845-691-7861
           T/L 8-320-8440
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
lose sight of the shore..........
 
 
"Dart, Jocelyn" <jocelyn.dart at sap.com>@MITVMA.MIT.EDU> on 01/24/2003
12:32:05 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Re: Workflow logically deleted instead of invoking default rule
 
 
 
Hi Dale,
The rules did change around what happens if you don't find any
responsible agents - actually as a result of issues in EBP/CRM.
Please read OSS note 491804.
 
However, for your scenario I still think the default rule should have been
 called
 - you may want to take this up with OSS.
 
The logical deletion is strange - you might want to raise
that via OSS if you find a way of replicating the problem.
 
Also there is a flag WFLOW.ROLE in table T77S0 that controls whether the
agents returned
by a rule are to be checked against the possible agents. Generally it
should be on.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Dale Davis [mailto:dkdavis at us.ibm.com]
Sent: Friday, 24 January 2003 5:54 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow logically deleted instead of invoking default rule
 
 
Sergei,
 
While I agree with you that the default rule is probably invoked only  if
the exception 'Nobody Found' is raised , I disagree that  it is accurate
that the system response is to set  the workflow status to either error or
cancelled when the agent found by the rule is not a possible agent.
Instead, I would at least expect it to broadcast the workitem and only set
the workflow to error status if the
terminate flag is turned on for the rule.
I believe the logical deletion is a system glitch since I have not been
able to reproduce it, but I think the setting of the workflow to error
status is invalid. I am on CRM 3.0 with a 6.20 kernel and I believe this is
a bug since this behavior is inconsistent with the behavior of roles in
releases 4.6C and below. I found no release notes that stated that the
behavior of rules had changed in this aspect.
 
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow/Webflow  PP Consultant - SAP Practice
 
IBM Business Consulting Services
Phone: 845-691-7861
           T/L 8-320-8440
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
lose sight of the shore..........
 
 
"Breslavets, Sergey" <Sergey.Breslavets at anheuser-busch.com>@MITVMA.MIT.EDU>
on 01/23/2003 01:19:25 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Re: Workflow logically deleted instead of invoking default rule
 
 
 
Hi Dale,
 
this is correct - they must be defined as possible agents, or task must be
classified as 'General task'.
 
Default role (for task) is evaluated when no other responsible agents for
the
corresponding workflow step were determined, and in any case all
responsible
agents found (whether explicitly specified, or default) are validated
against
the task possible agents (if the task is not General).
 
Sergey
 
 
 
 
 
 
-----Original Message-----
From: Dale Davis [mailto:dkdavis at us.ibm.com]
Sent: Thursday, January 23, 2003 5:51 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow logically deleted instead of invoking default rule
Importance: High
 
 
Hi Folks:
 
I have a CRM workflow which dynamically selects the agent  for a dialog
step based on rule type FM. I am testing the scenario where the agent
determined by the rule is not a possible agent of the task. My expectation
is that my default rule assigned to the task which selects an administrator
should be invoked. Instead, I receive an error message, 'Responsible Agent
ACXXXXXXXis not a possible agent of task' ,  the dialog workitem is never
created, and the workflow is logically deleted.
 
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow/Webflow  PP Consultant - SAP Practice
 
IBM Business Consulting Services
Phone: 845-691-7861
           T/L 8-320-8440
  Internet Address: DKDAVIS at US.IBM.COM
 
........You can never discover new oceans unless you have the courage to
  lose sight of the shore..........