Log information for active links

The following information is generated when an active link is executed:

  • Name
  • Transaction ID (only for PWA)
  • Start, end, and elapsed time (to 1/10,000 of a second)
  • Operation that fires the active link
  • Execution order
  • Form applied to
  • Linked to which field (if applicable)
  • Mode (for example, Query, Modify, Submit)
  • User's name
  • Qualification and if it passes or fails
  • Actions generated:
    • Action number
    • Type (for example, Set Fields, Set Characteristics, Push Fields)
    • Name, new characteristics, and value of affected fields, if applicable.

Related topics

Enabling-and-analyzing-logs

Analyzing-logs

Consider the logging for the Assignee field where Nisha Sharma is selected from the drop-down list.

image2021-3-2_16-41-22.png

The following example log shows the workflow of an active link named Assignee_010_SetID that starts execution when a user selects an assignee from the list. As a developer, you may define an active link action that must be taken when certain conditions are true and some when some conditions are false.

In the example, the activelink runs if a condition is fulfilled, which is why you see SetFields action named action 0 right after True actions. This is followed by action 1, which is also a SetFields action that changes the Assignee field to display Nisha Sharma.

ActiveLink Start:- HPD:INC:Assignee_010_SetID | HPD:Help Desk/Best Practice View - Tue Mar 02 2021 3:28:40 PM ms 349
True actions:
action 0
   SetFields:
         Assignee Login ID(4) = nisha
action 1
   SetFields:
<CLAT> /* Tue Mar 02 2021 09:58:40.386 */+API call, Procedure #181
<FLTR> <TrID: LO41-KtCQCWSII3kxfwFMw:0000065> <TID: 0000000674> <RPC ID: 0000559969> <Queue: List      > <Client-RPC: 390620   > <USER: ppan                                         > <Overlay-Group: 1         > /* Tue Mar 02 2021 09:58:40.3910 */    Start filter processing (phase 1) -- Operation - GET on CTM:Support Group Association - GGA000000000147
<FLTR> <TrID: LO41-KtCQCWSII3kxfwFMw:0000065> <TID: 0000000674> <RPC ID: 0000559969> <Queue: List      > <Client-RPC: 390620   > <USER: ppan                                         > <Overlay-Group: 1         > /* Tue Mar 02 2021 09:58:40.3910 */    End of filter processing (phase 1) -- Operation - GET on CTM:Support Group Association - GGA000000000147
<CLAT> /* Tue Mar 02 2021 09:58:40.392 */-API call, Procedure #181
<CLAT> /* Tue Mar 02 2021 09:58:40.392 */+API call, Procedure #7
<CLAT> /* Tue Mar 02 2021 09:58:40.394 */-API call, Procedure #7
 (ARNOTE 8914)
         Assignee+(1000000218) = Nisha Sharma
ActiveLink End:- HPD:INC:Assignee_010_SetID | HPD:Help Desk/Best Practice View - Tue Mar 02 2021 3:28:40 PM ms 397

Active link logging for PWA

image2021-3-2_15-8-32.png

In the Activelink Logging window, you can filter specific active link logs by pasting the AsyncExecId (transaction ID) in the field and clicking filter. You can hide interval activelinks by selecting the hide interval activelinks check box. You can revert to viewing all active link logs by clicking show all. 

Viewing Mid Tier logs

You can view the log files that record the activity of the Mid Tier. If you have no log files generated, it might be because the Log Viewer setting is set to Console. Change this setting to Files to generate Mid Tier log files.

Log file view settings

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*