WebSphere Process Server messages     Operating Systems: All supported
CWTKV0001I: Validated the task model ''{0}'' successfully: {1} information, {2} warnings, {3} errors.
Explanation: Summary of the successful validation of the task model.
User Action: No action is required.

 

CWTKV0002I: Validated the task model ''{0}'' with findings: {1} information, {2} warnings, {3} errors.
Explanation: Summary of the failed validation of the task model.
User Action: Update the task model to solve the problems.

 

CWTKV0003I: Validated the task model ''{0}'' with findings: {1} information, {2} warnings, {3} errors: {4}
Explanation: Summary of the failed validation of the task model.
User Action: Update the task model to solve the problems.

 

CWTKV0004E: A syntactical error was found (row: {0}, column: {1}): {2}
Explanation: The TEL file does not validate against the schema.
User Action: Ensure the syntactical correctness of the TEL file.

 

CWTKV0005W: A syntactical warning was found (row: {0}, column: {1}): {2}
Explanation: The TEL file validates with warnings against the schema.
User Action: Ensure the syntactical correctness of the TEL file.

 

CWTKV0006E: Cannot load and validate the TEL resource ''{0}''.
Explanation: The validation was canceled because of an invalid TEL resource.
User Action: Update the TEL resource to solve the problems.

 

CWTKV0007E: An exception occurred when the plug-in for the calendar validator was loaded. The exception was ''{0}''.
Explanation: The plug-in could not be instantiated.
User Action: Ensure that the plug-in is in the class path and that it is accessible.

 

CWTKV0008E: A calendar validator plug-in returned the following exception: {0}.
Explanation: The exception cannot be handled by the task validator.
User Action: Use the exception message to resolve the problem. If the problem persists, check the technical information databases at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or refer to http://www.ibm.com/software/integration/wps/support/ for information about IBM Software Support and Services.

 

CWTKV0050E: Task validation error: ''{0}''. Error parameters: {1}.
Explanation: This is a general purpose message that is used when the product is in service and a new error message is needed.
User Action: Check the error message for a description of the error.

 

CWTKV0051W: Task validation warning: ''{0}''. Warning parameters: {1}.
Explanation: This is a general purpose message that is used when the product is in service and a new warning message is needed.
User Action: Check the warning message for a description of the warning.

 

CWTKV0052I: Task validation information: ''{0}''. Information parameters: {1}.
Explanation: This is a general purpose message that is used when the product is in service and a new information message is needed.
User Action: No action is required.

 

CWTKV0100E: The interface element is missing.
Explanation: This task requires an interface element as part of its definition.
User Action: Add an interface element to this task. You may need to open the task file in the text editor and edit the source.

 

CWTKV0101E: The human task ''{0}'' has a task kind that does not support the people (staff) assignment role ''{1}''.
Explanation: Different task kinds support different people (staff) assignment roles.
User Action: Change the task kind or remove the people (staff) assignment role that is not supported.

 

CWTKV0102E: The contact query category ''{1}'' for the task model ''{0}'' is not unique.
Explanation: The category attributes in the contact queries list must be unique within a task definition.
User Action: Use different category names.

 

CWTKV0103E: The calendarName entry must be specified for the task model ''{0}'' if the calendarJNDIName attribute is set.
Explanation: If you specify a JNDI name for the calendar, you must specify a name for the calendar.
User Action: Add a value for the calendarName entry or remove the calendarJNDIName attribute.

 

CWTKV0104E: The ''{1}'' elements of the task ''{0}'' do not have a locale entry that matches the defaultLocale entry of the task.
Explanation: Exactly one element of the given type must have an attribute locale that is identical to the defaultLocale attribute.
User Action: Change the elements of the task so that both of the following conditions are true: Each description (documentation, displayName) has a locale attribute, and only one description (documentation, displayName) has an attribute locale that matches the defaultLocale attribute. You cannot have two descriptions (documentations, displayNames) with the same locale. In WebSphere Integration Developer, open the task file in the text editor to fix the problem in the source.

 

