Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • downloads • Versago & Bizweaver Templates • Introduction (Email) • Control Settings • Using APP Report Maintenance and Delivery
versago3:from_sp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
versago3:from_sp [2023/07/12 14:11]
dlee [Obtaining Form Values] 		versago3:from_sp [2024/04/09 14:33] (current)
dlee
Line 1: Line 1:
-====== Custom Store Procedures ======+====== Custom Stored Procedures ======
  
 There are two custom procedures available for use.  These procedures are automatically created when a new form is created. There are two custom procedures available for use.  These procedures are automatically created when a new form is created.
Line 74: Line 74:
  
 FormField1, ..2, ..3 must match the Field Name in the form control settings. It is case sensitive FormField1, ..2, ..3 must match the Field Name in the form control settings. It is case sensitive
- 
---------------------------------------------------------------------------------------- 
- 
-How to determine transaction type 
- 
-IF isnull(@FormMode,'X') = 'X' AND @ActionType = 'S' - the record is being added. 
-IF isnull(@FormMode,'X') = 'F' AND @ActionType = 'S' - the record is being updated. 
-IF isnull(@FormMode,'X') = 'X' AND @ActionType = 'D' - the record is being deleted. 
  
 --------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------
Line 94: Line 86:
  
 FormField1, ..2, ..3 must match the Field Name in the form control settings. It is case sensitive FormField1, ..2, ..3 must match the Field Name in the form control settings. It is case sensitive
-User SQL cursor to process each record+Use SQL cursor to process each record
 </code> </code>
  
Line 114: Line 106:
 You can now determine the form action based on the following code combinations. You can now determine the form action based on the following code combinations.
  
-IF isnull(@FormMode,'X') = 'X' AND @ActionType = 'S' - the record is being added. \\ +IF isnull(@FormMode,'') = 'A' AND @ActionType = 'S' - the record is being added. \\ 
-IF isnull(@FormMode,'X') = 'F' AND @ActionType = 'S' - the record is being updated. \\ +IF isnull(@FormMode,'') = 'F' AND @ActionType = 'S' - the record is being updated. \\ 
-IF isnull(@FormMode,'X') = 'X' AND @ActionType = 'D' - the record is being deleted.+IF isnull(@FormMode,'') = 'F' AND @ActionType = 'D' - the record is being deleted.
  
 The “IF” statements can be used in the form’s Custom_PreExecute procedure to prevent certain actions from occurring before the form record is posted. The same logic can also be used in the form’s Customer_PostExecute procedure to take other actions, like posting information to logging columns in the record or to a logging table, triggering a Bizweaver workflow, etc. Keep in mind that the updated record has already been posted when the Custom_PostExecute procedure is executed. The “IF” statements can be used in the form’s Custom_PreExecute procedure to prevent certain actions from occurring before the form record is posted. The same logic can also be used in the form’s Customer_PostExecute procedure to take other actions, like posting information to logging columns in the record or to a logging table, triggering a Bizweaver workflow, etc. Keep in mind that the updated record has already been posted when the Custom_PostExecute procedure is executed.
versago3/from_sp.1689185480.txt.gz · Last modified: 2023/07/12 14:11 by dlee

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki