- Do stick to naming conventions for workflow objects, especially the task abbreviation, method names and event names should be preceded by a
YorZ, even if SAP allows other - Don't use an existing event as your new trigger point, you risk triggering other workflows when they shouldn't
- Do reuse existing events if the triggering is the same as the existing event
- Don't build too much code in methods, keep it short and sweet, call a function module to do the work from your method instead
- Do make sure method parameters are filled in on the Business Object, it's possible to fetch any information from the container and placing anything on the container as well without specifying method parameters, but this is considered bad practice ! Maintaining method parameters makes usage of your methods in tasks a lot easier, as container contents can be defaulted by the system.
- Don't create unecessary activities in your workflow to gather information, every task is a process that consumes processing time. Use a single task to gather all you need or make good use of the Business Objects attributes (which are filled in when the business object is created) - performance !
- Do check the event log in a development system: find the events that do not have receivers and deactivate them, no receivers = no reason for the event to be created. !
- Don't drown in bigger flows: print them ! (print button on
SWO1)
Note: Version Management and e.g. the Code Inspector on Business Objects are available, all-be-it a bit hidden away: try SE38 with the main program name of your Business Object...