CWTKV0105E: The locale attributes specified for the ''{1}'' elements of the ''{0}'' task are not unique.
Explanation: You cannot have more than one documentation, description, and displayName element for each locale.
User Action: Change the elements of the task so that there is only one documentation, description, and displayName element for each locale. In WebSphere Integration Developer, open the task file in the text editor to fix the problem in the source.

 

CWTKV0106E: The ''{1}'' elements of the ''{0}'' escalation do not have a locale attribute that matches the defaultLocale attribute of the task.
Explanation: Exactly one element of the given type must have an attribute locale that is identical to the defaultLocale attribute.
User Action: Change the elements of the escalation so that both of the following conditions are true: Each description (documentation, displayName) has a locale attribute, and only one description (documentation, displayName) has an attribute locale that matches the defaultLocale attribute. You cannot have two descriptions (documentations, displayNames) with the same locale. In WebSphere Integration Developer, open this task file in the text editor to fix the problem in the source.

 

CWTKV0107E: The locale attributes specified for the ''{1}'' elements of the ''{0}'' escalation are not unique.
Explanation: You cannot have more than one documentation, description, and displayName element for each locale attribute.
User Action: Change the elements of the escalation so that there is only one documentation, description, and displayName element for each locale. In WebSphere Integration Developer, open this task file in the text editor to fix the problem in the source.

 

CWTKV0108E: The escalation name ''{1}'' is not unique for the escalations of the task model ''{0}''.
Explanation: Escalation names must be unique over the scope of a task. Escalation names are mandatory.
User Action: Choose a different name for the escalation.

 

CWTKV0109E: The file could not be read. Detail message: ''{0}''.
Explanation: The TEL file could not be found or another error occurred when reading the file.
User Action: Check the detail message.

 

CWTKV0110E: The XML namespace of the document is not set to ''{0}''.
Explanation: Unknown XML namespaces are not supported.
User Action: Use the correct XML namespace.

 

CWTKV0111E: The interface in the task model ''{0}'' has an incorrect number of operations.
Explanation: All task kinds must have interfaces that have only one operation.
User Action: Choose a different interface or modify the existing port type.

 

CWTKV0112E: Escalation action ''eMail'' is not allowed for the escalation receiver ''nobody'' ,''everybody'', or ''Group'' on the ''{1}'' escalation of the ''{0}'' task .
Explanation: Escalation action 'eMail' is not allowed for the escalation receiver people assignment criteria (verb) 'nobody', 'everybody', or 'Group'.
User Action: Choose a different escalation action or a different people assignment criteria for the escalation receiver.

 

CWTKV0113E: The import element is missing.
Explanation: The import element must be specified for collaboration tasks, invocation tasks and to-do tasks.
User Action: Specify the import element. In WebSphere Integration Developer, open this task file in the text editor. You should find something like <tel:importimportType=.http://schemas.xmlsoap.org/wsdl/

 

CWTKV0114E: The location attribute in the import element is missing.
Explanation: The location attribute in the import element must be specified for collaboration tasks, invocation tasks and to-do tasks.
User Action: Set the location attribute in the import element. In WebSphere Integration Developer, open the this task file in the text editor. You should find something like location="InterfaceName.wsdl".

 

CWTKV0115E: The namespace attribute in the import element is missing.
Explanation: The namespace attribute in the import element must be specified for collaboration tasks, invocation tasks and to-do tasks.
User Action: Set the namespace attribute in the import element. In WebSphere Integration Developer, open this task file in the text editor. You should find something like namespace="http://ModuleName/TaskInterface"/.

 

CWTKV0116E: The ''{0}'' WSDL file was not found.
Explanation: The WSDL file that the task refers to was not found.
User Action: Make sure that the WSDL file is available. In WebSphere Integration Developer, in the human task editor, select the Service Interface section on the canvas. In the Properties view, browse to select another interface.

 

