<div dir="ltr">Hi Rick,<div><br></div><div>Have a better idea of what you are looking for.</div><div>I am not aware of a standard WD4A solution like this, the EHSM uses PCBO (Process Control Business Objects) which are part of the BOPF framework, so suspect there are some (IF_WORKFLOW) classes that have this implemented.</div><div>Don't think it would be a simple exercise to decouple these for a generic solution. i.e. the results of the actions are persisted in the BOPF layer so likely they may be reading from there. More info <a href="https://help.sap.com/saphelp_ehsext10/helpdata/en/b4/07cb5f7c7c402a93744fda1bbad88d/content.htm">here</a></div><div><br></div><div>I have seem some generic WD4A around the SAP ISR (Internal Service Request), but don't think this would help you.</div><div>It might also be worthwhile looking at a WD4A CHIP solution for your requirements, where you map the work item # as an inbound parameter? Here is a good <a href="http://scn.sap.com/community/web-dynpro-abap/blog/2011/10/09/chips-pagebuilder-and-the-side-panel--part-1">blog</a> about CHIPS (but not specific for your scenario).</div><div><br></div><div>Regards, Warren</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 2 March 2015 at 14:44, Rick Bakker <span dir="ltr"><<a href="mailto:rbakker@gmail.com" target="_blank">rbakker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Warren,</div><div><br></div><div>Thank you for that. If I understand correctly, this is more for replacing standard EHSM</div><div>TS* tasks with custom TS* tasks. Very handy, but what I'm interested in is defining a TS</div><div>task somewhere such that a Webdynpro appears that reads the details of that TS task - independent</div><div>of EHSM - and presents it as a Webdynpro. Some sort of default, out-of-the-box Webdynpro. </div><div><br></div><div>I could be assuming way too much here.</div><div><br></div><div>(Note: I say "TS task" because EHSM has its own meaning for the word "task")</div><div><br></div><div>regards</div><span class="HOEnZb"><font color="#888888"><div>Rick</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 2, 2015 at 5:32 PM, Warren Eiserman <span dir="ltr"><<a href="mailto:warreneiserman@gmail.com" target="_blank">warreneiserman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Rick,<div><br></div><div>EHSM uses the BOPF (Business Object Processing Framework) for workflow handling and "shows" work items within a POWL list.</div><div>It is possible to add additional tasks into the EHSM inbox (POWL), this requires some undertaking some workflow inbox configuration in the IMG using the following inbox type: </div><div><br></div><div><img src="cid:ii_14bd965f6f2793e0" alt="Inline images 1" width="562" height="164"><br></div><div><br></div><div>Here is a document which provides some additional details: <a href="https://www.dropbox.com/s/5thst7pfkxs4ai8/Workflow%20Development%20011000358700001444412011E.pdf?dl=0" target="_blank">https://www.dropbox.com/s/5thst7pfkxs4ai8/Workflow%20Development%20011000358700001444412011E.pdf?dl=0</a> </div><div><br></div><div>Regards, </div><div>Warren</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On 2 March 2015 at 08:48, Rick Bakker <span dir="ltr"><<a href="mailto:rbakker@gmail.com" target="_blank">rbakker@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div style="font-size:12.8000001907349px">Hello WUGgers,</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">I'm working on an EHSM (Health & Safety) system. When I get sent an Action workitem TS00500027 and I click on it in my UWL, it comes up with a nice Webdynpro screen that has the text of the workitem (as seen in SWI1) along with the Approve and Reject buttons and the outcome texts. It even has a box for comments.</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">My question is: how is this done? I can't see the task in SWFVISU. I believe you can avoid using SWFVISU and generate the XML manually but then again it would seem very handy to have a routine that could do this for *any* Decision task and I suspect that this is the case here. The question then becomes: where is "TS00500027" listed?</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">The reason I ask is because I want to do the same with a custom task in a custom workflow. Hopefully it's as easy as adding TS901000xx to an existing list somewhere.</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">regards and thanks!</div><span><font color="#888888"><div style="font-size:12.8000001907349px">Rick Bakker</div></font></span></div>
<br></div></div>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br></div>