Case management and FileNet P8 API integration messages
The case management and FileNet® P8 API integration messages contain information about errors and warnings that come from components in FileNet P8, such as Content Engine and Process Engine.
- FNRPA0003E
The {0} argument is missing. - FNRPA0004E
The {0} argument has an invalid value of {1}. - FNRPA0005I
{0} - FNRPA0006E
{0} - FNRPA0007E
The object {0} cannot be added to the {1} cache because an object of that name already exists. - FNRPA0008E
The {0} object cannot be added to the {1} cache because the object name is invalid. - FNRPA0009E
The cached object cannot be loaded because the cache loader for the {0} cache is null. - FNRPA0010E
The {0} object cannot be loaded into the {1} cache. - FNRPA0011I
Causes of the problem: - FNRPA0020E
The current REST request cannot be processed because the required {0} parameter is missing. - FNRPA0021E
The solution cannot be deployed because the resource path that is specified for the GET deployment status method was not found. - FNRPA0022E
The solution cannot be deployed because the solution definition document cannot be parsed. - FNRPA0023E
The solution cannot be deployed because a case type contains two properties with the {0} key and {1} name. - FNRPA0024E
The Content Platform Engine is not available or the connection definition is inaccurate. - FNRPA0025E
The solution is not fully deployed because the {0} document type could not be deployed. - FNRPA0026E
Information about the {0} solution cannot be accessed because the solution was not found. - FNRPA0027E
The solution definition file cannot be loaded because a duplicate {0} case type was found. - FNRPA0028E
The solution cannot be deployed because a case type contains two {0} property types. - FNRPA0029E
The solution cannot be deployed because a duplicate {0} document type was found. - FNRPA0030E
The solution cannot be deployed because the Process Engine configuration document could not be found. Document ID: {0}. - FNRPA0031E
The solution cannot be deployed because the unsupported XML element {0} was found in the solution definition file. - FNRPA0032E
The solution cannot be deployed because the Process Engine configuration document could not be imported. See the following error: {0} - FNRPA0033E
The solution cannot be deployed because the XPDL document {0} could not be found. - FNRPA0034E
The solution cannot be deployed because the validation of the XPDL document failed with the following Process Engine error message: {0} - FNRPA0035E
The solution cannot be deployed because the following Process Engine error occurred during the transfer of the workflow: {0} - FNRPA0036E
The solution cannot be deployed because the following Process Engine error occurred during the deployment of the XPDL document: {0} - FNRPA0038E
The solution cannot be deployed because the following solution definition file is empty: {0}. This file is located in the {1} object store. - FNRPA0039E
The solution could not be deployed because the {0} solution definition file in the {1} object store is not valid. - FNRPA0040E
The request cannot be processed because the Content Platform Engine server cannot be found. - FNRPA0041I
The following case subfolder is being deployed: {0}. - FNRPA0042E
The request cannot be processed because the {0} resource path was not found. - FNRPA0043E
The request cannot be processed because duplicate {0} handlers were found. - FNRPA0044E
An error occurred during registration because a null handler was found. - FNRPA0045E
An error occurred because a null connection definition was found. - FNRPA0046E
The solution cannot be deployed because the solution definition file contains a case type or a document type for which no properties are defined. - FNRPA0047E
The solution cannot be deployed because the property type is not compatible with the {0} property that is defined in the solution. - FNRPA0048E
The {0} property type is invalid. - FNRPA0049E
The solution could not be deployed because it contains the following unsupported property type: {0}. - FNRPA0050E
The solution cannot be deployed because the {0} default base class is not defined. - FNRPA0051E
The solution cannot be deployed because a duplicate Content Platform Engine {0} class was found. - FNRPA0052E
The solution cannot be deployed because an empty resource path value or class name was found. - FNRPA0053E
The solution cannot be deployed because the solution definition contains the following unsupported hash time pattern: {0}. - FNRPA0054E
The solution cannot be deployed because an empty case type folder was found. - FNRPA0055E
The connection definition could not be opened because it has no content or is corrupted. - FNRPA0056E
The connection definition could not be opened. - FNRPA0057E
The solution cannot be deployed because the content transfer type document {0} was not found. This document is in the {1} object store. - FNRPA0058E
The following temporary deployment log file could not be deleted: {0}. - FNRPA0059E
The solution cannot be deployed because Case Manager Builder could not open the following deployment log file: {0}. - FNRPA0060E
The solution cannot be deployed because Case Manager Builder could not write to the following temporary deployment log file: {0}. - FNRPA0061I
ERROR - FNRPA0062I
WARNING - FNRPA0063E
The content for the following document is not valid: ID: {0}, design object store: {1} - FNRPA0064E
The solution cannot be deployed because the {0} solution definition file could not be found. - FNRPA0065E
The solution cannot be deployed because the connection definition document {0} could not be found. - FNRPA0066E
The solution cannot be deployed because Case Manager Builder could not retrieve one of the logs for the {0} solution. - FNRPA0067E
The solution cannot be deployed because Case Manager Builder could not create a case subscription for the {0} document type. - FNRPA0068E
The solution cannot be deployed because the {0} document type cannot be found for the case type {1} (unique identifier: {2}). - FNRPA0069E
The solution could not be deployed because the following GUID that is specified in the ID element is invalid: {0}. - FNRPA0070E
The connection definition cannot be updated because the following error occurred: {0} - FNRPA0071E
Data cannot be retrieved from the connection definition because the following error occurred: {0} - FNRPA0072E
The solution cannot be deployed because the temporary deployment log files could not be created. - FNRPA0073E
The page could not be registered because of the following error: {0} - FNRPA0074E
The {0} page name already exists for the solution {1}. - FNRPA0075E
The page could not be created because of the following error: {0} - FNRPA0076E
The current REST request cannot be processed because the resource path {0} was not found. - FNRPA0077E
The {0} page type is not a valid type. - FNRPA0078E
The {0} connection definition was not found. - FNRPA0079E
Retrieving the {0} connection definition document failed with the following exception: {1} - FNRPA0080E
The {0} request parameter has an invalid value of {1}. - FNRPA0081E
The version series ID of the document is not valid. - FNRPA0082E
The page ID for the test solution page was not found. - FNRPA0083E
The page ID could not be retrieved because of the following exception: {0} - FNRPA0084E
An internal server error occurred while running a Case REST API method. - FNRPA0085E
The following resource path does not support the specified HTTP method: {0}. - FNRPA0086E
The Request Body for the REST call is not in valid JSON format. - FNRPA0087E
An unexpected error occurred. - FNRPA0088E
The {0} page could not be found because of the following exception: {1} - FNRPA0089E
No authenticated JAAS subject could be determined in order to perform some processing in the background. - FNRPA0090E
The case folder could not be retrieved because of following error: {0} - FNRPA0091E
A request could not be completed because no resources were available to run a necessary operation in the background. - FNRPA0092E
The following exception occurred: {0} - FNRPA0093E
The previous error was caused by: {0} - FNRPA0094E
The {0} property in the content element of the {1} connection definition document in {2} object store could not be retrieved. - FNRPA0096E
The {0} object store could not be restarted. - FNRPA0097E
The DeployDataset object is missing required files: {0} - FNRPA0098E
The page ID could not be retrieved because of the following error: {0} - FNRPA0099E
The page could not be updated because of the following error: {0} - FNRPA0100E
The {0} status object for resetting the development environment is missing. - FNRPA0101E
The {0} status object for resetting the development environment could not be retrieved. - FNRPA0102E
The workflow name for the {0} task with the case ID of {1} in the {2} object store was not found. - FNRPA0103E
The server could not establish a session with Content Platform Engine. - FNRPA0104E
The workflow could not be started because of the following error: {0} - FNRPA0105E
The XML could not be parsed, or the schema could not be validated. - FNRPA0106E
The schema validation could not be configured. The parsed XML will not be validated against the schema. - FNRPA0107I
The {0} solution is being deployed. - FNRPA0108I
The {0} solution was deployed. - FNRPA0109I
The following property template is being checked: {0} ({1}). - FNRPA0110I
The following property template is being deployed: {0} ({1}). - FNRPA0111I
The following document class is being checked: {0} ({1}). - FNRPA0112I
The following document class is being deployed: {0} ({1}). - FNRPA0113I
The {0} case type is being checked. - FNRPA0114I
The {0} case type is being deployed. - FNRPA0115I
The latest version of the Process Engine configuration document with a version series ID of {0} is being checked. - FNRPA0116I
The latest version of the Process Engine configuration document with a version series ID of {0} is being deployed. - FNRPA0117I
The Process Engine XPDL document with an ID of {0} is being checked. - FNRPA0118I
The Process Engine XPDL document with an ID of {0} is being deployed. - FNRPA0119I
The {0} solution pages are being checked. The case creation page is {1}. - FNRPA0120I
The solution {0} pages are being deployed. - FNRPA0121I
The initiating document class {0} is being checked. - FNRPA0122I
The initiating document class {0} is being deployed. - FNRPA0123I
The Content Engine property definitions are being checked. - FNRPA0124I
The Content Platform Engine property definition for the {0} property is being checked. - FNRPA0125I
The task classes of the {0} case type are being deployed. - FNRPA0126I
The solution definition file properties for the following case type are being checked: {0} ({1}). - FNRPA0127I
The solution definition file properties for the following case type are being deployed: {0} ({1}). - FNRPA0128W
Auditing is not enabled for the object store {0}. No Case History data is being generated, so none can be returned. - FNRPA0129W
The Analytics and Case History Add-On was not installed for the {0} object store. - FNRPA0130E
The display name was not found for the {0} choice list. - FNRPA0131E
A display name was not found for the {0} choice item. - FNRPA0132E
A value was not found for the {0} choice item. - FNRPA0133E
The Process Engine region cannot be re-initialized. Check the {0} connection definition document. - FNRPA0134E
The data set import failed because of the following error: {0} - FNRPA0135E
The solution cannot be deployed because the reused {0} property is not found in Content Engine. - FNRPA0136E
The solution cannot be deployed because the reused {0} property ID does not match the ID that was specified in the solution. - FNRPA0137E
The solution cannot be deployed because the {0} case type is being reused. - FNRPA0138E
The solution cannot be deployed because the reused {0} case type ID does not match the ID that was specified in the solution. - FNRPA0139E
The solution cannot be deployed because the reused document type {0} was not found in Content Engine. - FNRPA0140E
The {0} content element could not be written to the disk. - FNRPA0141E
A content transfer I/O error occurred while a content element was being prepared for saving to the disk. - FNRPA0142E
There are no deploy data set files for the FileNet Deployment Manager import operation. - FNRPA0143E
The solution cannot be deployed because the {0} choice list already exists in Content Platform Engine. - FNRPA0144E
The {0} case type already exists in the target object store. Case types cannot be reused across multiple solutions. - FNRPA0145E
A big integer value, {0}, that was specified in the solution definition is too large to be used. - FNRPA0146E
A duplicate task group ID {0} was specified. - FNRPA0147E
The solution definition does not specify a unique identifier, which is also called a symbolic name in Content Platform Engine, for a task type. - FNRPA0148E
The solution definition does not specify an ID for a task. - FNRPA0149E
A task unique identifier, which is also called a symbolic name in Content Platform Engine, in the solution definition does not match the existing task class. - FNRPA0150E
An existing task class does not have the expected parent class. The actual parent class is {0}, but the expected class is {1}. - FNRPA0151E
A task class already exists and cannot be reused in a solution. - FNRPA0152E
The {0} task type was specified more than once in the solution definition. - FNRPA0153E
A property precondition cannot be specified for a task with filing document type. - FNRPA0154E
A precondition (document filing/property precondition/case property update) cannot be specified for the {0} discretionary task. - FNRPA0155E
The {0} repeatable task can be only a task with a filing document type or a property update precondition. - FNRPA0156E
The {0} filing document type that was specified for a task does not exist. - FNRPA0157E
A discretionary task cannot be in a group. - FNRPA0158E
A repeatable task cannot be in a group. - FNRPA0159E
The {0} task specifies a group that is missing from the solution definition. - FNRPA0160W
The {0} task does not specify a workflow name. - FNRPA0161E
A task type could not be deployed because there was an error during the attempt to save the task class in the object store. - FNRPA0162E
The {0} task workflow does not exist. - FNRPA0163W
An excess workflow launch subscription {0} was attached to a task. It is being removed. - FNRPA0164I
IBM Case Manager Solution List - FNRPA0165I
Object store - FNRPA0166I
Solution name - FNRPA0167I
Status - FNRPA0168I
Description - FNRPA0169I
FileNet P8 target environment - FNRPA0170I
Case Manager Client URL - FNRPA0171E
The XPDL document {0} is not valid. - FNRPA0172W
The {0} task type is being removed from the deployed {1} case type. The task class will not be removed. - FNRPA0174E
{0} is not a valid symbolic name in the {1} target object store . The symbolic name is called a unique identifier in IBM Case Manager. - FNRPA0175E
The {0} property template was not found in the target object store. - FNRPA0176E
The {0} document class was not found in the target object store. - FNRPA0177E
The {0} document class cannot be reused. - FNRPA0178E
The {0} property template cannot be reused. - FNRPA0179E
The {0} type is incorrect for the {1} JSON request body parameter. - FNRPA0180E
The {0} document type cannot be associated with the {1} case type (unique identifier: {2}) because the case type has a required property that has no default value. - FNRPA0181E
The task could not be retrieved because of following error: {0} - FNRPA0182E
The web application ID value was not found in the connection definition used for deployment. - FNRPA0183E
An automatic task in a group does not specify a precondition. - FNRPA0184E
When you redeploy a solution, a task cannot change from having a properties precondition to having no precondition. - FNRPA0185E
When you redeploy a solution, a task with a properties precondition cannot be changed to a different expression for that precondition. - FNRPA0186E
The {0} task type definition contains an invalid empty filingdocument tag. - FNRPA0187E
The {0} page does not exist in the solution. - FNRPA0188E
The isolated region is not associated with a target object store. - FNRPA0189E
The isolated region is not initialized. - FNRPA0190I
The {0} case subfolder is being deleted. - FNRPA0191I
The {0} subscription is being deleted. - FNRPA0192I
The subscription for the {0} case type is being deployed. - FNRPA0193I
An existing subscription for the {0} case type was found. - FNRPA0194I
The {0} document type will be reused. - FNRPA0195I
The {0} document type is being redeployed. - FNRPA0196I
The {0} choice list is being deployed. - FNRPA0197I
The {0} choice list is being redeployed. - FNRPA0200E
The following error occurred while retrieving localized group label for the {0} solution: {1} - FNRPA0201E
The base document class cannot be reused. - FNRPA0202E
The ID provided for the task instance is not valid. - FNRPA0203E
The {0} user-created task must have the required flag specified. - FNRPA0204I
The task classes of the {0} case type are being deployed with the appropriate workflow associations. - FNRPA0205I
The {0} task class is being deployed. - FNRPA0206I
The {0} task class is being deployed with the appropriate workflow association. - FNRPA0207I
The Content Platform Engine process services prerequisites to deploy the solution are being validated. - FNRPA0209E
A deployment of the solution is currently in progress and active. Another deployment cannot be started. - FNRPA0210E
The solution cannot be deployed because the development environment is being reset. - FNRPA0211E
The solution cannot be deployed because the initiating document type {0} for the case type (unique identifier: {1}) is the base document class. - FNRPA0212E
The permissions could not be retrieved from the target object store. - FNRPA0213E
The list of add-on features could not be retrieved from the target object store. - FNRPA0214E
The add-on features could not be retrieved from the domain. - FNRPA0215E
The new target object store {0} could not be configured. - FNRPA0216E
The class definition {0} could not be retrieved, so the subscription could not be added to the new target object store {1}. - FNRPA0217E
The class definition {0} could not be retrieved, so the event could not be added to the new target object store. - FNRPA0218I
No Content Platform Engine process services configuration file was specified for the solution. - FNRPA0219E
The solution cannot be deployed because the {0} Content Platform Engine process services configuration document is empty. This document is in the {1} object store. - FNRPA0220I
No XPDL was specified for the case type. - FNRPA0221E
The solution cannot be deployed because the {0} Content Platform Engine process services XPDL document is empty. This document is in the object store {1}. - FNRPA0222E
The solution cannot be deployed because the {0} property cardinality is incompatible with the original property. - FNRPA0223E
The page that is associated with a case cannot be found because no page ID exists for the {0} page. - FNRPA0228E
The solution cannot be deployed because you have insufficient access rights to the target object store. - FNRPA0229E
The reinitialization cannot be performed because you do not have sufficient access rights to the target object store. - FNRPA0230I
Because the {0} property already exists in the base class, the deployment of this property will be skipped. - FNRPA0231E
The page creation API cannot be invoked because the page ID parameter is null. - FNRPA0232E
The operation could not be completed because {0} is not a valid task name. - FNRPA0233E
The operation could not be completed because {0} is not a valid object store. - FNRPA0234E
The launch step element could not be retrieved because of the following error: {0} - FNRPA0235E
The method call failed because the {0} case type could not be found. - FNRPA0236E
{0} is not a valid key. Valid keys are ConnectionPoint, MashupServerURI, WebAppID, HomeSpaceTemplateID, CaseSpaceTemplateID, StepSpaceTemplateID. - FNRPA0237E
The user-created task could not be created because of the following error: {0} - FNRPA0238E
The configuration could not be parsed because of the following error: {0} - FNRPA0239E
The {0} resource was not found in the application. - FNRPA0240E
The servlet could not be initiated because of the following error: {0} - FNRPA0241E
The {0} class definition could not be saved because of the following error: {1} - FNRPA0242E
The property template {0} could not be saved because of the following error: {1} - FNRPA0243E
The {0} choice list could not be saved because of the following error: {1} - FNRPA0244E
The {0} class subscription could not be saved because of the following error: {1} - FNRPA0245E
The {0} class subscription could not be removed because of the following error: {1} - FNRPA0246E
The solution could not be copied because the {0} GUID for the XPDL document was not found. - FNRPA0247E
The solution could not be copied because the {0} prefix value is empty. - FNRPA0248E
The XPDL document with the {0} GUID could not be found. See the following error: {1} - FNRPA0249E
The case type folder {0} could not be created because the folder already exists. - FNRPA0250E
The case type folder {0} could not be created. See the following error: {1} - FNRPA0251E
The {0} case type folder could not be updated because of a concurrent update. - FNRPA0252E
The case type folder {0} could not be updated because of the following error: {1} - FNRPA0253E
The {0} folder could not be created because the folder already exists. - FNRPA0254E
The {0} folder could not be created. See the following error: {1} - FNRPA0255E
The {0} folder could not be updated because another update is running. - FNRPA0256E
The folder {0} could not be updated. See the following error: {1} - FNRPA0257E
The solution could not be deployed. See the following error: {0}. - FNRPA0258E
The solution could not be copied because the {0} target solution name already exists. - FNRPA0259E
The solution cannot be copied because some of the artifacts of the original solution, {0}, are locked. - FNRPA0260E
The solution cannot be promoted to a template because the solution folder contains a custom document. - FNRPA0261E
Some pages from the page folder could not be copied. See the following error: {0} - FNRPA0262E
The original solution could not be validated. See the following error: {0} - FNRPA0263E
The new solution could not be validated. See the following error: {0} - FNRPA0264E
The document was not filed because the {0} folder is missing. - FNRPA0265E
The folder could not be moved. See the following error: {0} - FNRPA0266E
The XPDL file for the new solution could not be updated because of the following error: {0} - FNRPA0267E
The operation failed because the {0} XPDL document does not exist. - FNRPA0268E
The Content Platform Engine process services configuration file with the GUID {0} could not be retrieved. See the following error: {1} - FNRPA0269E
The Content Platform Engine process services configuration file with GUID {0} could not be found. See the following error: {1} - FNRPA0270E
The solution could not be copied because of the following XML transform error: {0} - FNRPA0271E
The solution could not be copied because of the following XML parsing error: {0} - FNRPA0272E
The solution could not be copied because the Content Platform Engine process services configuration document could not be opened. See the following error: {0} - FNRPA0273E
The solution could not be copied because the Content Platform Engine process services configuration file is not writable. See the following error: {0} - FNRPA0274E
The Content Platform Engine process services configuration document for the original solution could not be copied. The document is checked out. - FNRPA0275E
The XPDL document for the original solution could not be copied. The document {0} is checked out. - FNRPA0276E
The XPDL document for the original solution could not be validated because of the following error: {0} - FNRPA0277E
The XPDL document for the new solution could not be validated because of the following error: {0} - FNRPA0278E
The build information could not be retrieved because of the following error: {0} - FNRPA0279E
The document could not be copied because of the following error: {0} - FNRPA0280E
The solution could not be copied. Deserialization of the {0} solution failed because of the following error: {1} - FNRPA0281E
The solution cannot be copied because the {0} solution definition file for the original solution is missing content. - FNRPA0282E
The path for the solution folder was not found: {0} - FNRPA0283E
The {0} document in the {1} folder was not found. - FNRPA0284W
A deployment error stopped the deployment. The continuation level was {0}. - FNRPA0285W
The second call to the DeploymentLogDocumentPairWriter.checkinLogs() method was ignored. - FNRPA0286W
The thread pool timed out during the shutdown of the application server. - FNRPA0287E
The {0} case type is missing a required views entry in the solution definition file. - FNRPA0288E
The {0} connection definition file could not be created because the file already exists. - FNRPA0289E
The connection definition file could not be created. See the following error: {0} - FNRPA0290E
The solution could not be copied. The original solution contains invalid pages. See the following error: {0} - FNRPA0291I
The following choice list is being checked: {0}. - FNRPA0292I
The following choice list is being deployed: {0}. - FNRPA0293E
The solution cannot be deployed because the reused {0} choice list was not found in Content Engine. - FNRPA0294E
The solution cannot be deployed because the reused choice list name {0} does not match the choice list name that is specified in the solution. - FNRPA0295E
The choice list {0} could not be saved because of the following error: {1} - FNRPA0296E
The solution cannot be deployed because the choice list type is not compatible with the choice list {0} that is defined in the solution. - FNRPA0297E
The solution cannot be deployed because it contains a choice list with an unknown data type. - FNRPA0298E
The solution could not be deployed because the choice list {0} has no choice list item defined. - FNRPA0299E
The solution cannot be copied because the {0} prefix cannot be found in the {1} choice list. - FNRPA0300E
The solution cannot be copied because the {0} prefix cannot be found in the {1} property. - FNRPA0301I
No status is available. - FNRPA0302E
The reinitialization status from the {0} design object store for the {1} connection definition could not be retrieved. - FNRPA0303E
The object store {0} was not found. - FNRPA0304E
Authentication with the IBM Content Manager server {0} failed. - FNRPA0305E
The IBM Content Manager server name property {0} is missing from the connection definition {1}. - FNRPA0306E
The item type could not be retrieved from IBM Content Manager. - FNRPA0307E
Authentication cannot proceed because the HttpServletRequest call did not contain an LTPA token. - FNRPA0308E
The following error occurred when properties from the {0} connection definition were being retrieved: {1} - FNRPA0309E
The item type could not be retrieved. - FNRPA0310E
The integrationType property value {0} in the connection definition {1} is invalid for the following operation: {2}. - FNRPA0311E
For an integration type of {0}, the document type {1} to be re-used already has an ID of {2}. An existing document type from the target object store cannot be reused. - FNRPA0312E
For an integration type of {0}, the document type {1} could not be validated on the external server. - FNRPA0313E
The development environment cannot be reset. - FNRPA0314E
For an integration type of {0}, the document ID {1} could not be validated on the external server. - FNRPA0315E
For an integration type of {0}, a document object that contains the document item ID {1} was not found. - FNRPA0316E
For an integration type of {0}, a document object that contains the document item ID {1} was not found. - FNRPA0400I
The development environment reinitialization started. - FNRPA0401I
Retrieving the reinitialization manifest. - FNRPA0402E
The manifest is missing required properties. Reinitialization cannot proceed. - FNRPA0403I
No DataSet object can be found for the FileNet Deployment Manager import operation. - FNRPA0404E
No CodeModule document object was found for the current manifest. - FNRPA0405I
The reinitialization of the object store started. - FNRPA0406I
Object store properties are being retrieved. - FNRPA0407I
The properties of installed add-ons are being retrieved. - FNRPA0408E
The installed add-ons could not be retrieved. - FNRPA0409I
Object store permissions are being retrieved. - FNRPA0410E
Object store permissions could not be retrieved. - FNRPA0411I
The CodeModules document object are being backed up. - FNRPA0412I
The object store manifest is being saved. - FNRPA0413I
The object store is being deleted. - FNRPA0414I
The object store is being saved. - FNRPA0415I
The new object store is being created. - FNRPA0416I
The object store properties are being set. - FNRPA0417I
Site {0} is being set. - FNRPA0418I
The object store is being saved. By design, some existing database objects were deleted with warnings. - FNRPA0419I
Add-ons are being installed. - FNRPA0420E
The add-ons could not be retrieved from the domain. - FNRPA0421I
Add-on {0} is being installed. - FNRPA0422I
The target object store is being configured. - FNRPA0423I
Code modules are being restored. - FNRPA0424E
The CodeModules folder cannot be created. - FNRPA0425I
Event actions and subscriptions are being created. - FNRPA0426I
The case index is being created. - FNRPA0427I
The object store reinitialization is complete. - FNRPA0428E
The reinitialization of the object store failed. - FNRPA0429I
Auditing is being enabled. - FNRPA0430I
The Content Platform Engine root folder is being retrieved. - FNRPA0431I
The IBM Case Manager root folder is being created. - FNRPA0432I
The solution deployments folder is being created. - FNRPA0433I
The CodeModules folder is being created. - FNRPA0434E
The reinitialization of Content Platform Engine process services or the object store failed. See the following error: {0} - FNRPA0435I
The CodeModules folder already exists. - FNRPA0436I
The CodeModules folder does not exist. - FNRPA0437E
The CodeModules folder could not be retrieved. See the following error: {0} - FNRPA0438I
The Content Platform Engine data set import process is being started. - FNRPA0439I
The data set content is being saved to {0}. - FNRPA0440I
The reinitialization succeeded. - FNRPA0441I
The reinitialization failed. - FNRPA0442I
The reinitialization finished. - FNRPA0443I
Solution space content is missing from the case management design object store. - FNRPA0444E
The solution cannot be copied because no solution name was entered. - FNRPA0445E
The solution cannot be copied because the solution name is longer than 255 characters. - FNRPA0446E
The solution cannot be copied because the new solution name does not start with a letter. - FNRPA0447E
The solution cannot be copied because the new solution name contains special characters. - FNRPA0448E
The solution cannot be copied because the prefix for the new solution must contain at least two characters. - FNRPA0449E
The solution cannot be copied because the prefix for the new solution contains more than five characters. - FNRPA0450E
The solution cannot be copied because the prefix for the new solution does not start with a letter. - FNRPA0451E
The solution cannot be copied because the prefix for the new solution contains characters that are not alphanumeric. - FNRPA0452E
The solution prefix cannot start with the following reserved keywords: CM, DITA, RM, EDM, EDISC, ICC, or VWV (case insensitive). - FNRPA0453E
The object store ID in the re-initialization manifest does not match the ID of the target object store {0}. - FNRPA0454E
No connection definition was found for the current user {0}. - FNRPA0455E
The {0} object store is not a target object store. The target object store add-on extension is not installed. - FNRPA0456E
No project area was found. - FNRPA0457E
The solution workflow definition document could not be fetched because of the following error: {0} - FNRPA0458E
The {0} workflow definition was not found. - FNRPA0459E
The {0} workflow field name specified in property mapping for the {1} task was not found in the {2} workflow definition. - FNRPA0460E
The {0} case type property name specified in property mapping for the {1} task was not found in the {2} case type. - FNRPA0461E
The data types of the {0} workflow field and the {1} case type property that are specified in the property mapping for the {2} task are not compatible. - FNRPA0462E
The solution definition document for the solution could not be fetched because of the following error: {0} - FNRPA0463E
TheContent Platform Engine process services configuration document for the solution could not be retrieved. See the following error message: {0} - FNRPA0464E
The request body contained an unrecognized property: {0}. - FNRPA0465E
An external data service is attempting to specify a choice list for the {0} property. The property already has a choice list. - FNRPA0466E
The external data service cannot override the maximum value constraint for the {0} property. The value {1} that was returned by the service is greater than the maximum value {2} that is already defined for the property. - FNRPA0467E
The external data service cannot override the minimum value constraint for the {0} property. The value {1} that was returned by the service is less than the minimum value {2} that is already defined for the property. - FNRPA0468E
The combination of minimum and maximum values that the external data service specified for the {0} property is invalid. The minimum value {1} must be less than or equal to the maximum value {2}. - FNRPA0469E
An external data service is attempting to specify an invalid maximum length constraint for the {0} property. The externally specified maximum length is {1}. The underlying maximum length is {2}. - FNRPA0470E
An external data service is attempting to specify a nonrequired setting for the property {0}. The underlying setting is already required. - FNRPA0471E
The value of the {0} property does not match the read-only display mode value specified by an external data service. - FNRPA0472E
The value of the {0} property does not meet the constraints of the choice list specified by an external data service. - FNRPA0473E
The value of the {0} property does not meet the minimum or maximum value constraints specified by an external data service. - FNRPA0474E
The value of the {0} property does not meet the maximum length constraint specified by an external data service. - FNRPA0475E
When you redeploy a solution, a task cannot change from having no precondition properties to having a precondition. - FNRPA0476W
The properties for a precondition for the {0} task have changed. After the deployment completes, run the precondition checker tool. - FNRPA0477I
Reset of the development environment is currently in progress. - FNRPA0478E
The integration type value on the solution or template does not match the integration type value on the destination project area. - FNRPA0479E
A subscription could not be created for {0} class because it was not found in the {1} target object store. - FNRPA0480E
An external data service returned the following error: {0} - FNRPA0481E
An external data service returned the following code and error response: {0} {1}. See the following message: {2} - FNRPA0482E
An external data service returned the following code and error response: {0} {1}. No additional details were returned. - FNRPA0483E
The following error occurred when connecting to an external data service: {0} - FNRPA0484E
The following error occurred while the response from an external data service was being processed: {0} - FNRPA0485E
The integration type of the solution either does not match the integration type value of the project area or does not match the integration type of the deployed solution class in the target object store. - FNRPA0486E
The {0} property template used as the case title property name for the {1} case type was not found in the target object store. - FNRPA0487E
The solution list could not be retrieved because the connection definition name resource path was not found. - FNRPA0489E
Retrieval of the external host connection properties failed for the {0} target object store. - FNRPA0490E
A value for the {0} property does not exist and an external data service has specified that a value is required. - FNRPA0491E
The {0} user is not allowed to connect to the IBM Business Process Manager process server. - FNRPA0492E
No process applications are available on the IBM Business Process Manager process server. - FNRPA0493E
The {0} process application is not available on the IBM Business Process Manager process server. - FNRPA0494E
The {0} snapshot is not active on the IBM Business Process Manager process server. - FNRPA0495E
No exposed processes are available on the IBM Business Process Manager process server. - FNRPA0496W
The integration data is not available for the IBM Business Process Manager process server. - FNRPA0497E
The {0} data field that is specified in the property mapping for the {1} task as an input or output field is not available as the appropriate input or output field in the IBM Business Process Manager {2} process. - FNRPA0498E
The data type or cardinality of the {0} data field that is specified in the property mapping for the {1} task is not compatible with the data type or cardinality of the field in the IBM Business Process Manager {2} process. - FNRPA0499E
Start up information is not available for the {0} task type. - FNRPA0500I
The Content Platform Engine isolated region reinitialization process is starting. - FNRPA0501E
The {0} process application name does not match the {1} acronym. - FNRPA0502I
The VWSession object is being retrieved. - FNRPA0503E
The {0} process application snapshot is not the default snapshot. - FNRPA0504I
The isolated region and system configuration are being retrieved. - FNRPA0505E
The {0} process application snapshot is not active. - FNRPA0506I
The system configuration object store ID and attribute information are being retrieved. - FNRPA0507E
The IBM Business Process Manager {0} process does not exist or is not exposed. - FNRPA0508I
The region is being initialized. This is attempt number {0}. - FNRPA0510I
The region reinitialization succeeded on attempt {0}. - FNRPA0511I
An attempt is being made to reinitialize Content Platform Engine. - FNRPA0512E
The following maximum number of Content Platform Engine reinitialization attempts was reached: {0}. - FNRPA0513I
There was an attempt to the set the Content Platform Engine region configuration with the {0} object store ID. - FNRPA0514I
The {0} object store ID for the Content Platform Engine region was successfully set. - FNRPA0515I
The custom object that contains the IBM Content Manager host properties is being created. - FNRPA0516I
The subscription class definition for IBM Content Manager is being retrieved. - FNRPA0517I
The IBM Case Manager root folder is being retrieved. - FNRPA0518I
The host properties custom object for IBM Content Manager is being created. - FNRPA0519I
The host properties custom object for IBM Content Manager is being saved. - FNRPA0520I
The host properties custom object for IBM Content Manager is being filed. - FNRPA0521I
The subscription OVP property for IBM Content Manager is being updated. - FNRPA0522I
The event actions and subscriptions for IBM Content Manager is being created. - FNRPA0523E
The logon to IBM Content Manager server failed. Verify that the IBM Content Manager host connectivity properties are correct: Host={0}, Port={1}, Library Name={2}, Schema Name={3}, JDBC Driver={4}, JDBC URL={5}. - FNRPA0524E
The operation cannot be completed because the development environment is being reset. - FNRPA0525E
The required process application and snapshot information is missing from the solution. - FNRPA0526I
{0, date, short} {1, time, long} {2} {3}\n - FNRPA0527I
The {0} marking set is being backed up. - FNRPA0528I
The {0} marking set is being restored. - FNRPA0529E
The IBM Content Manager host {0} could not be reset. - FNRPA0530E
The solution cannot be deployed because the Content Platform Engine process services configuration document was not imported. For more information, see the following error: {0} - FNRPA0531E
The solution template folder was not found. - FNRPA0532E
The integration data object for the subscription does not exist. - FNRPA0533I
Authenticating access. - FNRPA0534E
The following user could not be logged in: {0}. - FNRPA0535E
Resetting of development environment failed. - FNRPA0536E
The development environment cannot be reset because access to the object store failed. - FNRPA0537E
The development environment cannot be reset due to failed reset folder fetch. - FNRPA0538E
The development environment cannot be reset because a solution is being deployed. - FNRPA0539W
The workflow for the discretionary task {0} had the following Content Platform Engine process services warning messages: {1} - FNRPA0540E
The choice list definitions could not be created. For more information, see the following error: {0} - FNRPA0541E
The property templates definitions could not be created. For more information, see the following error: {0} - FNRPA0542E
The document types definitions could not be created. For more information, see the following error: {0} - FNRPA0543E
The case and task types definitions could not be created. For more information, see the following error: {0} - FNRPA0544E
The case and task types definitions could not be updated. For more information, see the following error: {0} - FNRPA0545E
A transaction failed. For more information, see the following error: {0} - FNRPA0546E
The operation to change the state of a task object failed because the current task state is incorrect. - FNRPA0547E
The operation to change the state of the task object failed because the current task state is incorrect. - FNRPA0548E
The operation to change the state of a task object failed. - FNRPA0549E
The operation to modify a task object failed because the current task has conflicting pending changes. - FNRPA0550E
A task type was not deployed. For more information, see the following error: {0} - FNRPA0551E
The property {0}, which was specified as a property update precondition for a task, does not exist. - FNRPA0552E
Tasks {0} and {1} in group {2} do not belong to the same container. - FNRPA0553W
The {0} compound task cannot be defined as editable. - FNRPA0554W
The {0} container task has workflow information defined. - FNRPA0555E
Compound task subtask {0} cannot be a discretionary task. - FNRPA0556E
The deployed task type info object for the {0} task type was not found. - FNRPA0557E
The {0} property is not a case property. - FNRPA0558E
The deployment operation could not remove the {0} case structure folder. See the following error for more information: {1} - FNRPA0559E
The method that you ran is not available on an instance pending creation. - FNRPA0560E
The restart action is invalid for a container task. - FNRPA0561E
The restart action is invalid for a discretionary task. - FNRPA0562E
The restart action is invalid for an IBM BPM task. - FNRPA0563E
The task cannot be restarted. - FNRPA0564E
The task could not be stopped. For more information, see the following error message: {0} - FNRPA0565E
The stop action is invalid for a container task. - FNRPA0566E
The stop action is invalid for an IBM BPM task. - FNRPA0567E
The task state is invalid for the stop action. - FNRPA0568E
One or more properties are not defined in the {0} target object store. For more information, see the following error message: {1} - FNRPA0569E
The expression that is specified as additional filter is not following correct Content Platform Engine SQL syntax. - FNRPA0570E
Launch information is required for the {0} task type. - FNRPA0571E
The case cannot be split because another split case action is pending on the case. - FNRPA0572E
A split case action was run on an existing case. - FNRPA0573E
A relate case action was run on a case that is being created. - FNRPA0574E
An unrelate case action was run on a case that is being created. - FNRPA0575E
The unrelate case action failed because the relationship object for the ID {0} could not be found. - FNRPA0576E
The unrelate case action failed. The relationship object for the ID {0} could not be found. - FNRPA0577E
The unrelate case action failed because of an invalid relationship object. - FNRPA0578E
The specified ID {0} is not for a valid case folder. - FNRPA0579E
The relationship type to filter on was either not specified or not set to Related. - FNRPA0580E
The document class {0} was found in Content Platform Engine with ID {1} but is defined in solution with ID {2}. - FNRPA0581E
The solution that you are trying to edit is either being edited by another user or was improperly closed in a previous session. Concurrent editing is not supported, and might cause loss of data. - FNRPA0582E
The solution is being modified by another user. - FNRPA0583E
The solution definition file for the {0} solution could not be found. - FNRPA0584E
A document filing and case property update preconditions cannot be specified simultaneously for task {0}. - FNRPA0585E
The Widgets folder was not found: {0} - FNRPA0586E
The {0} widgets package name already exists. - FNRPA0587E
The widgets package could not be created because of the following error: {0} - FNRPA0588E
The {0} widgets package could not be found because of the following exception: {1} - FNRPA0589E
The widgets package {0} does not exist in the design object store. - FNRPA0590E
The widgets package could not be registered because of the following error: {0} - FNRPA0591E
The widgets package could not be updated because of the following error: {0} - FNRPA0592E
The resource {0} could not be retrieved because of the following error: {1} - FNRPA0593E
The JVM system property {0} could not be found. - FNRPA0594E
The widgets packages could not be retrieved because of the following error: {0} - FNRPA0595E
The folder {0} was not found. - FNRPA0596E
The pages could not be deployed because of the following error: {0} - FNRPA0597E
The solution could not be deployed because the deployed solution {0} is using prefix {1}. - FNRPA0598I
The {0} solution views are being deployed. - FNRPA0599E
The views could not be deployed because of the following error: {0} - FNRPA0600E
The definition file for the case operations component queue was not found. - FNRPA0601E
The definition file for the case operations component queue is corrupted. - FNRPA0602E
The case operations code module was not found. - FNRPA0603I
The document objects for case history are being backed up. - FNRPA0604I
The system is removing Content Platform Engine process services connection points and isolated regions that are associated with the target object store. - FNRPA0605I
The system is removing the event export object store that is associated with the target object store. - FNRPA0606I
Content Platform Engine process services isolated regions are being created. - FNRPA0607I
The Content Platform Engine process services connection points are being created. - FNRPA0608I
Event export object stores are being created. - FNRPA0609I
The system is restoring the case history code module and queue definition file. - FNRPA0610I
The case operations definition file is being updated. - FNRPA0611I
The case operations definition file is being transferred. - FNRPA0612E
The ID fields in the definition file for the case operations component could not be updated. - FNRPA0613E
The system could not transfer the definition file for the case operations component to the isolated region. - FNRPA0614E
The system could not complete the call for a case history visualizer API. - FNRPA0615E
Some views from the view folder could not be copied. See the following error: {0} - FNRPA0616E
The solution locks custom object could not be created. See the following error: {0} - FNRPA0617E
The custom task class name {0} exceeds the 64-character limit. - FNRPA0618E
The validation of the custom task workflow definition failed with the following Process Engine error message: {0} - FNRPA0619E
The following Content Platform Engine process services error occurred during the transfer of the custom task workflow: {0} - FNRPA0620I
The solution {0} localization resources file is being generated. - FNRPA0621E
The case type {0} does not support custom tasks. - FNRPA0622E
Invalid operator in search filter: {0} - FNRPA0623E
Invalid data type in search filter: {0} - FNRPA0624E
The rules could not be deployed because of the following error: {0} - FNRPA0625I
The solution {0} rules are being deployed. - FNRPA0626E
The desktop URL value was not found or is invalid. - FNRPA0627E
The page ID for page type {0} was not found. - FNRPA0628E
The following error occurred while processing a request on the application server: {0} - FNRPA0629E
The solution cannot be deployed because a duplicate {0} business object type was found. - FNRPA0630I
The following business object class is being checked: {0} ({1}). - FNRPA0631E
The business object class {0} was found in Content Platform Engine with ID {1} but is defined in the solution with ID {2}. - FNRPA0632E
The solution is not fully deployed because the {0} business object could not be deployed. - FNRPA0633E
The solution is not fully deployed because the {0} case type could not be deployed. - FNRPA0634E
The solution cannot be deployed because the {0} property template was not found. - FNRPA0635E
The system could not find the event export store associated with the target object store. - FNRPA0636E
An attachment for the fileAttachmentsToCurrentCase case operations method is missing. - FNRPA0637E
The {0} property object trigger type that was specified for a task does not exist. - FNRPA0638E
The ILOG operations code module was not found. - FNRPA0639E
The definition file for the ILOG operations component queue was not found. - FNRPA0640I
The system is restoring the ILOG operations code module and queue definition file. - FNRPA0641I
The ILOG operations definition file is being updated. - FNRPA0642E
The ID fields in the definition file for the ILOG operations component could not be updated. - FNRPA0643I
The ILOG operations queue definition file is being transferred. - FNRPA0644E
The definition file for the ILOG operations component could not be transferred to the isolated region. - FNRPA0645E
The solution could not be deployed because it is currently locked. - FNRPA0646E
The solution could not be deployed because the following error occurred when the system checked for editing locks on the solution: {0} - FNRPA0647E
There is no step processor information for the step {0}. - FNRPA0648E
There is no step processor information for the launch step {0}. - FNRPA0649I
The ILOG data files are being removed from the shared drive. - FNRPA0650I
Removing views and pages from shared folder. - FNRPA0651E
The security manifest document with version series ID {0} could not be found. - FNRPA0652E
The security manifest document with version series ID {0} is empty. - FNRPA0653E
The security manifest document with version series ID {0} is not valid. - FNRPA0654E
The privilege definition document is empty. - FNRPA0655E
The privilege definition document is not valid. - FNRPA0656E
The permissions on the deployed solution artifacts could not be updated. - FNRPA0657E
The specified privilege value is not valid. - FNRPA0658E
The Content Platform Engine process services operation user information could not be retrieved. - FNRPA0660E
A DATE type property failed to initialize in a Case Operations method. - FNRPA0661E
A view with an invalid MIME type was detected during solution deployment. - FNRPA0662E
The pages and views resource file could not be generated because of the following error: {0} - FNRPA0663E
The component queue definition should not be present in the solution's PE configuration. - FNRPA0664E
The solution cannot be exported because some of the artifacts of the solution {0} are locked. - FNRPA0665E
The solution cannot be copied or created because its version, {0}, is not supported. - FNRPA0666W
The following user could not be authenticated: {0}. - FNRPA0667E
The step element with work object number {0} does not exist in the queue {1}. - FNRPA0668I
Security for the solution {0} is being configured. - FNRPA0669I
Security configuration for the solution {0} is finished. - FNRPA0670I
The solution security privilege definition is being loaded. - FNRPA067II
The solution security roles are being loaded. - FNRPA0672I
The solution security settings are being loaded. - FNRPA0673I
The solution case types security settings are being loaded. - FNRPA0674I
The solution administrator security settings are being loaded. - FNRPA0675I
The Process Engine operation user settings are being loaded. - FNRPA0676I
The roles security settings are being configured on the deployed solution folder. - FNRPA0677I
The add comment privilege is being configured. - FNRPA0678I
The full control privilege is being configured. - FNRPA0679I
The create case privilege is being configured. - FNRPA0680I
The create discretionary task privilege is being configured. - FNRPA0681I
The create custom task privilege is being configured. - FNRPA0682I
The create subfolder privilege is being configured. - FNRPA0683I
The manage case privilege is being configured. - FNRPA0684I
The manage role privilege is being configured. - FNRPA0685I
The Process Engine operation user privilege is being configured. - FNRPA0686I
The process work privilege is being configured. - FNRPA0687I
The start task privilege is being configured. - FNRPA0688I
The update case privilege is being configured. - FNRPA0689I
The view case privilege is being configured. - FNRPA0690I
The view work privilege is being configured. - FNRPA0691I
The add document privilege is being configured. - FNRPA0692I
The role membership is being configured. - FNRPA0693I
The process engine is being configured. - FNRPA0694I
The {0} page content has an invalid MIME type. The type application/x-zip-compressed was expected, but {1} was found. Skipping deployment. - FNRPA0695I
The page {0} reference name property has no value. Skipping deployment. - FNRPA0696E
An OOTB properties file was not read. - FNRPA0697I
The {0} solution audit is being configured. - FNRPA0698I
The {0} solution audit configuration is complete. - FNRPA0699I
The {0} Event class is being updated in Content Platform Engine with the properties to be audited. - FNRPA0700I
The audit manifest XML file is being read and the properties to be audited are being identified. - FNRPA0701I
OOTB properties to be audited for the class {0} by default are read from the properties file. - FNRPA0702I
The properties listed in Audit Entries are set with their corresponding AuditAs values in their respective classes. - FNRPA0703I
The Process Engine event log has been updated with the fields that are to be audited for case type {0}. - FNRPA0704I
In Content Platform Engine, only the OOTB properties in class {0} will be audited. - FNRPA0705I
Setting AuditAs is complete for all required properties in the type {0}. - FNRPA0706I
The audit configuration batch execution is complete. - FNRPA0707E
The audit manifest document with version series ID {0} could not be found. - FNRPA0708E
The audit manifest document with version series ID {0} is empty. - FNRPA0709E
The audit manifest document with version series ID {0} is invalid. - FNRPA0710E
An error occurred while the audit manifest was being run against the target object store. - FNRPA0711E
The audit entries on the deployed solution artifacts could not be updated. - FNRPA0712E
During audit configuration, updating the Process Engine event logs failed. - FNRPA0713I
{0} access rights are being added on the deployed solution folder for the following user: {1}. - FNRPA0714I
{0} access rights are being added on the deployed case type folder for the following user: {1}. - FNRPA0715I
{0} access rights are being added on the case type class definition for the following user: {1}. - FNRPA0716I
{0} access rights are being added for the user {1} on the class definition for case type discretionary tasks. - FNRPA0717I
{0} access rights are being added for the user {1} on the class definition for case type custom tasks. - FNRPA0718I
{0} access rights are being added for the user {1} on the class definition for case type tasks. - FNRPA0719I
{0} access rights are being added for the user {1} on the application space for the workflow region. - FNRPA0720I
{0} access rights are being added for the user {1} on the Process Engine work queue for the role. - FNRPA0721I
Adding {0} access right(s) for grantee name {1} on the process engine roster. - FNPRA0722I
Adding {0} to role {1}. - FNRPA0723I
Process Engine: All the system configuration changes that are required for the audit manifest to run are applied. - FNRPA0724I
Content Engine: In class {0} for the property {1}, the AuditAs value is set to {2}. - FNRPA0725I
Process Engine: The field {0} was added to event log defintion {1}. - FNRPA0726E
This version of the solution is not supported. - FNRPA0727E
Case type {0} is missing at least one task to meet the minimum requirement for custom task support. - FNRPA0728E
The requesting subject is not owned by the case: {0} - FNRPA0729E
Container task subtask cannot be excluded for case completion. - FNRPA0730E
Container task {0} cannot be excluded for case completion. - FNRPA0731E
Task {0} cannot be excluded for case completion and belong to a group. - FNRPA0733I
Security manifest GUID: {0} - FNRPA0734I
Security manifest version: {0} - FNRPA0735I
Audit manifest GUID: {0} - FNRPA0736I
Audit manifest version: {0} - FNRPA0737E
The task type {0} is not a discretionary task type. It cannot be created discretionally. - FNRPA0738E
The class description {0} could not be retrieved because of the following error: {1}. - FNRPA0739E
The value of the {0} property does not meet the validation requirement specified by an external data service. See the following error for additional information: {1} - FNRPA0740E
The step element for queue and work object number was not found. - FNRPA0741E
The step element for queue and work object number could not be retrieved because of the following error. - FNRPA0742E
The property was not found in the properties collection. - FNRPA0743E
The property description for property was not found in the collection. - FNRPA0744E
The custom task could not be generated and launched because of the following error. - FNRPA0745E
The task type is not a valid task type for case type. - FNRPA0746E
The task type is not a discretionary task. - FNRPA0747E
The widgets package cannot be opened because it has no content or is corrupted. Re-import your widgets package and try again. - FNRPA0748E
The solution cannot be moved to the template folder because it is already modified. See the following error message for more information: {0} - FNRPA0749E
The solution template cannot be moved to the solutions folder because it is already modified. See the following error message for more information: {0} - FNRPA0750E
The task search cannot be completed because of the following error: {0} - FNRPA0751E
The {0} choice list was not found in the target object store. - FNRPA0752E
The task search cannot be completed because of a syntax error. - FNRPA0753E
Case type {0} does not exist in the specified target object store. - FNRPA0754E
The case synchronization process cannot stop because of the following error: {0} - FNRPA0755I
The case synchronization process stopped. - FNRPA0756I
The case synchronization process is searching and updating case instances. - FNRPA0757I
The case synchronization is starting to process case instances. - FNRPA0758I
The case synchronization is waiting for case instance processing to complete. - FNRPA0759I
The case instances synchronization completed. - FNRPA0760I
The case synchronization is retrieving case instances to process. - FNRPA0761I
{0} case instances were retrieved for processing. - FNRPA0762E
The external document cannot be created. - FNRPA0763E
The search for the external document cannot be performed. - FNRPA0764E
The extensions directory {0} was not found. - FNRPA0765E
The {0} extensions package name already exists. - FNRPA0766E
The extensions package cannot be created because of the following error: {0} - FNRPA0767E
The {0} extensions package cannot be found because of the following error: {1} - FNRPA0768E
The extensions package {0} does not exist in the design object store. - FNRPA0769E
The extensions package cannot be registered because of the following error: {0} - FNRPA0770E
The extensions package cannot be updated because of the following error: {0} - FNRPA0771E
The extensions packages cannot be retrieved because of the following error: {0} - FNRPA0772E
The {0} folder that contains the extensions package definition file was not found. - FNRPA0773E
The extensions package cannot be opened because it has no content or is corrupted. Re-import your extensions package and try again. - FNRPA0774E
The Complete action is valid only for a to-do task. - FNRPA0775E
The task cannot be completed in its current state. - FNRPA0776E
No default value is set for the required task property {0}. - FNRPA0777E
The VWAttachment {0} uses the unsupported library type {1}. - FNRPA0778I
The security settings for the roles are being configured on the case type. - FNRPA0779I
The security settings for the roles are being configured on the roster. - FNRPA0780E
The work item cannot be saved because of the following database error: {0} - FNRPA0781I
Work item ID - FNRPA0782I
Queue name - FNRPA0783I
Map name - FNRPA0784I
Response - FNRPA0785I
Licensed Materials - Property of IBM Corp. (5725-A15) (C) Copyright 2010, 2015 IBM Corporation. IBM and the IBM logo are trademarks of IBM Corporation, registered in many jurisdictions worldwide. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Built on Eclipse is a trademark of Eclipse Foundation,Inc. Other product and service names might be trademarks of IBM or other companies. This Program is licensed under the terms of the license agreement accompanying the Program. This license agreement may be either located in a Program directory folder or library identified as "License" or "Non_IBM_License", if applicable, or provided as a printed license agreement. Please read this agreement carefully before using the Program. By using the Program, you agree to these terms. - FNRPA0786I
IBM Case Manager API plug-in - FNRPA0787E
Case type {0} is missing at least one task to meet the minimum requirement for custom task support.
Parent topic: IBM Case Manager messages
Terms of use | Notices
Last updated: September 2014 acmms002.htm
© Copyright IBM Corporation 2015.