CWTKV0117E: The ''{0}'' portType is missing.
Explanation: The portType referenced in the interface of the task must be defined in the WSDL file.
User Action: Define the interface correctly in the WSDL file. In WebSphere Integration Developer, open the interface in the text editor. You should add something like <wsdl:portType name="collaborationTaskInterface">;.

 

CWTKV0118E: The ''{0}'' operation that the interface refers to is missing.
Explanation: The operation that the interface refers to must be defined in the WSDL interface.
User Action: Define the operation correctly in the WSDL file. In WebSphere Integration Developer, open the interface either in the interface editor or the text editor to add the missing operation.

 

CWTKV0119E: The ''{0}'' parameter value is not allowed in stand-alone tasks.
Explanation: All parameter values starting with '%wf:' are only allowed in inline tasks, also known in WebSphere Integration Developer as tasks defined in a business process.
User Action: Use another parameter value. In WebSphere Integration Developer, use another variable.

 

CWTKV0120E: The notification type ''eMail'' is not supported by the ''{0}'' selected people directory configuration (staff plug-in configuration) (escalation ''{1}'', escalationAction attribute).
Explanation: The notification type 'eMail' is not supported by the built-in people directory configurations (staff plug-in configurations) with the JNDI names 'bpe/staff/userregistryconfiguration', 'bpe/staff/everybodyconfiguration' and 'bpe/staff/systemconfiguration'.
User Action: Either use a people directory configuration (staff plug-in configuration) that supports the notification type 'eMail' or select a different notification type. In WebSphere Integration Developer, select the specified escalation of this task. In the Properties view, on the Details tab, choose a different notification type than E-mail.

 

CWTKV0122E: The eventHandlerName attribute is missing.
Explanation: When an escalation with attribute escalationAction='event' is set, the eventHandlerName attribute must be specified.
User Action: Add the eventHandlerName attribute. In WebSphere Integration Developer, in the human task editor, open the task properties pages using the icon of the task section at the top of the canvas. On the Details tab, specify a valid event handler name.

 

CWTKV0123E: The durationUntilDeleted attribute in the ''{0}'' task model is not allowed for inline tasks.
Explanation: To-do inline tasks and administration inline tasks are part of the process and will be deleted with the process. In WebSphere Integration Developer, inline tasks are tasks that are defined inside the process.
User Action: Remove the durationUntilDeleted attribute. In WebSphere Integration Developer, open this file in the text editor. Remove something like durationUntilDeleted="DURATION_ZERO".

 

CWTKV0124E: The durationUntilExpires attribute in the ''{0}'' task model is not allowed for inline tasks.
Explanation: To-do inline tasks and administration inline tasks are part of the process and will expire with the process. In WebSphere Integration Developer, inline tasks are those that are defined inside the process.
User Action: Remove the durationUntilExpires attribute. In WebSphere Integration Developer, open the .tel file with a text editor and remove the attribute and the corresponding value (for example, remove durationUntilExpires="DURATION_ZERO").

 

CWTKV0125W: The validFrom attribute in the ''{0}'' task model is not allowed for inline tasks. In WebSphere Integration Developer, inline tasks are tasks that are defined inside the process.
Explanation: The validfrom attribute is used from the process. In WebSphere Integration Developer, inline tasks are tasks that are defined inside the process.
User Action: Remove the validFrom attribute. In WebSphere Integration Developer, open the task properties pages using the icon of the task section at the top of the canvas. On the Details page, remove the "Date (UTC) when task becomes valid" setting.

 

CWTKV0126W: The customProperty element in the ''{0}'' task model is not allowed for inline tasks.
Explanation: Inline tasks do not support custom properties. In WebSphere Integration Developer, inline tasks are tasks that are defined inside the process.
User Action: Remove the element customProperty. In WebSphere Integration Developer, open the task properties pages using the icon of the task section at the top of the canvas. On the Environment tab, remove the setting for the custom properties.

 

