DMS_MESSAGES -
The following messages are stored in message class DMS_MESSAGES: .
It is part of development package PLM-SE-DMS_XI_PROXY_T in software component CA-DMS. This development package consists of objects that can be grouped under "".
It is part of development package PLM-SE-DMS_XI_PROXY_T in software component CA-DMS. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
|---|---|
| 000 | XML attribute value of &1 exceeds its maximum length of &2 |
| 001 | XML element value of &1 exceeds its maximum length of &2 |
| 002 | Error converting the field &1 |
| 003 | Error in &1 mapping |
| 004 | File upload failed for document &1 |
| 005 | Creation of a folder failed for document &1 |
| 006 | Status list for document type &1 is empty |
| 007 | Document type &1 is not associated to &2 status |
| 008 | Document type &1 does not have &2 as release status |
| 009 | &1 documents created successfully; failed to create &2 |
| 010 | An error occured; &1 documents created successfully |
| 011 | &1 not considered during property valuation mapping |
| 012 | Document is already in release status &1 |
| 013 | Document released successfully |
| 014 | Document of type &1 cannot be created with &2 status |
| 015 | Document already exists |
| 016 | Document read successfully |
| 017 | Document created successfully |
| 018 | Characteristic &1 does not exist |
| 019 | Document &1 already exists |
| 020 | Document version &1 created successfully |
| 021 | Document deleted successfully |
| 022 | Search successful |
| 023 | Maximum length of document name is &1 |
| 024 | Maximum length of document type is &1 |
| 025 | Maximum length of document version is &1 |
| 026 | Internal error occured during conversion |
| 027 | Internal error occured during mapping |
| 028 | Internal error occured |
| 029 | Document does not exist |
| 030 | File created successfully |
| 031 | &1 is not a valid status |
| 032 | File checked in successfully |
| 033 | File size is mandatory when LargeFileIndicator is 'TRUE' |
| 034 | Binary object is mandatory when LargeFileIndicator is 'TRUE' |
| 035 | File ID is mandatory when LargeFileIndicator is 'TRUE' |
| 036 | FileVersionID is mandatory when LargeFileIndicator is set to 'TRUE' |
| 037 | File deleted successfully |
| 038 | File does not exist |
| 039 | Given DocumentChangeStateID is no longer valid |
| 040 | URL of the file storage location could not be obtained |
| 041 | Binary data of the file could not be obtained |
| 042 | Basic data of files read successfully |
| 043 | Files read successfully |
| 044 | Not all files could be read |
| 045 | File with specified details does not exist or is already checked out |
| 046 | QueryHitsMaxValue should not be provided with UnlimitedHitsInd as 'TRUE' |
| 047 | File is empty |
| 048 | Document can be created with CategoryCode '1' or '2' only |
| 049 | File size in content server (&1) and input does not match |
| 050 | File checked out successfully |
| 051 | Input field &1 is mandatory |
| 052 | Action code &1 not supported |
| 053 | Invalid entry; FileID or FileVersionID is empty |
| 054 | Invalid document status |
| 055 | Large file handling error |
| 056 | Invalid entry; DocumentChangeStateID is empty |
| 057 | Invalid entry; DocumentName is empty |
| 058 | Invalid entry; DocumentVersionID is empty |
| 059 | Invalid entry; DocumentAlternativeID is empty |
| 060 | Invalid entry; DocumentTypeCode is empty |
| 061 | Document status updated successfully |
| 062 | Allowed statuses read successfully |
| 063 | Document updated successfully |
| 064 | Long description should be more than 40 characters |
| 065 | Long description (less than 40 characters) assigned to short description |
| 066 | Invalid entry; DocumentObjectReferenceID is empty |
| 067 | Invalid entry; DocumentObjectReferenceTypeCode is empty |
| 068 | DocumentFormatCode is empty or invalid |
| 069 | DocumentStorageCategoryCode is empty or invalid |
| 070 | Cannot check-in, file not checked-out |
| 071 | File ID and file version ID relation is inconsistent |
| 072 | File version ID is already attached to a document |
| 073 | Invalid entry; document status is empty |
| 074 | Storage category for the file could not be obtained |
| 075 | Document path name is empty |
| 076 | Invalid or non-existent RepositoryCode: &1 |
| 077 | Document &1 created successfully |
| 078 | File variant &1 created successfully |
| 079 | Object type: &1 is linked with &3 documents |
| 080 | Class: &1 of type: &2 is assigned to &3 documents |
| 081 | Document &1 read successfully |
| 082 | Document &1 released successfully |
| 083 | Document &1 read successfully; &2 classes are assigned to the document |
| 084 | Document &1 updated successfully |
| 085 | Documents updated successfully |
| 086 | Error in conversion of language code for &1 |
| 087 | Search successful; &1 documents found based on search criteria |
| 088 | Search successful; &1 superordinate documents found |
| 089 | Search successful; &1 subordinate documents found |
| 090 | No document found with name: &1, type: &2 and part: &3 |
| 091 | Document &1 is already linked to product allowed component &2 |