Developing Workflow Templates in "namespace"

[Alon Raskin]

Workflow templates can not be in their own namespace (the objects can but not the workflow definitions). I believe you can contact the ICC and work out a number range which can be allocated to your company. Please follow up with your ICC contact for more information (there might even be an SAP note that talks about it) too.

Regards,

Alon Raskin
e: araskin at go3i.com<mailto:araskin at go3i.com>
p: +1 713 513 4820 c: +1 207 409 4983
One App for ALL devices<http://www.themobileworkplace.com>

From: Warren Eiserman <warreneiserman at gmail.com<mailto:warreneiserman at gmail.com>>
Reply-To: WUG <sap-wug at mit.edu<mailto:sap-wug at mit.edu>>
Date: Thursday, January 9, 2014 at 1:41 AM
To: WUG <sap-wug at mit.edu<mailto:sap-wug at mit.edu>>
Subject: Developing Workflow Templates in "namespace"

Hi Workflow Experts,

We are developing an ABAP solution in our own namespace /BLW/ (rather than the "Z" or "Y") and would like to include workflow templates as part of the solution.
These workflows would be shipped to multiple customers.

Obviously we would like to make sure that the "number range" configuration does not clash with "900 - 999" range that customers would typically configure.
Any ideas on the approach to include templates and tasks "safely" in the transport/package?

Thanks in advance,

Warren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140227/e23afce0/attachment.htm