Which name of the field would cause the logging process to become corrupted?

A developer creates an automation solution that processes a specific file stored in a Shared location. A developer uses Add Log Fields activity to add a field that indicates which file is being processed during each run.

Which name of the field would cause the logging process to become corrupted?
A . nameOfTheFile
B. fileName
C. processedFile
D. file

View Answer

Answer: B

Explanation:

Creating custom log fields that have the same name as a default log field causes the logging process to become corrupted and may cause issues in the workflow you are running.

For example, creating a custom log field called fileName causes this issue, as fileName is a log field that is generated by default.

Default fields

These log fields are present in all execution type logs, such as SQL (if configured),

Elasticsearch (if configured), and the default EventViewer Logs:

Message -The log message.

Level -Defines the log severity.

Timestamp -The exact date and time the action was performed.

FileName -The name of the .xaml file being executed.

jobId -The key of the job running the process.

processName -The name of the process that triggered the logging.

processVersion -The version number of the process.

windowsIdentity -The name of the user that performed the action that was logged.

robotName -The name of the robot (as defined in Orchestrator).

UiPath Documentation

Exam Topic: Describe how to write coherent log messages (default or user-defined), and how to use them to diagnose and debug a production process running in UiPath Studio