This page (revision-49) was last changed on 11-Mar-2022 15:50 by Lilia Urtan

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
49 11-Mar-2022 15:50 5 KB Lilia Urtan to previous
48 26-Nov-2021 10:22 5 KB kparrott to previous | to last
47 26-Nov-2021 10:22 5 KB RForbes to previous | to last
46 26-Nov-2021 10:22 5 KB RForbes to previous | to last
45 26-Nov-2021 10:22 4 KB RForbes to previous | to last
44 26-Nov-2021 10:22 4 KB RForbes to previous | to last
43 26-Nov-2021 10:22 4 KB RForbes to previous | to last
42 26-Nov-2021 10:22 4 KB RForbes to previous | to last
41 26-Nov-2021 10:22 4 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
VMEX
VMEX

Version management

Difference between version and

At line 14 changed one line
The information written out here is often of a technical nature and may not be meaningful to the average user but is aimed at a more technical user who is trying to resolve a problem with a workflow.
The information written out here is often of a technical nature and may not be meaningful to the average user but is aimed at a more technical user who is trying to resolve a problem with a work flow.
At line 17 added one line
Each time a process is run, an Execution ID is created (i.e. MEX ID 178309). This ID is important, so that when you go to VMEX, the correct Execution Log is being reviewed. For work flow tracing this is generated behind the scenes and you won't know it until opening VMEX.
At line 18 changed one line
Each time a process is run, an Execution ID is created (i.e. MEX ID 178309). This ID is important, so that when you go to VMEX, the correct Execution Log is being reviewed. For workflow tracing this is generated behind the scenes and you won't know it until opening VMEX.
The column entitled "Process" indicates the process that was run (i.e. P2k_pmwrkflw this refers to a workflow action). The column "Text" provides the actual details of what the process was trying to do. To view the error in its entirety, click on the line and view the information contained in the "Message" field.
At line 20 removed 2 lines
To view the error in its entirety, click on the line and view the information contained in the "Message" field.
At line 24 changed 6 lines
!Header Information
;[MEX ID|MEX_ID]:This field provides the execution ID created when a process is run.
;[Process|FUNCTION_NAME]: This identifies the name of the process that was executed
;[User|USER_NAME]:The user running the process will be identified in this field.
;[Identity|PERSON_CODE]:The identity information of the person running the process will be displayed in this field
;[Start Date|EXECUTION_START_DATE]/ [End Date|EXECUTION_END_DATE]: These fields indicate the beginning and end of the process
;[MEX ID|MEX_ID]
At line 31 changed one line
!Execution Information
;[Process| ]
At line 33 changed one line
;[Status|EXECUTION_STATUS]:This field displays the status of the execution. (e.g. pending, in process)
;[User|USER_NAME]
At line 35 changed one line
;[Destination Format|DESTINATION_FORMAT]:This field indicates the format of the output at the destination, for example, PDF, HTML, or TXT.
;[Status|STATUS_CODE]
At line 37 changed one line
;[Destination Type|DESTYPE]:This field identifies the format for the output, for example, CACHE, file, email, printer. This field is normally set to CACHE.
;[Destination Format|DESTINATION_FORMAT]
At line 39 changed one line
;[Start Date|EXECUTION_START_DATE]/ [End Date|EXECUTION_END_DATE]: These fields indicate the beginning and end of the process
;[Destination Type|DESTINATION_TYPE]
At line 41 changed one line
;[Report Mode|REPORT_MODE]:This field identifies the style of the report, either bitmap or character.
;[Start Date|START_DATE]
At line 43 changed one line
;[Job Name|JOB_NAME]:This field identifies the specific report execution. This field defaults to the Function+Execution ID. (e.g. RDJB#162852)
;[End Date|END_DATE]
At line 45 changed one line
;[Destination|DESTINATION]:This field identifies the name of the report server the report will be directed to when launched. Your system administrator will normally set a default for this field. e.g. rep_mercury_AS10G_RL2
;[Report Mode|REPORT_MODE]
At line 47 changed one line
;[Report History]:This button will bring up a dialog that shows all __your__ executions of that report that are stored on the report server, and you may view them
;[Job Name|JOB_NAME]
At line 43 added 4 lines
;[Destination|DESTINATION]
;[Destination Name|DESTINATION_NAME]
At line 53 changed one line
;[Process|MODULE_NAME]:This field indicates the process that was running when the message was issued (i.e. P2k_pmwrkflw this refers to a workflow action). When tracing, this indicates the program sub unit executing.
;[Process|PROCESS]:
At line 55 changed one line
;[Text|TEXT]:This field provides the actual details of what the process was trying to do.
;[Context 1|CONTEXT]:
At line 55 added 2 lines
;[Text|TEXT]:
At line 59 changed one line
;[Trace Level|TRACE_LEVEL]:This field used to indicate the level of trace (messages) that the calculation report should display when performing a trial calculation.
;[Trace Level|TRACE_LEVEL]:
At line 61 changed one line
;[Error Level|ERROR_LEVEL ]:This field indicates the error level, e.g. warning, information, error.
;[Error Level|ERROR_LEVEL ]:
At line 63 changed one line
;[Context 1|CONTEXT_1]/[Context 2|CONTEXT_2]: Provides additional information to frame the run log in context.
;[Context 1/Context 2|CONTEXT]:
At line 65 changed one line
;[Message Code|MESSAGE_CODE ]:This field provides the error in its entirety.
;[Message Code|MESSAGE_CODE ]:
At line 67 changed one line
;[Run Log Text|RUN_LOG_TEXT ]:This field that allows you to add notes for the run log.
;[Run Log Text|RUN_LOG_TEXT ]:
At line 71 changed one line
;[Parameter Name|PARAMETER_NAME ]:This field uniquely identifies the parameter within the system.
;[Parameter Name|PARAMETER_NAME ]:
At line 73 changed one line
;[Prompt|PARAMETER_PROMPT]:This field uniquely identifies the parameter prompt within the system.
;[Prompt|PROMPT]:
At line 75 changed one line
;[Value|PARAMETER_VALUE]:This field displays the value of the parameter.
;[Value|VALUE]:
At line 78 changed 2 lines
This tab identifies the tables that are changed by this process. The information comes from the [P2K_AM_EXECUTION_AUDITS] table
;[Table|TABLE_NAME]:This field identifies the table changed.
;[Table|TABLE]:
At line 81 changed one line
;[DML Action|DML_ACTION]: Identifies the type of change made (Insert/Update/Delete)
;[DML Action|DML_ACTION]:
At line 83 changed one line
;[Reference|REFERENCE_ID]: This identifies the [ID] of the record modified by the process, on the table identified
;[Reference|]:
At line 85 changed one line
;[Changed|CHANGE_DATE]:The date/time the table was changed is displayed in this field.
;[Changed|CHANGED]:
At line 86 added one line
[CLEANUP]
At line 88 removed 4 lines
----
![Notes|Edit:Internal.VMEX]
[{InsertPage page='Internal.VMEX' default='Click to create a new notes page'}]
This page (revision-49) was last changed on 11-Mar-2022 15:50 by Lilia UrtanTop