Log Entry

The Log Entry (CLOGENT) page allows a user to search for log entries using various criteria. The Log Entry page shows details of the error including error text, stack trace, and original request payload if log entry is associated with a service request.

The Log Entry page also allows the user to modify certain fields:

Reviewed: This field indicates that a user has reviewed the log entry; it allows system administrators to ignore log entries later on.
Request Payload: This field displays original service request payload if log entry is associated with a service request. The user may modify the request payload if needed, in which case the modified payload is saved along with log entry.
Mark for Resubmit: If an error indicates that the service request failed completely and it failed in an Orchestration module, the user may re-submit the service request back to the same Orchestration module. Setting this flag to Yes will make the Resubmit sub-module to select the log entry, use modified request payload or original payload and re-submit the service request back to the orchestration module where it was originally failed.

The following table provides the description of various Log Entry fields:

Field	Description
Log Entry Number	A unique number for Log Entry. It is internally generated by Connect.
Service Request Number	The Service Request Number for which the log entry was generated.
Correlation Id	The Correlation Id of the service request.
Error Date	The Date/Time when the log entry was created.
Saved Date	The Date/Time when the log entry was saved in the database.
Error Id	A Connect Specific Error identifier. All Error Identifiers are table driven.
Error Severity	Every Error Identifier has an associated severity – Fatal (F), Error (E), and Warning (W), which is displayed in this field.
Error Text	Error Text is table driven with placeholders for important values.
Error Additional Text	Error Additional Text is not table driven. It is optionally included by Connect when generating an error.
Source Application	The Source Application of the service request.
Reviewed?	A flag indicating whether an administrator has already reviewed this log entry. This field is also a search criterion allowing administrators to search for only non-reviewed log entries
Tenant Id	The Tenant ID associated with the Source Application of the service request.
Web Service	The Web Service Name associated with the service request.
Web Service Operation	The Web Service Operation associated with the service request.
Message Name	The Message Name associated with the service request.
Module Name	The Module Name where the error occurred.
Module Instance Id	The Module Instance Id where the error occurred.
Orchestration Service	The Orchestration Service Name that encountered the error.
Tran Type	A service request is typically for a specific Advantage transaction. Tran Type indicates the type of transaction, for example, PR, JV, ESMT, and so forth.
Tran Code	The Transaction Code for the service request, if it is for a specific Advantage transaction.
Department	The Department code for the service request, if it is for a specific Advantage transaction.
Tran Id	The Transaction ID for the service request, if it is for a specific Advantage transaction.
OS Route Name	The OS Route name that was used to process the service request.
Route Step Number	The OS Route Step number during which this log entry was created.
FPC Id	The FPC Id used for processing this file-based service request.
Resubmit
Reprocessable?	Yes indicates that the log entry may be re-submitted.
Marked for Resubmit	Yes indicates that an administrator has marked this log entry for re-submission.
Resubmitted?	Yes indicates that the associated service request has been re-submitted.
Resubmitted Date	The Date/Time when the associated service request was re-submitted.
Modified Payload	If request payload was modified by a user for the purpose of resubmitting the associated service request, then this field contains the modified payload; otherwise, it will contain the original service request payload.