start condition with virtual attribute doesn't work

[Breslavets, Sergey]

Hi Victor,
 
If this is the case then users might have the same issues during subsequent
dialog steps due to the missing authorization...
 
-----Original Message-----
From: Viktor Smusin [mailto:Viktor_Smusin at atlantm.com]
Sent: Friday, September 24, 2004 2:19 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: start condition with virtual attribute doesn't work
 
 
 
 
 
Hi, Wiz!
 
I'm dealing with a similar problem right now. I guess your problem is the
same as me: the code that calculates your virtual attribute requires some
authorizations. And for the "Condition" step type the user who performs
this code isn't necessarily WF-BATCH, and it doesn't necessarily have the
required authorizations. I've made several tests and it looks like the user
performing the code for this step type is the same user who was the agent
for the previous "Activity" step type.
 
I found 3 ways of solving this problem:
 
1. Rearrange your workflow so that the "Activity"-step previous to your
"Condition"-step is a background step. If it's so, then both steps are
performed by WF-BATCH which has SAP_ALL authorizations.
 
2. A more universal way. Add a method to your business object interface
which checks your condition and returns "X" if it's true or " " otherwise.
Create a background single-step task which calls this method. Then add an
element to your workflow's container which holds the values of the same
type. And just before your condition check in the workflow place an
"Activity"-step which calls this method. And in the condition itself check
the value of the container element, not of your virtual attribute (you
doesn't need it anymore).
 
3. Similar like 2., but specify a result parameter for your method with a
reference to an ABAP Dictionary field which has a domain that can hold 2
different values: "X" and " ". For example, you can specify the reference
to the field RSDXX-MARK. And instead of your "Condition" step type place an
"Acitvity" step type in your workflow. Then you'll have 2 branches after
this step which correspond to the 2 variants of the result of your
condition.
 
Hope that helps.
 
I'd like to know more exactly who is the user which performes the code
calculating the virtual attribute in the "Condition" step type, though. Am
I right that it's the agent for the last "Activity" step performed in the
WF?
 
Viktor Smusin
Minsk, Belarus
 
 
 
 
 
                      Wiz David
 
                      <yidysap at yahoo.com>        To:
SAP-WUG at MITVMA.MIT.EDU
 
                      Sent by: SAP               cc:       (bcc: Viktor
Smusin/072/Minsk/AtlantM-Inc)
                      Workflow                   Subject:  start condition
with virtual attribute doesn't work
                      <Owner-SAP-WUG at MITV
 
                      MA.MIT.EDU>
 
 
 
 
 
                      24.09.2004 08:23
 
                      Please respond to
 
                      SAP Workflow Users'
 
                      Group
 
 
 
 
 
 
 
 
 
Hi all,
 
 
 
While I create start condition that was based on virtual attribute I found
that it s ignore my condition. Further More I see in the log the virtual
attribute with the correct value,
 
Its looks like that in runtime it s not calculate the value yet. but when
we go inside the log it s already calculated.
 
If I m changing the condition as to be based on data based attribute it
works fine.
 
Even inside the workflow if the first step it s condition on virtual
attribute it s ignore my condition although in log I see value on my
virtual attribute.
 
 
 
How can I solve this problem without added field to my table that will
contain the calculate value?
 
 
 
T.I.A
 
 
 
Wiz
 
 
 
---------------------------------
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.