Reason Code

The optional ReasonCode parameter gives an indication of what the user is trying to do when the uQueryCanDeactivate check occurs. Note that one user action may result in multiple uQueryCanDeactivate checks.

Application Trace Shows Code Description

VF_FPM09:MEXECUTECOMMAND

1

Execute a command

VF_UM040:ITEMGOTFOCUSACCEPT

11

Main Instance List entry got focus

VF_UM083:ITEMGOTFOCUSACCEPT

12

Secondary Instance List entry got focus

VF_SY100:GET_LOCKSTATUS

13

Snap-in Instance List checking uCurrentLockStatus

VF_UM037.TABCHANGING

2

User clicked on a different tab

VF_UM014:ITEMGOTFOCUSACCEPT

21

Navigation pane (as two lists) application item selected

VF_UM015:APPVIEWBUTTONSBYID

22

Navigation pane (as two lists) – View button pressed

VF_UM015:ITEMGOTFOCUSACCEPT

23

Navigation pane (as two lists) business object selected

VF_UM016:UMENUITEMSELECTED

24

Navigation pane (as drop down) item selected

VF_UM016:ITEMGOTFOCUSACCEPT

25

Navigation pane (as tree view) item selected

VF_UM040.CLEAR_BUTTON

14

Clear the instance list

VF_UM003:CLOSEQUERY

3

Close a force-floated command handler

VF_UM046:CLOSEQUERY

4

Close a separate window command handler

VF_AC006:BEGINCLOSEFORM:A

31

Close Main Framework window

VF_AC006:BEGINCLOSEFORM:B

32

Close Secondary Framework window

VF_SY100:AVSWITCH

41

Switch

VF_SY150:USELECTAPPLICATION

26

Navigation pane application selected

VF_SY153.USETTHEME

43

User changes THEME

 

999

Unknown

 

An action may result in multiple uQueryCanDeactivate checks, and multiple reason codes.

If you want to determine the reason code/s for a particular action, start an application level trace in the Framework and carry out the action. The trace will show you the action/s that occurred.

The codes have been grouped in this way: