CWWBV

Edit online

CWWBV0001I
Validated process model ''0'' successfully: 1 warnings, 2 information.
CWWBV0002E
Validated process model ''0'' with findings: 1 errors, 2 warnings, 3 information.
CWWBV0003E
Validated process model ''0'' with findings: 1 errors, 2 warnings, 3 information: 4
CWWBV0004E
A syntactical error was found (row: 0, column: 1): 2
CWWBV0005W
A syntactical warning was found (row: 0, column: 1): 2
CWWBV0006E
The BPEL resource cannot be loaded.
CWWBV0007E
The file could not be read. Detail message: ''0''.
CWWBV0050E
BPEL validation error: 0.
CWWBV0051W
BPEL validation warning: 0.
CWWBV0052I
BPEL validation information: 0.
CWWBV0101E
The process element must contain an activity.
CWWBV0102E
The catch element must contain an activity (process fault handler, catch element number 0).
CWWBV0103E
The catchAll element must contain an activity (process fault handler).
CWWBV0104E
The onEvent event must contain an activity (process event handler, onEvent event number 0).
CWWBV0105E
The onAlarm event must contain an activity (process event handler, onAlarm event 0).
CWWBV0106E
The partnerLinkType must be set (process partnerLink ''0'').
CWWBV0107E
The partnerLink attribute for onEvent event number 0 is missing.
CWWBV0108E
The operation attribute must be set (process event handler, onEvent event number 0).
CWWBV0109E
The parameter variable must be set (process event handler, input/output element of onEvent event number 0, parameter number 1, parameter name ''2'').
CWWBV0110E
The correlation set must refer to at least one property (correlation set ''0'').
CWWBV0111E
The name attribute must be set (process adminTask or activityAdminTask element).
CWWBV0112E
The name attribute must be set (process event handler, onEvent event number 0, task element).
CWWBV0113E
The duration attribute on the timeout element must be set (process onAlarm event 0).
CWWBV0114E
The correlation ''set'' attribute must be set (process event handler, onEvent event number 0, correlation element number 1).
CWWBV0200E
The catch element must contain an activity (fault handler of activity ''0'', catch element number 1).
CWWBV0201E
The catchAll element must contain an activity (fault handler of activity ''0'').
CWWBV0202E
The compensation handler must contain an activity (compensation handler of activity ''0'').
CWWBV0203E
The partnerLink attribute must be set (activity ''0'').
CWWBV0204E
The operation for the ''0'' activity is missing.
CWWBV0205E
The duration attribute of the timeout element must be set (activity ''0'').
CWWBV0206E
The parameter variable must be set (input/output element of activity ''0'', parameter number 1, parameter name ''2'').
CWWBV0207E
The name attribute must be set (activity ''0'', adminTask element).
CWWBV0208E
The name attribute must be set (activity ''0'', task element).
CWWBV0209E
The correlation ''set'' attribute must be set (activity ''0'', correlation element number 1).
CWWBV0210E
An exception occurred when using the XML Path Language (XPath) plug-in for the 0 XPAth expression on the 1 activity (exception 2).
CWWBV0211E
The toVariable or fromVariable attribute in the fromPart or toPart element must be set (0 activity, fromPart or toPart number 1).
CWWBV0212E
The part attribute in the fromPart or toPart element must be set (0 activity, fromPart or toPart number 1).
CWWBV0300E
The assign activity must contain a copy element (assign activity ''0'').
CWWBV0301E
The copy element must contain a from-element (assign activity ''0'', copy element number 1).
CWWBV0302E
The copy element must contain a to-element (assign activity ''0'', copy element number 1).
CWWBV0303E
The reference-scheme attribute must be set (assign activity ''0'', copy element number 1, from-spec, serviceRef element).
CWWBV0304E
The serviceRef element cannot be empty (assign activity ''0'', copy element number 1, from-spec, serviceRef element).
CWWBV0400E
The target attribute must be set (0 compensateScope activity).
CWWBV0600E
The ''0'' Flow activity does not contain an activity.
CWWBV0650E
The generalized flow activity must contain an activity. Add an activity to it (generalized flow activity ''0'').
CWWBV0700E
The partnerLink attribute of the undo action must be set (invoke activity ''0'').
CWWBV0701E
The operation attribute of the undo action must be set (invoke activity ''0'').
CWWBV0702E
The parameter variable for the undo action must be set (input/output element of invoke activity ''0'', parameter number 1, parameter name ''2'').
CWWBV0800E
The pick activity must contain an onMessage element (pick activity ''0'').
CWWBV0801E
The onMessage element, number 1, in pick activity ''0'' is missing an activity.
CWWBV0802E
The onAlarm event must contain an activity (pick activity ''0'', onAlarm event 1).
CWWBV0803E
The partnerLink attribute for OnMessage element number 1 in pick activity ''0'' is missing.
CWWBV0804E
The operation attribute for OnMessage element number 1 in pick activity ''0'' is missing.
CWWBV0805E
The parameter variable must be set (pick activity ''0'', input/output element of onMessage element number 1, parameter number 2, parameter name ''3'').
CWWBV0806E
The name attribute must be set (pick activity ''0'', onMessage element number 1, task element).
CWWBV0807E
The duration attribute on the timeout element must be set (pick activity ''0'', onAlarm event 1).
CWWBV0808E
The correlation ''set'' attribute must be set (pick activity ''0'', onMessage element number 1, correlation element number 2).
CWWBV1200E
The ''0'' scope activity must contain an activity.
CWWBV1201E
The onEvent event must contain an activity (event handler of scope activity ''0'', onEvent event number 1).
CWWBV1202E
The onAlarm event must contain an activity (event handler of scope activity ''0'', onAlarm event 1).
CWWBV1203E
The partnerLink attribute must be set (scope activity ''0'', onEvent event number 1).
CWWBV1204E
The operation attribute must be set (scope activity ''0'', onEvent event number 1).
CWWBV1205E
The parameter variable must be set (scope activity ''0'', input/output element of onEvent event number 1, parameter number 2, parameter name ''3'').
CWWBV1206E
The name attribute must be set (scope activity ''0'', onEvent event 1, task element).
CWWBV1207E
The duration attribute on the timeout element must be set (scope activity ''0'', onAlarm event 1).
CWWBV1208E
The correlation ''set'' attribute must be set (scope event handler, of scope activity ''0'', onEvent event number 1, correlation element number 2).
CWWBV1300E
The sequence activity must contain an activity (sequence activity ''0'').
CWWBV1400E
The switch activity must contain a case element (switch activity ''0'').
CWWBV1401E
Case element number 1 in Switch activity ''0'' does not specify a condition.
CWWBV1402E
Case element number 1 in Switch activity ''0'' does not contain an activity.
CWWBV1403E
The otherwise element must contain an activity (switch activity ''0'').
CWWBV1500E
The throw activity requires a faultName attribute (throw activity ''0'').
CWWBV1700E
The ''0'' While activity does not specify a condition.
CWWBV1701E
The ''0'' While activity does not contain an activity.
CWWBV1950E
The forEach activity requires a counterName attribute (forEach activity ''0'').
CWWBV1951E
The forEach activity must contain a startCounterValue element (forEach activity ''0'').
CWWBV1952E
The forEach activity must contain a finalCounterValue element (forEach activity ''0'').
CWWBV1953E
The forEach activity must contain a scope activity (forEach activity ''0'').
CWWBV2000E
The 0 RepeatUntil activity does not specify a condition.
CWWBV2001E
The 0 RepeatUntil activity does not contain an activity.
CWWBV3000E
The schemaLocation attribute is not set. It must be one of ''0''.
CWWBV3001E
The value of the schemaLocation attribute is incorrect. It must be set to one of ''0'', or a value handled by a custom activity plug-in.
CWWBV3002E
The partnerLinkType ''0'' was not found (process partnerLink ''1'').
CWWBV3003E
The myRole role ''0'' was not found (process partnerLink ''1'', partnerLinkType ''2'').
CWWBV3004E
The portType in the role ''0'' is not set (process partnerLink ''1'', partnerLinkType ''2'').
CWWBV3005E
The portType ''0'' was not found (process partnerLink ''1'', partnerLinkType ''2'', role ''3'').
CWWBV3006E
The partnerRole role ''0'' was not found (process partnerLink ''1'', partnerLinkType ''2'').
CWWBV3007E
Either the myRole role, the partnerRole role, or both must be defined (process partnerLink ''0'').
CWWBV3008E
There are too many variable type definitions set for the process variable ''0'' (messageType ''1'', type ''2'', element ''3'').
CWWBV3009E
The process variable ''0'' must have a variable type definition.
CWWBV3010E
The messageType ''0'' was not found (process variable ''1'').
CWWBV3011E
The XSD type definition ''0'' was not found (process variable ''1'').
CWWBV3012E
The XSD element declaration ''0'' was not found (process variable ''1'').
CWWBV3013E
The process variable name ''0'' is used already.
CWWBV3014E
The catch element must have a fault name, a fault variable with a type specification, or both of these attributes set (process fault handler, catch element number 0).
CWWBV3015E
If the catch element has the fault variable set, it must also have a type specification set (process fault handler, catch element number 0, fault variable ''1'').
CWWBV3016E
The catch element cannot have the fault message type and the fault type set (process fault handler, catch element number 0, fault message type ''1'', faultType ''2'').
CWWBV3017E
If the catch element has the fault message type set, it must also have a fault variable set (process fault handler, catch element number 0, fault message type ''1'').
CWWBV3018E
If the catch element has the fault type set, it must also have a fault variable set (process fault handler, catch element number 0, fault type ''1'').
CWWBV3019E
The messageType ''0'' was not found (process fault handler, catch element number 1, fault variable ''2'').
CWWBV3020E
The type ''0'' was not found (process fault handler, catch element number 1, fault variable ''2'').
CWWBV3021E
The process fault handler must contain a catch element or a catchAll element.
CWWBV3023E
The display ID ''0'' is not unique.
CWWBV3024W
The microflow specifies the autonomy attribute. The attribute will be ignored.
CWWBV3025W
The macroflow specifies the compensationSphere attribute. The attribute will be ignored.
CWWBV3026E
The process event handler must contain an onEvent event or an onAlarm event.
CWWBV3027E
The partnerLink ''0'' was not found (process onEvent event 1).
CWWBV3028E
The partnerLink ''0'' does not define the myRole role (process onEvent event number 1).
CWWBV3029E
The portType ''0'' was not found (process onEvent event 1).
CWWBV3030E
The portType referenced in process onEvent event number 0 and in the myRole role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV3031E
The operation ''0'' was not found (process onEvent event 1).
CWWBV3032E
The input element is not defined in the operation ''0'' (process onEvent event number 1).
CWWBV3033E
The messageType is not set in the input element of the operation ''0'' (process onEvent event number 1).
CWWBV3034E
The messageType ''0'' referenced in the operation ''1'' was not found (process onEvent event number 2).
CWWBV3035E
The messageType of variable ''0'' and the input element of the operation ''1'' must be the same (process onEvent event number 2).
CWWBV3036E
The variable is not set (process onEvent event number 0).
CWWBV3037E
The messageType or element attribute is not set (process onEvent event number 0).
CWWBV3038E
The messageType ''0'' was not found (process onEvent event 1).
CWWBV3039E
The correlation set ''0'' was not found (process onEvent event 1).
CWWBV3040E
The process onAlarm event must specify at least a for expression, an until expression, or a repeatEvery expression (process onAlarm event 0).
CWWBV3041E
The process onAlarm event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (process onAlarm event 0).
CWWBV3042E
The process onAlarm event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (process onAlarm event 0).
CWWBV3043E
The expression language ''0'' is not supported. It must be one of ''1'' (process onAlarm event 2).
CWWBV3044E
The process query language ''0'' is not supported. It must be one of ''1''.
CWWBV3045E
The process expression language ''0'' is not supported. It must be one of ''1''.
CWWBV3046E
The property ''0'' was not found (process correlation set ''1'').
CWWBV3047E
The type of the property ''0'' is not set (process correlation set ''1'').
CWWBV3048E
The type ''0'' of the property ''1'' was not found or is not an allowed or valid XML schema simple type in this context (process correlation set ''2'').
CWWBV3049I
The correlation set ''0'' is not used.
CWWBV3050E
The correlation set ''0'' is used, but it is never initiated.
CWWBV3051E
A task activity cannot be used in a microflow (non-interruptible process) (task ''0'').
CWWBV3052E
A wait activity cannot be used in a microflow (non-interruptible process) (wait activity ''0'').
CWWBV3053E
An onAlarm event in a pick activity cannot be used in a microflow (non-interruptible process). The pick activity name is ''0''.
CWWBV3054E
A process that is not long-running must not contain more than one pick or receive activity: ''0''.
CWWBV3055E
The process does not implement the operation ''0'' of the port type ''1''.
CWWBV3056E
The process is not startable. No pick or receive activity was found that creates a new process instance and does not have incoming links or preceding basic activities.
CWWBV3057E
The variable must not be set because an output element is available (process onEvent event number 0, variable ''1'').
CWWBV3058E
Abstract processes are not supported.
CWWBV3059E
The parameter-extension cannot be used for the message ''0''. Modify the message or use a message-type variable (process onEvent event number 1).
CWWBV3060E
The parameter ''0'' is not mapped to an element or part. Map it to a valid element or part (process onEvent event number 1, parameter number 2).
CWWBV3061E
The variable name ''0'' is used already in the same onEvent event. Use another variable name (output element of process onEvent event number 1, parameter number 2).
CWWBV3062E
A matching propertyAlias definition was not found for the property ''0'' and the messageType ''1'' (process onEvent event number 2, correlation set ''3'').
CWWBV3063E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (process onEvent event number 3, correlation set ''4'').
CWWBV3064E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' does not reference a valid XML schema simple type (process onEvent event number 3, correlation set ''4'').
CWWBV3065E
The type of the part ''0'' of the messageType ''1'' and the type of the property ''2'' are not the same (process onEvent event number 3, correlation set ''4'').
CWWBV3066E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (process onEvent event number 2, correlation set ''3'').
CWWBV3067E
The human task ''0'' cannot be found (process adminTask or activityAdminTask element).
CWWBV3068E
The human task ''0'' is not an administration task (process adminTask or activityAdminTask element).
CWWBV3069E
The human task ''0'' cannot be found (process onEvent event number 1).
CWWBV3070E
The human task ''0'' is not an invocation task (process onEvent event number 1).
CWWBV3071E
The portType referenced in process onEvent event number 0 and in the human task ''1'' must be the same.
CWWBV3072E
The operation referenced in process onEvent event number 0 and in the human task ''1'' must be the same.
CWWBV3073E
The part is not set in the propertyAlias for the property ''0'' and the messageType ''1'' (process onEvent event number 2, correlation set ''3'').
CWWBV3074E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (process onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3075E
The expression is not valid (process onAlarm event 0, expression language ''1'').
CWWBV3076E
A reply activity was not found that matches process onEvent event number 0.
CWWBV3077E
An event handler cannot be used in a microflow (non-interruptible process).
CWWBV3078E
An event handler cannot be used in a microflow (non-interruptible process). The scope activity name is ''0''.
CWWBV3079E
A compensation handler cannot be used in a microflow (non-interruptible process). The activity name is ''0''.
CWWBV3080E
An expiration element cannot be used in a microflow (non-interruptible process). The activity name is ''0''.
CWWBV3081E
A compensate activity cannot be used in a microflow (non-interruptible process). The compensate activity name is ''0''.
CWWBV3082W
The one-way process cannot specify the autonomy 'child'. The attribute will be ignored.
CWWBV3083E
More than one variable type definition is set for the variable ''0''. Set only one (process onEvent event number 1, parameter number 2, type ''3'', element ''4'').
CWWBV3084E
The XSD element declaration ''0'' was not found (process onEvent event number 1, parameter number 2, variable ''3'').
CWWBV3085E
The XSD type definition ''0'' was not found (process onEvent event number 1, parameter number 2, variable ''3'').
CWWBV3086E
The variable ''0'' must have a variable type definition (process onEvent event number 1, parameter number 2).
CWWBV3087E
The XSD type definition ''0'' was not found (process onEvent event number 1, parameter number 2, matching part or element ''3'').
CWWBV3088E
The XSD element declaration ''0'' was not found (process onEvent event number 1, parameter number 2, matching part or element ''3'').
CWWBV3089E
The element ''0'' cannot be assigned to variable ''1'' because the data type does not match (process onEvent event number 2, parameter number 3).
CWWBV3090E
The part ''0'' cannot be assigned to variable ''1'' because the data type does not match (process onEvent event number 2, parameter number 3).
CWWBV3091E
The XSD element ''0'' must be mapped to a parameter (process onEvent event number 1).
CWWBV3092E
The message-part ''0'' must be mapped to a parameter (process onEvent event number 1).
CWWBV3093E
The process partnerLink name ''0'' is used already. Use a unique name.
CWWBV3094E
The process correlation set name ''0'' is used already. Use a unique name.
CWWBV3095E
The correlation set ''0'' is used already. It can only be used once (process onEvent event number 1).
CWWBV3096E
The process custom property name ''0'' has been used already. Provide a unique name.
CWWBV3097E
Process onEvent event number 0 implements operation ''1'' of portType ''2'', which is already implemented in another process onEvent event.
CWWBV3098E
Process onEvent event number 0 must use at least one correlation set.
CWWBV3099E
The referenced property ''0'' was not found (process variable ''1'', queryProperty element number 2).
CWWBV3100E
The variable ''0'' is not defined (activity ''1'').
CWWBV3101E
The catch element does not specify a fault name, a fault variable with a type specification, or both (fault handler of activity ''0'', catch element number 1).
CWWBV3102E
If the catch element has the fault variable set, it must also have a type specification set (fault handler of activity ''0'', catch element number 1, fault variable ''2'').
CWWBV3103E
The catch element cannot have the fault message type and the fault type set (fault handler of activity ''0'', catch element number 1, fault message type ''2'', faultType ''3'').
CWWBV3104E
If the catch element has the fault message type set, it must also have a fault variable set (fault handler of activity ''0'', catch element number 1, fault message type ''2'').
CWWBV3105E
If the catch element has the fault type set, it must also have a fault variable set (fault handler of activity ''0'', catch element number 1, fault type ''2'').
CWWBV3106E
The messageType ''0'' was not found (fault handler of activity ''1'', catch element number 2, fault variable ''3'').
CWWBV3107E
The type ''0'' was not found (fault handler of activity ''1'', catch element number 2, fault variable ''3'').
CWWBV3108E
The fault handler must contain a catch element or a catchAll element (fault handler of activity ''0'').
CWWBV3109E
The correlations element is not allowed (activity ''0'').
CWWBV3110E
Fault handlers are not allowed (activity ''0'').
CWWBV3111E
The expiration, script, and undo elements cannot be used in the activity ''0''. These elements are only allowed in invoke activities.
CWWBV3112E
The custom activity element ''0'' cannot be used in the activity ''1''. This element is only allowed in invoke activities.
CWWBV3113E
The task element cannot be used in the activity ''0''.
CWWBV3114E
The annotation element cannot be used in the activity ''0''. This element is only allowed in scope activities.
CWWBV3115E
The timeout element cannot be used in the activity ''0''. This element is only allowed in wait activities.
CWWBV3116E
The input element cannot be used in the activity ''0''. This element is only allowed in invoke and reply activities.
CWWBV3117E
The output element cannot be used in the activity ''0''. This element is only allowed in invoke and receive activities.
CWWBV3118E
The continueOnError attribute cannot be used in the ''0'' activity. It is allowed only in invoke activities.
CWWBV3120E
The compensable attribute cannot be used in the activity ''0''. This attribute is only allowed in scope activities.
CWWBV3121E
The script, task, and custom activity elements are mutually exclusive (invoke activity ''0'').
CWWBV3122E
The link ''0'' is not defined (referenced in the activity ''1'').
CWWBV3123E
The link ''0'' is parallel link-to-link ''1'' (from activity ''2'' to activity ''3''). Parallel links are not allowed.
CWWBV3124E
The XSD-typed variable cannot be used here (activity ''0'', variable ''1'').
CWWBV3125E
The undo action is not allowed (activity ''0'').
CWWBV3126E
The expiration element is not allowed for the activity ''0''.
CWWBV3127W
The expiration element is set for the activity ''0''. Define an appropriate timeout fault handler.
CWWBV3128E
The partnerLink ''0'' was not found (activity ''1'').
CWWBV3129E
The partnerLink ''0'' does not define the myRole role (activity ''1'').
CWWBV3130E
The portType ''0'' was not found (activity ''1'').
CWWBV3131E
The portType referenced in the activity ''0'' and in the role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV3132E
The operation ''0'' was not found (activity ''1'').
CWWBV3133E
The input element is not defined in the operation ''0'' (activity ''1'').
CWWBV3134E
The output element is not defined in the operation ''0'' (activity ''1'').
CWWBV3135E
The messageType is not set in the input element of the operation ''0'' (activity ''1'').
CWWBV3136E
The messageType is not set in the output element of the operation ''0'' (activity ''1'').
CWWBV3137E
The messageType is not set in the fault element of the operation ''0'' (activity ''1'').
CWWBV3138E
The messageType ''0'' referenced in the operation ''1'' was not found (activity ''2'').
CWWBV3139E
The messageType of the variable ''0'' and the input element of operation ''1'' must be the same (activity ''2'').
CWWBV3140E
The messageType of the variable ''0'' and the output element of operation ''1'' must be the same (activity ''2'').
CWWBV3141E
The messageType of the variable ''0'' and the fault ''1'' of the operation ''2'' must be the same (activity ''3'').
CWWBV3142E
The variable is not set (activity ''0'').
CWWBV3143E
The input variable for the ''0'' activity is not specified.
CWWBV3144E
The output variable is not set (activity ''0'').
CWWBV3145E
The output variable ''0'' must not be set, because the operation is one-way (activity ''1'', operation ''2'').
CWWBV3146E
The correlation set ''0'' was not found (activity ''1'').
CWWBV3147E
The onAlarm event must specify at least a for expression, an until expression, or a repeatEvery expression (activity ''0'', onAlarm event 1).
CWWBV3148E
The onAlarm event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (activity ''0'', onAlarm event 1).
CWWBV3149E
The onAlarm event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (activity ''0'', onAlarm event 1).
CWWBV3150E
The expression language ''0'' is not supported. It must be one of ''1'' (activity ''2'', onAlarm event 3).
CWWBV3151E
A matching propertyAlias definition was not found for the property ''0'' and messageType ''1'' (activity ''2'', correlation set ''3'').
CWWBV3152E
The part ''0'' referenced in the propertyAlias definition for the property ''1'' and messageType ''2'' was not found (activity ''3'', correlation set ''4'').
CWWBV3153E
The part ''0'' referenced in the propertyAlias definition for the property ''1'' and messageType ''2'' does not reference a valid XML schema simple type (activity ''3'', correlation set ''4'').
CWWBV3154E
The type of the part ''0'' of the messageType ''1'' and the type of the property ''2'' are not the same (activity ''3'', correlation set ''4'').
CWWBV3155E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (activity ''2'', correlation set ''3'').
CWWBV3156E
Because the pick or receive activity ''0'' creates a process instance, it cannot be placed after the activity or the activities ''1''.
CWWBV3157E
The activity ''0'' is the target of the link or links ''1'', but it can create a process instance or it contains activities that can create a process instance.
CWWBV3158W
The while activity ''1'' contains the pick or receive activity ''0'' that creates a process instance. If the condition of the while activity is false when the condition is evaluated for the first time, the process does not run correctly.
CWWBV3159E
The pick or receive activity ''0'' that creates a process instance cannot be contained in a catch, catchAll, onMessage, onEvent, onAlarm, compensation handler, case, or otherwise element.
CWWBV3160E
The flow activity ''0'' contains one or more activities that can start processes, but it also contains the activity ''1'' which cannot start a process.
CWWBV3161E
The activity ''0'' does not reference the partnerLink ''null'' (used partnerLink ''1'').
CWWBV3162E
The activity ''0'' does not reference the portType ''wpc:null'' (used portType ''1'').
CWWBV3163E
The activity ''0'' does not reference the operation ''null'' (used operation ''1'').
CWWBV3164W
The variable attribute ''0'' is not needed (activity ''1'').
CWWBV3165W
The input element is not needed (activity ''0'').
CWWBV3166W
The output element is not needed (activity ''0'').
CWWBV3167E
The output element must not be set, because the operation is one-way (activity ''0'', operation ''1'').
CWWBV3168E
The inputVariable attribute must not be set because an input element is available (activity ''0'', inputVariable ''1'').
CWWBV3169E
The outputVariable attribute must not be set because an output element is available (activity ''0'', outputVariable ''1'').
CWWBV3170E
The variable ''0'' is not defined (input or output element of activity ''1'', parameter number 2).
CWWBV3171E
The message-typed variable cannot be used here (input/output element of activity ''0'', parameter number 1, variable ''2'').
CWWBV3172E
The variable ''0'' cannot be used multiple times in the same input or output element (input or output element of activity ''1'', parameter number 2).
CWWBV3173E
The human task ''0'' cannot be found (activity ''1'').
CWWBV3174E
The portType that is referenced in the activity ''0'' and in the human task ''1'' must be the same.
CWWBV3175E
The operation that is referenced in the activity ''0'' and in the human task ''1'' must be the same.
CWWBV3176E
The human task ''0'' is not an administration task (activity ''1'').
CWWBV3177E
The part is not set in the propertyAlias definition for the property ''0'' and messageType ''1'' (activity ''2'', correlation set ''3'').
CWWBV3178E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (activity ''2'', correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3179E
The expiration element must specify at least a for expression, an until expression, or a timeout expression (activity ''0'').
CWWBV3180E
The expression language ''0'' of the expiration element is not supported. It must be one of ''1'' (activity ''2'').
CWWBV3181E
The expression language ''0'' of the transition condition is not supported. It must be one of ''1'' (activity ''2'', source element number 3, link ''4'').
CWWBV3182E
The expression language ''0'' of the join condition is not supported. It must be one of ''1'' (activity ''2'').
CWWBV3183E
The transition condition expression is invalid (activity ''0'', source element number 1, link ''2'', expression language ''3'').
CWWBV3184E
The join condition expression is invalid (activity ''0'', expression language ''1'').
CWWBV3185E
The parameter-extension cannot be used for the message ''0'' (activity ''1'').
CWWBV3186E
The parameter ''0'' must be removed or mapped to an element or part (activity ''1'', parameter number 2).
CWWBV3187E
The XSD type definition ''0'' was not found (activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3188E
The XSD element declaration ''0'' was not found (activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3189E
The variable ''0'' cannot be assigned to element or part ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3190E
The element or part ''0'' cannot be assigned to variable ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3191E
The XSD element ''0'' is not mapped to a parameter (activity ''1'').
CWWBV3192E
The message-part ''0'' is not mapped to a parameter (activity ''1'').
CWWBV3193E
The correlation set ''0'' is used already. It can only be used once (activity ''1'').
CWWBV3194E
The custom property name ''0'' is used already. The name can only be used once (activity ''1'').
CWWBV3195E
The forEach activity ''1'' must not contain the pick or receive activity ''0'' that can create a process instance.
CWWBV3196E
The compensation handler is not allowed (activity ''0'').
CWWBV3197E
The XPath transition condition is not valid: 0 (activity ''1'', source element number 2, link ''3'').
CWWBV3198E
The XPath join condition is not valid: 0 (activity ''1'').
CWWBV3199E
The XPath correlation set property propertyAlias query is not valid: 0 (activity ''1'', correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3200E
The XPath for- or until-expiration-expression is invalid: 0 (activity ''1'').
CWWBV3201W
The correlation set property propertyAlias query must not be empty (activity ''0'', correlation set ''1'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV3202W
Assigning the ''0'' xsd:anyType typed element or the part to the 1 xsd:anySimpleType typed variable might result in a runtime error (activity 2, parameter number 3).
CWWBV3203W
Assigning the ''0'' xsd:anyType typed variable to the ''1'' xsd:anySimpleType typed element or part might result in a runtime error (activity ''2'', parameter number 3).
CWWBV3204W
The XPath in the for-expiration expression or until-expiration expression for the ''1'' activity is not valid: ''0''
CWWBV3207W
The XPath in the for- or until-expiration-expression for ''1'' activity is not valid because the ''$'' notation used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3208W
The XPath join condition in the ''1'' activity is not valid: ''0''
CWWBV3211W
The XPath join condition for the activity ''1'' is not valid because the ''$'' notation used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3212W
The XML Path Language (XPath) transition condition for the 3 link, starting from source element number 2 in the 1 activity, is not valid. The error is: 0
CWWBV3215W
The XPath transition condition for the link ''3'', starting from source element number 2 in activity ''1'', is not valid because the ''$'' notation used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3216W
The XPath correlation set property propertyAlias query is not valid: ''0'' (activity ''1'', correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3219W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (activity ''1'', correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3220E
The adminTask elements cannot be used in the activity ''0''. These elements are only allowed in invoke and scope activities.
CWWBV3221W
Deprecation: The 0 expression or query language is deprecated. Use 1 instead (resource 2).
CWWBV3222W
Deprecation: The 0 value of the pattern attribute in the correlation element 1 is deprecated. Use one of the following pattern values: 2 (3 invoke activity).
CWWBV3223E
The pattern attribute in the 0 correlation element of the 1 invoke activity cannot be used for one-way operations.
CWWBV3224E
The 0 variable is not defined (1 activity, fromPart or toPart number 2).
CWWBV3225E
The message-typed variable cannot be used here (0 activity, fromPart or toPart number 1, 2 variable).
CWWBV3226E
The 0 variable cannot be used multiple times in the same fromParts or toParts element (1 activity, fromPart or toPart number 2).
CWWBV3227E
The 0 message part is not mapped to a fromPart or toPart element (1 activity).
CWWBV3228E
The 0 fromPart or toPart must be removed or mapped to an existing message-part (1 activity, fromPart or toPart number 2).
CWWBV3229E
The fromParts or toParts element cannot be used for the 0 message (1 activity).
CWWBV3230W
Assigning the 0 xsd:anyType typed message part to the 1 xsd:anySimpleType typed variable might result in a runtime error (2 activity, fromPart/toPart number 3).
CWWBV3231E
The 0 message part cannot be assigned to the 1 variable because the data type does not match (2 activity, fromPart or toPart number 3).
CWWBV3232E
The 0 activity uses the parameter extension and the fromParts or toParts element. This is not supported.
CWWBV3233E
The inputVariable attribute must not be set because a toParts element is available (0 activity, 1 inputVariable).
CWWBV3234E
The outputVariable attribute must not be set because a fromParts element is available (0 activity, 1 outputVariable).
CWWBV3235E
The variable must not be set because a fromParts element is available (process onEvent event number 0, 1 variable).
CWWBV3236E
The fromParts element must not be set because this is a one-way operation (0 activity, 1 operation).
CWWBV3237E
The transition condition is not allowed on the 0 source activity with the ''fork'' source type (source element number 1, 2 link).
CWWBV3238E
The transactionalBehavior attribute cannot be used in the ''0'' activity. It is allowed only in invoke, receive, and pick activities.
CWWBV3239E
The exit condition expression is invalid (activity ''0'', expression language ''1'').
CWWBV3240E
The expression language ''0'' of the exit condition is not supported. It must be one of ''1'' (activity ''2'').
CWWBV3241W
The XML Path Language (XPath) exit condition for the 1 activity, is not valid. The error is: 0
CWWBV3242E
The XPath exit condition is not valid: 0 (activity ''1'').
CWWBV3243E
The value of the executeAt attribute on an exit condition must not be BOTH or ENTRY on initiating receives (receive ''0'').
CWWBV3244E
The executeAt attribute must be set for an exit condition (activity ''0'').
CWWBV3245E
The otherwise transition condition expression is invalid in this context (activity ''0'', source element number 1, link ''2'').
CWWBV3246W
A variable in a XPath expression must not contain the ''.'' character. (variable ''0'', activity ''1'').
CWWBV3247E
The derived type of the ''0'' variable cannot be assigned to element or part ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3248E
The type of the ''0'' variable contains a chain of derivations with mixed derivation types. (element or part ''1'' ,activity ''2'', parameter number 3).
CWWBV3249E
The type of the ''0'' variable derives a type that disallows the used derivation. (1 activity, parameter number 2, matching part or element: 3).
CWWBV3250E
The derived type of the element or part ''0'' cannot be assigned to variable ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3251E
The type of the ''0'' element or part contains a chain of derivations with mixed derivation types. (element or part ''1'' ,activity ''2'', parameter number 3).
CWWBV3252E
The type of the ''0'' element or part derives a type that disallows the used derivation. (element or part ''1'' ,activity ''2'', parameter number 3).
CWWBV3253E
The 0 derived message part cannot be assigned to the 1 variable because the data type does not match (2 activity, fromPart or toPart number 3).
CWWBV3254E
The type of the ''0'' message part contains a chain of derivations with mixed derivation types. (1 variable, 2 activity, fromPart or toPart number 3).
CWWBV3255E
The type of the ''0'' message part derives a type that disallows the used derivation. (1 variable, 2 activity, fromPart or toPart number 3).
CWWBV3256E
Inline custom properties are not allowed on activity level.
CWWBV3300E
The from-specification is not allowed (assign activity ''0'', copy element number 1).
CWWBV3301E
The to-specification is not allowed (assign activity ''0'', copy element number 1).
CWWBV3302E
The from-to copy combination is not allowed (assign activity ''0'', copy element number 1).
CWWBV3303E
The from-variable ''0'' is not defined (assign activity ''1'', copy element number 2).
CWWBV3304E
The from-part ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'').
CWWBV3305E
The from-partnerLink ''0'' was not found (assign activity ''1'', copy element number 2).
CWWBV3306E
The to-variable ''0'' is not defined (assign activity ''1'', copy element number 2).
CWWBV3307E
The to-part ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'').
CWWBV3308E
The to-partnerLink ''0'' was not found (assign activity ''1'', copy element number 2).
CWWBV3309E
The to-partnerLink ''0'' does not define the partnerRole role (assign activity ''1'', copy element number 2).
CWWBV3310E
The messageType of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from messageType ''4'', to messageType ''5'').
CWWBV3311E
The XSD type of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3312E
The XSD element of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD element ''4'', to XSD element ''5'').
CWWBV3313E
The type of the from-part ''0'' and the to-part ''1'' must be the same (assign activity ''2'', copy element number 3).
CWWBV3314E
The from-partnerLink ''0'' does not define the myRole role (assign activity ''1'', copy element number 2).
CWWBV3315E
The from-partnerLink ''0'' does not define the partnerRole role (assign activity ''1'', copy element number 2).
CWWBV3316E
The portType of the from-role ''0'' and the to-role ''1'' are not the same (assign activity ''2'', copy element number 3, from partnerLink ''4'', to partnerLink ''5'').
CWWBV3317E
The message-typed from-variable ''0'' cannot be assigned to the type-typed or element-typed to-variable ''1'' (assign activity ''2'', copy element number 3, from messageType ''4'', to type/element ''5'').
CWWBV3318E
The type-typed from-variable ''0'' cannot be assigned to the message-typed to-variable ''1'' (assign activity ''2'', copy element number 3, from type ''4'', to messageType ''5'').
CWWBV3319E
The element-typed from-variable ''0'' cannot be assigned to the messageType-typed to-variable ''1'' (assign activity ''2'', copy element number 3, from element ''4'', to messageType ''5'').
CWWBV3320E
The literal type ''0:1'' is not allowed (assign activity ''2'', copy element number 3, from-specification).
CWWBV3321E
A literal value is not defined (assign activity ''0'', copy element number 1, from-specification).
CWWBV3322E
The literal type in the from element and the part type in the to element are not the same (assign activity ''0'', copy element number 1).
CWWBV3323E
The literal value is not of the type ''0'' (assign activity ''1'', copy element number 2, from-specification).
CWWBV3324E
The XSD type definition ''0'' was not found (assign activity ''1'', copy element number 2, base type ''3'', type referencing the type that was not found ''4'').
CWWBV3325E
The XSD type definition ''0'' is not valid (assign activity ''1'', copy element number 2).
CWWBV3326E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3, propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3327E
Part ''0'' referenced in the propertyAlias definition for property ''1'' and messageType ''2'' must reference a valid XML schema simple type (assign activity ''3'', copy element number 4).
CWWBV3328E
The type of part ''0'' of messageType ''1'' and the type of the property ''2'' must be the same XML schema type (assign activity ''3'', copy element number 4).
CWWBV3329E
The query language ''0'' is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3, from-specification).
CWWBV3330E
The query language ''0'' is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3, to-specification).
CWWBV3331E
The expression language ''0'' of the expression element is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3).
CWWBV3332E
The XSD-typed variable ''0'' cannot be used in combination with a property specification. Use a message-typed variable (assign activity ''1'', copy element number 2).
CWWBV3333E
The property ''0'' was not found (assign activity ''1'', copy element number 2).
CWWBV3334E
A matching propertyAlias definition is needed for the property ''0'' and the messageType ''1'' (assign activity ''2'', copy element number 3).
CWWBV3335E
The part must be set in the propertyAlias for the property ''0'' and the messageType ''1'' (assign activity ''2'', copy element number 3).
CWWBV3336E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (assign activity ''3'', copy element number 4).
CWWBV3337E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (assign activity ''2'', copy element number 3).
CWWBV3338E
The XSD type definition ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'', part ''4'').
CWWBV3339E
The XSD element declaration ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'', part ''4'').
CWWBV3340E
The XSD-typed part ''0'' cannot be assigned to the message-typed to-variable ''1'' (assign activity ''2'', copy element number 3).
CWWBV3341E
The message-typed from-variable ''0'' cannot be assigned to the XSD-typed part ''1'' (assign activity ''2'', copy element number 3).
CWWBV3342E
The XSD type definition ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'', element referencing the type that was not found ''4'').
CWWBV3343E
The type of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD element ''5'').
CWWBV3344E
The type of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD element ''4'', to XSD type ''5'').
CWWBV3345E
The XSD type of the from-part ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3346E
The XSD type of the from-variable ''0'' and the to-part ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3347E
The XSD type of the from-part ''0'' and the to-part ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3348E
The from-query is not valid: 0 (assign activity ''1'', copy element number 2).
CWWBV3349E
The to-query is not valid: 0 (assign activity ''1'', copy element number 2).
CWWBV3350E
The propertyAlias query which is referenced with the from property is not valid: 0 (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3351E
The to property propertyAlias query is not valid: 0 (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3352E
The from-expression is not valid: 0 (assign activity ''1'', copy element number 2).
CWWBV3353W
The from property propertyAlias query must not be empty (assign activity ''0'', copy element number 1, propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV3354W
The to property propertyAlias query must not be empty (assign activity ''0'', copy element number 1, propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV3355W
Assigning the xsd:anyType typed from-variable ''0'' to the xsd:anySimpleType typed to-variable ''1'' might result in a runtime error (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3356W
In assign activity ''1'', the from-expiration expression in copy element number 2 is not valid: ''0''
CWWBV3359W
In the ''1'' assign activity, copy element number 2, the from-expression is not valid: The ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (assign activity ''1'', copy element number 2)
CWWBV3360W
In the ''1'' assign activity, copy element number 2, the XPath query used in the assign from property ''3'' is not valid: ''0'' (messageType 4).
CWWBV3363W
In the ''2'' assign activity, copy element number 3, the XPath query used in the assign from property ''4'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3364W
In the ''1'' assign activity, copy element number 2, the from query is not valid: ''0''
CWWBV3367W
In the ''1'' assign activity, copy element number 2, the from query is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (assign activity ''1'', copy element number 2).
CWWBV3368W
In the ''1'' assign activity, copy element number 2, the XPath query used in the ''3'' assign-to property of a variable is not valid: ''0'' messageType ''4'').
CWWBV3371W
In the ''2'' assign activity, copy element number 3, the XPath query used in the ''4'' assign-to property of a variable is not valid because the ''$'' notation that is used to refer to a variable in the 0 XPath expression or query is not supported. (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3372W
In the ''1'' assign activity, copy element number 2, the to query is not valid: ''0''
CWWBV3375W
In the ''1'' assign activity, copy element number 2, the to query is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3376W
Deprecation: In the 0 assign activity, copy element number 1, the ''from'' element uses the deprecated schema for literal values.
CWWBV3378E
In the ''0'' assign activity, copy element number 1, the from element uses both schemas for literal values. This is not supported.
CWWBV3379E
The derived type of the 0 from variable and the type of the 1 to variable are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3380E
The type of the 0 from variable contains a chain of derivations with mixed derivation types. ( 1 assign variable, (2 assign activity, copy element number 3, 4 from XSD type).
CWWBV3381E
The type of the 0 from variable derives a type that disallows the used derivation. ( 1 assign variable, 2 assign activity, copy element number 3, 4 from XSD type).
CWWBV3382E
The derived data type of the 0 from part and the 1 to variable are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3383E
The data type of the 0 from part contains a chain of derivations with mixed derivation types. (1 to variable or part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3384E
The data type of the 0 from part derives a type that disallows the used derivation. (1 to variable or part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3385E
The derived type of the 0 from variable and the 1 to part are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3386E
The data type of the 0 from variable contains a chain of derivations with mixed derivation types. (1 to part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3387E
The data type of the 0 from variable derives a type that disallows the used derivation. (1 to part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3388E
The derived type of the 0 from part and the 1 to part are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3400E
The ''0''compensate activity can only be used inside a fault handler, a compensation handler, or directly in a generalized flow realizing the BPMN pattern.
CWWBV3401E
The referenced scope or invoke activity ''0'' was not found or can not be referenced. It must be defined in the process and contained in the scope (compensate activity ''1'').
CWWBV3402E
The compensate activity cannot be contained inside an invoke activity (compensate activity ''0'', invoke activity ''1'').
CWWBV3403E
The referenced scope activity ''0'' cannot be compensated (compensate activity ''1'').
CWWBV3406E
The activity name ''0'' must be unique (referenced in compensate activity ''1'').
CWWBV3407E
The compensate activity cannot be contained inside the fault handler of a non-compensable scope activity (compensate activity ''0'', scope activity ''1'').
CWWBV3408W
Deprecation: The use of the scope attribute on the 0 compensate activity is deprecated. Use the compensateScope activity instead.
CWWBV3409E
The compensateScope activity can be used only inside a fault handler or a compensation handler (0 compensate activity).
CWWBV3410E
The 0 referenced scope or invoke activity was not found or cannot be referenced. It must be defined in the process and contained in the scope (1 compensateScope activity).
CWWBV3411E
The compensateScope activity cannot be contained inside an invoke activity (0 compensateScope activity, 1 invoke activity).
CWWBV3412E
The 0 referenced scope activity cannot be compensated (1 compensateScope activity).
CWWBV3415E
The activity name 0 must be unique (referenced in the 1 compensateScope activity).
CWWBV3416E
The compensateScope activity cannot be contained in the fault handler of a non-compensable scope activity (0 compensateScope activity, 1 scope activity).
CWWBV3417I
The scope of the 0 compensateScope activity is the surrounding scope or the surrounding process.
CWWBV3418I
The scope of the 0 compensate activity is the surrounding scope or the surrounding process.
CWWBV3600E
The link ''0'' cannot cross the boundary of the while activity ''1'' (link defined in the flow activity ''2'').
CWWBV3601E
The link ''0'' cannot be used in the while activity ''1'', because it is defined outside of the while activity (link defined in the flow activity ''2'').
CWWBV3602E
The link ''0'' cannot cross the boundary of the compensation handler of the scope activity ''1'' (link defined in the flow activity ''2'').
CWWBV3603E
The link ''0'' cannot be used in the compensation handler of the scope activity ''1'', because it is defined outside of the scope activity (link defined in the flow activity ''2'').
CWWBV3604E
The link ''0'' cannot cross the boundary of the compensation handler of the invoke activity ''1'' (link defined in the flow activity ''2'').
CWWBV3605E
The link ''0'' cannot be used in the compensation handler of the invoke activity ''1'', because it is defined outside of the invoke activity (link defined in the flow activity ''2'').
CWWBV3606E
The link ''0'' cannot cross the boundary of the event handler of the scope activity ''1'' (link defined in the flow activity ''2'').
CWWBV3607E
The link ''0'' cannot be used in the event handler of the scope activity ''1'', because it is defined outside of the scope activity (link defined in the flow activity ''2'').
CWWBV3608E
The inbound link ''0'' cannot cross the boundary of the fault handler of the scope activity ''1'' (link defined in the flow activity ''2'').
CWWBV3609E
The link ''0'' cannot be used in the fault handler of the scope activity ''1'', because it is defined outside of the scope activity (link defined in the flow activity ''2'').
CWWBV3610E
The target of the link ''0'' cannot be nested in the scope activity ''1'', because the source of the link is nested in the fault handler of the scope activity (link defined in the flow activity ''2'').
CWWBV3611E
The inbound link ''0'' cannot cross the boundary of the fault handler of the invoke activity ''1'' (link defined in the flow activity ''2'').
CWWBV3612E
The link ''0'' cannot be used in the fault handler of the invoke activity ''1'', because it is defined outside of the invoke activity (link defined in the flow activity ''2'').
CWWBV3613E
The link ''0'' cannot cross the boundary of two serializable scope activities (source scope activity ''1'', target scope activity ''2'', link defined in the flow activity ''3'').
CWWBV3614E
The activity ''0'' cannot be part of a cycle.
CWWBV3615E
The link ''0'' cannot be part of a cycle.
CWWBV3616E
The source activity is missing for the link ''0'' (link defined in the flow activity ''1'', target activity ''2'').
CWWBV3617E
The target activity is missing for the link ''0'' (link defined in the flow activity ''1'', source activity ''2'').
CWWBV3618E
The link ''0'' is not used (link defined in the flow activity ''1'').
CWWBV3619E
The link ''0'' has more than one source activity: ''1'' (link defined in the flow activity ''2'').
CWWBV3620E
The 0 link has the following target activities: 1 (link defined in the 2 flow activity).
CWWBV3621E
The source type of the 0 activity must not be 2 (source of standard flow link 1).
CWWBV3622E
The target type of 0 activity must not be 2 (target of standard flow link 1).
CWWBV3623E
The link ''0'' cannot cross the boundary of the forEach activity ''1'' (link defined in the flow activity ''2'').
CWWBV3624E
The link ''0'' cannot be used in the forEach activity ''1'', because it is defined outside of the forEach activity (link defined in the flow activity ''2'').
CWWBV3625W
The type attribute of the sources or targets element is deprecated (0 activity, 1 link).
CWWBV3650E
The extension activity ''0'' is not supported. Only generalized flow activities are supported.
CWWBV3651E
The source type of the 0 activity must be one of split, fork, or ior (source of the 1 generalized flow link).
CWWBV3652E
The target type of the 0 activity must be merge, join, or ior (target of the 1 generalized flow link).
CWWBV3653E
The source activity ''0'' of the generalized flow link ''1'' must be directly nested in the generalized flow activity ''2''.
CWWBV3654E
The target activity ''0'' of the generalized flow link ''1'' must be directly nested in the generalized flow activity ''2''.
CWWBV3655E
The generalized flow activity ''0'' must contain exactly one start activity. Found start activities: ''1''.
CWWBV3656E
The generalized flow activity ''0'' must contain at least one end activity.
CWWBV3657E
The activity ''0'' cannot be reached from the start activity ''1'' of the generalized flow activity ''2''.
CWWBV3658E
An end activity cannot be reached from the activity ''0'' of the generalized flow activity ''1''. Connect the activity to an end activity.
CWWBV3659E
The activity ''0'' must not specify a join condition, because it is part of a graph.
CWWBV3660W
The generalized flow link ''0'' can never be navigated because the previously referenced generalized flow link ''1'' does not specify a transition condition (activity ''2'').
CWWBV3661E
The link ''0'' cannot cross the boundary of the generalized flow activity ''1'' (link defined in the flow activity ''2'').
CWWBV3662E
The link ''0'' cannot be used in the generalized flow activity ''1'', because it is defined outside of the generalized flow activity (link defined in the flow activity ''2'').
CWWBV3663E
The 0 flow activity is the source of multiple links but has no source type specified.
CWWBV3664E
The 0 flow activity is the target of multiple links but has no target type specified.
CWWBV3665W
The region analysis of ''0'' flow activity is failing.
CWWBV3666E
The fault source must contain a catch element or a catchAll element. (source activity ''0'', number of fault source ''1'')
CWWBV3667E
The fault source must not contain more than one catch element or a catchAll element. (source activity ''0'', number of fault source ''1'')
CWWBV3668E
There must not be more than one fault source with catch all. (source activity ''0'').
CWWBV3669E
The fault source requires either a faultName attribute, a faultVariable attribute or both (source activity ''0'', number of fault source ''1'')
CWWBV3670E
The fault variable ''0'' on the fault source cannot be found. (source activity ''1'', number of fault source ''2'')
CWWBV3671E
The source activity of a fault link must not be a structured activity (except the scope activity), a throw activity or a rethrow activity. (source activity ''0'').
CWWBV3672E
One region of generalized flow ''0'' is not mappable. (participating activities ''1'').
CWWBV3673E
The link or activity ''0'' is participating in a parallel region that contains a cycle (generalized flow ''1'').
CWWBV3674W
One region of generalized flow ''0'' might cause exceptions at runtime. (participating activities ''1'')
CWWBV3675W
The fault source requires a fault variable as the defined fault ''0'' has associated fault data. (source activity ''1'', number of fault source ''2'')
CWWBV3676W
The fault name ''0'' does not exist in the operation ''1''. (source activity ''2'', number of fault source ''3'')
CWWBV3677W
The fault variable ''0'' does not have the same message type as the fault data of the fault name ''1'' (source activity ''2'', number of fault source ''3'')
CWWBV3678W
The 0 link has a transition condition and is the only outgoing link of 1 activity.
CWWBV3700E
The partnerLink ''0'' referenced in the undo action was not found (invoke activity ''1'').
CWWBV3701E
The portType ''0'' referenced in the undo action was not found (invoke activity ''1'').
CWWBV3702E
The operation ''0'' referenced in the undo action was not found (invoke activity ''1'').
CWWBV3703E
The input element is not defined in the undo action operation ''0'' (invoke activity ''1'').
CWWBV3704E
The messageType is not set in the input element of the undo action operation ''0'' (invoke activity ''1'').
CWWBV3705E
The messageType ''0'' that is referenced in the input element of the undo action operation ''1'' is not defined (invoke activity ''2'').
CWWBV3706E
The messageType of the variable ''0'' and the input element of the undo action operation ''1'' must be the same (invoke activity ''2'').
CWWBV3707E
The undo action variable ''0'' is not defined (invoke activity ''1'').
CWWBV3708E
The XSD-typed variable cannot be used in the undo action (invoke activity ''0'', variable ''1'').
CWWBV3710E
An expiration element cannot be set for the undo action (invoke activity ''0'').
CWWBV3711E
The undo action partnerLink ''0'' does not define the partnerRole role (invoke activity ''1'').
CWWBV3712E
The portType attribute referenced in the undo action of the invoke activity ''0'' and in the partnerRole role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV3713E
The partnerLink ''0'' does not define the partnerRole role (invoke activity ''1'').
CWWBV3714E
The inputVariable attribute of the undo action must not be set because an undo action input element is available (invoke activity ''0'', undo action inputVariable ''1'').
CWWBV3715E
The variable ''0'' used in the undo action is not defined (input element of the undo action of invoke activity ''1'', parameter number 2).
CWWBV3716E
The message-typed variable cannot be used here (input element of the undo action of invoke activity ''0'', parameter number 1, variable ''2'').
CWWBV3717E
The variable ''0'' cannot be used multiple times in the same input element (input element of the undo action of invoke activity ''1'', parameter number 2).
CWWBV3718E
The invoke activity cannot contain both a compensation handler and an undo action (invoke activity ''0'').
CWWBV3719E
The undo action must specify a variable if the invoke activity specifies a variable by using the parameter extension (invoke activity ''0'').
CWWBV3720E
The parameter-extension cannot be used for the message ''0'' (undo action of invoke activity ''1'').
CWWBV3721E
The parameter ''0'' is not mapped to an element or part (undo action of invoke activity ''1'', parameter number 2).
CWWBV3722E
The XSD type definition ''0'' was not found (undo action of invoke activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3723E
The XSD element declaration ''0'' was not found (undo action of invoke activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3724E
The variable ''0'' cannot be assigned to element or part ''1'' because the data type does not match (undo action of invoke activity ''2'', parameter number 3).
CWWBV3725E
The XSD element ''0'' is not mapped to a parameter (undo action of invoke activity ''1'').
CWWBV3726E
The message-part ''0'' is not mapped to a parameter (undo action of invoke activity ''1'').
CWWBV3727W
In the undo action of the ''2'' invoke activity, parameter number 3, assigning the ''0'' xsd:anyType typed variable to the ''1'' xsd:anySimpleType typed element or part might cause a runtime error.
CWWBV3800E
The XSD-typed variable cannot be used here (pick activity ''0'', onMessage element number 1, variable ''2'').
CWWBV3801E
The partnerLink ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3802E
The partnerLink ''0'' does not define the myRole role (pick activity ''1'', onMessage element number 2).
CWWBV3803E
The portType ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3804E
The portType referenced in the pick activity ''0'' and in the myRole role ''1'' must be the same (onMessage element number 2, partnerLink ''3'', partnerLinkType ''4'').
CWWBV3805E
The operation ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3806E
The input element is not defined in the operation ''0'' (pick activity ''1'', onMessage element number 2).
CWWBV3807E
The messageType is not set in the input element of the operation ''0'' (pick activity ''1'', onMessage element number 2).
CWWBV3808E
The messageType ''0'' referenced in the operation ''1'' was not found (pick activity ''2'', onMessage element number 3).
CWWBV3809E
The messageType of the variable ''0'' and of the input element of operation ''1'' must be the same (pick activity ''2'', onMessage element number 3).
CWWBV3810E
The variable for onMessage element number 1 in pick activity ''0'' is not set.
CWWBV3811E
The variable ''0'' is not defined (pick activity ''1'', onMessage element number 2).
CWWBV3812E
The correlation set ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3813E
A matching propertyAlias definition was not found for the property ''0'' and messageType ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'').
CWWBV3814E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (pick activity ''3'', onMessage element number 4, correlation set ''5'').
CWWBV3815E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' does not reference a valid XML schema simple type (pick activity ''3'', onMessage element number 4, correlation set ''5'').
CWWBV3816E
The type of the part ''0'' of the messageType ''1'' and the property ''2'' is not the same (pick activity ''3'', onMessage element number 4, correlation set ''5'').
CWWBV3817E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'').
CWWBV3818E
The onMessage element, number 0, in pick activity ''1'' does not use a correlation set.
CWWBV3819E
The wrong set of correlation sets is used in onMessage element number 0 of the pick activity ''1''. The expected set of correlation sets, as used in the activity ''2'', is: ''3''.
CWWBV3821E
The pick activity ''0'' can create process instances but it has onAlarm events.
CWWBV3822E
A reply activity was not found that matches onMessage element number 0 of the pick activity ''1''.
CWWBV3823E
The variable must not be set because an output element is available (pick activity ''0'', onMessage element number 1, variable ''2'').
CWWBV3824E
The variable ''0'' is not defined (pick activity ''1'', output element of onMessage element number 2, parameter number 3).
CWWBV3825E
The message-typed variable cannot be used here (pick activity ''0'', output element of onMessage element number 1, parameter number 2, variable ''3'').
CWWBV3826E
The variable ''0'' cannot be used multiple times in the same output element (pick activity ''1'', output element of onMessage element number 2, parameter number 3).
CWWBV3827E
The human task ''0'' cannot be found (pick activity ''1'', onMessage element number 2).
CWWBV3828E
The human task ''0'' is not an invocation task (pick activity ''1'', onMessage element number 2).
CWWBV3829E
The portType that is referenced in onMessage element number 0 and in the human task ''1'' must be the same (pick activity ''2'').
CWWBV3830E
The operation that is referenced in onMessage element number 0 and in the human task ''1'' must be the same (pick activity ''2'').
CWWBV3831E
The part is not set in the propertyAlias for the property ''0'' and the messageType ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'').
CWWBV3832E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'', propertyAlias for the property ''5'' and the messageType ''6'').
CWWBV3833E
The onAlarm event must specify at least a for expression, or an until expression (pick activity ''0'', onAlarm event 1).
CWWBV3834E
The onAlarm event must specify at least a for expression, an until expression, or a timeout expression (pick activity ''0'', onAlarm event 1).
CWWBV3835E
The onAlarm event cannot specify a for expression and a timeout expression, or an until expression and a timeout expression (pick activity ''0'', onAlarm event 1).
CWWBV3836E
The repeatEvery expression is not allowed in pick activities (pick activity ''0'', onAlarm event 1).
CWWBV3837E
The onMessage element, number 0, implements operation ''1'' of portType ''2'', which is already implemented in another onMessage element (pick activity ''3'').
CWWBV3838E
The parameter-extension cannot be used for the message ''0'' (pick activity ''1'', onMessage element number 2).
CWWBV3839E
The parameter ''0'' is not mapped to an element or part (pick activity ''1'', onMessage element number 2, parameter number 3).
CWWBV3840E
The XSD type definition ''0'' was not found (pick activity ''1'', onMessage element number 2, parameter number 3, matching part or element ''4'').
CWWBV3841E
The XSD element declaration ''0'' was not found (pick activity ''1'', onMessage element number 2, parameter number 3, matching part or element ''4'').
CWWBV3842E
The element or part ''0'' cannot be assigned to variable ''1'' because the data type does not match (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3843E
The XSD element ''0'' must be mapped to a parameter (pick activity ''1'', onMessage element number 2).
CWWBV3844E
The message-part ''0'' is not mapped to a parameter (pick activity ''1'', onMessage element number 2).
CWWBV3845E
The correlation set ''0'' is used already (pick activity ''1'', onMessage element number 2).
CWWBV3846W
The pick activity ''0'' is contained in the parallel forEach activity ''1''. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3847E
The same operation of the same port type is implemented by process onEvent event number 0. This would result in the standard fault ''bpws:conflictingReceive'' (pick activity ''1'', onMessage element number 2).
CWWBV3848E
The same operation of the same port type is implemented by onEvent event number 0 of the scope activity ''1''. This would result in the standard fault ''bpws:conflictingReceive'' (pick activity ''2'', onMessage element number 3).
CWWBV3849W
The pick activity ''0'' is contained in process onEvent event number 1, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3850W
The pick activity ''0'' is contained in onEvent event number 1 of the scope activity ''2'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3851E
The XPath for- or until-expression is not valid: 0 (pick activity ''1'', onAlarm event 2).
CWWBV3852E
The XPath correlation set property propertyAlias query is not valid: 0 (pick activity ''1'', onMessage element number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3853W
The XPath correlation set property propertyAlias query must not be empty (pick activity ''0'', onMessage element number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3854W
Assigning the xsd:anyType typed element or part ''0'' to the xsd:anySimpleType typed variable ''1'' might result in a runtime error (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3855W
The XPath for-expression or until-expression in onAlarm event number 2 of pick activity ''1'' is not valid: ''0''
CWWBV3862W
The XPath for-expression or until-expression in onAlarm event number 2 of pick activity ''1'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (onMessage switch activity ''1'', onAlarm event number 2).
CWWBV3863W
The XPath correlation set property propertyAlias query is not valid: ''0'' (pick activity ''1'', onMessage element number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3866W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (pick activity ''1'', onMessage element number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3867W
The onMessage element, number 0, in pick activity ''1'' does not use a correlation set.
CWWBV3868E
The variable must not be set because a fromParts element is available (0 pick activity, onMessage element number 1, 2 variable).
CWWBV3869E
The derived type of the 0 element or part cannot be assigned to variable ''1'' because the data type does not match (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3870E
The derived type of the ''0'' element or part cannot be assigned to variable ''1'' because it contains a chain of derivations with mixed derivation types. (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3871E
The derived type of the ''0'' element or part cannot be assigned to variable ''1'' because it derives a type that disallows the used derivation. (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3900E
The receive activity ''0'' does not use a correlation set.
CWWBV3901E
A wrong set of correlation sets is used in the receive activity ''0''. The expected set of correlation sets, as used in activity ''1'', is: ''2''.
CWWBV3902E
A reply activity was not found that matches the receive activity ''0''.
CWWBV3903E
The variable must not be set because an output element is available (receive activity ''0'', variable ''1'').
CWWBV3904E
The human task ''0'' is not an invocation task (receive activity ''1'').
CWWBV3905W
The receive activity ''0'' is contained in the parallel forEach activity ''1''. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3906E
The same operation of the same port type is implemented by process onEvent event number 0. This would result in the standard fault ''bpws:conflictingReceive'' (receive activity ''1'').
CWWBV3907E
The same operation of the same port type is implemented by onEvent event number 0 of the scope activity ''1''. This would result in the standard fault ''bpws:conflictingReceive'' (receive activity ''2'').
CWWBV3908W
The receive activity ''0'' is contained in the process onEvent event number 1, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3909W
The receive activity ''0'' is contained in onEvent event number 1 of the scope activity ''2'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3910W
The receive activity ''0'' does not use a correlation set.
CWWBV3911E
The variable must not be set because a fromParts element is available (0 receive activity, 1 variable).
CWWBV4000E
The fault ''0'' was not found in the operation ''1'' (activity ''2'').
CWWBV4001E
The process is triggered by a one-way operation, but it contains the reply activity ''0''.
CWWBV4002E
No pick activity, receive activity, or onEvent event found to match the reply activity ''0''.
CWWBV4003E
The variable must not be set because an input element is available (reply activity ''0'', variable ''1'').
CWWBV4004E
A variable must not be set because a toParts element is available (0 reply activity, 1 variable).
CWWBV4100E
The rethrow activity ''0'' cannot be used outside of a fault handler.
CWWBV4101E
The rethrow activity ''0'' cannot be used inside of a scope.
CWWBV4200E
The serializable scope activity ''0'' must not be nested in the serializable scope activity ''1''.
CWWBV4201E
There are too many variable type definitions set for the scope variable ''0'' (scope activity ''1'', messageType ''2'', type ''3'', element ''4'').
CWWBV4202E
The scope variable ''0'' must have a variable type definition (scope activity ''1'').
CWWBV4203E
The messageType definition ''0'' was not found (scope activity ''1'', scope variable ''2'').
CWWBV4204E
The XSD type definition ''0'' was not found (scope activity ''1'', scope variable ''2'').
CWWBV4205E
The XSD element declaration ''0'' was not found (scope activity ''1'', scope variable ''2'').
CWWBV4206E
The scope variable name ''0'' is already used (scope activity ''1'').
CWWBV4207E
The event handler of the scope activity must contain an onEvent event or an onAlarm event (scope activity ''0'').
CWWBV4208E
The partnerLink ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4209E
The partnerLink ''0'' does not define the myRole role (scope activity ''1'', onEvent event number 2).
CWWBV4210E
The portType ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4211E
The portType referenced in onEvent event number 0 and in myRole role ''1'' must be the same (scope activity ''2'', partnerLink ''3'', partnerLinkType ''4'').
CWWBV4212E
The operation ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4213E
The input element is not defined in the operation ''0'' (scope activity ''1'', onEvent event number 2).
CWWBV4214E
The messageType is not set in the input element of the operation ''0'' (scope activity ''1'', onEvent event number 2).
CWWBV4215E
The messageType ''0'' referenced in the operation ''1'' was not found (scope activity ''2'', onEvent event number 3).
CWWBV4216E
The messageType of the variable ''0'' and the messageType of the input element of the operation ''1'' must be the same (scope activity ''2'', onEvent event number 3).
CWWBV4217E
The variable is not set (scope activity ''0'', onEvent event number 1).
CWWBV4218E
The messageType or element is not set (0 scope activity, onEvent event number 1).
CWWBV4219E
The messageType ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4220E
The correlation set ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4221E
The variable must not be set because an output element is available (scope activity ''0'', onEvent event number 1, variable ''2'').
CWWBV4222E
The scope activity has a compensation handler, but the compensable attribute of the scope activity is set to ''no'' (scope activity ''0'').
CWWBV4223E
The parameter-extension cannot be used for the message ''0'' (scope activity ''1'', onEvent event number 2).
CWWBV4224E
The parameter ''0'' is not mapped to an element or part (scope activity ''1'', onEvent event number 2, parameter number 3).
CWWBV4225E
The variable name ''0'' is used already in the same onEvent event (scope activity ''1'', output element of onEvent event number 2, parameter number 3).
CWWBV4226E
A matching propertyAlias definition was not found for the property ''0'' and messageType ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'').
CWWBV4227E
The part ''0'' that is referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (scope activity ''3'', onEvent event number 4, correlation set ''5'').
CWWBV4228E
The part ''0'' that is referenced in the propertyAlias for the property ''1'' and the messageType ''2'' does not reference a valid XML schema simple type (scope activity ''3'', onEvent event number 4, correlation set ''5'').
CWWBV4229E
The type of the part ''0'' of the messageType ''1'' and the type of the property ''2'' are not the same (scope activity ''3'', onEvent event number 4, correlation set ''5'').
CWWBV4230E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'').
CWWBV4231E
The human task ''0'' cannot be found (scope activity ''1'', onEvent event number 2).
CWWBV4232E
The human task ''0'' is not an invocation task (scope activity ''1'', onEvent event number 2).
CWWBV4233E
The portType referenced in onEvent event number 0 and in the human task ''1'' must be the same (scope activity ''2'').
CWWBV4234E
The operation that is referenced in onEvent event number 0 and in the human task ''1'' must be the same (scope activity ''2'').
CWWBV4235E
The part is not set in the propertyAlias for the property ''0'' and the messageType ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'').
CWWBV4236E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'', propertyAlias for the property ''5'' and the messageType ''6'').
CWWBV4237E
A reply activity was not found that matches onEvent event number 0 of the scope activity ''1''.
CWWBV4238E
The expression is not valid (scope activity ''0'', onAlarm event 1, expression language ''2'').
CWWBV4239E
There are too many variable type definitions set for the variable ''0'' (scope activity ''1'', onEvent event number 2, parameter number 3, type ''4'', element ''5'').
CWWBV4240E
The XSD element declaration ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, variable ''4'').
CWWBV4241E
The XSD type definition ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, variable ''4'').
CWWBV4242E
The variable ''0'' must have a variable type definition (scope activity ''1'', onEvent event number 2, parameter number 3).
CWWBV4243E
The XSD type definition ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, matching part or element ''4'').
CWWBV4244E
The XSD element declaration ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, matching part or element ''4'').
CWWBV4245E
The element ''0'' cannot be assigned to variable ''1'' because the data type does not match (scope activity ''2'', onEvent event number 3, parameter number 4).
CWWBV4246E
The part ''0'' cannot be assigned to variable ''1'' because the data type does not match (scope activity ''2'', onEvent event number 3, parameter number 4).
CWWBV4247E
The XSD element ''0'' is not mapped to a parameter (scope activity ''1'', onEvent event number 2).
CWWBV4248E
The message-part ''0'' is not mapped to a parameter (scope activity ''1'', onEvent event number 2).
CWWBV4249E
The correlation set ''0'' is used already (scope activity ''1'', onEvent event number 2).
CWWBV4250W
The scope activity ''0'' defines event handlers and is contained in the parallel forEach activity ''1''. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV4251E
The onEvent event, number 0, implements operation ''1'' of portType ''2'', which is already implemented in another onEvent event (scope activity ''3'').
CWWBV4252E
The onEvent event, number 0, does not use a correlation set (scope activity ''1'').
CWWBV4253E
The same operation of the same port type is implemented by process onEvent event number 0. This would result in the standard fault ''bpws:conflictingReceive'' (scope activity ''1'', onEvent event number 2).
CWWBV4254E
The same operation of the same port type is implemented by onEvent event number 0 of the outer scope activity ''1''. This would result in the standard fault ''bpws:conflictingReceive'' (inner scope activity ''2'', onEvent event number 3).
CWWBV4255W
The scope activity ''0'' defines event handlers and is contained in process onEvent event number 1, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV4256W
The inner scope activity ''0'' defines event handlers and is contained in onEvent event number 1 of the outer scope activity ''2'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV4257E
The query properties extension is only allowed for process variables (scope activity ''0'', scope variable ''1'').
CWWBV4258E
The XPath for-, until- or repeatEvery-expression is not valid: 0 (scope activity ''1'', onAlarm event 2).
CWWBV4259E
The XPath correlation set property propertyAlias query is not valid: 0 (scope activity ''1'', onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV4260W
The XPath correlation set property propertyAlias query must not be empty (scope activity ''0'', onEvent event number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV4261W
In onEvent event number 3 from the event handler that is attached to the scope activity ''2'', assigning the ''0'' xsd:anyType typed element to the ''1'' xsd:anySimpleType typed variable might cause a runtime error (parameter number 4).
CWWBV4262W
In onEvent event number 3 of the event handler that is attached to scope activity ''2'', assigning the ''0'' xsd:anyType typed part to the ''1'' xsd:anySimpleType variable might cause a runtime error (parameter number 4).
CWWBV4263W
The XPath for-expression, until-expression, or repeatEvery-expression in onAlarm event number 2 in scope activity ''1'' is not valid: ''0''
CWWBV4266W
The XPath for-expression, until-expression, or repeatEvery-expression in onAlarm event number 2 in scope activity ''1'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV4267W
The XPath correlation set property propertyAlias query is not valid: ''0'' (scope activity ''1'', onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV4270W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (scope activity ''1'', onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV4271E
You cannot specify both the element and messageType attributes for the onEvent element. Remove one of the attributes (0 scope activity, onEvent number 1).
CWWBV4272E
The 0 element was not found (1 scope activity, onEvent number 2).
CWWBV4273E
The variable must not be set because a fromParts element is available (0 scope activity, onEvent event number 1, 2 variable).
CWWBV4274E
The from-specification is not allowed (scope variable ''0'', scope ''1'').
CWWBV4275E
The from-variable ''0'' is not defined (scope variable ''1'', scope ''2'').
CWWBV4276E
The from-part ''0'' was not found (scope variable ''1'', variable ''2'', scope ''3'').
CWWBV4277E
The from-partnerLink ''0'' was not found (scope variable ''1'', scope ''2'').
CWWBV4278E
The query language ''0'' is not supported. It must be one of ''1'' (scope variable ''2'', from-specification, scope ''3'').
CWWBV4279E
The from-query is not valid: 0 (scope variable ''1'', scope ''2'').
CWWBV4280W
In the ''1'' scope variable, the from query is not valid: ''0'' (scope ''2'').
CWWBV4281E
The expression language ''0'' of the expression element is not supported. It must be one of ''1'' (scope variable ''2'', scope ''3'').
CWWBV4282E
The from-expression is not valid: 0 (scope variable ''1'', scope ''2'').
CWWBV4283W
In the scope variable ''1'', the from-expiration expression is not valid: ''0'' (scope ''2'').
CWWBV4284E
The XSD-typed variable ''0'' cannot be used in combination with a property specification. Use a message-typed variable (scope variable ''1'', scope ''2'').
CWWBV4285E
The property ''0'' was not found (scope variable ''1'', scope ''2'').
CWWBV4286E
A matching propertyAlias definition is needed for the property ''0'' and the messageType ''1'' (scope variable ''2'', scope ''3'').
CWWBV4287E
The part must be set in the propertyAlias for the property ''0'' and the messageType ''1'' (scope variable ''2'', scope ''3'').
CWWBV4288E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (scope variable ''3'', scope ''4'').
CWWBV4289E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (scope variable ''2'', scope ''5'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV4290W
The from property propertyAlias query must not be empty (scope variable ''0'', scope ''3'', propertyAlias for the property ''1'' and the messageType ''2'').
CWWBV4291E
The propertyAlias query which is referenced with the from property is not valid: 0 (scope variable ''1'', scope ''4'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV4292W
In the ''1'' process variable, the XPath query used in the assign from property ''2'' is not valid: ''0'' (scope ''4'', messageType 3).
CWWBV4293E
Part ''0'' referenced in the propertyAlias definition for property ''1'' and messageType ''2'' must reference a valid XML schema simple type (scope variable ''3'', scope ''4'').
CWWBV4294E
The type of part ''0'' of messageType ''1'' and the type of the property ''2'' must be the same XML schema type (scope variable ''3'', scope ''4'').
CWWBV4295E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (scope variable ''2'', scope ''3'').
CWWBV4296E
The messageType of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from messageType ''2'', to messageType ''3'').
CWWBV4297E
The message-typed from-variable ''0'' cannot be assigned to the type-typed or element-typed scope variable ''1'' (scope ''4'', from messageType ''2'', to type/element ''3'').
CWWBV4298E
The XSD type definition ''0'' is not valid (scope variable ''1'', scope ''2'').
CWWBV4299E
The XSD type definition ''0'' was not found (scope variable ''1'', scope ''4'', base type ''2'', type referencing the type that was not found ''3'').
CWWBV4400E
The expression language ''0'' of the condition element is not supported. It must be one of ''1'' (switch activity ''2'', case element number 3).
CWWBV4401E
The condition expression is not valid (switch activity ''0'', case element number 1, expression language ''2'').
CWWBV4402E
The XPath case condition is not valid: 0 (switch activity ''1'', case element number 2).
CWWBV4403W
The XPath case condition in case element number 2 of the ''1'' switch activity is not valid: ''0''
CWWBV4406W
The XPath case condition in case element number 2 of switch activity ''1'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (switch activity ''1'', case element number 2).
CWWBV4500E
The fault variable ''0'' is not defined (throw activity ''1'').
CWWBV4600E
The wait activity must specify a for-expression or an until-expression (wait activity ''0'').
CWWBV4601E
The wait activity specifies a for-expression and an until-expression (wait activity ''0'').
CWWBV4602E
The wait activity must specify a for expression, an until expression or a timeout expression (wait activity ''0'').
CWWBV4603E
The wait activity specifies more than one expression (wait activity ''0'').
CWWBV4604E
The expression language ''0'' is not supported. It must be one of ''1'' (wait activity ''2'').
CWWBV4605E
The XPath for- or until-expression is not valid: 0 (wait activity ''1'').
CWWBV4606W
In the ''1'' wait activity, the XPath for-expression or until-expression is not valid: ''0''
CWWBV4609W
In the ''1'' wait activity, the XPath for-expression or until-expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV4700E
The expression language ''0'' of the condition element is not supported. It must be one of ''1'' (while activity ''2'').
CWWBV4701E
The condition expression is not valid (while activity ''0'', expression language ''1'').
CWWBV4702E
The XPath while condition is not valid: 0 (while activity ''1'').
CWWBV4703W
In the ''1'' while activity, the XPath while condition is not valid: ''0''
CWWBV4706W
In the ''1'' while activity, the XPath while condition is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV4800E
The namespace of the custom activity ''0'' is not valid: ''http://'' is missing or ''http:///'' is used (used namespace ''1'', element name ''2'').
CWWBV4801E
The plug-in found for the custom activity ''0'' does not implement the expected interface (found plug-in ''1'').
CWWBV4802E
An exception occurred when the plug-in for the custom activity ''0'' was loaded (exception ''1'').
CWWBV4803E
0 (custom activity ''1'', plug-in ''2'').
CWWBV4804W
0 (custom activity ''1'', plug-in ''2'').
CWWBV4805I
0 (custom activity ''1'', plug-in ''2'').
CWWBV4806E
The result returned from the plug-in validation is not valid: 0 (custom activity ''1'', plug-in ''2'').
CWWBV4900E
The portType must be set (human task activity ''0'').
CWWBV4901E
The adminTask element is not allowed (human task activity ''0'').
CWWBV4902E
The human task ''0'' is not a To-do task (human task activity ''1'').
CWWBV4903E
The name of the human task activity and the referenced participating human task must be the same (human task activity ''0'', participating human task ''1'').
CWWBV4904E
The operation must be a request-response operation (human task activity ''0'', operation ''1'').
CWWBV4905E
The process contains a human task that contains errors (human task name ''0'').
CWWBV4906E
A human task cannot contain both a compensation handler and an undo action (human task ''0'').
CWWBV4907E
An expiration element cannot be set for the undo action (human task ''0'').
CWWBV4908E
The message-part ''0'' is not mapped to a parameter (undo action of human task ''1'').
CWWBV4909E
The XSD element ''0'' is not mapped to a parameter (undo action of human task ''1'').
CWWBV4910E
The variable ''0'' cannot be used multiple times in the same input element (input element of the undo action of human task ''1'', parameter number 2).
CWWBV4911E
The message-typed variable cannot be used here (input element of the undo action of human task ''0'', parameter number 1, variable ''2'').
CWWBV4912E
The variable ''0'' used in the undo action is not defined (input element of the undo action of human task ''1'', parameter number 2).
CWWBV4913E
The parameter ''0'' is not mapped to an element or part (undo action of human task ''1'', parameter number 2).
CWWBV4914E
The parameter-extension cannot be used for the message ''0'' (undo action of human task ''1'').
CWWBV4915E
The XSD-typed variable cannot be used in the undo action (human task ''0'', variable ''1'').
CWWBV4916E
The undo action variable ''0'' is not defined (human task ''1'').
CWWBV4917E
The inputVariable attribute of the undo action must not be set because an undo action input element is available (human task ''0'', undo action inputVariable ''1'').
CWWBV4918E
The undo action must specify a variable if the human task specifies a variable by using the parameter extension (invoke activity ''0'').
CWWBV4919E
The messageType of the variable ''0'' and the input element of the undo action operation ''1'' must be the same (human task ''2'').
CWWBV4920E
The messageType ''0'' that is referenced in the input element of the undo action operation ''1'' is not defined (human task ''2'').
CWWBV4921E
The input element is not defined in the undo action operation ''0'' (human task ''1'').
CWWBV4922E
The operation ''0'' referenced in the undo action was not found (human task ''1'').
CWWBV4923E
The portType attribute referenced in the undo action of the human task ''0'' and in the partnerRole role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV4924E
The portType ''0'' referenced in the undo action was not found (human task ''1'').
CWWBV4925E
The undo action partnerLink ''0'' does not define the partnerRole role (human task ''1'').
CWWBV4926E
The partnerLink ''0'' referenced in the undo action was not found (human task ''1'').
CWWBV4927E
The XSD type definition ''0'' was not found (undo action of human task ''1'', parameter number 2, matching part or element ''3'').
CWWBV4928W
In the undo action of the ''2'' human task, parameter number 3, assigning the ''0'' xsd:anyType typed variable to the ''1'' xsd:anySimpleType typed element or part might cause a runtime error.
CWWBV4929E
The variable ''0'' cannot be assigned to element or part ''1'' because the data type does not match (undo action of human task ''2'', parameter number 3).
CWWBV4930E
The XSD element declaration ''0'' was not found (undo action of human task ''1'', parameter number 2, matching part or element ''3'').
CWWBV5000E
The expression language ''0'' of the startCounterValue element is not supported. It must be one of ''1'' (forEach activity ''2'').
CWWBV5001E
The expression language ''0'' of the finalCounterValue element is not supported. It must be one of ''1'' (forEach activity ''2'').
CWWBV5002E
The expression language ''0'' of the completionCondition element is not supported. It must be one of ''1'' (forEach activity ''2'').
CWWBV5003E
A variable with the name ''0'' must not be defined on the scope activity ''1'', because a variable with that name is defined on that scope activity implicitly in the forEach activity ''2''.
CWWBV5004E
The XPath startCounterValue expression is not valid: 0 (forEach activity ''1'').
CWWBV5005E
The XPath finalCounterValue expression is not valid: 0 (forEach activity ''1'').
CWWBV5006E
The XPath completionCondition expression is not valid: 0 (forEach activity ''1'').
CWWBV5007W
In the ''1'' forEach activity, the XPath completionCondition expression is not valid: ''0''
CWWBV5010W
In the ''1'' forEach activity, the XPath completionCondition expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (forEach activity ''1'').
CWWBV5011W
In the ''1'' forEach activity, the XPath finalCounterValue expression is not valid: ''0''
CWWBV5014W
In the ''1'' forEach activity, the XPath finalCounterValue expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (forEach activity ''1'').
CWWBV5015W
In the ''1'' forEach activity, the XPath startCounterValue expression is not valid: ''0''
CWWBV5018W
In the 1 forEach activity, the XPath startCounterValue expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (forEach activity ''1'').
CWWBV6000E
The XSD-typed variable can only use inline defined query properties (process variable ''0'', queryProperty element number 1, referenced property ''2'').
CWWBV6001E
The property ''0'' is already used as query property in this variable (process variable ''1'', queryProperty element number 2).
CWWBV6002E
The property ''0'' is referenced to be used as query property, but attribute ''name'', ''type'' and/or ''part'' and/or a query expression is specified (process variable ''1'', queryProperty element number 2).
CWWBV6003E
The queryProperty element, number 0, must either reference an existing property or define an inline property (process variable ''1'').
CWWBV6004E
The inline defined query property does not specify a name (process variable ''0'', queryProperty element number 1).
CWWBV6005E
The inline defined query property ''0'' does not specify the type (process variable ''1'', queryProperty element number 2).
CWWBV6006E
The type of the referenced property ''0'' is not set (process variable ''1'', queryProperty element number 2).
CWWBV6007E
The type ''0'' of the referenced property ''1'' was not found or is not an allowed or valid XML schema simple type in this context (process variable ''2'', queryProperty element number 3).
CWWBV6008E
A matching propertyAlias definition was not found for the referenced property ''0'' and the messageType ''1'' (process variable ''2'', queryProperty element number 3).
CWWBV6009E
The part ''0'' was not found referenced in the propertyAlias for the referenced property ''1'' and the messageType ''2'' (process variable ''3'', queryProperty element number 4).
CWWBV6010E
The part ''0'' does not reference a valid XML schema simple type (process variable ''1'', queryProperty element number 2, part referenced in the propertyAlias for the referenced property ''3'' and the messageType ''4'').
CWWBV6011E
The type of part ''0'' of messageType ''1'' and property ''2'' are not the same (process variable ''3'', queryProperty element number 4).
CWWBV6012E
Multiple propertyAlias definitions were found for referenced property ''0'' and messageType ''1'' (process variable ''2'', queryProperty element number 3).
CWWBV6013E
The part is not set in the propertyAlias for referenced property ''0'' and messageType ''1'' (process variable ''2'', queryProperty element number 3).
CWWBV6014E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (process variable ''2'', queryProperty element number 3, propertyAlias for the referenced property ''4'' and the messageType ''5'').
CWWBV6015E
The type ''0'' was not found or is not an allowed or valid XML schema simple type in this context (process variable ''1'', queryProperty element number 2, inline defined query property ''3'').
CWWBV6016E
The inline defined query property ''0'' must specify the part, because the variable is message-typed (process variable ''1'', queryProperty element number 2, messageType ''3'').
CWWBV6017E
The inline defined query property ''0'' specifies a part, but the variable is not message-typed (process variable ''1'', queryProperty element number 2).
CWWBV6018E
The part ''0'' was not found in the messageType ''1'' (process variable ''2'', queryProperty element number 3, inline defined query property ''4'').
CWWBV6019E
The part ''0'' does not reference a valid XML schema simple type (process variable ''1'', queryProperty element number 2, inline defined query property ''3'', messageType ''4'').
CWWBV6020E
The query language ''0'' is not supported. It must be one of ''1'' (process variable ''2'', queryProperty element number 3, inline defined query property ''4'').
CWWBV6021E
The part must be the same as the part ''0'' as specified in process variable ''1'', in queryProperty element number 2 (process variable ''3'', queryProperty element number 4, inline defined query property ''5'').
CWWBV6022E
The query must be the same as the query specified in process variable ''0'' in queryProperty element number 1 (process variable ''2'', queryProperty element number 3, inline defined query property ''4'').
CWWBV6023E
The property type of the inline defined query property ''0'' must be ''1'' as specified in process variable ''2'' in queryProperty element number 3 (process variable ''4'', queryProperty element number 5).
CWWBV6024E
The XPath queryProperty propertyAlias query is not valid: 0 (process variable ''1'', queryProperty element number 2, propertyAlias for referenced property ''3'' and messageType ''4'').
CWWBV6025E
The XPath queryProperty query is not valid: 0 (process variable ''1'', queryProperty element number 2, inline defined query property ''3'').
CWWBV6026E
The XPath for-, until- or repeatEvery-expression is not valid: 0 (process onAlarm event 1).
CWWBV6027E
The XPath correlation set property propertyAlias query is not valid: 0 (process onEvent event number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6028W
The XPath queryProperty propertyAlias query must not be empty (process variable ''0'', queryProperty element number 1, propertyAlias for the referenced property ''2'' and the messageType ''3'').
CWWBV6029W
The XPath correlation set property propertyAlias query must not be empty (process onEvent event number 0, correlation set ''1'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV6030W
In process onAlarm event number 1, the XPath for-expression, until-expression, or repeatEvery-expression is not valid: ''0''.
CWWBV6033W
In process onAlarm event number 1, the XPath for-expression, until-expression, or repeatEvery-expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV6034W
The XPath queryProperty propertyAlias query is not valid: ''0'' (process variable ''1'', queryProperty element number 2, propertyAlias for the referenced property ''3'' and the messageType ''4'').
CWWBV6037W
The XPath queryProperty propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (process variable ''1'', queryProperty element number 2, propertyAlias for the referenced property ''3'' and the messageType ''4'').
CWWBV6038W
For the process variable ''1'', queryProperty element number 2 points to the inline defined query property ''3'', which is not valid: ''0''
CWWBV6041W
For the process variable ''1'', queryProperty element number 2 points to the inline defined query property ''3'', which is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV6042W
The XPath correlation set property propertyAlias query is not valid: ''0'' (process onEvent event 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6045W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (process onEvent event number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6046W
An administration task cannot be used in a microflow (non-interruptible process). The administration task is defined on the ''0'' activity.
CWWBV6047E
The value of the continueOnError attribute is not valid in this context. For processes, only the value 'yes' or 'no' is allowed.
CWWBV6048W
Deprecation: The 0 role defines a portType element. This use is deprecated. Use the portType attribute instead. (1 process partnerLink, 2 partnerLinkType).
CWWBV6049E
The 0 role defines a portType element and a portType attribute. You must use only a portType attribute. (1 process partnerLink, 2 partnerLinkType)
CWWBV6050E
The 0 element was not found (process onEvent event 1).
CWWBV6051E
The onEvent element cannot specify both element and messageType attributes. Remove one of the attributes (process onEvent event 0).
CWWBV6052W
The catch requires that a fault variable as the defined fault ''0'' has associated fault data. (fault handler of activity ''1'', catch element number 2).
CWWBV6053W
The fault name ''0'' does not exist in the operation ''1''. (fault handler of activity ''2'', catch element number 3).
CWWBV6054W
The fault message type ''0'' does not match the message type of fault data of the fault name ''1'' (fault handler of activity ''2'', catch element number 3).
CWWBV6055E
The from-specification is not allowed (process variable ''0'').
CWWBV6056E
The from-variable ''0'' is not defined (process variable ''1'').
CWWBV6057E
The from-part ''0'' was not found (process variable ''1'', variable ''2'').
CWWBV6058E
The from-partnerLink ''0'' was not found (process variable ''1'').
CWWBV6059E
The query language ''0'' is not supported. It must be one of ''1'' (process variable ''2'', from-specification).
CWWBV6060E
The from-query is not valid: 0 (process variable ''1'').
CWWBV6061W
In the ''1'' process variable, the from query is not valid: ''0''
CWWBV6062E
The expression language ''0'' of the expression element is not supported. It must be one of ''1'' (process variable ''2'').
CWWBV6063E
The from-expression is not valid: 0 (process variable ''1'').
CWWBV6064W
In process variable ''1'', the from-expiration expression is not valid: ''0''
CWWBV6065E
The XSD-typed variable ''0'' cannot be used in combination with a property specification. Use a message-typed variable (process variable ''1'').
CWWBV6066E
The property ''0'' was not found (process variable ''1'').
CWWBV6067E
A matching propertyAlias definition is needed for the property ''0'' and the messageType ''1'' (process variable ''2'').
CWWBV6068E
The part must be set in the propertyAlias for the property ''0'' and the messageType ''1'' (process variable ''2'').
CWWBV6069E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (process variable ''3'').
CWWBV6070E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (process variable ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6071W
The from property propertyAlias query must not be empty (process variable ''0'', propertyAlias for the property ''1'' and the messageType ''2'').
CWWBV6072E
The propertyAlias query which is referenced with the from property is not valid: 0 (process variable ''1'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV6073W
In the ''1'' process variable, the XPath query used in the assign from property ''2'' is not valid: ''0'' (messageType 3).
CWWBV6074E
Part ''0'' referenced in the propertyAlias definition for property ''1'' and messageType ''2'' must reference a valid XML schema simple type (process variable ''3'').
CWWBV6075E
The type of part ''0'' of messageType ''1'' and the type of the property ''2'' must be the same XML schema type (process variable ''3'').
CWWBV6076E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (process variable ''2'').
CWWBV6077E
The messageType of the from-variable ''0'' and the process variable ''1'' must be the same (from messageType ''2'', to messageType ''3'').
CWWBV6078E
The message-typed from-variable ''0'' cannot be assigned to the type-typed or element-typed process variable ''1'' (from messageType ''2'', to type/element ''3'').
CWWBV6079E
The XSD type definition ''0'' is not valid (process variable ''1'').
CWWBV6080E
The XSD type definition ''0'' was not found (process variable ''1'', base type ''2'', type referencing the type that was not found ''3'').
CWWBV6081W
Assigning the xsd:anyType typed from-variable ''0'' to the xsd:anySimpleType typed process variable ''1'' might result in a runtime error (from XSD type ''2'', to XSD type ''3'').
CWWBV6082E
The XSD type of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD type ''2'', to XSD type ''3'').
CWWBV6083E
The type-typed from-variable ''0'' cannot be assigned to the message-typed process variable ''1'' (from type ''2'', to messageType ''3'').
CWWBV6084E
The XSD type definition ''0'' was not found (process variable ''1'', element referencing the type that was not found ''2'').
CWWBV6085E
The type of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD type ''2'', to XSD element ''3'').
CWWBV6086E
The XSD element of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD element ''2'', to XSD element ''3'').
CWWBV6087E
The element-typed from-variable ''0'' cannot be assigned to the messageType-typed process variable ''1'' (from element ''2'', to messageType ''3'').
CWWBV6088E
The type of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD element ''2'', to XSD type ''3'').
CWWBV6089E
The XSD-typed part ''0'' cannot be assigned to the message-typed process variable ''1''.
CWWBV6090E
The XSD type definition ''0'' was not found (process variable ''1'', from variable ''2'', part ''3'').
CWWBV6091E
The XSD type of the from-part ''0'' and the process variable ''1'' must be the same (from XSD type ''2'', to XSD type ''3'').
CWWBV6092E
The XSD element declaration ''0'' was not found (process variable ''1'', from variable ''2'', part ''3'').
CWWBV6093E
The literal type ''0:1'' is not allowed (process variable ''2'', from-specification).
CWWBV6094E
A literal value is not defined (process variable ''0'', from-specification).
CWWBV6095E
The literal value is not of the type ''0'' (process variable ''1'', from-specification).
CWWBV6096E
The derived type of the 0 from variable and the type of the 1 process variable are not the same. (2 from XSD type, 3, to XSD type).
CWWBV6097E
The type of the 0 from variable contains a chain of derivations with mixed derivation types. (1 process variable, 2 from XSD type).
CWWBV6098E
The type of the 0 from variable derives a type that disallows the used derivation. ( 1 process variable, 2 from XSD type, 3, to XSD type).
CWWBV6099E
The 0 element or part with a derived type cannot be assigned to the 1 variable because the data type does not match (process onEvent event number 2, parameter number 3).
CWWBV6100E
The type of the 0 element or part contains a chain of derivations with mixed derivation types. (1 to variable, process onEvent event number 2, parameter number 3).
CWWBV6101E
The type of the 0 from variable derives a type that disallows the used derivation. (1 to variable, process onEvent event number 2, parameter number 3).
CWWBV6102E
The derived data type of the 0 from part and the 1 process variable are not the same (2 from XSD type, 3 to XSD type).
CWWBV6103E
The derived data type of the 0 from part contains a chain of derivations with mixed derivation types. (1 process variable, 2 from XSD type, 3 to XSD type)
CWWBV6104E
The type of the 0 from part derives a type that disallows the used derivation. (1 process variable, 2 from XSD type, 3 to XSD type)
CWWBV6300E
The 0 expression language of the condition element is not supported. It must be one of 1 (2 RepeatUntil activity).
CWWBV6301E
The condition expression is not valid (0 RepeatUntil activity, 1 expression language).
CWWBV6302E
The XML Path Language (XPath) RepeatUntil condition is not valid. The error is: 0 (1 RepeatUntil activity).
CWWBV6303W
In the 1 RepeatUntil activity, the XML Path Language (XPath) RepeatUntil condition is not valid. The error is: 0
CWWBV6400W
Assigning the xsd:anyType typed from-variable ''0'' to the xsd:anySimpleType typed scope variable ''1'' might result in a runtime error (scope ''4'', from XSD type ''2'', to XSD type ''3'').
CWWBV6401E
The XSD type of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD type ''2'', to XSD type ''3'').
CWWBV6402E
The type-typed from-variable ''0'' cannot be assigned to the message-typed scope variable ''1'' (scope ''4'', from type ''2'', to messageType ''3'').
CWWBV6403E
The XSD type definition ''0'' was not found (scope variable ''1'', scope ''3'', element referencing the type that was not found ''2'').
CWWBV6404E
The type of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD type ''2'', to XSD element ''3'').
CWWBV6405E
The XSD element of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD element ''2'', to XSD element ''3'').
CWWBV6406E
The element-typed from-variable ''0'' cannot be assigned to the messageType-typed scope variable ''1'' (scope ''4'', from element ''2'', to messageType ''3'').
CWWBV6407E
The type of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD element ''2'', to XSD type ''3'').
CWWBV6408E
The XSD-typed part ''0'' cannot be assigned to the message-typed scope variable ''1'' (scope ''2'').
CWWBV6409E
The XSD type definition ''0'' was not found (scope variable ''1'', scope ''4'', from variable ''2'', part ''3'').
CWWBV6410E
The XSD type of the from-part ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD type ''2'', to XSD type ''3'').
CWWBV6411E
The XSD element declaration ''0'' was not found (scope variable ''1'', scope ''4'', from variable ''2'', part ''3'').
CWWBV6412E
The literal type ''0:1'' is not allowed (scope variable ''2'', from-specification, scope ''3'').
CWWBV6413E
A literal value is not defined (scope variable ''0'', from-specification, scope ''1'').
CWWBV6414E
The literal value is not of the type ''0'' (scope variable ''1'', from-specification, scope ''2'').
CWWBV6415E
The derived type of the 0 from variable and the 1 scope variable are not the same (4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV6416E
The type of the 0 from variable contains a chain of derivations with mixed derivation types. (1 scope variable, 2 scope activity, 3 from XSD type).
CWWBV6417E
The type of the 0 from variable derives a type that disallows the used derivation. (1 scope variable, 2 scope activity, 3 from XSD type, 4 to XSD type).
CWWBV6418E
The derived type of the 0 element or the message part cannot be assigned to variable 1 because the data type does not match ((2 scope activity, onEvent event number 3, input number 4).
CWWBV6419E
The type of the 0 element or message part contains a chain of derivations with mixed derivation types. (1 to variable, 2 scope activity, onEvent event number 3, input number 4).
CWWBV6420E
The type of the 0 element or message type derives a type that disallows the used derivation. (1 to variable, 2 scope activity, onEvent event number 3, input number 4).
CWWBV6421E
The derived data type of the 0 from part and the 1 scope variable are not the same (4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV6422E
The derived data type of the 0 from part contains a chain of derivations with mixed derivation types. (1 scope variable, 4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV6423E
The type of the 0 from part derives a type that disallows the used derivation. (1 scope variable, 4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV9000I
Validated the process component model ''0'' successfully: 1 information, 2 warnings, 3 errors.
CWWBV9001I
Validated the process component model ''0'' with findings: 1 information, 2 warnings, 3 errors.
CWWBV9002I
Validated the process component model ''0'' with findings: 1 information, 2 warnings, 3 errors: 4
CWWBV9050E
Process component validation error: ''0''. Error parameters: 1.
CWWBV9051W
Process component validation warning: ''0''. Warning parameters: 1.
CWWBV9052I
Process component validation information: ''0''. Information parameters: 1.
CWWBV9100E
The process component file ''0'' contains at least one interface of the wrong type. Be sure to use only WSDL port type interfaces.
CWWBV9101E
The process component file ''0'' contains a reference ''1'' without an interface.
CWWBV9102E
The process component file ''0'' contains a reference ''1'' with more than one interface.
CWWBV9103E
The process component file ''0'' contains a reference ''1'' with at least one interface of the wrong type. Be sure to use only WSDL port type interfaces.
CWWBV9104E
The process component file ''0'' contains a reference ''1'' that specifies an interface different to the one specified in the process implementation file.
CWWBV9105E
The process component file ''0'' contains an interface ''1'' that does not have a corresponding partnerLink in the process implementation file.
CWWBV9106E
The process component file ''0'' contains a reference ''1'' that does not have a corresponding partnerLink in the process implementation file.
CWWBV9107E
The process component file ''0'' does not contain an interface that corresponds to the inbound partnerLink ''1'' in the process implementation file.
CWWBV9108E
The process component file ''0'' does not contain a reference that corresponds to the outbound partnerLink ''1'' in the process implementation file.
CWWBV9200E
The interface ''1'' in the process component file ''0'' needs the preferredInteractionStyle attribute with a value of ''async''.
CWWBV9201E
The process component file ''0'' requires either the Transaction or the ActivitySession implementation qualifier.
CWWBV9202E
The interface ''1'' in the process component file ''0'' does not specify the mandatory JoinTransaction interface qualifier.
CWWBV9203E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not specify the mandatory JoinTransaction interface qualifier.
CWWBV9204E
The interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
CWWBV9205E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
CWWBV9206E
The interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''true''.
CWWBV9207E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''true''.
CWWBV9208E
The interface ''1'' in the process component file ''0'' specifies the JoinTransaction interface qualifier although it is not allowed in processes running in an activity session.
CWWBV9209E
The operation ''2'' of the interface ''1'' in the process component file ''0'' specifies the JoinTransaction interface qualifier although it is not allowed in processes running in an activity session.
CWWBV9210E
The reference ''1'' in the process component file ''0'' specifies the SuspendTransaction reference qualifier although this qualifier is not allowed in processes that run in an activity session.
CWWBV9211E
The process component file ''0'' must contain the Transaction implementation qualifier with a value of ''global''.
CWWBV9212E
The process component file ''0'' must contain the Transaction implementation qualifier with a value of ''global''.
CWWBV9213E
The process component file ''0'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundary with a value of ''activity session''.
CWWBV9214E
The process component file ''0'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundary with a value of ''activity session''.
CWWBV9215E
The interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed in long-running processes.
CWWBV9216E
The interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed in processes that run in a transaction.
CWWBV9217E
The interface ''1'' in the process component file ''0'' does not specify the mandatory JoinActivitySession interface qualifier.
CWWBV9218E
The interface ''1'' in the process component file ''0'' does not contain the JoinActivitySession interface qualifier with a value of ''true''.
CWWBV9219E
The operation ''2'' of the interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed for processes that run in a transaction.
CWWBV9220E
The operation ''2'' of the interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed in long-running processes.
CWWBV9221E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not specify the mandatory JoinActivitySession interface qualifier.
CWWBV9222E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not contain the JoinActivitySession interface qualifier with a value of ''true''.
CWWBV9223E
The reference ''1'' in the process component file ''0'' specifies the SuspendActivitySession reference qualifier although this qualifier is not allowed in processes that run in a transaction.
CWWBV9224E
The process component file ''0'' specifies the ActivitySession implementation qualifier although it is not allowed in long-running processes.
CWWBV9225E
The process component file ''0'' specifies the ActivitySession implementation qualifier although it is not allowed in processes that run in a transaction.
CWWBV9226E
The process component file ''0'' does not specify the mandatory ActivitySession implementation qualifier.
CWWBV9227E
The process component file ''0'' does not contain an ActivitySession implementation qualifier with a value of ''true''.
CWWBV9228E
The interface ''1'' of the process component file ''0'' specifies the interface qualifier ''2'' more than once.
CWWBV9229E
The reference ''1'' of the process component file ''0'' specifies the reference qualifier ''2'' more than once.
CWWBV9230E
The process component file ''0'' specifies the implementation qualifier ''1'' more than once.
CWWBV9231E
The reference ''1'' in the process component file ''0'' needs the reference qualifier ''Asynchronous Invocation'' with a value of ''commit''.
CWWBV9232E
The reference ''1'' in the process component file ''0'' specifies a multiplicity other than ''1..1''. This is not supported for process component files.
CWWBV9300E
The process implementation file ''1'' referenced by the process component file ''0'' was not found.
CWWBV9301W
The reference ''1'' in the process component file ''0'' is wired to another component, but this component is ignored because the corresponding partnerLink has a process template specified.
CWWBV9302W
In process onEvent event handler number 2, parameter number 3, assigning the ''0'' xsd:anyType typed element to the ''1'' xsd:anySimpleType typed variable might cause a runtime error.
CWWBV9303W
In process onEvent event handler number 2, parameter number 3, assigning the ''0'' xsd:anyType typed part to the ''1'' xsd:anySimpleType typed variable might cause a runtime error.
CWWBV9304I
The activity name ''0'' is already used.
CWWBV9305E
The process inline custom property name ''0'' has been used already. Provide a unique name.
CWWBV0001I
Validated process model ''0'' successfully: 1 warnings, 2 information.
CWWBV0002E
Validated process model ''0'' with findings: 1 errors, 2 warnings, 3 information.
CWWBV0003E
Validated process model ''0'' with findings: 1 errors, 2 warnings, 3 information: 4
CWWBV0004E
A syntactical error was found (row: 0, column: 1): 2
CWWBV0005W
A syntactical warning was found (row: 0, column: 1): 2
CWWBV0006E
The BPEL resource cannot be loaded.
CWWBV0007E
The file could not be read. Detail message: ''0''.
CWWBV0050E
BPEL validation error: 0.
CWWBV0051W
BPEL validation warning: 0.
CWWBV0052I
BPEL validation information: 0.
CWWBV0101E
The process element must contain an activity.
CWWBV0102E
The catch element must contain an activity (process fault handler, catch element number 0).
CWWBV0103E
The catchAll element must contain an activity (process fault handler).
CWWBV0104E
The onEvent event must contain an activity (process event handler, onEvent event number 0).
CWWBV0105E
The onAlarm event must contain an activity (process event handler, onAlarm event 0).
CWWBV0106E
The partnerLinkType must be set (process partnerLink ''0'').
CWWBV0107E
The partnerLink attribute for onEvent event number 0 is missing.
CWWBV0108E
The operation attribute must be set (process event handler, onEvent event number 0).
CWWBV0109E
The parameter variable must be set (process event handler, input/output element of onEvent event number 0, parameter number 1, parameter name ''2'').
CWWBV0110E
The correlation set must refer to at least one property (correlation set ''0'').
CWWBV0111E
The name attribute must be set (process adminTask or activityAdminTask element).
CWWBV0112E
The name attribute must be set (process event handler, onEvent event number 0, task element).
CWWBV0113E
The duration attribute on the timeout element must be set (process onAlarm event 0).
CWWBV0114E
The correlation ''set'' attribute must be set (process event handler, onEvent event number 0, correlation element number 1).
CWWBV0200E
The catch element must contain an activity (fault handler of activity ''0'', catch element number 1).
CWWBV0201E
The catchAll element must contain an activity (fault handler of activity ''0'').
CWWBV0202E
The compensation handler must contain an activity (compensation handler of activity ''0'').
CWWBV0203E
The partnerLink attribute must be set (activity ''0'').
CWWBV0204E
The operation for the ''0'' activity is missing.
CWWBV0205E
The duration attribute of the timeout element must be set (activity ''0'').
CWWBV0206E
The parameter variable must be set (input/output element of activity ''0'', parameter number 1, parameter name ''2'').
CWWBV0207E
The name attribute must be set (activity ''0'', adminTask element).
CWWBV0208E
The name attribute must be set (activity ''0'', task element).
CWWBV0209E
The correlation ''set'' attribute must be set (activity ''0'', correlation element number 1).
CWWBV0210E
An exception occurred when using the XML Path Language (XPath) plug-in for the 0 XPAth expression on the 1 activity (exception 2).
CWWBV0211E
The toVariable or fromVariable attribute in the fromPart or toPart element must be set (0 activity, fromPart or toPart number 1).
CWWBV0212E
The part attribute in the fromPart or toPart element must be set (0 activity, fromPart or toPart number 1).
CWWBV0300E
The assign activity must contain a copy element (assign activity ''0'').
CWWBV0301E
The copy element must contain a from-element (assign activity ''0'', copy element number 1).
CWWBV0302E
The copy element must contain a to-element (assign activity ''0'', copy element number 1).
CWWBV0303E
The reference-scheme attribute must be set (assign activity ''0'', copy element number 1, from-spec, serviceRef element).
CWWBV0304E
The serviceRef element cannot be empty (assign activity ''0'', copy element number 1, from-spec, serviceRef element).
CWWBV0400E
The target attribute must be set (0 compensateScope activity).
CWWBV0600E
The ''0'' Flow activity does not contain an activity.
CWWBV0650E
The generalized flow activity must contain an activity. Add an activity to it (generalized flow activity ''0'').
CWWBV0700E
The partnerLink attribute of the undo action must be set (invoke activity ''0'').
CWWBV0701E
The operation attribute of the undo action must be set (invoke activity ''0'').
CWWBV0702E
The parameter variable for the undo action must be set (input/output element of invoke activity ''0'', parameter number 1, parameter name ''2'').
CWWBV0800E
The pick activity must contain an onMessage element (pick activity ''0'').
CWWBV0801E
The onMessage element, number 1, in pick activity ''0'' is missing an activity.
CWWBV0802E
The onAlarm event must contain an activity (pick activity ''0'', onAlarm event 1).
CWWBV0803E
The partnerLink attribute for OnMessage element number 1 in pick activity ''0'' is missing.
CWWBV0804E
The operation attribute for OnMessage element number 1 in pick activity ''0'' is missing.
CWWBV0805E
The parameter variable must be set (pick activity ''0'', input/output element of onMessage element number 1, parameter number 2, parameter name ''3'').
CWWBV0806E
The name attribute must be set (pick activity ''0'', onMessage element number 1, task element).
CWWBV0807E
The duration attribute on the timeout element must be set (pick activity ''0'', onAlarm event 1).
CWWBV0808E
The correlation ''set'' attribute must be set (pick activity ''0'', onMessage element number 1, correlation element number 2).
CWWBV1200E
The ''0'' scope activity must contain an activity.
CWWBV1201E
The onEvent event must contain an activity (event handler of scope activity ''0'', onEvent event number 1).
CWWBV1202E
The onAlarm event must contain an activity (event handler of scope activity ''0'', onAlarm event 1).
CWWBV1203E
The partnerLink attribute must be set (scope activity ''0'', onEvent event number 1).
CWWBV1204E
The operation attribute must be set (scope activity ''0'', onEvent event number 1).
CWWBV1205E
The parameter variable must be set (scope activity ''0'', input/output element of onEvent event number 1, parameter number 2, parameter name ''3'').
CWWBV1206E
The name attribute must be set (scope activity ''0'', onEvent event 1, task element).
CWWBV1207E
The duration attribute on the timeout element must be set (scope activity ''0'', onAlarm event 1).
CWWBV1208E
The correlation ''set'' attribute must be set (scope event handler, of scope activity ''0'', onEvent event number 1, correlation element number 2).
CWWBV1300E
The sequence activity must contain an activity (sequence activity ''0'').
CWWBV1400E
The switch activity must contain a case element (switch activity ''0'').
CWWBV1401E
Case element number 1 in Switch activity ''0'' does not specify a condition.
CWWBV1402E
Case element number 1 in Switch activity ''0'' does not contain an activity.
CWWBV1403E
The otherwise element must contain an activity (switch activity ''0'').
CWWBV1500E
The throw activity requires a faultName attribute (throw activity ''0'').
CWWBV1700E
The ''0'' While activity does not specify a condition.
CWWBV1701E
The ''0'' While activity does not contain an activity.
CWWBV1950E
The forEach activity requires a counterName attribute (forEach activity ''0'').
CWWBV1951E
The forEach activity must contain a startCounterValue element (forEach activity ''0'').
CWWBV1952E
The forEach activity must contain a finalCounterValue element (forEach activity ''0'').
CWWBV1953E
The forEach activity must contain a scope activity (forEach activity ''0'').
CWWBV2000E
The 0 RepeatUntil activity does not specify a condition.
CWWBV2001E
The 0 RepeatUntil activity does not contain an activity.
CWWBV3000E
The schemaLocation attribute is not set. It must be one of ''0''.
CWWBV3001E
The value of the schemaLocation attribute is incorrect. It must be set to one of ''0'', or a value handled by a custom activity plug-in.
CWWBV3002E
The partnerLinkType ''0'' was not found (process partnerLink ''1'').
CWWBV3003E
The myRole role ''0'' was not found (process partnerLink ''1'', partnerLinkType ''2'').
CWWBV3004E
The portType in the role ''0'' is not set (process partnerLink ''1'', partnerLinkType ''2'').
CWWBV3005E
The portType ''0'' was not found (process partnerLink ''1'', partnerLinkType ''2'', role ''3'').
CWWBV3006E
The partnerRole role ''0'' was not found (process partnerLink ''1'', partnerLinkType ''2'').
CWWBV3007E
Either the myRole role, the partnerRole role, or both must be defined (process partnerLink ''0'').
CWWBV3008E
There are too many variable type definitions set for the process variable ''0'' (messageType ''1'', type ''2'', element ''3'').
CWWBV3009E
The process variable ''0'' must have a variable type definition.
CWWBV3010E
The messageType ''0'' was not found (process variable ''1'').
CWWBV3011E
The XSD type definition ''0'' was not found (process variable ''1'').
CWWBV3012E
The XSD element declaration ''0'' was not found (process variable ''1'').
CWWBV3013E
The process variable name ''0'' is used already.
CWWBV3014E
The catch element must have a fault name, a fault variable with a type specification, or both of these attributes set (process fault handler, catch element number 0).
CWWBV3015E
If the catch element has the fault variable set, it must also have a type specification set (process fault handler, catch element number 0, fault variable ''1'').
CWWBV3016E
The catch element cannot have the fault message type and the fault type set (process fault handler, catch element number 0, fault message type ''1'', faultType ''2'').
CWWBV3017E
If the catch element has the fault message type set, it must also have a fault variable set (process fault handler, catch element number 0, fault message type ''1'').
CWWBV3018E
If the catch element has the fault type set, it must also have a fault variable set (process fault handler, catch element number 0, fault type ''1'').
CWWBV3019E
The messageType ''0'' was not found (process fault handler, catch element number 1, fault variable ''2'').
CWWBV3020E
The type ''0'' was not found (process fault handler, catch element number 1, fault variable ''2'').
CWWBV3021E
The process fault handler must contain a catch element or a catchAll element.
CWWBV3023E
The display ID ''0'' is not unique.
CWWBV3024W
The microflow specifies the autonomy attribute. The attribute will be ignored.
CWWBV3025W
The macroflow specifies the compensationSphere attribute. The attribute will be ignored.
CWWBV3026E
The process event handler must contain an onEvent event or an onAlarm event.
CWWBV3027E
The partnerLink ''0'' was not found (process onEvent event 1).
CWWBV3028E
The partnerLink ''0'' does not define the myRole role (process onEvent event number 1).
CWWBV3029E
The portType ''0'' was not found (process onEvent event 1).
CWWBV3030E
The portType referenced in process onEvent event number 0 and in the myRole role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV3031E
The operation ''0'' was not found (process onEvent event 1).
CWWBV3032E
The input element is not defined in the operation ''0'' (process onEvent event number 1).
CWWBV3033E
The messageType is not set in the input element of the operation ''0'' (process onEvent event number 1).
CWWBV3034E
The messageType ''0'' referenced in the operation ''1'' was not found (process onEvent event number 2).
CWWBV3035E
The messageType of variable ''0'' and the input element of the operation ''1'' must be the same (process onEvent event number 2).
CWWBV3036E
The variable is not set (process onEvent event number 0).
CWWBV3037E
The messageType or element attribute is not set (process onEvent event number 0).
CWWBV3038E
The messageType ''0'' was not found (process onEvent event 1).
CWWBV3039E
The correlation set ''0'' was not found (process onEvent event 1).
CWWBV3040E
The process onAlarm event must specify at least a for expression, an until expression, or a repeatEvery expression (process onAlarm event 0).
CWWBV3041E
The process onAlarm event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (process onAlarm event 0).
CWWBV3042E
The process onAlarm event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (process onAlarm event 0).
CWWBV3043E
The expression language ''0'' is not supported. It must be one of ''1'' (process onAlarm event 2).
CWWBV3044E
The process query language ''0'' is not supported. It must be one of ''1''.
CWWBV3045E
The process expression language ''0'' is not supported. It must be one of ''1''.
CWWBV3046E
The property ''0'' was not found (process correlation set ''1'').
CWWBV3047E
The type of the property ''0'' is not set (process correlation set ''1'').
CWWBV3048E
The type ''0'' of the property ''1'' was not found or is not an allowed or valid XML schema simple type in this context (process correlation set ''2'').
CWWBV3049I
The correlation set ''0'' is not used.
CWWBV3050E
The correlation set ''0'' is used, but it is never initiated.
CWWBV3051E
A task activity cannot be used in a microflow (non-interruptible process) (task ''0'').
CWWBV3052E
A wait activity cannot be used in a microflow (non-interruptible process) (wait activity ''0'').
CWWBV3053E
An onAlarm event in a pick activity cannot be used in a microflow (non-interruptible process). The pick activity name is ''0''.
CWWBV3054E
A process that is not long-running must not contain more than one pick or receive activity: ''0''.
CWWBV3055E
The process does not implement the operation ''0'' of the port type ''1''.
CWWBV3056E
The process is not startable. No pick or receive activity was found that creates a new process instance and does not have incoming links or preceding basic activities.
CWWBV3057E
The variable must not be set because an output element is available (process onEvent event number 0, variable ''1'').
CWWBV3058E
Abstract processes are not supported.
CWWBV3059E
The parameter-extension cannot be used for the message ''0''. Modify the message or use a message-type variable (process onEvent event number 1).
CWWBV3060E
The parameter ''0'' is not mapped to an element or part. Map it to a valid element or part (process onEvent event number 1, parameter number 2).
CWWBV3061E
The variable name ''0'' is used already in the same onEvent event. Use another variable name (output element of process onEvent event number 1, parameter number 2).
CWWBV3062E
A matching propertyAlias definition was not found for the property ''0'' and the messageType ''1'' (process onEvent event number 2, correlation set ''3'').
CWWBV3063E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (process onEvent event number 3, correlation set ''4'').
CWWBV3064E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' does not reference a valid XML schema simple type (process onEvent event number 3, correlation set ''4'').
CWWBV3065E
The type of the part ''0'' of the messageType ''1'' and the type of the property ''2'' are not the same (process onEvent event number 3, correlation set ''4'').
CWWBV3066E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (process onEvent event number 2, correlation set ''3'').
CWWBV3067E
The human task ''0'' cannot be found (process adminTask or activityAdminTask element).
CWWBV3068E
The human task ''0'' is not an administration task (process adminTask or activityAdminTask element).
CWWBV3069E
The human task ''0'' cannot be found (process onEvent event number 1).
CWWBV3070E
The human task ''0'' is not an invocation task (process onEvent event number 1).
CWWBV3071E
The portType referenced in process onEvent event number 0 and in the human task ''1'' must be the same.
CWWBV3072E
The operation referenced in process onEvent event number 0 and in the human task ''1'' must be the same.
CWWBV3073E
The part is not set in the propertyAlias for the property ''0'' and the messageType ''1'' (process onEvent event number 2, correlation set ''3'').
CWWBV3074E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (process onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3075E
The expression is not valid (process onAlarm event 0, expression language ''1'').
CWWBV3076E
A reply activity was not found that matches process onEvent event number 0.
CWWBV3077E
An event handler cannot be used in a microflow (non-interruptible process).
CWWBV3078E
An event handler cannot be used in a microflow (non-interruptible process). The scope activity name is ''0''.
CWWBV3079E
A compensation handler cannot be used in a microflow (non-interruptible process). The activity name is ''0''.
CWWBV3080E
An expiration element cannot be used in a microflow (non-interruptible process). The activity name is ''0''.
CWWBV3081E
A compensate activity cannot be used in a microflow (non-interruptible process). The compensate activity name is ''0''.
CWWBV3082W
The one-way process cannot specify the autonomy 'child'. The attribute will be ignored.
CWWBV3083E
More than one variable type definition is set for the variable ''0''. Set only one (process onEvent event number 1, parameter number 2, type ''3'', element ''4'').
CWWBV3084E
The XSD element declaration ''0'' was not found (process onEvent event number 1, parameter number 2, variable ''3'').
CWWBV3085E
The XSD type definition ''0'' was not found (process onEvent event number 1, parameter number 2, variable ''3'').
CWWBV3086E
The variable ''0'' must have a variable type definition (process onEvent event number 1, parameter number 2).
CWWBV3087E
The XSD type definition ''0'' was not found (process onEvent event number 1, parameter number 2, matching part or element ''3'').
CWWBV3088E
The XSD element declaration ''0'' was not found (process onEvent event number 1, parameter number 2, matching part or element ''3'').
CWWBV3089E
The element ''0'' cannot be assigned to variable ''1'' because the data type does not match (process onEvent event number 2, parameter number 3).
CWWBV3090E
The part ''0'' cannot be assigned to variable ''1'' because the data type does not match (process onEvent event number 2, parameter number 3).
CWWBV3091E
The XSD element ''0'' must be mapped to a parameter (process onEvent event number 1).
CWWBV3092E
The message-part ''0'' must be mapped to a parameter (process onEvent event number 1).
CWWBV3093E
The process partnerLink name ''0'' is used already. Use a unique name.
CWWBV3094E
The process correlation set name ''0'' is used already. Use a unique name.
CWWBV3095E
The correlation set ''0'' is used already. It can only be used once (process onEvent event number 1).
CWWBV3096E
The process custom property name ''0'' has been used already. Provide a unique name.
CWWBV3097E
Process onEvent event number 0 implements operation ''1'' of portType ''2'', which is already implemented in another process onEvent event.
CWWBV3098E
Process onEvent event number 0 must use at least one correlation set.
CWWBV3099E
The referenced property ''0'' was not found (process variable ''1'', queryProperty element number 2).
CWWBV3100E
The variable ''0'' is not defined (activity ''1'').
CWWBV3101E
The catch element does not specify a fault name, a fault variable with a type specification, or both (fault handler of activity ''0'', catch element number 1).
CWWBV3102E
If the catch element has the fault variable set, it must also have a type specification set (fault handler of activity ''0'', catch element number 1, fault variable ''2'').
CWWBV3103E
The catch element cannot have the fault message type and the fault type set (fault handler of activity ''0'', catch element number 1, fault message type ''2'', faultType ''3'').
CWWBV3104E
If the catch element has the fault message type set, it must also have a fault variable set (fault handler of activity ''0'', catch element number 1, fault message type ''2'').
CWWBV3105E
If the catch element has the fault type set, it must also have a fault variable set (fault handler of activity ''0'', catch element number 1, fault type ''2'').
CWWBV3106E
The messageType ''0'' was not found (fault handler of activity ''1'', catch element number 2, fault variable ''3'').
CWWBV3107E
The type ''0'' was not found (fault handler of activity ''1'', catch element number 2, fault variable ''3'').
CWWBV3108E
The fault handler must contain a catch element or a catchAll element (fault handler of activity ''0'').
CWWBV3109E
The correlations element is not allowed (activity ''0'').
CWWBV3110E
Fault handlers are not allowed (activity ''0'').
CWWBV3111E
The expiration, script, and undo elements cannot be used in the activity ''0''. These elements are only allowed in invoke activities.
CWWBV3112E
The custom activity element ''0'' cannot be used in the activity ''1''. This element is only allowed in invoke activities.
CWWBV3113E
The task element cannot be used in the activity ''0''.
CWWBV3114E
The annotation element cannot be used in the activity ''0''. This element is only allowed in scope activities.
CWWBV3115E
The timeout element cannot be used in the activity ''0''. This element is only allowed in wait activities.
CWWBV3116E
The input element cannot be used in the activity ''0''. This element is only allowed in invoke and reply activities.
CWWBV3117E
The output element cannot be used in the activity ''0''. This element is only allowed in invoke and receive activities.
CWWBV3118E
The continueOnError attribute cannot be used in the ''0'' activity. It is allowed only in invoke activities.
CWWBV3120E
The compensable attribute cannot be used in the activity ''0''. This attribute is only allowed in scope activities.
CWWBV3121E
The script, task, and custom activity elements are mutually exclusive (invoke activity ''0'').
CWWBV3122E
The link ''0'' is not defined (referenced in the activity ''1'').
CWWBV3123E
The link ''0'' is parallel link-to-link ''1'' (from activity ''2'' to activity ''3''). Parallel links are not allowed.
CWWBV3124E
The XSD-typed variable cannot be used here (activity ''0'', variable ''1'').
CWWBV3125E
The undo action is not allowed (activity ''0'').
CWWBV3126E
The expiration element is not allowed for the activity ''0''.
CWWBV3127W
The expiration element is set for the activity ''0''. Define an appropriate timeout fault handler.
CWWBV3128E
The partnerLink ''0'' was not found (activity ''1'').
CWWBV3129E
The partnerLink ''0'' does not define the myRole role (activity ''1'').
CWWBV3130E
The portType ''0'' was not found (activity ''1'').
CWWBV3131E
The portType referenced in the activity ''0'' and in the role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV3132E
The operation ''0'' was not found (activity ''1'').
CWWBV3133E
The input element is not defined in the operation ''0'' (activity ''1'').
CWWBV3134E
The output element is not defined in the operation ''0'' (activity ''1'').
CWWBV3135E
The messageType is not set in the input element of the operation ''0'' (activity ''1'').
CWWBV3136E
The messageType is not set in the output element of the operation ''0'' (activity ''1'').
CWWBV3137E
The messageType is not set in the fault element of the operation ''0'' (activity ''1'').
CWWBV3138E
The messageType ''0'' referenced in the operation ''1'' was not found (activity ''2'').
CWWBV3139E
The messageType of the variable ''0'' and the input element of operation ''1'' must be the same (activity ''2'').
CWWBV3140E
The messageType of the variable ''0'' and the output element of operation ''1'' must be the same (activity ''2'').
CWWBV3141E
The messageType of the variable ''0'' and the fault ''1'' of the operation ''2'' must be the same (activity ''3'').
CWWBV3142E
The variable is not set (activity ''0'').
CWWBV3143E
The input variable for the ''0'' activity is not specified.
CWWBV3144E
The output variable is not set (activity ''0'').
CWWBV3145E
The output variable ''0'' must not be set, because the operation is one-way (activity ''1'', operation ''2'').
CWWBV3146E
The correlation set ''0'' was not found (activity ''1'').
CWWBV3147E
The onAlarm event must specify at least a for expression, an until expression, or a repeatEvery expression (activity ''0'', onAlarm event 1).
CWWBV3148E
The onAlarm event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (activity ''0'', onAlarm event 1).
CWWBV3149E
The onAlarm event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (activity ''0'', onAlarm event 1).
CWWBV3150E
The expression language ''0'' is not supported. It must be one of ''1'' (activity ''2'', onAlarm event 3).
CWWBV3151E
A matching propertyAlias definition was not found for the property ''0'' and messageType ''1'' (activity ''2'', correlation set ''3'').
CWWBV3152E
The part ''0'' referenced in the propertyAlias definition for the property ''1'' and messageType ''2'' was not found (activity ''3'', correlation set ''4'').
CWWBV3153E
The part ''0'' referenced in the propertyAlias definition for the property ''1'' and messageType ''2'' does not reference a valid XML schema simple type (activity ''3'', correlation set ''4'').
CWWBV3154E
The type of the part ''0'' of the messageType ''1'' and the type of the property ''2'' are not the same (activity ''3'', correlation set ''4'').
CWWBV3155E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (activity ''2'', correlation set ''3'').
CWWBV3156E
Because the pick or receive activity ''0'' creates a process instance, it cannot be placed after the activity or the activities ''1''.
CWWBV3157E
The activity ''0'' is the target of the link or links ''1'', but it can create a process instance or it contains activities that can create a process instance.
CWWBV3158W
The while activity ''1'' contains the pick or receive activity ''0'' that creates a process instance. If the condition of the while activity is false when the condition is evaluated for the first time, the process does not run correctly.
CWWBV3159E
The pick or receive activity ''0'' that creates a process instance cannot be contained in a catch, catchAll, onMessage, onEvent, onAlarm, compensation handler, case, or otherwise element.
CWWBV3160E
The flow activity ''0'' contains one or more activities that can start processes, but it also contains the activity ''1'' which cannot start a process.
CWWBV3161E
The activity ''0'' does not reference the partnerLink ''null'' (used partnerLink ''1'').
CWWBV3162E
The activity ''0'' does not reference the portType ''wpc:null'' (used portType ''1'').
CWWBV3163E
The activity ''0'' does not reference the operation ''null'' (used operation ''1'').
CWWBV3164W
The variable attribute ''0'' is not needed (activity ''1'').
CWWBV3165W
The input element is not needed (activity ''0'').
CWWBV3166W
The output element is not needed (activity ''0'').
CWWBV3167E
The output element must not be set, because the operation is one-way (activity ''0'', operation ''1'').
CWWBV3168E
The inputVariable attribute must not be set because an input element is available (activity ''0'', inputVariable ''1'').
CWWBV3169E
The outputVariable attribute must not be set because an output element is available (activity ''0'', outputVariable ''1'').
CWWBV3170E
The variable ''0'' is not defined (input or output element of activity ''1'', parameter number 2).
CWWBV3171E
The message-typed variable cannot be used here (input/output element of activity ''0'', parameter number 1, variable ''2'').
CWWBV3172E
The variable ''0'' cannot be used multiple times in the same input or output element (input or output element of activity ''1'', parameter number 2).
CWWBV3173E
The human task ''0'' cannot be found (activity ''1'').
CWWBV3174E
The portType that is referenced in the activity ''0'' and in the human task ''1'' must be the same.
CWWBV3175E
The operation that is referenced in the activity ''0'' and in the human task ''1'' must be the same.
CWWBV3176E
The human task ''0'' is not an administration task (activity ''1'').
CWWBV3177E
The part is not set in the propertyAlias definition for the property ''0'' and messageType ''1'' (activity ''2'', correlation set ''3'').
CWWBV3178E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (activity ''2'', correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3179E
The expiration element must specify at least a for expression, an until expression, or a timeout expression (activity ''0'').
CWWBV3180E
The expression language ''0'' of the expiration element is not supported. It must be one of ''1'' (activity ''2'').
CWWBV3181E
The expression language ''0'' of the transition condition is not supported. It must be one of ''1'' (activity ''2'', source element number 3, link ''4'').
CWWBV3182E
The expression language ''0'' of the join condition is not supported. It must be one of ''1'' (activity ''2'').
CWWBV3183E
The transition condition expression is invalid (activity ''0'', source element number 1, link ''2'', expression language ''3'').
CWWBV3184E
The join condition expression is invalid (activity ''0'', expression language ''1'').
CWWBV3185E
The parameter-extension cannot be used for the message ''0'' (activity ''1'').
CWWBV3186E
The parameter ''0'' must be removed or mapped to an element or part (activity ''1'', parameter number 2).
CWWBV3187E
The XSD type definition ''0'' was not found (activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3188E
The XSD element declaration ''0'' was not found (activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3189E
The variable ''0'' cannot be assigned to element or part ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3190E
The element or part ''0'' cannot be assigned to variable ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3191E
The XSD element ''0'' is not mapped to a parameter (activity ''1'').
CWWBV3192E
The message-part ''0'' is not mapped to a parameter (activity ''1'').
CWWBV3193E
The correlation set ''0'' is used already. It can only be used once (activity ''1'').
CWWBV3194E
The custom property name ''0'' is used already. The name can only be used once (activity ''1'').
CWWBV3195E
The forEach activity ''1'' must not contain the pick or receive activity ''0'' that can create a process instance.
CWWBV3196E
The compensation handler is not allowed (activity ''0'').
CWWBV3197E
The XPath transition condition is not valid: 0 (activity ''1'', source element number 2, link ''3'').
CWWBV3198E
The XPath join condition is not valid: 0 (activity ''1'').
CWWBV3199E
The XPath correlation set property propertyAlias query is not valid: 0 (activity ''1'', correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3200E
The XPath for- or until-expiration-expression is invalid: 0 (activity ''1'').
CWWBV3201W
The correlation set property propertyAlias query must not be empty (activity ''0'', correlation set ''1'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV3202W
Assigning the ''0'' xsd:anyType typed element or the part to the 1 xsd:anySimpleType typed variable might result in a runtime error (activity 2, parameter number 3).
CWWBV3203W
Assigning the ''0'' xsd:anyType typed variable to the ''1'' xsd:anySimpleType typed element or part might result in a runtime error (activity ''2'', parameter number 3).
CWWBV3204W
The XPath in the for-expiration expression or until-expiration expression for the ''1'' activity is not valid: ''0''
CWWBV3207W
The XPath in the for- or until-expiration-expression for ''1'' activity is not valid because the ''$'' notation used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3208W
The XPath join condition in the ''1'' activity is not valid: ''0''
CWWBV3211W
The XPath join condition for the activity ''1'' is not valid because the ''$'' notation used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3212W
The XML Path Language (XPath) transition condition for the 3 link, starting from source element number 2 in the 1 activity, is not valid. The error is: 0
CWWBV3215W
The XPath transition condition for the link ''3'', starting from source element number 2 in activity ''1'', is not valid because the ''$'' notation used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3216W
The XPath correlation set property propertyAlias query is not valid: ''0'' (activity ''1'', correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3219W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (activity ''1'', correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3220E
The adminTask elements cannot be used in the activity ''0''. These elements are only allowed in invoke and scope activities.
CWWBV3221W
Deprecation: The 0 expression or query language is deprecated. Use 1 instead (resource 2).
CWWBV3222W
Deprecation: The 0 value of the pattern attribute in the correlation element 1 is deprecated. Use one of the following pattern values: 2 (3 invoke activity).
CWWBV3223E
The pattern attribute in the 0 correlation element of the 1 invoke activity cannot be used for one-way operations.
CWWBV3224E
The 0 variable is not defined (1 activity, fromPart or toPart number 2).
CWWBV3225E
The message-typed variable cannot be used here (0 activity, fromPart or toPart number 1, 2 variable).
CWWBV3226E
The 0 variable cannot be used multiple times in the same fromParts or toParts element (1 activity, fromPart or toPart number 2).
CWWBV3227E
The 0 message part is not mapped to a fromPart or toPart element (1 activity).
CWWBV3228E
The 0 fromPart or toPart must be removed or mapped to an existing message-part (1 activity, fromPart or toPart number 2).
CWWBV3229E
The fromParts or toParts element cannot be used for the 0 message (1 activity).
CWWBV3230W
Assigning the 0 xsd:anyType typed message part to the 1 xsd:anySimpleType typed variable might result in a runtime error (2 activity, fromPart/toPart number 3).
CWWBV3231E
The 0 message part cannot be assigned to the 1 variable because the data type does not match (2 activity, fromPart or toPart number 3).
CWWBV3232E
The 0 activity uses the parameter extension and the fromParts or toParts element. This is not supported.
CWWBV3233E
The inputVariable attribute must not be set because a toParts element is available (0 activity, 1 inputVariable).
CWWBV3234E
The outputVariable attribute must not be set because a fromParts element is available (0 activity, 1 outputVariable).
CWWBV3235E
The variable must not be set because a fromParts element is available (process onEvent event number 0, 1 variable).
CWWBV3236E
The fromParts element must not be set because this is a one-way operation (0 activity, 1 operation).
CWWBV3237E
The transition condition is not allowed on the 0 source activity with the ''fork'' source type (source element number 1, 2 link).
CWWBV3238E
The transactionalBehavior attribute cannot be used in the ''0'' activity. It is allowed only in invoke, receive, and pick activities.
CWWBV3239E
The exit condition expression is invalid (activity ''0'', expression language ''1'').
CWWBV3240E
The expression language ''0'' of the exit condition is not supported. It must be one of ''1'' (activity ''2'').
CWWBV3241W
The XML Path Language (XPath) exit condition for the 1 activity, is not valid. The error is: 0
CWWBV3242E
The XPath exit condition is not valid: 0 (activity ''1'').
CWWBV3243E
The value of the executeAt attribute on an exit condition must not be BOTH or ENTRY on initiating receives (receive ''0'').
CWWBV3244E
The executeAt attribute must be set for an exit condition (activity ''0'').
CWWBV3245E
The otherwise transition condition expression is invalid in this context (activity ''0'', source element number 1, link ''2'').
CWWBV3246W
A variable in a XPath expression must not contain the ''.'' character. (variable ''0'', activity ''1'').
CWWBV3247E
The derived type of the ''0'' variable cannot be assigned to element or part ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3248E
The type of the ''0'' variable contains a chain of derivations with mixed derivation types. (element or part ''1'' ,activity ''2'', parameter number 3).
CWWBV3249E
The type of the ''0'' variable derives a type that disallows the used derivation. (1 activity, parameter number 2, matching part or element: 3).
CWWBV3250E
The derived type of the element or part ''0'' cannot be assigned to variable ''1'' because the data type does not match (activity ''2'', parameter number 3).
CWWBV3251E
The type of the ''0'' element or part contains a chain of derivations with mixed derivation types. (element or part ''1'' ,activity ''2'', parameter number 3).
CWWBV3252E
The type of the ''0'' element or part derives a type that disallows the used derivation. (element or part ''1'' ,activity ''2'', parameter number 3).
CWWBV3253E
The 0 derived message part cannot be assigned to the 1 variable because the data type does not match (2 activity, fromPart or toPart number 3).
CWWBV3254E
The type of the ''0'' message part contains a chain of derivations with mixed derivation types. (1 variable, 2 activity, fromPart or toPart number 3).
CWWBV3255E
The type of the ''0'' message part derives a type that disallows the used derivation. (1 variable, 2 activity, fromPart or toPart number 3).
CWWBV3256E
Inline custom properties are not allowed on activity level.
CWWBV3300E
The from-specification is not allowed (assign activity ''0'', copy element number 1).
CWWBV3301E
The to-specification is not allowed (assign activity ''0'', copy element number 1).
CWWBV3302E
The from-to copy combination is not allowed (assign activity ''0'', copy element number 1).
CWWBV3303E
The from-variable ''0'' is not defined (assign activity ''1'', copy element number 2).
CWWBV3304E
The from-part ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'').
CWWBV3305E
The from-partnerLink ''0'' was not found (assign activity ''1'', copy element number 2).
CWWBV3306E
The to-variable ''0'' is not defined (assign activity ''1'', copy element number 2).
CWWBV3307E
The to-part ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'').
CWWBV3308E
The to-partnerLink ''0'' was not found (assign activity ''1'', copy element number 2).
CWWBV3309E
The to-partnerLink ''0'' does not define the partnerRole role (assign activity ''1'', copy element number 2).
CWWBV3310E
The messageType of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from messageType ''4'', to messageType ''5'').
CWWBV3311E
The XSD type of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3312E
The XSD element of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD element ''4'', to XSD element ''5'').
CWWBV3313E
The type of the from-part ''0'' and the to-part ''1'' must be the same (assign activity ''2'', copy element number 3).
CWWBV3314E
The from-partnerLink ''0'' does not define the myRole role (assign activity ''1'', copy element number 2).
CWWBV3315E
The from-partnerLink ''0'' does not define the partnerRole role (assign activity ''1'', copy element number 2).
CWWBV3316E
The portType of the from-role ''0'' and the to-role ''1'' are not the same (assign activity ''2'', copy element number 3, from partnerLink ''4'', to partnerLink ''5'').
CWWBV3317E
The message-typed from-variable ''0'' cannot be assigned to the type-typed or element-typed to-variable ''1'' (assign activity ''2'', copy element number 3, from messageType ''4'', to type/element ''5'').
CWWBV3318E
The type-typed from-variable ''0'' cannot be assigned to the message-typed to-variable ''1'' (assign activity ''2'', copy element number 3, from type ''4'', to messageType ''5'').
CWWBV3319E
The element-typed from-variable ''0'' cannot be assigned to the messageType-typed to-variable ''1'' (assign activity ''2'', copy element number 3, from element ''4'', to messageType ''5'').
CWWBV3320E
The literal type ''0:1'' is not allowed (assign activity ''2'', copy element number 3, from-specification).
CWWBV3321E
A literal value is not defined (assign activity ''0'', copy element number 1, from-specification).
CWWBV3322E
The literal type in the from element and the part type in the to element are not the same (assign activity ''0'', copy element number 1).
CWWBV3323E
The literal value is not of the type ''0'' (assign activity ''1'', copy element number 2, from-specification).
CWWBV3324E
The XSD type definition ''0'' was not found (assign activity ''1'', copy element number 2, base type ''3'', type referencing the type that was not found ''4'').
CWWBV3325E
The XSD type definition ''0'' is not valid (assign activity ''1'', copy element number 2).
CWWBV3326E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3, propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3327E
Part ''0'' referenced in the propertyAlias definition for property ''1'' and messageType ''2'' must reference a valid XML schema simple type (assign activity ''3'', copy element number 4).
CWWBV3328E
The type of part ''0'' of messageType ''1'' and the type of the property ''2'' must be the same XML schema type (assign activity ''3'', copy element number 4).
CWWBV3329E
The query language ''0'' is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3, from-specification).
CWWBV3330E
The query language ''0'' is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3, to-specification).
CWWBV3331E
The expression language ''0'' of the expression element is not supported. It must be one of ''1'' (assign activity ''2'', copy element number 3).
CWWBV3332E
The XSD-typed variable ''0'' cannot be used in combination with a property specification. Use a message-typed variable (assign activity ''1'', copy element number 2).
CWWBV3333E
The property ''0'' was not found (assign activity ''1'', copy element number 2).
CWWBV3334E
A matching propertyAlias definition is needed for the property ''0'' and the messageType ''1'' (assign activity ''2'', copy element number 3).
CWWBV3335E
The part must be set in the propertyAlias for the property ''0'' and the messageType ''1'' (assign activity ''2'', copy element number 3).
CWWBV3336E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (assign activity ''3'', copy element number 4).
CWWBV3337E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (assign activity ''2'', copy element number 3).
CWWBV3338E
The XSD type definition ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'', part ''4'').
CWWBV3339E
The XSD element declaration ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'', part ''4'').
CWWBV3340E
The XSD-typed part ''0'' cannot be assigned to the message-typed to-variable ''1'' (assign activity ''2'', copy element number 3).
CWWBV3341E
The message-typed from-variable ''0'' cannot be assigned to the XSD-typed part ''1'' (assign activity ''2'', copy element number 3).
CWWBV3342E
The XSD type definition ''0'' was not found (assign activity ''1'', copy element number 2, variable ''3'', element referencing the type that was not found ''4'').
CWWBV3343E
The type of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD element ''5'').
CWWBV3344E
The type of the from-variable ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD element ''4'', to XSD type ''5'').
CWWBV3345E
The XSD type of the from-part ''0'' and the to-variable ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3346E
The XSD type of the from-variable ''0'' and the to-part ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3347E
The XSD type of the from-part ''0'' and the to-part ''1'' must be the same (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3348E
The from-query is not valid: 0 (assign activity ''1'', copy element number 2).
CWWBV3349E
The to-query is not valid: 0 (assign activity ''1'', copy element number 2).
CWWBV3350E
The propertyAlias query which is referenced with the from property is not valid: 0 (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3351E
The to property propertyAlias query is not valid: 0 (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3352E
The from-expression is not valid: 0 (assign activity ''1'', copy element number 2).
CWWBV3353W
The from property propertyAlias query must not be empty (assign activity ''0'', copy element number 1, propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV3354W
The to property propertyAlias query must not be empty (assign activity ''0'', copy element number 1, propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV3355W
Assigning the xsd:anyType typed from-variable ''0'' to the xsd:anySimpleType typed to-variable ''1'' might result in a runtime error (assign activity ''2'', copy element number 3, from XSD type ''4'', to XSD type ''5'').
CWWBV3356W
In assign activity ''1'', the from-expiration expression in copy element number 2 is not valid: ''0''
CWWBV3359W
In the ''1'' assign activity, copy element number 2, the from-expression is not valid: The ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (assign activity ''1'', copy element number 2)
CWWBV3360W
In the ''1'' assign activity, copy element number 2, the XPath query used in the assign from property ''3'' is not valid: ''0'' (messageType 4).
CWWBV3363W
In the ''2'' assign activity, copy element number 3, the XPath query used in the assign from property ''4'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3364W
In the ''1'' assign activity, copy element number 2, the from query is not valid: ''0''
CWWBV3367W
In the ''1'' assign activity, copy element number 2, the from query is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (assign activity ''1'', copy element number 2).
CWWBV3368W
In the ''1'' assign activity, copy element number 2, the XPath query used in the ''3'' assign-to property of a variable is not valid: ''0'' messageType ''4'').
CWWBV3371W
In the ''2'' assign activity, copy element number 3, the XPath query used in the ''4'' assign-to property of a variable is not valid because the ''$'' notation that is used to refer to a variable in the 0 XPath expression or query is not supported. (assign activity ''1'', copy element number 2, propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3372W
In the ''1'' assign activity, copy element number 2, the to query is not valid: ''0''
CWWBV3375W
In the ''1'' assign activity, copy element number 2, the to query is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV3376W
Deprecation: In the 0 assign activity, copy element number 1, the ''from'' element uses the deprecated schema for literal values.
CWWBV3378E
In the ''0'' assign activity, copy element number 1, the from element uses both schemas for literal values. This is not supported.
CWWBV3379E
The derived type of the 0 from variable and the type of the 1 to variable are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3380E
The type of the 0 from variable contains a chain of derivations with mixed derivation types. ( 1 assign variable, (2 assign activity, copy element number 3, 4 from XSD type).
CWWBV3381E
The type of the 0 from variable derives a type that disallows the used derivation. ( 1 assign variable, 2 assign activity, copy element number 3, 4 from XSD type).
CWWBV3382E
The derived data type of the 0 from part and the 1 to variable are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3383E
The data type of the 0 from part contains a chain of derivations with mixed derivation types. (1 to variable or part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3384E
The data type of the 0 from part derives a type that disallows the used derivation. (1 to variable or part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3385E
The derived type of the 0 from variable and the 1 to part are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3386E
The data type of the 0 from variable contains a chain of derivations with mixed derivation types. (1 to part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3387E
The data type of the 0 from variable derives a type that disallows the used derivation. (1 to part, 2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3388E
The derived type of the 0 from part and the 1 to part are not the same (2 assign activity, copy element number 3, 4 from XSD type, 5 to XSD type).
CWWBV3400E
The ''0''compensate activity can only be used inside a fault handler, a compensation handler, or directly in a generalized flow realizing the BPMN pattern.
CWWBV3401E
The referenced scope or invoke activity ''0'' was not found or can not be referenced. It must be defined in the process and contained in the scope (compensate activity ''1'').
CWWBV3402E
The compensate activity cannot be contained inside an invoke activity (compensate activity ''0'', invoke activity ''1'').
CWWBV3403E
The referenced scope activity ''0'' cannot be compensated (compensate activity ''1'').
CWWBV3406E
The activity name ''0'' must be unique (referenced in compensate activity ''1'').
CWWBV3407E
The compensate activity cannot be contained inside the fault handler of a non-compensable scope activity (compensate activity ''0'', scope activity ''1'').
CWWBV3408W
Deprecation: The use of the scope attribute on the 0 compensate activity is deprecated. Use the compensateScope activity instead.
CWWBV3409E
The compensateScope activity can be used only inside a fault handler or a compensation handler (0 compensate activity).
CWWBV3410E
The 0 referenced scope or invoke activity was not found or cannot be referenced. It must be defined in the process and contained in the scope (1 compensateScope activity).
CWWBV3411E
The compensateScope activity cannot be contained inside an invoke activity (0 compensateScope activity, 1 invoke activity).
CWWBV3412E
The 0 referenced scope activity cannot be compensated (1 compensateScope activity).
CWWBV3415E
The activity name 0 must be unique (referenced in the 1 compensateScope activity).
CWWBV3416E
The compensateScope activity cannot be contained in the fault handler of a non-compensable scope activity (0 compensateScope activity, 1 scope activity).
CWWBV3417I
The scope of the 0 compensateScope activity is the surrounding scope or the surrounding process.
CWWBV3418I
The scope of the 0 compensate activity is the surrounding scope or the surrounding process.
CWWBV3600E
The link ''0'' cannot cross the boundary of the while activity ''1'' (link defined in the flow activity ''2'').
CWWBV3601E
The link ''0'' cannot be used in the while activity ''1'', because it is defined outside of the while activity (link defined in the flow activity ''2'').
CWWBV3602E
The link ''0'' cannot cross the boundary of the compensation handler of the scope activity ''1'' (link defined in the flow activity ''2'').
CWWBV3603E
The link ''0'' cannot be used in the compensation handler of the scope activity ''1'', because it is defined outside of the scope activity (link defined in the flow activity ''2'').
CWWBV3604E
The link ''0'' cannot cross the boundary of the compensation handler of the invoke activity ''1'' (link defined in the flow activity ''2'').
CWWBV3605E
The link ''0'' cannot be used in the compensation handler of the invoke activity ''1'', because it is defined outside of the invoke activity (link defined in the flow activity ''2'').
CWWBV3606E
The link ''0'' cannot cross the boundary of the event handler of the scope activity ''1'' (link defined in the flow activity ''2'').
CWWBV3607E
The link ''0'' cannot be used in the event handler of the scope activity ''1'', because it is defined outside of the scope activity (link defined in the flow activity ''2'').
CWWBV3608E
The inbound link ''0'' cannot cross the boundary of the fault handler of the scope activity ''1'' (link defined in the flow activity ''2'').
CWWBV3609E
The link ''0'' cannot be used in the fault handler of the scope activity ''1'', because it is defined outside of the scope activity (link defined in the flow activity ''2'').
CWWBV3610E
The target of the link ''0'' cannot be nested in the scope activity ''1'', because the source of the link is nested in the fault handler of the scope activity (link defined in the flow activity ''2'').
CWWBV3611E
The inbound link ''0'' cannot cross the boundary of the fault handler of the invoke activity ''1'' (link defined in the flow activity ''2'').
CWWBV3612E
The link ''0'' cannot be used in the fault handler of the invoke activity ''1'', because it is defined outside of the invoke activity (link defined in the flow activity ''2'').
CWWBV3613E
The link ''0'' cannot cross the boundary of two serializable scope activities (source scope activity ''1'', target scope activity ''2'', link defined in the flow activity ''3'').
CWWBV3614E
The activity ''0'' cannot be part of a cycle.
CWWBV3615E
The link ''0'' cannot be part of a cycle.
CWWBV3616E
The source activity is missing for the link ''0'' (link defined in the flow activity ''1'', target activity ''2'').
CWWBV3617E
The target activity is missing for the link ''0'' (link defined in the flow activity ''1'', source activity ''2'').
CWWBV3618E
The link ''0'' is not used (link defined in the flow activity ''1'').
CWWBV3619E
The link ''0'' has more than one source activity: ''1'' (link defined in the flow activity ''2'').
CWWBV3620E
The 0 link has the following target activities: 1 (link defined in the 2 flow activity).
CWWBV3621E
The source type of the 0 activity must not be 2 (source of standard flow link 1).
CWWBV3622E
The target type of 0 activity must not be 2 (target of standard flow link 1).
CWWBV3623E
The link ''0'' cannot cross the boundary of the forEach activity ''1'' (link defined in the flow activity ''2'').
CWWBV3624E
The link ''0'' cannot be used in the forEach activity ''1'', because it is defined outside of the forEach activity (link defined in the flow activity ''2'').
CWWBV3625W
The type attribute of the sources or targets element is deprecated (0 activity, 1 link).
CWWBV3650E
The extension activity ''0'' is not supported. Only generalized flow activities are supported.
CWWBV3651E
The source type of the 0 activity must be one of split, fork, or ior (source of the 1 generalized flow link).
CWWBV3652E
The target type of the 0 activity must be merge, join, or ior (target of the 1 generalized flow link).
CWWBV3653E
The source activity ''0'' of the generalized flow link ''1'' must be directly nested in the generalized flow activity ''2''.
CWWBV3654E
The target activity ''0'' of the generalized flow link ''1'' must be directly nested in the generalized flow activity ''2''.
CWWBV3655E
The generalized flow activity ''0'' must contain exactly one start activity. Found start activities: ''1''.
CWWBV3656E
The generalized flow activity ''0'' must contain at least one end activity.
CWWBV3657E
The activity ''0'' cannot be reached from the start activity ''1'' of the generalized flow activity ''2''.
CWWBV3658E
An end activity cannot be reached from the activity ''0'' of the generalized flow activity ''1''. Connect the activity to an end activity.
CWWBV3659E
The activity ''0'' must not specify a join condition, because it is part of a graph.
CWWBV3660W
The generalized flow link ''0'' can never be navigated because the previously referenced generalized flow link ''1'' does not specify a transition condition (activity ''2'').
CWWBV3661E
The link ''0'' cannot cross the boundary of the generalized flow activity ''1'' (link defined in the flow activity ''2'').
CWWBV3662E
The link ''0'' cannot be used in the generalized flow activity ''1'', because it is defined outside of the generalized flow activity (link defined in the flow activity ''2'').
CWWBV3663E
The 0 flow activity is the source of multiple links but has no source type specified.
CWWBV3664E
The 0 flow activity is the target of multiple links but has no target type specified.
CWWBV3665W
The region analysis of ''0'' flow activity is failing.
CWWBV3666E
The fault source must contain a catch element or a catchAll element. (source activity ''0'', number of fault source ''1'')
CWWBV3667E
The fault source must not contain more than one catch element or a catchAll element. (source activity ''0'', number of fault source ''1'')
CWWBV3668E
There must not be more than one fault source with catch all. (source activity ''0'').
CWWBV3669E
The fault source requires either a faultName attribute, a faultVariable attribute or both (source activity ''0'', number of fault source ''1'')
CWWBV3670E
The fault variable ''0'' on the fault source cannot be found. (source activity ''1'', number of fault source ''2'')
CWWBV3671E
The source activity of a fault link must not be a structured activity (except the scope activity), a throw activity or a rethrow activity. (source activity ''0'').
CWWBV3672E
One region of generalized flow ''0'' is not mappable. (participating activities ''1'').
CWWBV3673E
The link or activity ''0'' is participating in a parallel region that contains a cycle (generalized flow ''1'').
CWWBV3674W
One region of generalized flow ''0'' might cause exceptions at runtime. (participating activities ''1'')
CWWBV3675W
The fault source requires a fault variable as the defined fault ''0'' has associated fault data. (source activity ''1'', number of fault source ''2'')
CWWBV3676W
The fault name ''0'' does not exist in the operation ''1''. (source activity ''2'', number of fault source ''3'')
CWWBV3677W
The fault variable ''0'' does not have the same message type as the fault data of the fault name ''1'' (source activity ''2'', number of fault source ''3'')
CWWBV3678W
The 0 link has a transition condition and is the only outgoing link of 1 activity.
CWWBV3700E
The partnerLink ''0'' referenced in the undo action was not found (invoke activity ''1'').
CWWBV3701E
The portType ''0'' referenced in the undo action was not found (invoke activity ''1'').
CWWBV3702E
The operation ''0'' referenced in the undo action was not found (invoke activity ''1'').
CWWBV3703E
The input element is not defined in the undo action operation ''0'' (invoke activity ''1'').
CWWBV3704E
The messageType is not set in the input element of the undo action operation ''0'' (invoke activity ''1'').
CWWBV3705E
The messageType ''0'' that is referenced in the input element of the undo action operation ''1'' is not defined (invoke activity ''2'').
CWWBV3706E
The messageType of the variable ''0'' and the input element of the undo action operation ''1'' must be the same (invoke activity ''2'').
CWWBV3707E
The undo action variable ''0'' is not defined (invoke activity ''1'').
CWWBV3708E
The XSD-typed variable cannot be used in the undo action (invoke activity ''0'', variable ''1'').
CWWBV3710E
An expiration element cannot be set for the undo action (invoke activity ''0'').
CWWBV3711E
The undo action partnerLink ''0'' does not define the partnerRole role (invoke activity ''1'').
CWWBV3712E
The portType attribute referenced in the undo action of the invoke activity ''0'' and in the partnerRole role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV3713E
The partnerLink ''0'' does not define the partnerRole role (invoke activity ''1'').
CWWBV3714E
The inputVariable attribute of the undo action must not be set because an undo action input element is available (invoke activity ''0'', undo action inputVariable ''1'').
CWWBV3715E
The variable ''0'' used in the undo action is not defined (input element of the undo action of invoke activity ''1'', parameter number 2).
CWWBV3716E
The message-typed variable cannot be used here (input element of the undo action of invoke activity ''0'', parameter number 1, variable ''2'').
CWWBV3717E
The variable ''0'' cannot be used multiple times in the same input element (input element of the undo action of invoke activity ''1'', parameter number 2).
CWWBV3718E
The invoke activity cannot contain both a compensation handler and an undo action (invoke activity ''0'').
CWWBV3719E
The undo action must specify a variable if the invoke activity specifies a variable by using the parameter extension (invoke activity ''0'').
CWWBV3720E
The parameter-extension cannot be used for the message ''0'' (undo action of invoke activity ''1'').
CWWBV3721E
The parameter ''0'' is not mapped to an element or part (undo action of invoke activity ''1'', parameter number 2).
CWWBV3722E
The XSD type definition ''0'' was not found (undo action of invoke activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3723E
The XSD element declaration ''0'' was not found (undo action of invoke activity ''1'', parameter number 2, matching part or element ''3'').
CWWBV3724E
The variable ''0'' cannot be assigned to element or part ''1'' because the data type does not match (undo action of invoke activity ''2'', parameter number 3).
CWWBV3725E
The XSD element ''0'' is not mapped to a parameter (undo action of invoke activity ''1'').
CWWBV3726E
The message-part ''0'' is not mapped to a parameter (undo action of invoke activity ''1'').
CWWBV3727W
In the undo action of the ''2'' invoke activity, parameter number 3, assigning the ''0'' xsd:anyType typed variable to the ''1'' xsd:anySimpleType typed element or part might cause a runtime error.
CWWBV3800E
The XSD-typed variable cannot be used here (pick activity ''0'', onMessage element number 1, variable ''2'').
CWWBV3801E
The partnerLink ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3802E
The partnerLink ''0'' does not define the myRole role (pick activity ''1'', onMessage element number 2).
CWWBV3803E
The portType ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3804E
The portType referenced in the pick activity ''0'' and in the myRole role ''1'' must be the same (onMessage element number 2, partnerLink ''3'', partnerLinkType ''4'').
CWWBV3805E
The operation ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3806E
The input element is not defined in the operation ''0'' (pick activity ''1'', onMessage element number 2).
CWWBV3807E
The messageType is not set in the input element of the operation ''0'' (pick activity ''1'', onMessage element number 2).
CWWBV3808E
The messageType ''0'' referenced in the operation ''1'' was not found (pick activity ''2'', onMessage element number 3).
CWWBV3809E
The messageType of the variable ''0'' and of the input element of operation ''1'' must be the same (pick activity ''2'', onMessage element number 3).
CWWBV3810E
The variable for onMessage element number 1 in pick activity ''0'' is not set.
CWWBV3811E
The variable ''0'' is not defined (pick activity ''1'', onMessage element number 2).
CWWBV3812E
The correlation set ''0'' was not found (pick activity ''1'', onMessage element number 2).
CWWBV3813E
A matching propertyAlias definition was not found for the property ''0'' and messageType ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'').
CWWBV3814E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (pick activity ''3'', onMessage element number 4, correlation set ''5'').
CWWBV3815E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' does not reference a valid XML schema simple type (pick activity ''3'', onMessage element number 4, correlation set ''5'').
CWWBV3816E
The type of the part ''0'' of the messageType ''1'' and the property ''2'' is not the same (pick activity ''3'', onMessage element number 4, correlation set ''5'').
CWWBV3817E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'').
CWWBV3818E
The onMessage element, number 0, in pick activity ''1'' does not use a correlation set.
CWWBV3819E
The wrong set of correlation sets is used in onMessage element number 0 of the pick activity ''1''. The expected set of correlation sets, as used in the activity ''2'', is: ''3''.
CWWBV3821E
The pick activity ''0'' can create process instances but it has onAlarm events.
CWWBV3822E
A reply activity was not found that matches onMessage element number 0 of the pick activity ''1''.
CWWBV3823E
The variable must not be set because an output element is available (pick activity ''0'', onMessage element number 1, variable ''2'').
CWWBV3824E
The variable ''0'' is not defined (pick activity ''1'', output element of onMessage element number 2, parameter number 3).
CWWBV3825E
The message-typed variable cannot be used here (pick activity ''0'', output element of onMessage element number 1, parameter number 2, variable ''3'').
CWWBV3826E
The variable ''0'' cannot be used multiple times in the same output element (pick activity ''1'', output element of onMessage element number 2, parameter number 3).
CWWBV3827E
The human task ''0'' cannot be found (pick activity ''1'', onMessage element number 2).
CWWBV3828E
The human task ''0'' is not an invocation task (pick activity ''1'', onMessage element number 2).
CWWBV3829E
The portType that is referenced in onMessage element number 0 and in the human task ''1'' must be the same (pick activity ''2'').
CWWBV3830E
The operation that is referenced in onMessage element number 0 and in the human task ''1'' must be the same (pick activity ''2'').
CWWBV3831E
The part is not set in the propertyAlias for the property ''0'' and the messageType ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'').
CWWBV3832E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (pick activity ''2'', onMessage element number 3, correlation set ''4'', propertyAlias for the property ''5'' and the messageType ''6'').
CWWBV3833E
The onAlarm event must specify at least a for expression, or an until expression (pick activity ''0'', onAlarm event 1).
CWWBV3834E
The onAlarm event must specify at least a for expression, an until expression, or a timeout expression (pick activity ''0'', onAlarm event 1).
CWWBV3835E
The onAlarm event cannot specify a for expression and a timeout expression, or an until expression and a timeout expression (pick activity ''0'', onAlarm event 1).
CWWBV3836E
The repeatEvery expression is not allowed in pick activities (pick activity ''0'', onAlarm event 1).
CWWBV3837E
The onMessage element, number 0, implements operation ''1'' of portType ''2'', which is already implemented in another onMessage element (pick activity ''3'').
CWWBV3838E
The parameter-extension cannot be used for the message ''0'' (pick activity ''1'', onMessage element number 2).
CWWBV3839E
The parameter ''0'' is not mapped to an element or part (pick activity ''1'', onMessage element number 2, parameter number 3).
CWWBV3840E
The XSD type definition ''0'' was not found (pick activity ''1'', onMessage element number 2, parameter number 3, matching part or element ''4'').
CWWBV3841E
The XSD element declaration ''0'' was not found (pick activity ''1'', onMessage element number 2, parameter number 3, matching part or element ''4'').
CWWBV3842E
The element or part ''0'' cannot be assigned to variable ''1'' because the data type does not match (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3843E
The XSD element ''0'' must be mapped to a parameter (pick activity ''1'', onMessage element number 2).
CWWBV3844E
The message-part ''0'' is not mapped to a parameter (pick activity ''1'', onMessage element number 2).
CWWBV3845E
The correlation set ''0'' is used already (pick activity ''1'', onMessage element number 2).
CWWBV3846W
The pick activity ''0'' is contained in the parallel forEach activity ''1''. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3847E
The same operation of the same port type is implemented by process onEvent event number 0. This would result in the standard fault ''bpws:conflictingReceive'' (pick activity ''1'', onMessage element number 2).
CWWBV3848E
The same operation of the same port type is implemented by onEvent event number 0 of the scope activity ''1''. This would result in the standard fault ''bpws:conflictingReceive'' (pick activity ''2'', onMessage element number 3).
CWWBV3849W
The pick activity ''0'' is contained in process onEvent event number 1, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3850W
The pick activity ''0'' is contained in onEvent event number 1 of the scope activity ''2'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3851E
The XPath for- or until-expression is not valid: 0 (pick activity ''1'', onAlarm event 2).
CWWBV3852E
The XPath correlation set property propertyAlias query is not valid: 0 (pick activity ''1'', onMessage element number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3853W
The XPath correlation set property propertyAlias query must not be empty (pick activity ''0'', onMessage element number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV3854W
Assigning the xsd:anyType typed element or part ''0'' to the xsd:anySimpleType typed variable ''1'' might result in a runtime error (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3855W
The XPath for-expression or until-expression in onAlarm event number 2 of pick activity ''1'' is not valid: ''0''
CWWBV3862W
The XPath for-expression or until-expression in onAlarm event number 2 of pick activity ''1'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (onMessage switch activity ''1'', onAlarm event number 2).
CWWBV3863W
The XPath correlation set property propertyAlias query is not valid: ''0'' (pick activity ''1'', onMessage element number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3866W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (pick activity ''1'', onMessage element number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV3867W
The onMessage element, number 0, in pick activity ''1'' does not use a correlation set.
CWWBV3868E
The variable must not be set because a fromParts element is available (0 pick activity, onMessage element number 1, 2 variable).
CWWBV3869E
The derived type of the 0 element or part cannot be assigned to variable ''1'' because the data type does not match (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3870E
The derived type of the ''0'' element or part cannot be assigned to variable ''1'' because it contains a chain of derivations with mixed derivation types. (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3871E
The derived type of the ''0'' element or part cannot be assigned to variable ''1'' because it derives a type that disallows the used derivation. (pick activity ''2'', onMessage element number 3, parameter number 4).
CWWBV3900E
The receive activity ''0'' does not use a correlation set.
CWWBV3901E
A wrong set of correlation sets is used in the receive activity ''0''. The expected set of correlation sets, as used in activity ''1'', is: ''2''.
CWWBV3902E
A reply activity was not found that matches the receive activity ''0''.
CWWBV3903E
The variable must not be set because an output element is available (receive activity ''0'', variable ''1'').
CWWBV3904E
The human task ''0'' is not an invocation task (receive activity ''1'').
CWWBV3905W
The receive activity ''0'' is contained in the parallel forEach activity ''1''. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3906E
The same operation of the same port type is implemented by process onEvent event number 0. This would result in the standard fault ''bpws:conflictingReceive'' (receive activity ''1'').
CWWBV3907E
The same operation of the same port type is implemented by onEvent event number 0 of the scope activity ''1''. This would result in the standard fault ''bpws:conflictingReceive'' (receive activity ''2'').
CWWBV3908W
The receive activity ''0'' is contained in the process onEvent event number 1, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3909W
The receive activity ''0'' is contained in onEvent event number 1 of the scope activity ''2'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV3910W
The receive activity ''0'' does not use a correlation set.
CWWBV3911E
The variable must not be set because a fromParts element is available (0 receive activity, 1 variable).
CWWBV4000E
The fault ''0'' was not found in the operation ''1'' (activity ''2'').
CWWBV4001E
The process is triggered by a one-way operation, but it contains the reply activity ''0''.
CWWBV4002E
No pick activity, receive activity, or onEvent event found to match the reply activity ''0''.
CWWBV4003E
The variable must not be set because an input element is available (reply activity ''0'', variable ''1'').
CWWBV4004E
A variable must not be set because a toParts element is available (0 reply activity, 1 variable).
CWWBV4100E
The rethrow activity ''0'' cannot be used outside of a fault handler.
CWWBV4101E
The rethrow activity ''0'' cannot be used inside of a scope.
CWWBV4200E
The serializable scope activity ''0'' must not be nested in the serializable scope activity ''1''.
CWWBV4201E
There are too many variable type definitions set for the scope variable ''0'' (scope activity ''1'', messageType ''2'', type ''3'', element ''4'').
CWWBV4202E
The scope variable ''0'' must have a variable type definition (scope activity ''1'').
CWWBV4203E
The messageType definition ''0'' was not found (scope activity ''1'', scope variable ''2'').
CWWBV4204E
The XSD type definition ''0'' was not found (scope activity ''1'', scope variable ''2'').
CWWBV4205E
The XSD element declaration ''0'' was not found (scope activity ''1'', scope variable ''2'').
CWWBV4206E
The scope variable name ''0'' is already used (scope activity ''1'').
CWWBV4207E
The event handler of the scope activity must contain an onEvent event or an onAlarm event (scope activity ''0'').
CWWBV4208E
The partnerLink ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4209E
The partnerLink ''0'' does not define the myRole role (scope activity ''1'', onEvent event number 2).
CWWBV4210E
The portType ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4211E
The portType referenced in onEvent event number 0 and in myRole role ''1'' must be the same (scope activity ''2'', partnerLink ''3'', partnerLinkType ''4'').
CWWBV4212E
The operation ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4213E
The input element is not defined in the operation ''0'' (scope activity ''1'', onEvent event number 2).
CWWBV4214E
The messageType is not set in the input element of the operation ''0'' (scope activity ''1'', onEvent event number 2).
CWWBV4215E
The messageType ''0'' referenced in the operation ''1'' was not found (scope activity ''2'', onEvent event number 3).
CWWBV4216E
The messageType of the variable ''0'' and the messageType of the input element of the operation ''1'' must be the same (scope activity ''2'', onEvent event number 3).
CWWBV4217E
The variable is not set (scope activity ''0'', onEvent event number 1).
CWWBV4218E
The messageType or element is not set (0 scope activity, onEvent event number 1).
CWWBV4219E
The messageType ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4220E
The correlation set ''0'' was not found (scope activity ''1'', onEvent event number 2).
CWWBV4221E
The variable must not be set because an output element is available (scope activity ''0'', onEvent event number 1, variable ''2'').
CWWBV4222E
The scope activity has a compensation handler, but the compensable attribute of the scope activity is set to ''no'' (scope activity ''0'').
CWWBV4223E
The parameter-extension cannot be used for the message ''0'' (scope activity ''1'', onEvent event number 2).
CWWBV4224E
The parameter ''0'' is not mapped to an element or part (scope activity ''1'', onEvent event number 2, parameter number 3).
CWWBV4225E
The variable name ''0'' is used already in the same onEvent event (scope activity ''1'', output element of onEvent event number 2, parameter number 3).
CWWBV4226E
A matching propertyAlias definition was not found for the property ''0'' and messageType ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'').
CWWBV4227E
The part ''0'' that is referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (scope activity ''3'', onEvent event number 4, correlation set ''5'').
CWWBV4228E
The part ''0'' that is referenced in the propertyAlias for the property ''1'' and the messageType ''2'' does not reference a valid XML schema simple type (scope activity ''3'', onEvent event number 4, correlation set ''5'').
CWWBV4229E
The type of the part ''0'' of the messageType ''1'' and the type of the property ''2'' are not the same (scope activity ''3'', onEvent event number 4, correlation set ''5'').
CWWBV4230E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'').
CWWBV4231E
The human task ''0'' cannot be found (scope activity ''1'', onEvent event number 2).
CWWBV4232E
The human task ''0'' is not an invocation task (scope activity ''1'', onEvent event number 2).
CWWBV4233E
The portType referenced in onEvent event number 0 and in the human task ''1'' must be the same (scope activity ''2'').
CWWBV4234E
The operation that is referenced in onEvent event number 0 and in the human task ''1'' must be the same (scope activity ''2'').
CWWBV4235E
The part is not set in the propertyAlias for the property ''0'' and the messageType ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'').
CWWBV4236E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (scope activity ''2'', onEvent event number 3, correlation set ''4'', propertyAlias for the property ''5'' and the messageType ''6'').
CWWBV4237E
A reply activity was not found that matches onEvent event number 0 of the scope activity ''1''.
CWWBV4238E
The expression is not valid (scope activity ''0'', onAlarm event 1, expression language ''2'').
CWWBV4239E
There are too many variable type definitions set for the variable ''0'' (scope activity ''1'', onEvent event number 2, parameter number 3, type ''4'', element ''5'').
CWWBV4240E
The XSD element declaration ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, variable ''4'').
CWWBV4241E
The XSD type definition ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, variable ''4'').
CWWBV4242E
The variable ''0'' must have a variable type definition (scope activity ''1'', onEvent event number 2, parameter number 3).
CWWBV4243E
The XSD type definition ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, matching part or element ''4'').
CWWBV4244E
The XSD element declaration ''0'' was not found (scope activity ''1'', onEvent event number 2, parameter number 3, matching part or element ''4'').
CWWBV4245E
The element ''0'' cannot be assigned to variable ''1'' because the data type does not match (scope activity ''2'', onEvent event number 3, parameter number 4).
CWWBV4246E
The part ''0'' cannot be assigned to variable ''1'' because the data type does not match (scope activity ''2'', onEvent event number 3, parameter number 4).
CWWBV4247E
The XSD element ''0'' is not mapped to a parameter (scope activity ''1'', onEvent event number 2).
CWWBV4248E
The message-part ''0'' is not mapped to a parameter (scope activity ''1'', onEvent event number 2).
CWWBV4249E
The correlation set ''0'' is used already (scope activity ''1'', onEvent event number 2).
CWWBV4250W
The scope activity ''0'' defines event handlers and is contained in the parallel forEach activity ''1''. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV4251E
The onEvent event, number 0, implements operation ''1'' of portType ''2'', which is already implemented in another onEvent event (scope activity ''3'').
CWWBV4252E
The onEvent event, number 0, does not use a correlation set (scope activity ''1'').
CWWBV4253E
The same operation of the same port type is implemented by process onEvent event number 0. This would result in the standard fault ''bpws:conflictingReceive'' (scope activity ''1'', onEvent event number 2).
CWWBV4254E
The same operation of the same port type is implemented by onEvent event number 0 of the outer scope activity ''1''. This would result in the standard fault ''bpws:conflictingReceive'' (inner scope activity ''2'', onEvent event number 3).
CWWBV4255W
The scope activity ''0'' defines event handlers and is contained in process onEvent event number 1, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV4256W
The inner scope activity ''0'' defines event handlers and is contained in onEvent event number 1 of the outer scope activity ''2'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
CWWBV4257E
The query properties extension is only allowed for process variables (scope activity ''0'', scope variable ''1'').
CWWBV4258E
The XPath for-, until- or repeatEvery-expression is not valid: 0 (scope activity ''1'', onAlarm event 2).
CWWBV4259E
The XPath correlation set property propertyAlias query is not valid: 0 (scope activity ''1'', onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV4260W
The XPath correlation set property propertyAlias query must not be empty (scope activity ''0'', onEvent event number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV4261W
In onEvent event number 3 from the event handler that is attached to the scope activity ''2'', assigning the ''0'' xsd:anyType typed element to the ''1'' xsd:anySimpleType typed variable might cause a runtime error (parameter number 4).
CWWBV4262W
In onEvent event number 3 of the event handler that is attached to scope activity ''2'', assigning the ''0'' xsd:anyType typed part to the ''1'' xsd:anySimpleType variable might cause a runtime error (parameter number 4).
CWWBV4263W
The XPath for-expression, until-expression, or repeatEvery-expression in onAlarm event number 2 in scope activity ''1'' is not valid: ''0''
CWWBV4266W
The XPath for-expression, until-expression, or repeatEvery-expression in onAlarm event number 2 in scope activity ''1'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV4267W
The XPath correlation set property propertyAlias query is not valid: ''0'' (scope activity ''1'', onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV4270W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (scope activity ''1'', onEvent event number 2, correlation set ''3'', propertyAlias for the property ''4'' and the messageType ''5'').
CWWBV4271E
You cannot specify both the element and messageType attributes for the onEvent element. Remove one of the attributes (0 scope activity, onEvent number 1).
CWWBV4272E
The 0 element was not found (1 scope activity, onEvent number 2).
CWWBV4273E
The variable must not be set because a fromParts element is available (0 scope activity, onEvent event number 1, 2 variable).
CWWBV4274E
The from-specification is not allowed (scope variable ''0'', scope ''1'').
CWWBV4275E
The from-variable ''0'' is not defined (scope variable ''1'', scope ''2'').
CWWBV4276E
The from-part ''0'' was not found (scope variable ''1'', variable ''2'', scope ''3'').
CWWBV4277E
The from-partnerLink ''0'' was not found (scope variable ''1'', scope ''2'').
CWWBV4278E
The query language ''0'' is not supported. It must be one of ''1'' (scope variable ''2'', from-specification, scope ''3'').
CWWBV4279E
The from-query is not valid: 0 (scope variable ''1'', scope ''2'').
CWWBV4280W
In the ''1'' scope variable, the from query is not valid: ''0'' (scope ''2'').
CWWBV4281E
The expression language ''0'' of the expression element is not supported. It must be one of ''1'' (scope variable ''2'', scope ''3'').
CWWBV4282E
The from-expression is not valid: 0 (scope variable ''1'', scope ''2'').
CWWBV4283W
In the scope variable ''1'', the from-expiration expression is not valid: ''0'' (scope ''2'').
CWWBV4284E
The XSD-typed variable ''0'' cannot be used in combination with a property specification. Use a message-typed variable (scope variable ''1'', scope ''2'').
CWWBV4285E
The property ''0'' was not found (scope variable ''1'', scope ''2'').
CWWBV4286E
A matching propertyAlias definition is needed for the property ''0'' and the messageType ''1'' (scope variable ''2'', scope ''3'').
CWWBV4287E
The part must be set in the propertyAlias for the property ''0'' and the messageType ''1'' (scope variable ''2'', scope ''3'').
CWWBV4288E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (scope variable ''3'', scope ''4'').
CWWBV4289E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (scope variable ''2'', scope ''5'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV4290W
The from property propertyAlias query must not be empty (scope variable ''0'', scope ''3'', propertyAlias for the property ''1'' and the messageType ''2'').
CWWBV4291E
The propertyAlias query which is referenced with the from property is not valid: 0 (scope variable ''1'', scope ''4'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV4292W
In the ''1'' process variable, the XPath query used in the assign from property ''2'' is not valid: ''0'' (scope ''4'', messageType 3).
CWWBV4293E
Part ''0'' referenced in the propertyAlias definition for property ''1'' and messageType ''2'' must reference a valid XML schema simple type (scope variable ''3'', scope ''4'').
CWWBV4294E
The type of part ''0'' of messageType ''1'' and the type of the property ''2'' must be the same XML schema type (scope variable ''3'', scope ''4'').
CWWBV4295E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (scope variable ''2'', scope ''3'').
CWWBV4296E
The messageType of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from messageType ''2'', to messageType ''3'').
CWWBV4297E
The message-typed from-variable ''0'' cannot be assigned to the type-typed or element-typed scope variable ''1'' (scope ''4'', from messageType ''2'', to type/element ''3'').
CWWBV4298E
The XSD type definition ''0'' is not valid (scope variable ''1'', scope ''2'').
CWWBV4299E
The XSD type definition ''0'' was not found (scope variable ''1'', scope ''4'', base type ''2'', type referencing the type that was not found ''3'').
CWWBV4400E
The expression language ''0'' of the condition element is not supported. It must be one of ''1'' (switch activity ''2'', case element number 3).
CWWBV4401E
The condition expression is not valid (switch activity ''0'', case element number 1, expression language ''2'').
CWWBV4402E
The XPath case condition is not valid: 0 (switch activity ''1'', case element number 2).
CWWBV4403W
The XPath case condition in case element number 2 of the ''1'' switch activity is not valid: ''0''
CWWBV4406W
The XPath case condition in case element number 2 of switch activity ''1'' is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (switch activity ''1'', case element number 2).
CWWBV4500E
The fault variable ''0'' is not defined (throw activity ''1'').
CWWBV4600E
The wait activity must specify a for-expression or an until-expression (wait activity ''0'').
CWWBV4601E
The wait activity specifies a for-expression and an until-expression (wait activity ''0'').
CWWBV4602E
The wait activity must specify a for expression, an until expression or a timeout expression (wait activity ''0'').
CWWBV4603E
The wait activity specifies more than one expression (wait activity ''0'').
CWWBV4604E
The expression language ''0'' is not supported. It must be one of ''1'' (wait activity ''2'').
CWWBV4605E
The XPath for- or until-expression is not valid: 0 (wait activity ''1'').
CWWBV4606W
In the ''1'' wait activity, the XPath for-expression or until-expression is not valid: ''0''
CWWBV4609W
In the ''1'' wait activity, the XPath for-expression or until-expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV4700E
The expression language ''0'' of the condition element is not supported. It must be one of ''1'' (while activity ''2'').
CWWBV4701E
The condition expression is not valid (while activity ''0'', expression language ''1'').
CWWBV4702E
The XPath while condition is not valid: 0 (while activity ''1'').
CWWBV4703W
In the ''1'' while activity, the XPath while condition is not valid: ''0''
CWWBV4706W
In the ''1'' while activity, the XPath while condition is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV4800E
The namespace of the custom activity ''0'' is not valid: ''http://'' is missing or ''http:///'' is used (used namespace ''1'', element name ''2'').
CWWBV4801E
The plug-in found for the custom activity ''0'' does not implement the expected interface (found plug-in ''1'').
CWWBV4802E
An exception occurred when the plug-in for the custom activity ''0'' was loaded (exception ''1'').
CWWBV4803E
0 (custom activity ''1'', plug-in ''2'').
CWWBV4804W
0 (custom activity ''1'', plug-in ''2'').
CWWBV4805I
0 (custom activity ''1'', plug-in ''2'').
CWWBV4806E
The result returned from the plug-in validation is not valid: 0 (custom activity ''1'', plug-in ''2'').
CWWBV4900E
The portType must be set (human task activity ''0'').
CWWBV4901E
The adminTask element is not allowed (human task activity ''0'').
CWWBV4902E
The human task ''0'' is not a To-do task (human task activity ''1'').
CWWBV4903E
The name of the human task activity and the referenced participating human task must be the same (human task activity ''0'', participating human task ''1'').
CWWBV4904E
The operation must be a request-response operation (human task activity ''0'', operation ''1'').
CWWBV4905E
The process contains a human task that contains errors (human task name ''0'').
CWWBV4906E
A human task cannot contain both a compensation handler and an undo action (human task ''0'').
CWWBV4907E
An expiration element cannot be set for the undo action (human task ''0'').
CWWBV4908E
The message-part ''0'' is not mapped to a parameter (undo action of human task ''1'').
CWWBV4909E
The XSD element ''0'' is not mapped to a parameter (undo action of human task ''1'').
CWWBV4910E
The variable ''0'' cannot be used multiple times in the same input element (input element of the undo action of human task ''1'', parameter number 2).
CWWBV4911E
The message-typed variable cannot be used here (input element of the undo action of human task ''0'', parameter number 1, variable ''2'').
CWWBV4912E
The variable ''0'' used in the undo action is not defined (input element of the undo action of human task ''1'', parameter number 2).
CWWBV4913E
The parameter ''0'' is not mapped to an element or part (undo action of human task ''1'', parameter number 2).
CWWBV4914E
The parameter-extension cannot be used for the message ''0'' (undo action of human task ''1'').
CWWBV4915E
The XSD-typed variable cannot be used in the undo action (human task ''0'', variable ''1'').
CWWBV4916E
The undo action variable ''0'' is not defined (human task ''1'').
CWWBV4917E
The inputVariable attribute of the undo action must not be set because an undo action input element is available (human task ''0'', undo action inputVariable ''1'').
CWWBV4918E
The undo action must specify a variable if the human task specifies a variable by using the parameter extension (invoke activity ''0'').
CWWBV4919E
The messageType of the variable ''0'' and the input element of the undo action operation ''1'' must be the same (human task ''2'').
CWWBV4920E
The messageType ''0'' that is referenced in the input element of the undo action operation ''1'' is not defined (human task ''2'').
CWWBV4921E
The input element is not defined in the undo action operation ''0'' (human task ''1'').
CWWBV4922E
The operation ''0'' referenced in the undo action was not found (human task ''1'').
CWWBV4923E
The portType attribute referenced in the undo action of the human task ''0'' and in the partnerRole role ''1'' must be the same (partnerLink ''2'', partnerLinkType ''3'').
CWWBV4924E
The portType ''0'' referenced in the undo action was not found (human task ''1'').
CWWBV4925E
The undo action partnerLink ''0'' does not define the partnerRole role (human task ''1'').
CWWBV4926E
The partnerLink ''0'' referenced in the undo action was not found (human task ''1'').
CWWBV4927E
The XSD type definition ''0'' was not found (undo action of human task ''1'', parameter number 2, matching part or element ''3'').
CWWBV4928W
In the undo action of the ''2'' human task, parameter number 3, assigning the ''0'' xsd:anyType typed variable to the ''1'' xsd:anySimpleType typed element or part might cause a runtime error.
CWWBV4929E
The variable ''0'' cannot be assigned to element or part ''1'' because the data type does not match (undo action of human task ''2'', parameter number 3).
CWWBV4930E
The XSD element declaration ''0'' was not found (undo action of human task ''1'', parameter number 2, matching part or element ''3'').
CWWBV5000E
The expression language ''0'' of the startCounterValue element is not supported. It must be one of ''1'' (forEach activity ''2'').
CWWBV5001E
The expression language ''0'' of the finalCounterValue element is not supported. It must be one of ''1'' (forEach activity ''2'').
CWWBV5002E
The expression language ''0'' of the completionCondition element is not supported. It must be one of ''1'' (forEach activity ''2'').
CWWBV5003E
A variable with the name ''0'' must not be defined on the scope activity ''1'', because a variable with that name is defined on that scope activity implicitly in the forEach activity ''2''.
CWWBV5004E
The XPath startCounterValue expression is not valid: 0 (forEach activity ''1'').
CWWBV5005E
The XPath finalCounterValue expression is not valid: 0 (forEach activity ''1'').
CWWBV5006E
The XPath completionCondition expression is not valid: 0 (forEach activity ''1'').
CWWBV5007W
In the ''1'' forEach activity, the XPath completionCondition expression is not valid: ''0''
CWWBV5010W
In the ''1'' forEach activity, the XPath completionCondition expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (forEach activity ''1'').
CWWBV5011W
In the ''1'' forEach activity, the XPath finalCounterValue expression is not valid: ''0''
CWWBV5014W
In the ''1'' forEach activity, the XPath finalCounterValue expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (forEach activity ''1'').
CWWBV5015W
In the ''1'' forEach activity, the XPath startCounterValue expression is not valid: ''0''
CWWBV5018W
In the 1 forEach activity, the XPath startCounterValue expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported. (forEach activity ''1'').
CWWBV6000E
The XSD-typed variable can only use inline defined query properties (process variable ''0'', queryProperty element number 1, referenced property ''2'').
CWWBV6001E
The property ''0'' is already used as query property in this variable (process variable ''1'', queryProperty element number 2).
CWWBV6002E
The property ''0'' is referenced to be used as query property, but attribute ''name'', ''type'' and/or ''part'' and/or a query expression is specified (process variable ''1'', queryProperty element number 2).
CWWBV6003E
The queryProperty element, number 0, must either reference an existing property or define an inline property (process variable ''1'').
CWWBV6004E
The inline defined query property does not specify a name (process variable ''0'', queryProperty element number 1).
CWWBV6005E
The inline defined query property ''0'' does not specify the type (process variable ''1'', queryProperty element number 2).
CWWBV6006E
The type of the referenced property ''0'' is not set (process variable ''1'', queryProperty element number 2).
CWWBV6007E
The type ''0'' of the referenced property ''1'' was not found or is not an allowed or valid XML schema simple type in this context (process variable ''2'', queryProperty element number 3).
CWWBV6008E
A matching propertyAlias definition was not found for the referenced property ''0'' and the messageType ''1'' (process variable ''2'', queryProperty element number 3).
CWWBV6009E
The part ''0'' was not found referenced in the propertyAlias for the referenced property ''1'' and the messageType ''2'' (process variable ''3'', queryProperty element number 4).
CWWBV6010E
The part ''0'' does not reference a valid XML schema simple type (process variable ''1'', queryProperty element number 2, part referenced in the propertyAlias for the referenced property ''3'' and the messageType ''4'').
CWWBV6011E
The type of part ''0'' of messageType ''1'' and property ''2'' are not the same (process variable ''3'', queryProperty element number 4).
CWWBV6012E
Multiple propertyAlias definitions were found for referenced property ''0'' and messageType ''1'' (process variable ''2'', queryProperty element number 3).
CWWBV6013E
The part is not set in the propertyAlias for referenced property ''0'' and messageType ''1'' (process variable ''2'', queryProperty element number 3).
CWWBV6014E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (process variable ''2'', queryProperty element number 3, propertyAlias for the referenced property ''4'' and the messageType ''5'').
CWWBV6015E
The type ''0'' was not found or is not an allowed or valid XML schema simple type in this context (process variable ''1'', queryProperty element number 2, inline defined query property ''3'').
CWWBV6016E
The inline defined query property ''0'' must specify the part, because the variable is message-typed (process variable ''1'', queryProperty element number 2, messageType ''3'').
CWWBV6017E
The inline defined query property ''0'' specifies a part, but the variable is not message-typed (process variable ''1'', queryProperty element number 2).
CWWBV6018E
The part ''0'' was not found in the messageType ''1'' (process variable ''2'', queryProperty element number 3, inline defined query property ''4'').
CWWBV6019E
The part ''0'' does not reference a valid XML schema simple type (process variable ''1'', queryProperty element number 2, inline defined query property ''3'', messageType ''4'').
CWWBV6020E
The query language ''0'' is not supported. It must be one of ''1'' (process variable ''2'', queryProperty element number 3, inline defined query property ''4'').
CWWBV6021E
The part must be the same as the part ''0'' as specified in process variable ''1'', in queryProperty element number 2 (process variable ''3'', queryProperty element number 4, inline defined query property ''5'').
CWWBV6022E
The query must be the same as the query specified in process variable ''0'' in queryProperty element number 1 (process variable ''2'', queryProperty element number 3, inline defined query property ''4'').
CWWBV6023E
The property type of the inline defined query property ''0'' must be ''1'' as specified in process variable ''2'' in queryProperty element number 3 (process variable ''4'', queryProperty element number 5).
CWWBV6024E
The XPath queryProperty propertyAlias query is not valid: 0 (process variable ''1'', queryProperty element number 2, propertyAlias for referenced property ''3'' and messageType ''4'').
CWWBV6025E
The XPath queryProperty query is not valid: 0 (process variable ''1'', queryProperty element number 2, inline defined query property ''3'').
CWWBV6026E
The XPath for-, until- or repeatEvery-expression is not valid: 0 (process onAlarm event 1).
CWWBV6027E
The XPath correlation set property propertyAlias query is not valid: 0 (process onEvent event number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6028W
The XPath queryProperty propertyAlias query must not be empty (process variable ''0'', queryProperty element number 1, propertyAlias for the referenced property ''2'' and the messageType ''3'').
CWWBV6029W
The XPath correlation set property propertyAlias query must not be empty (process onEvent event number 0, correlation set ''1'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV6030W
In process onAlarm event number 1, the XPath for-expression, until-expression, or repeatEvery-expression is not valid: ''0''.
CWWBV6033W
In process onAlarm event number 1, the XPath for-expression, until-expression, or repeatEvery-expression is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV6034W
The XPath queryProperty propertyAlias query is not valid: ''0'' (process variable ''1'', queryProperty element number 2, propertyAlias for the referenced property ''3'' and the messageType ''4'').
CWWBV6037W
The XPath queryProperty propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (process variable ''1'', queryProperty element number 2, propertyAlias for the referenced property ''3'' and the messageType ''4'').
CWWBV6038W
For the process variable ''1'', queryProperty element number 2 points to the inline defined query property ''3'', which is not valid: ''0''
CWWBV6041W
For the process variable ''1'', queryProperty element number 2 points to the inline defined query property ''3'', which is not valid because the ''$'' notation that is used to refer to a variable in the ''0'' XPath expression or query is not supported.
CWWBV6042W
The XPath correlation set property propertyAlias query is not valid: ''0'' (process onEvent event 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6045W
The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''0'' is not supported. (process onEvent event number 1, correlation set ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6046W
An administration task cannot be used in a microflow (non-interruptible process). The administration task is defined on the ''0'' activity.
CWWBV6047E
The value of the continueOnError attribute is not valid in this context. For processes, only the value 'yes' or 'no' is allowed.
CWWBV6048W
Deprecation: The 0 role defines a portType element. This use is deprecated. Use the portType attribute instead. (1 process partnerLink, 2 partnerLinkType).
CWWBV6049E
The 0 role defines a portType element and a portType attribute. You must use only a portType attribute. (1 process partnerLink, 2 partnerLinkType)
CWWBV6050E
The 0 element was not found (process onEvent event 1).
CWWBV6051E
The onEvent element cannot specify both element and messageType attributes. Remove one of the attributes (process onEvent event 0).
CWWBV6052W
The catch requires that a fault variable as the defined fault ''0'' has associated fault data. (fault handler of activity ''1'', catch element number 2).
CWWBV6053W
The fault name ''0'' does not exist in the operation ''1''. (fault handler of activity ''2'', catch element number 3).
CWWBV6054W
The fault message type ''0'' does not match the message type of fault data of the fault name ''1'' (fault handler of activity ''2'', catch element number 3).
CWWBV6055E
The from-specification is not allowed (process variable ''0'').
CWWBV6056E
The from-variable ''0'' is not defined (process variable ''1'').
CWWBV6057E
The from-part ''0'' was not found (process variable ''1'', variable ''2'').
CWWBV6058E
The from-partnerLink ''0'' was not found (process variable ''1'').
CWWBV6059E
The query language ''0'' is not supported. It must be one of ''1'' (process variable ''2'', from-specification).
CWWBV6060E
The from-query is not valid: 0 (process variable ''1'').
CWWBV6061W
In the ''1'' process variable, the from query is not valid: ''0''
CWWBV6062E
The expression language ''0'' of the expression element is not supported. It must be one of ''1'' (process variable ''2'').
CWWBV6063E
The from-expression is not valid: 0 (process variable ''1'').
CWWBV6064W
In process variable ''1'', the from-expiration expression is not valid: ''0''
CWWBV6065E
The XSD-typed variable ''0'' cannot be used in combination with a property specification. Use a message-typed variable (process variable ''1'').
CWWBV6066E
The property ''0'' was not found (process variable ''1'').
CWWBV6067E
A matching propertyAlias definition is needed for the property ''0'' and the messageType ''1'' (process variable ''2'').
CWWBV6068E
The part must be set in the propertyAlias for the property ''0'' and the messageType ''1'' (process variable ''2'').
CWWBV6069E
The part ''0'' referenced in the propertyAlias for the property ''1'' and the messageType ''2'' was not found (process variable ''3'').
CWWBV6070E
The query language ''0'' used in the propertyAlias is not supported. It must be one of ''1'' (process variable ''2'', propertyAlias for the property ''3'' and the messageType ''4'').
CWWBV6071W
The from property propertyAlias query must not be empty (process variable ''0'', propertyAlias for the property ''1'' and the messageType ''2'').
CWWBV6072E
The propertyAlias query which is referenced with the from property is not valid: 0 (process variable ''1'', propertyAlias for the property ''2'' and the messageType ''3'').
CWWBV6073W
In the ''1'' process variable, the XPath query used in the assign from property ''2'' is not valid: ''0'' (messageType 3).
CWWBV6074E
Part ''0'' referenced in the propertyAlias definition for property ''1'' and messageType ''2'' must reference a valid XML schema simple type (process variable ''3'').
CWWBV6075E
The type of part ''0'' of messageType ''1'' and the type of the property ''2'' must be the same XML schema type (process variable ''3'').
CWWBV6076E
Multiple propertyAlias definitions were found for the property ''0'' and the messageType ''1'' (process variable ''2'').
CWWBV6077E
The messageType of the from-variable ''0'' and the process variable ''1'' must be the same (from messageType ''2'', to messageType ''3'').
CWWBV6078E
The message-typed from-variable ''0'' cannot be assigned to the type-typed or element-typed process variable ''1'' (from messageType ''2'', to type/element ''3'').
CWWBV6079E
The XSD type definition ''0'' is not valid (process variable ''1'').
CWWBV6080E
The XSD type definition ''0'' was not found (process variable ''1'', base type ''2'', type referencing the type that was not found ''3'').
CWWBV6081W
Assigning the xsd:anyType typed from-variable ''0'' to the xsd:anySimpleType typed process variable ''1'' might result in a runtime error (from XSD type ''2'', to XSD type ''3'').
CWWBV6082E
The XSD type of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD type ''2'', to XSD type ''3'').
CWWBV6083E
The type-typed from-variable ''0'' cannot be assigned to the message-typed process variable ''1'' (from type ''2'', to messageType ''3'').
CWWBV6084E
The XSD type definition ''0'' was not found (process variable ''1'', element referencing the type that was not found ''2'').
CWWBV6085E
The type of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD type ''2'', to XSD element ''3'').
CWWBV6086E
The XSD element of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD element ''2'', to XSD element ''3'').
CWWBV6087E
The element-typed from-variable ''0'' cannot be assigned to the messageType-typed process variable ''1'' (from element ''2'', to messageType ''3'').
CWWBV6088E
The type of the from-variable ''0'' and the process variable ''1'' must be the same (from XSD element ''2'', to XSD type ''3'').
CWWBV6089E
The XSD-typed part ''0'' cannot be assigned to the message-typed process variable ''1''.
CWWBV6090E
The XSD type definition ''0'' was not found (process variable ''1'', from variable ''2'', part ''3'').
CWWBV6091E
The XSD type of the from-part ''0'' and the process variable ''1'' must be the same (from XSD type ''2'', to XSD type ''3'').
CWWBV6092E
The XSD element declaration ''0'' was not found (process variable ''1'', from variable ''2'', part ''3'').
CWWBV6093E
The literal type ''0:1'' is not allowed (process variable ''2'', from-specification).
CWWBV6094E
A literal value is not defined (process variable ''0'', from-specification).
CWWBV6095E
The literal value is not of the type ''0'' (process variable ''1'', from-specification).
CWWBV6096E
The derived type of the 0 from variable and the type of the 1 process variable are not the same. (2 from XSD type, 3, to XSD type).
CWWBV6097E
The type of the 0 from variable contains a chain of derivations with mixed derivation types. (1 process variable, 2 from XSD type).
CWWBV6098E
The type of the 0 from variable derives a type that disallows the used derivation. ( 1 process variable, 2 from XSD type, 3, to XSD type).
CWWBV6099E
The 0 element or part with a derived type cannot be assigned to the 1 variable because the data type does not match (process onEvent event number 2, parameter number 3).
CWWBV6100E
The type of the 0 element or part contains a chain of derivations with mixed derivation types. (1 to variable, process onEvent event number 2, parameter number 3).
CWWBV6101E
The type of the 0 from variable derives a type that disallows the used derivation. (1 to variable, process onEvent event number 2, parameter number 3).
CWWBV6102E
The derived data type of the 0 from part and the 1 process variable are not the same (2 from XSD type, 3 to XSD type).
CWWBV6103E
The derived data type of the 0 from part contains a chain of derivations with mixed derivation types. (1 process variable, 2 from XSD type, 3 to XSD type)
CWWBV6104E
The type of the 0 from part derives a type that disallows the used derivation. (1 process variable, 2 from XSD type, 3 to XSD type)
CWWBV6300E
The 0 expression language of the condition element is not supported. It must be one of 1 (2 RepeatUntil activity).
CWWBV6301E
The condition expression is not valid (0 RepeatUntil activity, 1 expression language).
CWWBV6302E
The XML Path Language (XPath) RepeatUntil condition is not valid. The error is: 0 (1 RepeatUntil activity).
CWWBV6303W
In the 1 RepeatUntil activity, the XML Path Language (XPath) RepeatUntil condition is not valid. The error is: 0
CWWBV6400W
Assigning the xsd:anyType typed from-variable ''0'' to the xsd:anySimpleType typed scope variable ''1'' might result in a runtime error (scope ''4'', from XSD type ''2'', to XSD type ''3'').
CWWBV6401E
The XSD type of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD type ''2'', to XSD type ''3'').
CWWBV6402E
The type-typed from-variable ''0'' cannot be assigned to the message-typed scope variable ''1'' (scope ''4'', from type ''2'', to messageType ''3'').
CWWBV6403E
The XSD type definition ''0'' was not found (scope variable ''1'', scope ''3'', element referencing the type that was not found ''2'').
CWWBV6404E
The type of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD type ''2'', to XSD element ''3'').
CWWBV6405E
The XSD element of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD element ''2'', to XSD element ''3'').
CWWBV6406E
The element-typed from-variable ''0'' cannot be assigned to the messageType-typed scope variable ''1'' (scope ''4'', from element ''2'', to messageType ''3'').
CWWBV6407E
The type of the from-variable ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD element ''2'', to XSD type ''3'').
CWWBV6408E
The XSD-typed part ''0'' cannot be assigned to the message-typed scope variable ''1'' (scope ''2'').
CWWBV6409E
The XSD type definition ''0'' was not found (scope variable ''1'', scope ''4'', from variable ''2'', part ''3'').
CWWBV6410E
The XSD type of the from-part ''0'' and the scope variable ''1'' must be the same (scope ''4'', from XSD type ''2'', to XSD type ''3'').
CWWBV6411E
The XSD element declaration ''0'' was not found (scope variable ''1'', scope ''4'', from variable ''2'', part ''3'').
CWWBV6412E
The literal type ''0:1'' is not allowed (scope variable ''2'', from-specification, scope ''3'').
CWWBV6413E
A literal value is not defined (scope variable ''0'', from-specification, scope ''1'').
CWWBV6414E
The literal value is not of the type ''0'' (scope variable ''1'', from-specification, scope ''2'').
CWWBV6415E
The derived type of the 0 from variable and the 1 scope variable are not the same (4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV6416E
The type of the 0 from variable contains a chain of derivations with mixed derivation types. (1 scope variable, 2 scope activity, 3 from XSD type).
CWWBV6417E
The type of the 0 from variable derives a type that disallows the used derivation. (1 scope variable, 2 scope activity, 3 from XSD type, 4 to XSD type).
CWWBV6418E
The derived type of the 0 element or the message part cannot be assigned to variable 1 because the data type does not match ((2 scope activity, onEvent event number 3, input number 4).
CWWBV6419E
The type of the 0 element or message part contains a chain of derivations with mixed derivation types. (1 to variable, 2 scope activity, onEvent event number 3, input number 4).
CWWBV6420E
The type of the 0 element or message type derives a type that disallows the used derivation. (1 to variable, 2 scope activity, onEvent event number 3, input number 4).
CWWBV6421E
The derived data type of the 0 from part and the 1 scope variable are not the same (4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV6422E
The derived data type of the 0 from part contains a chain of derivations with mixed derivation types. (1 scope variable, 4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV6423E
The type of the 0 from part derives a type that disallows the used derivation. (1 scope variable, 4 scope activity, 2 from XSD type, 3 to XSD type).
CWWBV9000I
Validated the process component model ''0'' successfully: 1 information, 2 warnings, 3 errors.
CWWBV9001I
Validated the process component model ''0'' with findings: 1 information, 2 warnings, 3 errors.
CWWBV9002I
Validated the process component model ''0'' with findings: 1 information, 2 warnings, 3 errors: 4
CWWBV9050E
Process component validation error: ''0''. Error parameters: 1.
CWWBV9051W
Process component validation warning: ''0''. Warning parameters: 1.
CWWBV9052I
Process component validation information: ''0''. Information parameters: 1.
CWWBV9100E
The process component file ''0'' contains at least one interface of the wrong type. Be sure to use only WSDL port type interfaces.
CWWBV9101E
The process component file ''0'' contains a reference ''1'' without an interface.
CWWBV9102E
The process component file ''0'' contains a reference ''1'' with more than one interface.
CWWBV9103E
The process component file ''0'' contains a reference ''1'' with at least one interface of the wrong type. Be sure to use only WSDL port type interfaces.
CWWBV9104E
The process component file ''0'' contains a reference ''1'' that specifies an interface different to the one specified in the process implementation file.
CWWBV9105E
The process component file ''0'' contains an interface ''1'' that does not have a corresponding partnerLink in the process implementation file.
CWWBV9106E
The process component file ''0'' contains a reference ''1'' that does not have a corresponding partnerLink in the process implementation file.
CWWBV9107E
The process component file ''0'' does not contain an interface that corresponds to the inbound partnerLink ''1'' in the process implementation file.
CWWBV9108E
The process component file ''0'' does not contain a reference that corresponds to the outbound partnerLink ''1'' in the process implementation file.
CWWBV9200E
The interface ''1'' in the process component file ''0'' needs the preferredInteractionStyle attribute with a value of ''async''.
CWWBV9201E
The process component file ''0'' requires either the Transaction or the ActivitySession implementation qualifier.
CWWBV9202E
The interface ''1'' in the process component file ''0'' does not specify the mandatory JoinTransaction interface qualifier.
CWWBV9203E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not specify the mandatory JoinTransaction interface qualifier.
CWWBV9204E
The interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
CWWBV9205E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
CWWBV9206E
The interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''true''.
CWWBV9207E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not contain the JoinTransaction interface qualifier with a value of ''true''.
CWWBV9208E
The interface ''1'' in the process component file ''0'' specifies the JoinTransaction interface qualifier although it is not allowed in processes running in an activity session.
CWWBV9209E
The operation ''2'' of the interface ''1'' in the process component file ''0'' specifies the JoinTransaction interface qualifier although it is not allowed in processes running in an activity session.
CWWBV9210E
The reference ''1'' in the process component file ''0'' specifies the SuspendTransaction reference qualifier although this qualifier is not allowed in processes that run in an activity session.
CWWBV9211E
The process component file ''0'' must contain the Transaction implementation qualifier with a value of ''global''.
CWWBV9212E
The process component file ''0'' must contain the Transaction implementation qualifier with a value of ''global''.
CWWBV9213E
The process component file ''0'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundary with a value of ''activity session''.
CWWBV9214E
The process component file ''0'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundary with a value of ''activity session''.
CWWBV9215E
The interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed in long-running processes.
CWWBV9216E
The interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed in processes that run in a transaction.
CWWBV9217E
The interface ''1'' in the process component file ''0'' does not specify the mandatory JoinActivitySession interface qualifier.
CWWBV9218E
The interface ''1'' in the process component file ''0'' does not contain the JoinActivitySession interface qualifier with a value of ''true''.
CWWBV9219E
The operation ''2'' of the interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed for processes that run in a transaction.
CWWBV9220E
The operation ''2'' of the interface ''1'' in the process component file ''0'' specifies the JoinActivitySession interface qualifier although it is not allowed in long-running processes.
CWWBV9221E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not specify the mandatory JoinActivitySession interface qualifier.
CWWBV9222E
The operation ''2'' of the interface ''1'' in the process component file ''0'' does not contain the JoinActivitySession interface qualifier with a value of ''true''.
CWWBV9223E
The reference ''1'' in the process component file ''0'' specifies the SuspendActivitySession reference qualifier although this qualifier is not allowed in processes that run in a transaction.
CWWBV9224E
The process component file ''0'' specifies the ActivitySession implementation qualifier although it is not allowed in long-running processes.
CWWBV9225E
The process component file ''0'' specifies the ActivitySession implementation qualifier although it is not allowed in processes that run in a transaction.
CWWBV9226E
The process component file ''0'' does not specify the mandatory ActivitySession implementation qualifier.
CWWBV9227E
The process component file ''0'' does not contain an ActivitySession implementation qualifier with a value of ''true''.
CWWBV9228E
The interface ''1'' of the process component file ''0'' specifies the interface qualifier ''2'' more than once.
CWWBV9229E
The reference ''1'' of the process component file ''0'' specifies the reference qualifier ''2'' more than once.
CWWBV9230E
The process component file ''0'' specifies the implementation qualifier ''1'' more than once.
CWWBV9231E
The reference ''1'' in the process component file ''0'' needs the reference qualifier ''Asynchronous Invocation'' with a value of ''commit''.
CWWBV9232E
The reference ''1'' in the process component file ''0'' specifies a multiplicity other than ''1..1''. This is not supported for process component files.
CWWBV9300E
The process implementation file ''1'' referenced by the process component file ''0'' was not found.
CWWBV9301W
The reference ''1'' in the process component file ''0'' is wired to another component, but this component is ignored because the corresponding partnerLink has a process template specified.
CWWBV9302W
In process onEvent event handler number 2, parameter number 3, assigning the ''0'' xsd:anyType typed element to the ''1'' xsd:anySimpleType typed variable might cause a runtime error.
CWWBV9303W
In process onEvent event handler number 2, parameter number 3, assigning the ''0'' xsd:anyType typed part to the ''1'' xsd:anySimpleType typed variable might cause a runtime error.
CWWBV9304I
The activity name ''0'' is already used.
CWWBV9305E
The process inline custom property name ''0'' has been used already. Provide a unique name.

Parent topic: Workflow Server messages