ObjectAction
EntitySet of valid and invalid state/view transitions.
Fields
| WindowTag | Identifies the tag of the window executing the action. This field can have the value “Unknown” which matches any window tag. |
| Action | Identifies the action to occur. This field can have the value “Unknown” which matches any action. |
| State | Identifies current state of the window. This field can have the value “Unknown” which matches any state. |
| View | Identifies the current view of the window. It is not currently used . |
| ValidAction | Identifies if the action is valid for the given state and view. A value of $false means the action is invalid. All other values are interpreted to mean the transition is valid. |
| NewState | Identifies the new state the window should enter if the action is valid. |
| NewView | Identifies the new view the window should enter if the action is valid. |
| SaveData | Identifies what should be done if the data in the window has been modified. If it is blank, no checking is done for modified data. “Yes” means the data should be unconditionally saved. “No” means the data should be unconditionally discarded. “PromptYes” and “PromptNo” means the user should be prompted to see if the data should be saved. The default button would be Yes or No respectively. |
| ValidCondition | This field is not currently used. |
| Comment | Contains free-form comments for documentation purposes only. |
| ObjectActionOwner | Defines the owner of this entry. Standard entries have ObjectActionOwner set to “System”. If you add your own application specific entries, you should specify a different owner (“Application” for example). You should not change or delete any entries with a “System” owner. This field is not used by pValidateAction. Its purpose is to distinguish standard entries from application specific entries. |
| RecId | RecId contains a unique key (an integer) for each entry in the table. As long as the value is unique, any numeric value can be used in this field. |
Comments
ObjectAction is an EntitySet defined in $DeployServices. Every Zim database has its own copy of ObjectAction.
Note: The actual filename for the copy of ObjectAction is Zim0126 and is located in a sub-directory of your database directory called DPSRT.
Standard Object/Action Definitions
The Framework provides standard state and view definitions that are suitable for implementing many kinds of single table editing and header/detail type applications. In developing your own applications, you can employ these state transitions or implement your own. You can view and update this table from within the Development Center using the Tools | State Transitions menu item.