Workflow Start Conditions

Thu Nov 11 06:08:20 EST 2010

@Berry: Sometimes things get confused between client-dependent and client
independent start conditions. In SWB_COND -> Extras -> Settings ->
Processing mode.
SWDD will show one type (I think client-dependent, no time to check). But
if SWB_COND is set to the other, you will see the discrepancy you
described.

@Rick - you can code whatever you want into an object attribute and
evaluate that in a start condition. SWB_COND is also aimed at the
tech-savvy business user. Having ZCL_MYOBJ.GET_ACTIVE_WORKFLOWS in there
is more visible than a check FM in the event linkage.

Cheers,
Mike

On Wed, November 10, 2010 8:42 pm, Berry Martin wrote:
> My issue was solved ... but to be honest, I did not get to try your
> suggestions ... as it was a production issue and I was in a time crunch.
>
> I could not get the start condition activated ... neither through SWDD nor
> through SWU_COND.  Crazy thing is, when in SWDD, looking at the start
> event, I could click on the start condition box/button and it showed the
> conditions.  I could not get anything to work.   So ..... being in a rush
> ....
>
> I deleted the start event of the workflow and transported.
> Then, I add back the start event ... with out the start condition ... and
> transported.
> Then, I add the start condition to the start event and transported.
>
> This seems to have gotten everything back in the proper state ... though I
> really don't know what caused it to be wrong in the first place.
>
> Thank you for your suggestions.  I have filed them away for the next time
> workflow frustrates me!
>
>
>
>
>
> From:   "Sample, Rick" <Rick.Sample at graybar.com>
> To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date:   11/09/2010 08:00 AM
> Subject:        RE: Workflow Start Conditions
> Sent by:        sap-wug-bounces at mit.edu
>
>
>
> Yea, probably why I never used them. Nice reminder though. I guess if I
> ever need to check one simple flag on an object like block record or
> something I would use it. But then again, I didn't see any option "if
> other wf already exists, don't start newâ€¦"
>
> Berry, did this answer your question? You solve your issue?
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Rick Bakker
> Sent: Monday, November 08, 2010 2:50 PM
> To: SAP Workflow Users' Group
> Subject: Re: Workflow Start Conditions
>
> You can't get much simpler than Start Conditions! Click, enter condition,
> save!
>
> By the way, if the Start Condition is inactive you can see it by the
> button being grey instead of green or red in SWDD.
> On Tue, Nov 9, 2010 at 7:29 AM, Sample, Rick <Rick.Sample at graybar.com>
> wrote:
> I never use Start Conditions. After reading last post, I recall looking at
> this many years ago.
> I have used CFM since the beginning. Any advantages to using this over
> simple CFM?
>
>
> From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
> Of Rick Bakker
> Sent: Monday, November 08, 2010 2:06 PM
> To: SAP Workflow Users' Group
> Subject: Re: Workflow Start Conditions
>
> Hi Berry,
>
> What is probably happening is that the Start Condition itself is not
> active. To see this, go to tx SWB_COND and look for your start condition -
> if you created it via SWDD then it will be in there with the workflow's
> number (WS....) attached to it. If it you see a red square then it's not
> active. Happens sometimes. Click on it to make it green.
>
> When you delete it and it still appears to be there - did you do a
> SWU_OBUF?
>
> regards
> Rick Bakker
> hanabi technology
> On Tue, Nov 9, 2010 at 2:38 AM, Sample, Rick <Rick.Sample at graybar.com>
> wrote:
> Hi Berry,
>
> Need more information. Not sure if I completely understand your meanings
> like start condition, clean up, delete, criteria, etc.
> A little vague you see.
>
> Start condition? Meaning check function module? Start events just says, on
> this event, start. No conditions on that screen that I know of anyway.
>
> If you have a WF with something like bus2032.CREATED with no CFM, it will
> start.
> If you have a CFM assigned and whatever you are evaluating does not raise
> WF off, it will start.
>
> What client you dev and testing in? If you develop in say RD0-110 and test
> in 120, you must SCC1 the type linkage to that client.
>
> How are you testing? SWLD and triggering or via an actual event from
> something like a sales order change?
>
> More than happy to help, just need more info.
>
>
> Rick Sample | SAP Workflow Analyst/Developer
> 11885 Lackland Road | Maryland Heights, MO 63146 | Office (314) 573-5822 |
> Mobile (314) 952-2273 | rick.sample at graybar.com
> www.graybar.com - Works to Your Advantage
> Error! Filename not specified.
>
>
>
>
>
>
> From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
> Of Berry Martin
> Sent: Monday, November 08, 2010 9:01 AM
> To: sap-wug at MIT.EDU
> Subject: Workflow Start Conditions
>
> Having some issues with workflow start conditions and need some
> recommendations.
>
> For some reason, the start condition does not appear to be working.  When
> I look at the definition in SWDD->Basic Data ->Start Events, I see the
> condition.  When I open the conditions and test them in the editor, they
> are evaluated properly (meaning it reads the data correctly and gives the
> appropriate response).  When I kick off the event, using data that should
> not pass the start condition, the workflow starts ... almost like it did
> not have a start condition.
>
> The approach I have been trying to take is to delete the start condition
> and start over.  Some that is concerning me is that even though I remove
> the start condition from SWDD->Basic Data ->Start Events, when I click on
> the condition button/box, I still see all the start condition criteria ...
> almost like something is not getting cleaned up when I am deleting.
>
> I know this is a little vague, but any ideas for trouble shooting will be
> welcomed.
>
> Thanks,
>
>
>
>
>
> **** Confidentiality and Commercial Terms and Conditions Notice: *****
> Privileged/Confidential information may be contained in this message
> and is intended only for the use of the addressee. Please advise
> immediately if you or your employer do not consent to Internet e-mail
> for messages of this kind. If you are not the addressee, or person
> responsible for delivering to the person addressed, you may not copy or
> deliver this to anyone else. If you receive this message by mistake,
> please notify the sender immediately by return e-mail. All commercial
> transactions, offers and acceptances are exclusively subject/limited to
> and conditioned upon our terms posted at www.milliken.com/terms,
> and we object to and reject any of your additional/different terms and
> conditions unless we expressly agree to them in a signed writing.
> Thank you.
> ***********************************************************************
>
> _______________________________________________
> 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
>
>
>
>
>
>
>
> **** Confidentiality and Commercial Terms and Conditions Notice: *****
> Privileged/Confidential information may be contained in this message
> and is intended only for the use of the addressee. Please advise
> immediately if you or your employer do not consent to Internet e-mail
> for messages of this kind. If you are not the addressee, or person
> responsible for delivering to the person addressed, you may not copy or
> deliver this to anyone else. If you receive this message by mistake,
> please notify the sender immediately by return e-mail. All commercial
> transactions, offers and acceptances are exclusively subject/limited to
> and conditioned upon our terms posted at www.milliken.com/terms,
> and we object to and reject any of your additional/different terms and
> conditions unless we expressly agree to them in a signed writing.
> Thank you.
> ***********************************************************************
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>