CWTKV0127E: The ''{0}'' task model contains a businessRelevance attribute with the value ''yes'', which is not allowed for inline tasks.
Explanation: The businessRelevance attribute from the process is used. In WebSphere Integration Developer, inline tasks are tasks that are defined inside the process.
User Action: Either set the businessRelevance attribute to "no" or remove the attribute. In WebSphere Integration Developer, open the task properties pages using the icon of the task section at the top of the canvas. On the Details tab, clear the Business-relevant checkbox.

 

CWTKV0128E: The e-mail receiver is missing in the ''{0}'' escalation.
Explanation: If the escalation action is 'eMail', then the e-mail receiver must be specified.
User Action: Specify the e-mail receiver or select a different action. In WebSphere Integration Developer, in the human task editor, select the escalation and open the "Assign People" properties page. Make sure, that "nobody", "everybody", and "Group" are not selected as people assignment criteria in the drop down combo box.

 

CWTKV0129E: Context authorization for ''{1}'' must be ''none'' in the ''{0}'' task model.
Explanation: Only inline to-do tasks are allowed to have the reader authorization of the context.
User Action: Change the context authorization to 'none'.

 

CWTKV0131W: Escalation action ''eMail'' is defined, but the email attribute has not been specified in the ''{1}'' escalation of the ''{0}'' task model.
Explanation: If an escalation action is set to 'eMail' an 'email' entry must be defined, which refers to the e-mail message.
User Action: Change the escalation action to a different action or define the 'email' entry on the escalation. In WebSphere Integration Developer, open this task file in the text editor. You should find something like email="DefaultMessage".

 

CWTKV0132W: The ''{0}'' email entry is specified, but the escalation action ''eMail'' is not defined in the ''{2}'' escalation of the ''{1}'' task model.
Explanation: If an 'email' entry is specified, but the escalation action 'eMail' is not defined, the email entry will be ignored.
User Action: Change the escalation action to "eMail" or remove the email entry on the escalation. In WebSphere Integration Developer, in the human task editor, select the escalation. In the Properties view, on the Details tab, set the notification type to "E-mail" or open the text editor and delete the email entry.

 

CWTKV0133E: The ''{0}'' email entry in the ''{2}'' escalation refers to an e-mail message that is not specified on the ''{1}'' task model.
Explanation: If an email attribute is specified on an escalation, the referenced e-mail message must be defined on the task.
User Action: Insert the referenced e-mail message on the task model or change the email attribute to an existing e-mail message. In WebSphere Integration Developer, open this task file in the text editor. You should find something like email="DefaultMessage".

 

CWTKV0134E: No e-mail message was found with a locale equals to the task defaultlocale for the ''{0}'' email entry in the ''{2}'' escalation on the ''{1}'' task model.
Explanation: An e-mail message must have exactly one entry with a locale that is equal to the default locale defined on the task model.
User Action: Insert an email message entry with a locale that is equal to the default locale. In Websphere Integretation Developer open this file in the text editor. Set the locale of the localizedEmail to the same value as the defaultLocale of the task.

 

CWTKV0135E: Locale ''{0}'' is not unique in e-mail message ''{2}'' on the task model ''{1}''.
Explanation: All locales in an e-mail message must be unique. If no locale attribute exists, the default locale defined on the task will be used.
User Action: Edit the locales so that they are unique.

 

CWTKV0136W: Locale ''{0}'' in e-mail message ''{2}'' differs from the default locale defined on the task model ''{1}''.
Explanation: Only e-mail messages with a locale equal to the default locale are allowed.
User Action: Ensure that the locale is equal to default locale defined on the task model.

 

CWTKV0137E: The ''{1}'' client type for customClientSetting is not unique on the ''{0}'' task model.
Explanation: Multiple sub-elements of the same type are not supported in uiSettings that have the same clientType.
User Action: Edit the clientType so that it is unique. In WebSphere Integration Developer, open the specified task file in the text editor and eliminate the duplicate entries for the same client type.

 

