For more efficient debugging of autopopulated properties, generate logs
that contain events connected with specific properties that you select. Consequently,
the troubleshooting process is better targeted and you can more quickly identify and fix
issues in your application.
Autopopulated properties hold metadata on
clipboard pages and are declarative, which means that the system triggers autopopulated
properties automatically. Debugging autopopulated properties can be challenging without
specific information about metadata that the properties store, so creating logs that include
this information can accelerate the troubleshooting process.
You can generate logs for autopopulated properties by
setting the logging level to DEBUG. For more information
about logging levels, see Log levels for log categories.
In the navigation pane of Admin Studio, click ResourcesLog categories.
In the Category name column, locate the
pxAutoPopulate category.
Tip: To find the category faster, you can enter a logger of the
pxAutoPopulate category in the Search
categories by loggers field. A sample logger of the
pxAutoPopulate category is
autopopulate.lifecycle.
In the row of the pxAutoPopulate category, click MoreChange log level.
In the Modify log level dialog box, in the Log
level list, select DEBUG.
In the Reset in (hours) list, select the number of hours
that pass before the log resets.
Optional: To filter the results that the log file includes, define filter criteria:
To generate logs only for a specific requestor session, in the
Operator field, enter the operator ID for which
you want to generate logs.
To restrict logs to properties that are associated with a specific rule
type, in the Rule Type list, select a rule type that
you want to use.
To restrict logs to properties that are part of a specific class, in the
Class field, enter the class that you want to
use.
To restrict logs to properties that are associated with a specific rule,
in the Rule field, enter a rule that you want to
use.
In the Auto Populate Property Name(s) field, enter the
name of the property for which you want to generate logs.
Tip: You can generate logs for multiple properties by entering the
properties' names in a comma-separated list. If you skip specifying
autopopulated properties, the system generates logs for all autopopulated
properties in the current cluster.
For example: To generate logs for multiple properties, enter
pyDuplicateCaseRef,pyGetCasePredictions.
Click Submit.
For example: The following figure shows a sample configuration of the
pxAutoPopulate log category that generates logs for the
pyDuplicateCaseRef and
pyGetCasePredictions properties that are associated with an
activity:pxAutoPopulate log category configuration
