- 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: None.
- 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.
- 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: None.
- 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.
- CWTKV0101E: The task ''{0}'' has a type that does not support the staff query role ''{1}''.
- Explanation: Different task types support different staff query roles.
- User Action: Change the task type or remove the staff query 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 attribute 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 attribute or remove the calendarJNDIName attribute.
- CWTKV0104E: The ''{1}'' elements of the task ''{0}'' do not have a locale attribute matching with the defaultLocale attribute of the task.
- Explanation: Exactly one element of the given type must have an attribute locale which is identical with the defaultLocale attribute.
- User Action: Ensure that both of the following conditions are true: 1) Each description (documentation, displayName) has a locale attribute 2) Exactly one description (documentation, displayName) have an attribute locale which matches the attribute 'defaultLocale'. You cannot have two descriptions (documentations, displayNames) with the same locale.
- CWTKV0105E: The locale attributes specified for the ''{1}'' elements of the task ''{0}'' are not unique.
- Explanation: You cannot have more than one documentation, description, and displayName element for each locale.
- User Action: Ensure that there is only one documentation, description, and displayName element for each locale.
- CWTKV0106E: The ''{1}'' elements of the escalation ''{0}'' do not have a locale attribute matching with the defaultLocale attribute of the task.
- Explanation: Exactly one element of the given type must have an attribute locale which is identical with the defaultLocale attribute.
- User Action: Ensure that both of the following conditions are true: 1) Each description (documentation, displayName) has a locale attribute 2) Exactly one description (documentation, displayName) have an attribute locale which matches the attribute 'defaultLocale'. You cannot have two descriptions (documentations, displayNames) with the same locale.
- CWTKV0107E: The locale attributes specified for the ''{1}'' elements of the escalation ''{0}'' are not unique.
- Explanation: You cannot have more than one documentation, description, and displayName element for each locale attribute.
- User Action: Ensure that there is only one documentation, description, and displayName element for each locale.
- 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'' and ''Group'' on escalation ''{1}'' of task ''{0}''.
- Explanation: Escalation action 'eMail' is not allowed for the escalation receiver verb 'nobody', 'everybody' and 'Group'.
- User Action: Choose a different escalation action or a different verb for the escalation receiver.
- CWTKV0113E: No import element is specified.
- Explanation: The import element must be specified for pure human tasks, originating tasks and participating tasks.
- User Action: Ensure the import element is set.
- CWTKV0114E: The location attribute in the import element must be set.
- Explanation: The location attribute in the import element must be specified for pure human tasks, originating tasks and participating tasks.
- User Action: Ensure the location attribute in the import element is set.
- CWTKV0115E: The namespace attribute in the import element must be set.
- Explanation: The namespace attribute in the import element must be specified for pure human tasks, originating tasks and participating tasks.
- User Action: Ensure the namespace attribute in the import element is set.
- CWTKV0116E: The WSDL file ''{0}'' was not found.
- Explanation: The WSDL file referenced in the task was not found.
- User Action: Check that the WSDL file is available.
- CWTKV0117E: The portType ''{0}'' was not found.
- Explanation: The portType referenced in the interface of the task is not defined in the WSDL interface.
- User Action: Check that the portType is defined correctly in the WSDL interface.
- CWTKV0118E: The operation ''{0}'' was not found.
- Explanation: The operation referenced in the interface of the task is not defined in the WSDL interface.
- User Action: Check that the operation is defined correctly in the WSDL interface.
- CWTKV0119E: The parameter value ''{0}'' is not allowed in standalone tasks.
- Explanation: All parameter values starting with '%wf:' are only allowed in inline tasks.
- User Action: Use another parameter value.
- CWTKV0120E: The notification type ''E-mail'' is not supported by the selected staff plug-in provider ''{0}'' (escalation ''{1}'', escalationAction attribute).
- Explanation: The notification type 'E-mail' is only supported by the built-in staff plug-in provider with JNDI name 'bpe/staff/sampleldapconfiguration' or a user-defined staff plug-in provider.
- User Action: Either use a staff plug-in provider which supports the notification type 'E-mail' or select an other notification type.
- CWTKV0122E: A escalation with notification type 'event' was found, but no eventHandlerName attribute is set.
- Explanation: When an escalation with attribute escalationAction='event' is set the eventHandlerName attribute is recommended.
- User Action: Add the eventHandlerName attribute.
- CWTKV0123E: The durationUntilDeleted attribute in task model ''{0}'' is not allowed for inline tasks.
- Explanation: Participating inline tasks and administrative inline tasks are part of the process and will be deleted with the process.
- User Action: Remove the attribute durationUntilDeleted.
- CWTKV0124E: The durationUntilExpires attribute in task model ''{0}'' is not allowed for inline tasks.
- Explanation: The expiration of the inline task is controlled by the surrounding activity.
- User Action: Remove the attribute 'durationUntilExpires'.
- CWTKV0125W: The validFrom attribute in task model ''{0}'' is not allowed for inline tasks.
- Explanation: The validfrom attribute is used from process.
- User Action: Remove the validFrom attribute.
- CWTKV0126W: The customProperty element in task model ''{0}'' is not allowed for inline tasks.
- Explanation: Inline tasks does not support custom properties.
- User Action: Remove the element customProperty.
- CWTKV0127E: The task model ''{0}'' contains a businessRelevance attribute with the value ''yes'', which is not allowed for inline tasks.
- Explanation: The businessRelevance attribute from process is used.
- User Action: Set the businessRelevance attribute to 'no' or remove the attribute.
- CWTKV0128E: Email receiver is missing in escalation ''{0}''.
- Explanation: If the escalation action is 'eMail', then the email receiver must be specified.
- User Action: Specify the email receiver or select another action.
- CWTKV0129E: Context authorization for ''{1}'' must be ''none'' in the task model ''{0}''.
- Explanation: Only inline participating tasks are allowed to have the reader authorization of the context.
- User Action: Change the context authorization to 'none'.
- CWTKV0131E: Escalation action ''eMail'' is defined, but no email attribute has been specified in escalation ''{1}'' of the task model ''{0}''.
- Explanation: If an escalation action is set to 'eMail' an email attribute must be defined, which references the email message.
- User Action: Change the escalation action to another action or define the email attribute on the escalation.
- CWTKV0132W: Email attribute ''{0}'' is specified, but no escalation action ''eMail'' is defined in escalation ''{2}'' of the task model ''{1}''.
- Explanation: If an email attribute is specified, but no escalation action 'eMail' is defined, the email attribute will be ignored.
- User Action: Change the escalation action to 'eMail' or remove the email attribute.
- CWTKV0133E: Email attribute ''{0}'' in escalation ''{2}'' references to an email message which is not specified on the task model ''{1}''.
- Explanation: If an email attribute is specified on an escalation, the referenced email message must be defined on task.
- User Action: Insert referenced email message on the task model or change the email attribute to an existing email message.
- CWTKV0134E: No email message found with a locale equals to the task defaultlocale for the email attribute ''{0}'' in escalation ''{2}'' on the task model ''{1}'' .
- Explanation: An email message must have exactly one entry with a locale equals to the default locale defined on the task model.
- User Action: Insert email message entry with a locale equals to the default locale.
- CWTKV0135E: Locale ''{0}'' not unique in email message ''{2}'' on the task model ''{1}''.
- Explanation: All locales in an email message must be unique. If no locale attribute exists, the default locale defined on the task will be used.
- User Action: Ensure that the locales are unique.
- CWTKV0136W: Locale ''{0}'' in email message ''{2}'' differs from default locale defined on the task model ''{1}''.
- Explanation: Only email messages with a locale equals to the defaultlocale are allowed.
- User Action: Ensure that the locale is equal to default locale defined on the task model.
- CWTKV0137E: Client type ''{1}'' for customClientSetting is not unique on the task model ''{0}''.
- Explanation: It is not allowed to have multiple sub-elements of the same type within uiSettings that have the same clientType.
- User Action: Ensure that the clientType is unique.
- CWTKV0138E: Name ''{2}'' for customSetting in clientType ''{1}'' is not unique on the task model ''{0}''.
- Explanation: It is not allowed to specify two customSettings sections with the same name.
- User Action: Ensure that the name is unique.
- CWTKV0201W: The supportsSubTask attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Administrative tasks do not support subtasks.
- User Action: Change the value of the supportsSubTask attribute to 'no'.
- CWTKV0202E: The allowClaimWhenSuspended attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Administrative tasks cannot be claimed.
- User Action: Change the value of the allowClaimWhenSuspended attribute to 'no' or remove.
- CWTKV0203E: The autoClaim attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Administrative tasks cannot be claimed.
- User Action: Change the value of the autoClaim attribute to 'no' or remove attribute.
- CWTKV0204E: Administrative task in task model ''{0}'' contains the activation state waitingForSubTask.
- Explanation: Administrative tasks do not support the activation state waitingForSubTask. Reserved for future use.
- User Action: Remove the activation state waitingForSubTask.
- CWTKV0205E: AtLeastExpectedState ''{2}'' in escalation ''{1}'' is not valid for administrative tasks in the task model ''{0}''.
- Explanation: Administrative are allowed to have the atLeastExpextedState 'ended'.
- User Action: Change the atLeastExpectedState to 'ended'.
- CWTKV0206W: The supportsFollowOnTask attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Administrative tasks do not support followon tasks.
- User Action: Change the value of the supportsFollowOnTask attribute to 'no'.
- CWTKV0300I: A potential owner element is missing in the task model ''{0}''.
- Explanation: If a pure human task contains no potential owner element, the default 'Everybody' is used.
- User Action: Add a potential owner element, if the default 'Everybody' should not be used.
- CWTKV0301I: A potential instance creator element is missing in the task model ''{0}''.
- Explanation: If a pure human task contains no potential instance creator element, the default 'Everybody' is used.
- User Action: Add a potential instance creator element, if the default 'Everybody' should not be used.
- 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'.
- CWTKV0303E: AtLeastExpectedState ''{2}'' in escalation ''{1}'' is not valid for pure human tasks in the task model ''{0}''.
- Explanation: Pure human tasks are allowed to have the atLeastExpextedStates 'claimed', 'subTasksCompleted' and 'ended'.
- User Action: Change the atLeastExpectedState to 'claimed', 'subTasksCompleted' or 'ended'.
- CWTKV0304E: The AtLeastExpectedState ''{2}'' in escalation ''{1}'' is not valid for pure human tasks after the atLeastExpectedState ''{3}'' in the task model ''{0}''.
- Explanation: Escalations in a chain must not have decreasing expected state.
- User Action: Change the sequence of the atLeastExpectedState or change the atLeastExpectedState itself.
- CWTKV0400I: A potential instance creator element is missing in the task model ''{0}''.
- Explanation: If an originating task contains no potential instance creator element, the default 'Everybody' is used.
- User Action: Add a potential instance creator element, if the default 'Everybody' should not be used.
- CWTKV0401I: A potential starter element is missing in the task model ''{0}''.
- Explanation: If an originating task contains no potential starter element, the default originator is used.
- User Action: Add a potential starter element, if the default originator should not be used.
- CWTKV0402E: The interface kind is not ''outbound'' in the task model ''{0}''.
- Explanation: The interface kind of the originating task must be 'outbound'.
- User Action: Change the interface kind to 'outbound'.
- CWTKV0404W: The supportsSubTask attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Originating tasks do not support subtasks.
- User Action: Change the value for the supportsSubTask attribute to 'no'.
- CWTKV0405E: The allowClaimWhenSuspended attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Originating tasks cannot be claimed.
- User Action: Change the value of the attribute 'allowClaimWhenSuspended' attribute to 'no' or remove the attribute.
- CWTKV0406E: The autoClaim attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Originating tasks cannot be claimed.
- User Action: Change the value of the attribute 'autoClaim' to 'no' or remove the attribute.
- CWTKV0407E: Originating task contains an activation state waitingForSubTask in task model ''{0}''.
- Explanation: Originating tasks does not support the activation state waitingForSubTask. Reserved for future use.
- User Action: Remove the activation state waitingForSubTask.
- CWTKV0408E: The potential starter is ''{1}'' not equal to the potential instance creator in the task model ''{0}''.
- Explanation: It is required for originating tasks, that the potential starter is equal to the potential instance creator.
- User Action: Ensure that the potential starter is equal to the potential instance creator.
- CWTKV0409E: AtLeastExpectedState ''{2}'' in escalation ''{1}'' not valid for originating tasks in the task model ''{0}''.
- Explanation: Originating task are allowed to have the atLeastExpextedStates 'ended'.
- User Action: Change the atLeastExpectedState to 'ended'.
- CWTKV0410E: The task model ''{0}'' contains a description, which is not allowed for inline originating tasks.
- Explanation: Originating inline tasks must not have a description, because it used from the surrounding activity.
- User Action: Remove the description element.
- CWTKV0411E: The task model ''{0}'' contains a documentation, which is not allowed for inline originating tasks.
- Explanation: Originating inline tasks must not have a documentation, because it used from the surrounding activity.
- User Action: Remove the documentation element.
- CWTKV0412E: The task model ''{0}'' contains a display name, which is not allowed for inline originating tasks.
- Explanation: Originating inline tasks must not have a display name, because it used from the surrounding activity.
- User Action: Remove the displayName element.
- CWTKV0413W: The supportsFollowOnTask attribute must have the value ''no'' in the task model ''{0}''.
- Explanation: Originating tasks do not support followon tasks.
- User Action: Change the value of the supportsFollowOnTask attribute to 'no'.
- CWTKV0500E: The interface kind is not ''inbound'' in the task model ''{0}''.
- Explanation: The interface kind of the participating task must be 'inbound'.
- User Action: Change the interface kind to 'inbound'.
- CWTKV0501I: A potential owner element is missing in the task model ''{0}''.
- Explanation: If a participating task contains no potential owner element, the default 'Everybody' is used.
- User Action: Add a potential owner element, if the default 'Everybody' should not be used.
- CWTKV0502E: The task model ''{0}'' contains a description, which is not allowed for inline participating tasks.
- Explanation: Participating inline tasks must not have a description, because it used from the surrounding activity.
- User Action: Remove the description element.
- CWTKV0503E: The task model ''{0}'' contains a documentation, which is not allowed for inline participating tasks.
- Explanation: Participating inline tasks must not have a documentation, because it used from the surrounding activity.
- User Action: Remove the documentation element.
- CWTKV0504E: The task model ''{0}'' contains a display name, which is not allowed for inline participating tasks.
- Explanation: Participating inline tasks must not have a display name, because it used from the surrounding activity.
- User Action: Remove the displayName element.
- CWTKV0505E: AtLeastExpectedState ''{2}'' in escalation ''{1}'' not valid for participating tasks in the task model ''{0}''.
- Explanation: Participating task are allowed to have the atLeastExpextedStates 'claimed', 'subTasksCompleted' and 'ended'.
- User Action: Change the atLeastExpectedState to 'claimed', 'subTasksCompleted' or 'ended'
- CWTKV0506E: The AtLeastExpectedState ''{2}'' in escalation ''{1}'' is not valid for participating tasks after the atLeastExpectedState ''{3}'' in the task model ''{0}''.
- Explanation: Escalations in a chain must not have decreasing expected state.
- User Action: Change the sequence of the atLeastExpectedState or change the atLeastExpectedState itself.