Re: SWI1_COND for work item Start/End Conditions or Agent Determination/Rules?

Wed Oct 5 10:05:20 EDT 2011

Hi,
You can check condition of a workitem by using Tcode SWI1_COND.
Thanks and regards,
SNJY

On Wed, 05 Oct 2011 19:22:02 +0530  wrote
>Please what is the Function and Usage of workflow administration

transaction SWI1_COND?

Does this transaction:

(a) re-evaluate the conditions for work item start and work item end like

background job SWWCOND, and/or

(b) re-evaluate agent determination/rules for work item delivery like

transaction SWI1_RULE.

The documentation on transaction SWI1_COND is confusing:

Title: Check Conditions for Work Items

Description: You can use this function to repeat definition of the

recipients for a work item. A rule entered for the determination is also

re-executed.

Thank you very much.

SHELDON OXENBERG

System Architect Principal Leader

LMP Technical Architect, SAP Workflow

CSC

 From:    Sheldon Oxenberg/USA/CSC at CSC                                     

 To:     "SAP Workflow Users' Group"                              

 Date:    10/03/2011 01:49 PM                                          

 Subject:  RE: Strange Behavior of Decision Work Item                              

Sue,

Another thought if it works in DEV but not QAS or PRD would be the

transports.

Maybe you should do a thorough review and synchronization check between DEV

and QAS to be sure that every object was transported properly, check the

details of the transport logs and return codes, make sure that all objects

were generated and activated, make sure that you transported every workflow

and non-workflow object that is needed for this workflow and non-workflow

functionality, rebundle and retransport the objects, maybe there are SAP

Notes that were applied in DEV but not yet moved to QAS/PRD?

Thank you.

SHELDON OXENBERG

System Architect Principal Leader

LMP Technical Architect, SAP Workflow

CSC

 From:    Sue Doughty 

 To:     "'SAP Workflow Users' Group'" 

 Date:    10/03/2011 01:18 PM

 Subject:  RE: Strange Behavior of Decision Work Item

Sheldon,

Thank you for your response. I am really struggling with this one!!

Yes, decision, then dialog with synchronous method then loop back to

decision task.

I thought about the adjusting of the workflow settings, but what confuses

me greatly is that it works in DEV, but not QAS or PRD, so I did not think

the workflow settings would be an issue.

I will look at the specific transaction behavior, but when I execute the

transaction outside of the workflow it does not seem to have any issues.

I have opened an OSS note with SAP....I just don't know what else to look

at.

Regards,

Sue Doughty

-----Original Message-----

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of

Sheldon Oxenberg

Sent: Monday, October 03, 2011 10:10 AM

To: SAP Workflow Users' Group

Subject: RE: Strange Behavior of Decision Work Item

Hi Sue,

Does your workflow have a decision task, then a dialog task with a

synchronous method, then a loop back to the decision task?

The behaviour sounds like it might be related to Advance with dialog,

Confirm end of processing, or Method Synchronous/Asynchronous settings.

Maybe you could try adjusting these settings in your workflow and see what

happens?

If it works in DEV but not QAS or PRD, it could be related to the specific

transaction behaviour and the system being open for change or not.

Maybe you could try changing the workflow to replace the transaction with a

simple display dialog task and see what happens?

Regards.

SHELDON OXENBERG

System Architect Principal Leader

LMP Technical Architect, SAP Workflow

CSC

 From:    Sue Doughty 

 To:     "'SAP Workflow Users' Group'" 

 Date:    10/03/2011 08:41 AM

 Subject:  RE: Strange Behavior of Decision Work Item

Hi Rick,

I'm sorry.....If she makes a change, it comes back to the front screen with

the message at the bottom.

(Embedded image moved to file: pic05097.jpg)

Regards,

Sue

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of

Rick Bakker

Sent: Monday, October 03, 2011 8:28 AM

To: SAP Workflow Users' Group

Subject: Re: Strange Behavior of Decision Work Item

Hi Sue,

It doesn't ask if she wants to save her changes? (if she makes a change

and backs out of the transaction wholly outside of workflow)

regards

Rick Bakker

hanabi technology

On Mon, Oct 3, 2011 at 11:19 PM, Sue Doughty  wrote:

Hi Rick,

Thank you for your response.

When the user goes into the transaction itself

(Embedded image moved to file: pic16512.jpg)

(Embedded image moved to file: pic23986.jpg)

And then backs out (like she does from the workflow), it goes back to the

screen that brought her into the transaction.

(Embedded image moved to file: pic13290.jpg)

Regards,

Sue

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of

Rick Bakker

Sent: Monday, October 03, 2011 8:01 AM

To: SAP Workflow Users' Group

Subject: Re: Strange Behavior of Decision Work Item

Hi Sue,

What if that same user in QAS or PRD goes into that transaction (not via

worklow) makes a change and then does Back?

regards

Rick Bakker

hanabi technology

On Mon, Oct 3, 2011 at 10:45 PM, Sue Doughty  wrote:

We are in ECC 6.0, EHP4. Any help would be greatly appreciated.

I have a very simple custom workflow. It loops until the user clicks the

Complete Workflow button.

(Embedded image moved to file: pic09161.jpg)

The first button takes the user into change mode of the custom transaction.

(Embedded image moved to file: pic18636.jpg)

When clicking the Green Arrow back in QAS or PRD, it returns to a blank

screen. In DEV, it takes the user back to the first screenshot above,

which is what should happen. Then the user can Complete the Workflow or go

back into the transaction.

(Embedded image moved to file: pic22355.jpg)

Like I said, in DEV, the workflow works perfectly, but in QAS and PRD, the

blank screen appears. The user then has to go out of the workflow in-box

and back in before executing it again to get the decision steps again.

Sometimes there is a pop-up window that appears when exiting the

transaction saying that the data has changed and asking if the user wants

to save the changes. The pop-up will display in DEV, but not in QAS or

PRD. In QAS and PRD, it goes to the blank Decision screen.

(Embedded image moved to file: pic24767.jpg)

We have created a test user in DEV that has the user's security that is in

QAS. So, the security is the same in all three systems.

I feel like it must have something to do with the pop-up screen, but don't

know why that would display in DEV, but not QAS or PRD.

Regards,

Sue Doughty

SAP Workflow Specialist

_______________________________________________

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

_______________________________________________

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20111005/8bde65b2/attachment.htm