Ad Hoc Anchor Steps in ECC 6

[Griffiths, Mark]

Ad Hoc Anchors have been around since the early days of EBP / SRM (about
46D).  They are used extensively in SRM from the ITS end user graphical
process view of the approval to add additional approval steps.  There is
a nice button in SRM for end users to do this.  In ECC the usage is not
quite so obvious as it only works in a fairly clunky manner from the
Graphical Workflow Logs.
 
So, in ECC you are unlikely to come up with a use for it, but it is
pretty good in SRM.
 
Regards,
 
 
Mark
 
SAP UK

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Gambier
Sent: 16 January 2009 14:11
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Ad Hoc Anchor Steps in ECC 6



Hi,

 

Has anyone used the new 'Ad Hoc' Anchor node type in a definition yet?
If so, what's it for?

 

>From the write-up and help text the node seems to cater for the
execution of any number of other Workflow definitions that are supposed
to share the same container definition. Sort of like a list of Sub-WFs I
suppose. But no check seems to be performed to ensure the WFs listed
against the anchor are consistent or syntax check OK. And  no sequencing
or conditions are involved.

 

Presumably since this new Ad Hoc Anchor step is part of the WF
definition it is version controlled so it's not as if you can maitain a
list of WFs to call at this step to affect all running instances of the
WF in any version that supports the Anchor. To achieve that we have
dynamic steps to return WFs on-the-fly.

 

So I'm a bit at a loss to understand why you would use this feature at
all...

 

Regards,

 

Mike GT


________________________________

Are you a PC? Upload your PC story and show the world
<http://clk.atdmt.com/UKM/go/122465942/direct/01/>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090116/e2cfc74d/attachment.htm