Message codes
Messages codes will either be presented as errors, warnings or informational messages.
Note that some warning messages may be elevated to error messages, please see the extension configuration settings. The full list of codes which may be elevated are provided below.
Account Codes
AC_001: Error
No company ID to fetch account codes.. To resolve this issue, a valid Unit 4 company/client ID will need to be provided. either through the document schema or through the Rossum extension configuration.
AC_002: Error
Failed to fetch account codes. Received ERP status code:. This is returned when we receive an invalid response from your Unit4 ERP. The error message returned should provide further details, such as the HTTP status returned, in order for you to debug the Unit4 connection or permissions as required.
AC_003: Error
Failed to fetch any account codes, response was empty. ERP Status:. This is returned when we receive an OK http response code but the data we received back was either empty or not in the correct format.
Accounting Lines
ACL_001: Information
Could not verify tax percentage. The tax percentage on the line was null but there was a tax code on the purchase order.
ACL_002: Error
Tax code must be provided for line. The purchase order has a tax code but no tax code is present on the accounting line. The account rule for the line has a mandatory tax code.
ACL_003: Warning
No tax code found for line. The purchase order has a tax code but no tax code is present on the accounting line. The account rule for the line has a non-mandatory tax code.
ACL_004: Warning
Invoice tax percentage does not match PO coding. The line has a non-null tax percentage, the accounting line has a tax code but the percentage on the tax code does not match the line tax.
ACL_005: Error
Please choose tax code. A tax code must be provided on the accounting line.
ACL_006: Error
Please choose tax system. A tax system must be provided on the accounting line.
ACL_007: Error
Tax code does not match fixed value. There is a tax code selected which does not match the fixed tax code on the account rule.
ACL_008: Error
Tax system does not match fixed value. There is a tax system selected which does not match the fixed tax code on the account rule.
ACL_009: Error
Please choose account code. Every accounting row should have an account code to enable the data to be passed to ERP. In this case a valid account code has not been chosen.
ACL_010: Error
Please choose accounting dimension. This dimension must have a value selected based on the account rule
ACL_011: Information
Options available for accounting dimension. This dimension may optionally have a value selected based on the account rule
Account Rules
AR_001: Error
CompanyId or account rule IDs not provided for account rules lookup. To resolve this issue, a valid Unit 4 company/client ID will need to be provided. either through the document schema or through the Rossum extension configuration.
AR_002: Error
Failed to fetch account rules: received status code:. This is returned when we receive an invalid response from your Unit4 ERP. The error message returned should provide further details, such as the HTTP status returned, in order for you to debug the Unit4 connection or permissions as required.
AR_003: Error
Account Rules not an array of at least one item. This is usually because the input or discovered account rule Ids were invalid and should be double-checked in the document.
Attributes & Relations
AT_001: Error
Failed to fetch attribute values received status code:. Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
AT_002: Error
Invalid response when fetching attributes.. A valid HTTP response was received but the body did not decode as expected. This is likely an issue with your Unit4 ERP API.
AT_003: Error
Company ID required to fetch attributes.. To resolve this issue, a valid Unit 4 company/client ID will need to be provided. either through the document schema or through the Rossum extension configuration.
AT_004: Error
Failed to fetch attribute relations: received status code:. Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
AT_005: Error
Invalid response when fetching relations. A valid HTTP response was received but the body did not decode as expected. This is likely an issue with your Unit4 ERP API.
Caching
CA_001: Information
Caching is disabled. Requests may be slow.. Caching has been disabled for this document and therefore more requests will be made to ERP. See the caching documentation here
ERP configuration
CF_001: Error
We could not read ERP connection settings. This error is returned if we cannot find either IDS or basic auth and is usually caused by partial credentials being provided. This will be an error with the extension settings or the secrets configuration
CF_001A: Error
Could not read ERP basic config settings. This error is thrown if we need to make a SOAP request and no Basic auth credentials are supplied in your extension secrets or settings. This will be an error with the extension settings or the secrets configuration
CF_002: Error
Failed to fetch company. This may be due to a missing company ID in the settings or the confirmed invoice if auto-detected.. This may be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
Company / Client
CO_001: Error
Failed to fetch company XX received status XX from ERP.. This may be due to a missing or invalid company ID in the Rossum extension configuration or the document schema. It may also be a permissions or access issue with your Unit4 ERP API. The included message in your extension logs should provide more detailed information.
CO_002: Error
Cannot fetch company. No ID provided.. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
CO_003: Error
Failed to fetch company XX currentAccountingPeriod is not a number. Although this seems impossible, somehow the system has returned a non-numer for the current accounting period. This is required for pulling the correct account codes and attributes.
Currency
CR_001: Error
Missing currency code. The currency code pulled from the invoice is not a valid currency code in Unit4 ERP.
Document Archive Issues
DA_001: Error
Failed to send document. Received ERP status. Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
DA_002: Error
Failed to send document to archive due to missing company ID.. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
DA_003: Error
Failed to send document to archive. No response body. (Status: ). The Unit4 SOAP response did not contain the expected response and so we could not confirm receipt of the document by U4.
DA_004: Error
Failed to retrieve the document file from Rossum. We were unable to get the actual invoice file from Rossum to send to ERP. This is usually due to a timeout when the internal Rossum authorisation token has expired as the calls to ERP took too long. Export should be retried.
Document Type Details
DT_001: Error
No document type provided to lookup properties. We tried to validate the document type properties but no document type was provided. Check you have this setting
DT_002
Failed to retrieve document type details Received ERP. We received a http response status other than 200. The error from ERP should be provided with the message.
DT_003
Request for document type XX did not return the expected response. We had a 200 response back from ERP but the response was not in the expected format.
DT_004
No company id provided to lookup document type properties. We tried to look up a document type but had no companyId (client) to use.
DT_005: Warning
Authentication failed when trying to retrieve document type details. Please ensure that your credentials are correct and have the necessary permissions.. We tried to look up the document type details but received an authentication error. This is a warning as you may simply not have added this endpoint to your user access yet.
DT_006:
The document file size (XX KB) exceeds the maximum allowed size of XX KB as set on the ERP document type.. The document you are processing is too large to be sent to ERP. The only real way to resolve this is increase the document size limit in ERP or download, resize and re-process the document in rossum
DT_007: Error
Failed to retrieve document type details. No response body. (Status: ). We had a 200 response back from ERP but the response was empty.
Invoice Export Issues
EX_001: Error
Failed to export invoice. This was a failure to mark the invoice exported with Rossum and is most commonly due to not setting a token owner in the advanced extension settings. In most cases more information should be logged in your extension logging.
EX_002: Error
Failed to export invoice AND failed to mark as failed. When an export fails, we attempt to mark the document as export_failed in the Rossum UI. In some cases, such as when we are missing a token owner, we cannot complete either API call. Check your extension settings to ensure that a Token Owner is correctly set.
EX_003: Error
Failed to export invoice due to missing rossum token. Please check that there is a token owner in the advanced extension settings on rossum
EX_004: Error
Failed to export invoice due to missing Company id. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
EX_005: Error
Invoice exported but transaction number not updated to invoice. This happens if there is a missing transactionIdDataPoint on the schema. When present, we will patch the schema with the U4 ERP transactionId for the new transaction to assist with audit-trails. If this field does not exist in the schema we cannot patch to it. The extension will work but the audit-trail will be incomplete.
EX_006: Error
Invoice exported but transaction number not updated as it was not returned. This would happen if your Unit4 ERP does not return a transaction number for the newly posted invoice. The invoice should be posted to ERP, but the transaction number will not be shown in Rossum.
EX_007: Error
Invoice export failed due to missing Rossum token. If an authorisation token is not provided we will not attempt the export as we cannot complete several key steps. This is an automatic process in Rossum so please log a support ticket if you see this error.
EX_008: Error
Failed to read document contents. the impact of this error varies depending on ERP version. On ERP-X the invoice is posted digitally, and then the file is appended to the transaction. On prior versions of ERP the File is uploaded to document archive first and then the invoice is posted with the file reference included. As such, this error will mean either:
- On ERP7 / CR the invoice was not posted as we could not retrieve the document from Rossum. It will need to be retried once the underlying issue is resolved.
- On ERPx the invoice will have been posted but the invoice file was not attached. This can be resolved manually by appending the file in Unit4 directly.
EX_009: Information
When exporting this invoice to ERP Net and Tax values will be ignored. You have told the system to ignore tax and therefore net and tax values extracted from the invoice will not be sent to ERP.
EX_010: Information
Transaction exported to ERP successfully with EI02 number XXXXXX. Hurray! Your invoice has exported to ERP7 / CR. note that the EI02 number is approximate, if multiple requests are sent closely together, the ERP system will process multiple invoices on one EI02 report. Unfortunatly we are not able to retrieve the transaction number from ERPCR/ERP7 as the EI02 runs asynchronously when we request it.
EX_011: Information
Transaction exported to ERP successfully with transactionNumber XXXXXX. Hurray! Your invoice has exported to ERPx.
Invoice Formatting and Validation Issues
IF_001: Error
Failed to export invoice due to missing company id on the request from queue. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
IF_002: Error
Failed to export invoice due to missing invoice number in the data. This is a document level issue. We cannot export the invoice without a reference and the document schema was missing a reference. Ensure the reference is identified in the UI before confirming.
IF_003: Error
Failed to export invoice due to missing vendor number in the data. This is a document level issue. We cannot export the invoice without a valid vendor and the document schema was missing a vendor number. You can either specify a default supplier in the Rossum extension configuration or manually search for the supplier in the UI as outlined in the User Guide before confirming.
IF_004: Error
Failed to export invoice due to missing currency in the data. This is a document level issue. We cannot export the invoice without a valid currency. Ensure one is selected in the UI before confirming.
IF_005: Error
Failed to export invoice due to missing invoice date in the data. Ensure one is input to the document before confirming.
IF_006: Error
Failed to export invoice due to missing totals in the data. Ensure the totals are correct in the document before confirming.
IF_007: Error
EI02Variant not provided for MS7 invoice formatter. Your settings specify that you use ERP7 but there is no ei02Variant configured in Rossum extension configuration. This configuration is required for this setup.
IF_008: Error
currentAccountingPeriod not provided for invoice formatter. This happens if we have failed to fetch the company details from unit4 ERP and may be caused by missing or incorrect company / client ID.
IN_008: Error
Transaction with this invoice ID already exists in ERP. The combination of supplier, invoice and company / client id already exists in ERP. The invoice can not be sent to ERP.
IN_009: Error
Failed to post invoice did not receive body response. We attempted to send the Invoice but received an incorrect response body back from ERP.
INL_001: Error
Line totals do not balance. The total line amounts do not balance to the header amounts.
INL_003: Warning
Invoice quantity exceeds GRN quantity. The quantity on the invoice line exceeds what ERP is reporting as the GRN amount against the order line.
INL_004: Information
OCR XX does not match PO value XX. Certain information from the invoice line has been checked against the matched PO line and is different. We check the product code, the description and the quantity. (Values are picked up with further checks)
INL_005: Error OR Information
Line item has zero value. Please review the line item's values or remove line. If the extension setting ignoreZeroRows is on and a row with no value is found then this will be treated as an information message, otherwise it will be presented as an error message.
INL_006: Error
XX does not match calculated value XX. Values on the invoice line are not as expected.
INL_007: Error
Cannot validate totals. Missing some values.. Either the total gross, net or tax amount is missing.
INL_008: Information
Tax amount is non-zero and ignoreTax is switched on. Tax will be zero'd on submission. You have told the system to ignore tax and therefore net and tax values extracted from the invoice will not be sent to ERP.
INL_009: Error
Total amount does not match base amount + tax amount.
INL_010: Error
Total net amount does not match sum of line net amounts.
INL_011: Error
Total tax amount does not match sum of line tax amounts.
INL_012: Error
Total gross amount does not match sum of line gross amounts.
PA_001: Information
Skipping parked document. The document is set to parked status so no processing will happen.
TR_001
Failed to fetch transaction. CompanyId is required. This occurs during the invoice-number validation. If there is an invoice number and a supplier ID we check to ensure this invoice is not a duplicate. This error means that the check failed to search existing transactions due to missing company id on the request from the queue. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
TR_002
Failed to fetch transaction. Received status XX from ERP. This occurs during the invoice-number validation. If there is an invoice number and a supplier ID we check to ensure this invoice is not a duplicate. This error is due to the ERP system sending an unexpected response.
Invoice Export
IF_009: Error
Failed to export invoice due to errors in the document. This is thrown if there are unresolved errors in the document UI. To continue with the export, please address issues as listed in the UI. Export will still be attempted if there are only info and warning messages, but errors will block the exporter. If you are not seeing any errors in the UI, try clicking on the "Automation Blockers" button in the top of the sidebar.
IN_001: Error
CompanyId not provided for sending invoice to ERP. We tried to send the invoice but we did not have a company / client id to be able to do so. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
IN_002: Error
Failed to post invoice: (Status: ). We attempted to send the Invoice but received an incorrect status back from ERPx.
IN_003: Error
Failed to post invoice XML: (Status: $1). We attempted to send the Invoice but received an incorrect status back from ERP.
IN_004: Error
Purchase orders are not all from the same supplier. The invoice contained multiple purchase order numbers but they were not all from the same supplier. This invoice can not be processed as it is.
IN_005: Error
Purchase orders are not all for the same client ID.The invoice contained multiple purchase order numbers but they were not all for the same company / client ID. This invoice can not be processed as it is.
IN_006: Information
No order number found. The OCR system did not find a purchase order number on the invoice.
IN_007: Information
No matching orders found in ERP. The OCR system did find purchase order number(s) but a matching order number was not found in ERP.
Purchase Orders
PO_001: Error
Failed to retrieve purchase orders from ERP System (Status: ). This is reported when the ERP system responds in an unexpected way when fetching purchase orders. Check your extension logs for more specific details such as returned HTTP codes.
PO_002: Error
Splitting invoices across purchase orders not supported. This error is raised when a single invoice document contains lines which apply to multiple purchase orders. This is currently unsupported as ERP is unable to accept consolidated invoices via any input. Please contact us if you are impacted by this issue and we may schedule changes to support it on our side if required.
PO_003: Warning
Matching Order(s) were found in ERP, but none at the correct status:. The OCR found orders on the document, we found orders in ERP but the status didn't match either our defaults or your allowed PO status settings
PO_004: Error
No-PO-No_Pay A valid order number is required for every line item.. This supplier has been set as no-po-no-pay and so every line on the invoice must have a valid purchase order number. Please see this documentation about no-po no pay
PO_005: Error
Could not find purchase order. At a line level an order has been identified within the OCR, but we were not able to find a matching purchase order in ERP. Check the order exists in ERP and has the correct status based on your allowed PO status settings
PO_006: Error
Could not match purchase order line due to schema error. This is a configuration level, we couldn't find the correct field to store the purchase order in. Check the queue schema is correcly configured
PO_007: Error
Cannot split across multiple purchase orders. A line level error when multiple purchase orders are found on different lines. This is currently unsupported as ERP is unable to accept consolidated invoices via any input. Please contact us if you are impacted by this issue and we may schedule changes to support it on our side if required.
Supplier Group Issues
SG_001: Error
Failed to retrieve supplier-group from ERP System (Status: ). Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
SG_002: Error
CompanyId not provided for supplier-group lookup. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
SG_003: Error
Failed to retrieve supplier-group from ERP System. Not an array. Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
SG_004: Error
Failed to retrieve supplier-group from ERP System. Invalid group structure. When retrieving supplier-group from ERP we extracted a supplier group from the response but the group was invalid.
Supplier Issues
SU_001
Failed to retrieve suppliers from ERP System (Status: ). Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
SU_002
CompanyId not provided for supplier lookup. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
SU_003: Warning or Error
Supplier currency XX does not match invoice currency XX. There is a mismatch between the currency on the invoice and the currency on the supplier. If the supplier has a fixed currency then this will be raised as an error, otherwise it will be a warning.
SU_004: Warning
Bank account does not match pay recipient. The supplier has a pay recipient attached and the bank account on the invoice does not match the bank account on the pay recipient record in ERP.
SU_005: Warning
Bank sort code does not match pay recipient. The supplier has a pay recipient attached and the sort code on the invoice does not match the sort code on the pay recipient record in ERP.
SU_006: Warning
IBAN does not match supplier. The normalised IBAN on the invoice does not match the IBAN on the ERP supplier record. This will be generated on the normalised IBAN field which is where we have taken the IBAN identified by OCR and cleaned it up.
SU_007: Warning
IBAN does not match pay recipient. The supplier has a pay recipient attached and the IBAN on the invoice does not match the IBAN on the pay recipient record in ERP. his will be generated on the normalised IBAN field which is where we have taken the IBAN identified by OCR and cleaned it up.
SU_008: Warning
Normalised IBAN does not match supplier (see adjusted field below). The normalised IBAN on the invoice does not match the IBAN on the ERP supplier record. This will be generated on the standard IBAN field but you should look at the normalised IBAN field for the error.
SU_009: Warning
Normalised IBAN does not match pay recipient (see adjusted field below). The normalised IBAN on the invoice does not match the IBAN on the pay recipient record in ERP. This will be generated on the standard IBAN field but you should look at the normalised IBAN field for the error.
SU_010: Warning
SWIFT/BIC does not match supplier. The SWIFT / BIC code on the invoice does not match the SWIFT / BIC code on the ERP supplier record.
SU_011: Warning
SWIFT/BIC does not match pay recipient. The supplier has a pay recipient attached and the SWIFT / BIC code on the invoice does not match the SWIFT / BIC code on the pay recipient record in ERP.
SU_012: Warning
Supplier is linked to an inactive pay recipient XX. The supplier has a pay recipient attached, but that pay recipient record is inactive in ERP.
SU_013: Warning
Bank account does not match supplier. The bank account on the invoice does not match the bank account on the ERP supplier record.
SU_014: Warning
Bank sort code does not match supplier. The sort code on the invoice does not match the sort code on the ERP supplier record.
SU_015: Information
Supplier has pay recipient XX configured. An information message to tell the user that the supplier has a pay recipient attached to its record in ERP
SU_016: Error
Supplier not matched. We were unable to match a supplier and no default supplier id was provided to use.
Tax codes
TC_001: Error
Failed to fetch tax codes from ERP system (Status: ). Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
Transactions
TR_001: Error
Failed to fetch transaction. CompanyId is required. We tried to look up transactions to check for duplicates but we didn't have a company / client id. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
TR_002: Error
Failed to fetch transaction. Received status XX from ERP. We tried to look up transactions to check for duplicates but we received an invalid status. Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
Tax systems
TS_001: Error
Failed to fetch tax system. CompanyId is required. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
TS_002: Error
Failed to fetch tax systems from ERP (Status: ). Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
TS_003: Error
Failed to fetch tax system. Invalid response body. The HTTP request to fetch the tax system succeeded but the response body was empty.
TS_004: Error
Failed to fetch tax systems from ERP. Response was not an array. The HTTP request to fetch the tax system succeeded but the response body was malformed.
ERP Users
US_001: Error
CompanyId not provided for user lookup. We try and get a user matching the Rossum logged in email, so we can pass this as the responsible. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
Value Matrix Issues
VM_001: Error
Failed to fetch value matrix from ERP (Status: ). Further details, such as the HTTP status code received, should be logged to your extension logs to help debug the issue.
VM_002: Error
Failed to fetch value matrix from ERP. Invalid response. The HTTP request to fetch the value matrix succeeded but the response body was malformed.
VM_003: Error
Failed to fetch value matrix. Missing company ID. This is likely to be due to a missing or invalid company ID in the Rossum extension configuration or the document schema.
VM_004: Error
Value matrix incorrectly formatted. ERP7 / CR does not support value-matrixes through the API like ERP-x does. As such this requires a simple custom object to be configured, which must match the expected format. Please see the setup documentation for more details.
Elevated Warnings
WARN_001: Error
The following warnings have been elevated to errors:. This is where your configuration elevates some warning messages to errors. Please see the settings documentation for elevated warning and the user documentation for elevated warnings for further information
Queue Configuration
QCONF_001: Error
Invalid event body. This error is raised very early in the extraction process if the request from Rossum is not of the expected format. This may happen if the wrong events are selected for the extension.
QCONF_002: Error
No shared secret configured. This is likely to happen if we have not yet configured authorisation for you, or if the authorisation details were not input correctly into the Shared Secret in your Rossum extension configuration. It is caused by being unable to read the secret from our data store.
QCONF_003: Error
Invalid signature. This is likely to happen if we have not yet configured authorisation for you, or if the authorisation details were not input correctly into the Shared Secret in your Rossum extension configuration. It is caused by Rossum signing the payload with a secret which does not match the secret we have in our data stores. s.
QCONF_004: Error
Invalid ERP connection settings, please check your extension secrets and / or settings configured in Rossum extension configuration or your
QCONF_005: Error
Missing field XX in schema. Please check your schema aligns with the documented required schema as a field appears to be missing from your configuration.
Queue Settings Issues
QSET_001: Error
ei02Variant is required in settings for ERP7 export to function correctly. Your settings specify that you use ERP7 but there is no ei02Variant configured in Rossum extension configuration. This configuration is required for this setup.
QSET_002: Error
invoiceDocumentTypes is required in extension settings for queue. There is no document type configured in Rossum extension configuration. This configuration is required to be able to export documents.
Network Issues
Note for all of these codes, you should also check that there are no further messages in the details section presented as the high level code may be caused by an underlying issue with it's own code.
TIME_000 / TIME_001 / TIME_002
This will present in the extension logs as the extension has timed out.
It may also present with Read Timeout. (read timeout = XXs)
This will be down to the response from Unit4 being too slow when calling the APIs. The total request time in making those calls has combined to exceeded the timeout.
As standard, the timeout on your extension will be 30s. If you are seeing this error then please log a ticket with support to request that the timeout is increased.
The maximum that this can be set to is 60s.
You may also wish to consider your caching settings
99_000
This code means that we could not establish a network connection to your ERP server. This indicates a low-level network error such as DNS, TLS, connection refused by firewall, etc. You will need to ensure that the connection URL returned in the error message is correct and accessible from our egress IP addresses. For our up-to-date egress addresses please contact support. You may find POSTman or a similar tool useful for debugging this.
99_400 99_500 99_401 99_403 99_404 99_405 99_503
These codes are usually going to be "standard https" error responses from the ERP system, however they may occasionally be related to internal errors.
Please see the http error codes in the FAQ
The first place to check should be the extension log as it will usually state something like HTTP request failed [your server address]
If you see your API or SOAP address in there, then you should check the logs from your ERP system and configuration for those endpoints on your ERP system in the first instance.
Internal error codes
These codes relate to internal issues. These may occasionally be triggered by unexpected configuration but are not simple to resolve externally. If you receive one of these error codes and there are no further messages in the details section, please contact support for assistance.
- CACHE_001
- CACHE_002
- ASP_001
- ASP_002
- ASP_003
- ASP_004
- SYS_001
- SYS_999
- 99_406
- 99_408
- 99_409
- 99_410
- 99_411
- 99_412
- 99_413
- 99_414
- 99_415
- 99_416
- 99_417
- 99_418
- 99_422
- 99_425
- 99_426
- 99_428
- 99_429
- 99_431
- 99_451
- 99_501
- 99_502
- 99_504
Test extension message codes
These should only be generated when testing the extension and should only be generated within the extension logs (activities)
TEST_000:
Failed to test extension due to missing rossum token. Please check that there is a token owner in the advanced extension settings on rossum. You should check there is a valid token owner in your extension configuration
TEST_001:
Test Failed. THe test has failed, see the logs for more details.
TEST_002:
TEST EXTENSION: ClientID is required in queue settings to be able to test ERP access. There is no client / company id in the extension settings. You may have chosen not to set this and you are setting it at the document level, but for tests to run it must be included in the extension settings.
TEST_003:
TEST EXTENSION: Unknown test name. There is an unknown test in your test configuration in extension settings, please check the configuration and the casing of your test name.
TEST_004:
TEST EXTENSION: Test name XX requires a value to be provided in the test value
TEST_005:
TEST EXTENSION: XX: Failed to connect to endpoint: XX Runtime: XXms
TEST_006:
TEST EXTENSION: XX: Connected to endpoint OK, retrieved: XX Runtime: XXms
TEST_007:
TEST EXTENSION: XX: Running test...
TEST_008:
TEST EXTENSION: COMPANIES: Found companyId (clientId) XX configured in the extension settings
TEST_009:
TEST EXTENSION: Identified system: XX successfully
TEST_999:
Message will be generated by test runner
Message codes that can be elevated to errors
- ACL_003
- ACL_004
- DT_005
- INL_003
- PO_003
- SU_003
- SU_004
- SU_005
- SU_006
- SU_007
- SU_008
- SU_009
- SU_010
- SU_011
- SU_012
- SU_013
- SU_014