SAP Workflow Improvements (courtesy of SAP Customer Connection) – Part 3
Continuing on about the SAP Customer Connection for Workflow...In case you are just tuning in, I am running through the list of SAP Workflow improvements that have been delivered as a result of this Customer Connection.
Okay, so I really didn’t intend for this to become a multi-blog series, so I hope you don’t mind that I broke this up into manageable chunks… Honestly, there have been so many improvements delivered, and I wanted to be able to do each justice (without losing the blogs to the fickle gods of bloggers)…
ALL IMAGES ARE COURTESY OF SAP and property of SAP unless otherwise noted.
Note 2191614 – The specification of Workflow Administrator allows you to specify User, Role, Org Unit, Center, Position and Work Center. In some cases, this is not really sufficient for the variety of customers out there (OK, I am one of them). Now, if you implement this note, you will be allowed to specify an Agent Rule. Sadly, no binding to the rule can be defined *but* the workflow container is passed at run time via the table parameter AC_Container. So you will now have the flexibility to determine programmatically who the appropriate workflow administrator is.
For large SAP installations, I can see a huge benefit to implementing this.
Note 2188631 This is one I really wanted… it doesn’t have such an impact on workflows running in core ECC, but I do a significant portion of my development in SRM, and it always frustrated me when I could not forward an item to myself (in order to execute through the UWL, for example). That restriction is now addressed.
Note 2202595 – This note will allow you to use a new option when sending workflow notificati9ons through SWNADMIN or SWNCONFIG (Extended Notifications). Previously, you were restricted to Internet Mail, SMS or Pager (I bet Pager gets a lot of use these days 😉 ) or an Internal SAP User – which is fine, as long as you only wants to send to a single user. With the implementation of this note, your notifications can go out to all SAP users identified by a specific ‘User Group’ (as seen on the SU01 record, not ASUG or VNSG or DSAG).
Note 2201971 – I know for a fact that doing a where-used list for workflow development objects can be frustrating. Say you are looking for the workflows that use a particular task… well, you get ALL the workflows – every single version of a workflow – if it calls that task, you get it. SAP really listened when they took on this Customer Connection Request – this is an item that causes the back office workflow developer some pain – but of course we hide it very well. Anyway, with this note implemented, you’ll now be able to see the Version Number and whether an ACTIVE version of a workflow uses that task.
Note 2254783 – While we are on the subject of versions… Workflow developers always could see the versions of BOR objects – but only if they used SE38, and even then it would only show source code changes. When you implement this note, you’ll be able to see the difference of things like attributes! W00t!
I think I have covered all the requests that have already been delivered by this Customer Connection activity. But I urge you to go to the Influence to see what other influence projects are out there, as well as to keep tabs on this activity. Hopefully you will also check out some of these notes and get your friendly Basis team to implement them – and then provide feedback!
Meanwhile, thanks to Ronen Weisz who worked hard to get this influence activity going, to Daniel-Alexander Heller who led the activity, and of course, the people at SAP who tirelessly support the developers and administrators of SAP Workflow by making our day-to-day lives a little easier. (This means you Alan Rickayzen and you Ralf Goetzinger)