CWTKV0138E: The ''{2}'' name for customSetting in the ''{1}'' clientType is not unique in the ''{0}'' task model.
Explanation: Two customSettings sections cannot have the same name.
User Action: Edit the name for one of the customSetting sections so that it is unique.

 

CWTKV0139E: The ''{0}'' substitutionPolicy is not supported by the ''{1}'' selected people directory configuration (staff plug-in configuration).
Explanation: The selected substitution policy is not supported by the built-in people directory configurations (staff plug-in configurations) with the JNDI names 'bpe/staff/userregistryconfiguration', 'bpe/staff/everybodyconfiguration', and 'bpe/staff/systemconfiguration'.
User Action: Either use a people directory configuration (staff plug-in configuration) that supports the selected substitutionPolicy or select the substitutionPolicy 'NoSubstitution'. You can find the substitution settings in the human task editor of the task settings, in the Properties view, on the Details tab. Click the properties pages button in the top section of the canvas.

 

CWTKV0140E: The ''{0}'' priorityDefinition value is not a valid variable or an integer greater than or equal to zero.
Explanation: The value of priorityDefinition must contain a valid variable (starting with '%' and ending with '%') or an integer that is greater than or equal to zero.
User Action: Insert a valid variable or an integer that is greater than or equal to zero. You can find this setting on the "Details" page in the properties view of the task settings. Press the properties pages button in the top section of the canvas. Make sure to provide a valid value.

 

CWTKV0141E: The duration attribute ''{1}'' defined on task model ''{0}'', contains a value ''{2}'' that is not valid. The calendar validation message is ''{3}''.
Explanation: If you specify a duration, the value must be valid for the calendar in use.
User Action: Correct the duration value so that it is valid for the calendar that is used. In WebSphere Integration Developer, select the button in the top row of the canvas to open the task properties pages. On the Duration tab, choose the calendar type and enter a value in the duration field that conforms to the selected format. Press F1 to get more information about the format.

 

CWTKV0142W: The duration attribute ''{1}'' defined on task model ''{0}'' contains a value ''{2}'' that is not valid. The calendar validation message is ''{3}''.
Explanation: If you specify a duration, the value must be valid for the calendar in use.
User Action: Correct the duration value so that it is valid for the calendar that is used. In WebSphere Integration Developer, select the button in the top row of the canvas to open the task properties pages. Go to "Duration" page. Choose the calendar type and enter a value in the duration field related to that selected format. Press F1 to get more information about the format.

 

CWTKV0143I: The calendar validation reports the following information for the ''{1}'' attribute which is defined on the ''{0}'' task model: ''{2}''
Explanation: This is an information message that is created by the calendar validator.
User Action: No action is required.

 

CWTKV0144E: The ''{2}'' entry defined on the ''{1}'' escalation in task model ''{0}'' contains an invalid value ''{3}'': ''{4}''
Explanation: If you specify a duration, the value must be valid for the calendar in use.
User Action: Correct the duration value so that it is valid for the calendar that is used. In WebSphere Integration Developer, select the button in the top row of the canvas to open the task properties pages. Go to "Duration" page. Choose the calendar type and enter a value in the duration field related to that selected format. Press F1 to get more information about the format.

 

CWTKV0145W: The ''{2}'' entry defined on the ''{1}'' escalation in task model ''{0}'' contains an invalid value ''{3}'': ''{4}''
Explanation: If you specify a duration, the value must be valid for the calendar that is used.
User Action: Correct the duration value so that it is valid for the calendar. In WebSphere Integration Developer, select the button in the top row of the canvas to open the task properties pages. Go to "Duration" page. Choose the calendar type and enter a value in the duration field related to that selected format. Press F1 to get more information about the format.

 

CWTKV0146I: The calendar validation reports the following information for the ''{2}'' attribute, which is defined on the ''{1}'' escalation in the ''{0}'' task model: ''{3}''.
Explanation: This is a information message, created from the calendar validation.
User Action: No action is required.

 

