Skip to Content

Work Items don't disappear from My Inbox app, but they disappear when opened from SBWP

Dear Community,

In the activity step of the Workflow, a work item is sent to the responsible agents. When these work items are opened in T-Code: SBWP by double-clicking on these items, the WF resumes the execution of the subsequent steps and the Work item disappears from the SBWP inbox and also from the My Inbox FIORI app.

However, when the same work item is opened from the 'My Inbox' FIORI app using the 'Open Task' button, the work items still remain in the Inbox(both My Inbox Fiori app & SBWP), as a result, the WF execution is not resumed.

Do we need to do any additional configuration? to make the behavior of the 'My Inbox' FIORI app and the T-Code: SBWP consistent in terms of handling the work item.

Following is the SWFVISU configuration :

This work item is just to call a T-Code: IQS23 to view some information and no action is required in this step. When it disappears from the Inbox, it means that this Work Item is complete and the WF execution resumes with the subsequent steps.

Thanks for your time!

Regards,

Karthik

swfvisu.png (12.0 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jul 16, 2020 at 01:12 PM

    Just in case, if it helps someone else.

    In our WF, we have an activity step(not user-decision step) which creates a Work Item(WI) based on certain business logic. This WI requires user interaction to execute this activity, in order for the WF to resume the execution.

    In SBWP, we readily have the 'Execute' button(also double click does the same thing), which will execute this WI and this WI disappears from the INBOX( SBWP & MY Inbox). However, we do not readily have this 'Execute' action button to complete this WF. Therefore, we need to create a new custom button and add the relevant logic to execute the item. Adding the custom button and the relevant business logic/action code for this custom button is clearly explained here: https://www.sap.com/documents/2015/08/ac409c27-5a7c-0010-82c7-eda71af511fa.html. Thanks to the author of this document!

    Though there is 'Open Task' button readily available, however, we wanted to make use of this 'Open Task' to call the T-code and the custom 'Execute' to actually execute the item and resume the WF.There might some better approach to achieve both of these functionalities with 'Open Task' button, but the above implemented solution will fulfill our requirements.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.