Presentation on Classy Workflows / BOR vs ABAP OO

[Alon Raskin]

Jocelyn,

Just out of curiosity, has there been any changes to the Workflow Builder to allow the declaration of interface container elements?. This would be a really powerful feature and would allow the use of polymorphism in Workflow.

Regards,

Alon Raskin
e: araskin at 3i-consulting.com
p: +1 207 523 3489
c: +1 207 409 4983
f:  +1 806 403-4983

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Dart, Jocelyn
Sent: Thursday, June 21, 2007 1:44 AM
To: SAP Workflow Users' Group
Subject: Presentation on Classy Workflows / BOR vs ABAP OO

Actually Mike, I think if you show ABAP OO using both the ABAP OO pattern builder, and the latest ABAP OO editor which has that Java-like instant help with putting together your ABAP statements, that would go a long way to helping folk such as Sherie to make the transition from BOR to ABAP OO. 

The creation of attributes and methods is really no harder - as you needed to specify instance/static, dictionary types, parameters and exceptions even in BOR, and as any workflow specific settings such as the "synchronous" flag are now on the task or are no longer relevant (such as "dialog"). 

Also Sherie I would recommend you try the SDN blogs yourself as they do show you all the critical code which gives you the patterns you need to create your own classes. 

I'm hoping to finish the final blog on linking BOR to ABAP OO very soon. Just having some access problems from this site. 

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. 
Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.
Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
Sent: Thursday, 14 June 2007 9:33 PM
To: SAP Workflow Users' Group
Subject: Re: Workflow development standards

Hi,
This can vary quite wildly by company. I would start with your ABAP dev
standards and follow the general theme.

I usually end up with a "Development Standards" doc that incorporates WF.
Some of my favoured naming conventions:

Workflows: Z<module>_name - e.g. ZMM_POAppr, ZFI_InvAppr, ZHR_LeavReq
Bus Objects: Z<original object> for subtypes
  --> Components (attr, methods): zNameWithProperCase
Classes: ZCL_WF_<description>

Hope that helps for a start, maybe people can chip in....
Mike

On Wed, June 13, 2007 9:31 pm, Michelle Van Patten wrote:
> Good afternoon,
>
> Does anyone have development standards for workflow they could share?  I
> have been tasked with creating them for our company.
>
> Thanks,
> Michelle
>
>
> NOTICE: This e-mail message and any attachments are confidential and
> intended solely for use of the intended recipient. If you are not the
> intended recipient, you should not review, retransmit, convert to hard
> copy, copy, use or disseminate this e-mail or any attachments to it. If
> you have received this e-mail in error, please immediately notify us by
> return e-mail and delete this message and any attachments from your
> computer system.  Please note that if this e-mail message contains a
> forwarded message or is a reply to a prior message, some or all of the
> contents of this message or any attachments may not have been produced by
> the sender. This notice is automatically appended to each e-mail message
> leaving the sender’s e-mail domain. Thank you.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


-- 
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855

_______________________________________________
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