CWTKV0147E: The calendar validation plug-in reports a result that is not valid for the ''{1}'' attribute with the value ''{2}'', which is defined on the ''{0}'' task model: ''{3}''.
Explanation: Because the result is not valid, it could not be analyzed.
User Action: Adapt the calendar validation plug-in.

 

CWTKV0148E: The calendar validation plug-in reports a result that is not valid for the ''{2}'' attribute with the value ''{3}'', which is defined on the ''{1}'' escalation in the ''{0}'' task model: ''{4}''.
Explanation: Because the result is not valid, it could not be analyzed.
User Action: Adapt the calendar validation plug-in.

 

CWTKV0149W: The autonomy attribute must not be set in the ''{0}'' inline task model.
Explanation: Inline tasks must not contain the autonomy attribute. For inline tasks, the autonomy attribute is ignored during deployment.
User Action: Remove the autonomy attribute. In WebSphere Integration Developer, open the specified task file in a text editor to correct the setting in the source code.

 

CWTKV0150E: The autonomy attribute must not have the ''child'' value in the ''{0}'' task model.
Explanation: Invocation tasks with a one-way interface must not contain the autonomy attribute with the 'child' value .
User Action: Either change the value of the attribute 'autonomy' to 'peer' or remove the attribute. Another option is to use a two-way interface. In WebSphere Integration Developer, open the specified task file in a text editor to correct this setting in the source code.

 

CWTKV0151E: The autonomy attribute must not have the value ''child'' in the ''{0}'' task model.
Explanation: Collaboration and to-do tasks must not contain the autonomy attribute with the value 'child'.
User Action: Either change the value of the attribute 'autonomy' to 'peer' or remove the attribute. In WebSphere Integration Developer, open the specified task file in a text editor to correct this setting in the source code.

 

CWTKV0201W: The supportsSubTask attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Administration tasks do not support subtasks.
User Action: Change the value of the supportsSubTask attribute to "no". In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code.

 

CWTKV0202E: The allowClaimWhenSuspended attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Administration tasks cannot be claimed.
User Action: Change the value of the allowClaimWhenSuspended attribute to "no" or remove it. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code.

 

CWTKV0203E: The autoClaim attribute must have the value ''no'' in the ''{0}'' task model .
Explanation: Administration tasks cannot be claimed.
User Action: Either change the value of the autoClaim attribute to "no" or remove the attribute. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code.

 

CWTKV0204E: The administration task in ''{0}'' task model contains the activation state waitingForSubTask.
Explanation: Administration tasks do not support the activation state waitingForSubTask. Reserved for future use.
User Action: Remove the activation state waitingForSubTask. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code.

 

CWTKV0205E: The ''{2}'' atLeastExpectedState in the ''{1}'' escalation is not valid for administration tasks in the ''{0}'' task model.
Explanation: Administration tasks must have the atLeastExpectedState set to 'ended'.
User Action: Change the atLeastExpectedState to 'ended'. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code.

 

CWTKV0206W: The supportsFollowOnTask attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Administration tasks do not support follow-on tasks.
User Action: Change the value of the supportsFollowOnTask attribute to "no". In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code.

 

CWTKV0300I: A potential owner element is missing in the ''{0}'' task model.
Explanation: If a collaboration task does not contain a potential owner element, the default 'Everybody' is used.
User Action: If the default 'Everybody' should not be used, add a potential owner element. In WebSphere Integration Developer, in the human task editor canvas, go to the "People Assignment" sections and add the Potential Owners by clicking on the "+" symbol on the canvas in this section.

 

CWTKV0301I: A potential instance creator element is missing in the ''{0}'' task model.
Explanation: If a collaboration task does not contain a potential instance creator element, the default 'Everybody' is used.
User Action: If the default 'Everybody' should not be used, add a potential instance creator element. In WebSphere Integration Developer, in the human task editor canvas, go to the "People Assignment" sections and add the Potential Creators by clicking on the "+" symbol the canvas in this section.

 

