Before you develop a business process, consider its design, including the overall flow of the business process, and types of services that must be included in the business process.
The tasks required to build a business process can be done at different times during the design process. For example, you may want to identify and define services before you begin modeling your process. You may also want to create data transformation maps that you anticipate using in the process model.
Conversely, you could lay out the high-level business logic using the Service editor and later add services and create maps. Placeholder activities can be created and defined later in the design phase. For example, one user could create a complex activity container as a placeholder in the process. This complex activity could contain resources that need properties, correlation sets, or a monitor service defined. A second, probably more technical user, can later define the required resources. After the business process design is complete and tested, it is packaged and is then available for configuration and deployment to the runtime instance.
Support for the simple type datatype does provide a convenient method to assign operation parameters when developing a message service, however, during runtime a synthetic schema element is generated. Consider how the message output by the message service is consumed and what requirements the message must meet in determining whether to use simple type.
Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com
Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.