CWTKV0302E: The interface kind is not 'internal'.
Explanation: The interface kind of the human task must be 'internal'.
User Action: Change the interface kind to "internal". In WebSphere Integration Developer, open the task file in the text editor to correct this setting in the source code: <tel:interface kind="internal".

 

CWTKV0303E: The ''{2}'' atLeastExpectedState in the ''{1}'' escalation is not valid for collaboration tasks in the ''{0}'' task model.
Explanation: Collaboration tasks must have the atLeastExpectedStates set to "claimed", "subTasksCompleted," or "ended".
User Action: Change the atLeastExpectedState to either "claimed", "subTasksCompleted" or "ended".

 

CWTKV0304E: The ''{2}'' atLeastExpectedState in the ''{1}'' escalation is not valid for collaboration tasks after the ''{3}'' atLeastExpectedState in the ''{0}'' task model.
Explanation: Escalations in a chain must not have a decreasing expected state sequence.
User Action: Change the sequence of the atLeastExpectedState or change the atLeastExpectedState.

 

CWTKV0400I: A potential instance creator element is missing in the ''{0}'' task model.
Explanation: If an invocation task does not contain a potential instance creator element, the default 'Everybody' is used.
User Action: If the default 'Everybody' should not be used, add a potential instance creator element. In WebSphere Integration Developer, in the human task editor canvas, go to the "People Assignment" section and add the Potential Creators by clicking on the "+" symbol on the canvas in this section.

 

CWTKV0401I: A potential starter element is missing in the ''{0}'' task model.
Explanation: If an invocation task contains no potential starter element, the default originator is used.
User Action: If the default originator should not be used, add a potential starter element. In WebSphere Integration Developer, in the human task editor canvas, go to the "People Assignment" sections and add the Potential Starters by clicking on the "+" symbol on the canvas in this section.

 

CWTKV0402E: The interface kind is not ''outbound'' in the ''{0}'' task model.
Explanation: The interface kind of the invocation task must be 'outbound'.
User Action: Change the interface kind to 'outbound'. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code: <tel:interface kind="outbound".

 

CWTKV0404W: The supportsSubTask attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Invocation tasks do not support subtasks.
User Action: Change the value for the supportsSubTask attribute to "no". In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code: supportsSubTask="no".

 

CWTKV0405E: The allowClaimWhenSuspended attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Invocation tasks cannot be claimed.
User Action: Change the value of the allowClaimWhenSuspended attribute to "no". In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code: allowClaimWhenSuspended="no". Alternately remove the attribute.

 

CWTKV0406E: The autoClaim attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Invocation tasks cannot be claimed.
User Action: Either change the value of the attribute 'autoClaim' to 'no' or remove the attribute. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code: autoClaim="no".

 

CWTKV0407E: The invocation task contains an activation state waitingForSubTask in the ''{0}'' task model.
Explanation: Invocation tasks does not support the activation state waitingForSubTask. Reserved for future use.
User Action: Remove the activation state waitingForSubTask. In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code. Set the activation state to activationState="running".

 

CWTKV0408E: The potential starter, ''{1}'', is not the same as the potential instance creator in the ''{0}'' task model.
Explanation: For invocation tasks, the potential starter must be the same as the potential instance creator.
User Action: Edit the potential starter so that it is the same as the potential instance creator.

 

CWTKV0409E: The ''{2}'' atLeastExpectedState in the ''{1}'' escalation is not valid for invocation tasks in the ''{0}'' task model.
Explanation: The invocation task must have all atLeastExpectedStates set to "ended".
User Action: Change the atLeastExpectedState to "ended". In WebSphere Integration Developer, in the human task editor, select the escalation on the canvas. In the Properties view, on the Details tab, select "Ended" in the Expected task state field.

 

CWTKV0410E: The ''{0}'' task model contains a description for the inline invocation tasks.
Explanation: Invocation inline tasks must not have a description because they are used by the surrounding activity. In WebSphere Integration Developer, inline tasks are tasks defined inside a business process.
User Action: Remove the description element. In WebSphere Integration Developer, open the specified task file in the text editor and remove the description entry.

 

CWTKV0411E: The ''{0}'' task model contains documentation for the inline invocation tasks.
Explanation: Invocation inline tasks must not have documentation because they are used by the surrounding activity. In WebSphere Integration Developer, inline tasks are tasks defined inside a business process.
User Action: Remove the documentation element. In WebSphere Integration Developer, open the specified task file in the text editor and remove the documentation entry.

 

CWTKV0412E: The ''{0}'' task model contains a display name for the inline invocation tasks.
Explanation: InlInvocation inline tasks must not have a display name because they are used from the surrounding activity. In WebSphere Integration Developer, inline tasks are tasks defined inside a business process.
User Action: Remove the displayName element. In WebSphere Integration Developer, open the specified task file in the text editor and remove the display name entry.

 

CWTKV0413W: The supportsFollowOnTask attribute must have the value ''no'' in the ''{0}'' task model.
Explanation: Invocation tasks do not support follow-on tasks.
User Action: Change the value of the supportsFollowOnTask attribute to "no". In WebSphere Integration Developer, open the task file in the text editor to correct the setting in the source code: supportsFollowOnTask="no".

 

CWTKV0500E: The interface kind is not ''inbound'' in the ''{0}'' task model.
Explanation: The interface kind of the to-do task must be 'inbound'.
User Action: Change the interface kind to "inbound". In WebSphere Integration Developer, open the specified task file in the text editor to correct this setting in the source code: tel:interface kind="inbound".

 

CWTKV0501I: A potential owner element is missing in the ''{0}'' task model.
Explanation: If a to-do task does not contain a potential owner element, the default 'Everybody' is used.
User Action: If the default 'Everybody' should not be used, add a potential owner element. In WebSphere Integration Developer, on the canvas, go to the "People Assignment" section and add the Potential Owners by clicking on the "+" symbol on the canvas in this section.

 

CWTKV0502E: The ''{0}'' task model contains a description for the to-do inline tasks.
Explanation: To-do inline tasks must not have a description element, they are used from the surrounding activity. In WebSphere Integration Developer, inline tasks are tasks defined inside of a business process.
User Action: Remove the description element. In WebSphere Integration Developer, open the specified task file in the text editor and remove the description entry.

 

CWTKV0503E: The ''{0}'' task model contains documentation for the to-do inline tasks.
Explanation: To-do inline tasks must not have a documentation element because they are used from the surrounding activity. In WebSphere Integration Developer, inline tasks are tasks defined inside of a business process.
User Action: Remove the documentation element. In WebSphere Integration Developer, open the task file in the text editor. Remove the documentation entry.

 

CWTKV0504E: The ''{0}'' task model contains a display name for the to-do inline tasks.
Explanation: To-do inline tasks must not have a display name element because they are used from the surrounding activity. In WebSphere Integration Developer, inline tasks are tasks defined inside a business process.
User Action: Remove the displayName element. In WebSphere Integration Developer, open the task file in the text editor and remove the display name entry.

 

CWTKV0505E: The ''{2}'' atLeastExpectedState in the ''{1}'' escalation is not valid for to-do tasks in the ''{0}'' task model .
Explanation: To-do tasks must have atLeastExpectedStates set to "claimed", "subTasksCompleted" or "ended".
User Action: Change the atLeastExpectedState to "claimed", "subTasksCompleted", or "ended".

 

CWTKV0506E: The ''{2}'' atLeastExpectedState in the ''{1}'' escalation is not valid for to-do tasks after the ''{3}'' atLeastExpectedState in the ''{0}'' task model .
Explanation: Escalations in a chain must not have a decreasing expected state sequence.
User Action: Change the sequence of the atLeastExpectedState or change the atLeastExpectedState.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009