Wiki

Scale Your Enterprise

User Tools

Site Tools


versago3:dataview_payment

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:dataview_payment [2024/03/12 11:00]
dlee
versago3:dataview_payment [2024/03/12 11:14] (current)
dlee
Line 1: Line 1:
 ====== Record/Payment Submission ====== ====== Record/Payment Submission ======
  
-The “Record/Payment Submission” page is used to configure a special type of data view that allows the user to select records for additional processing by Bizweaver. In addition, payment processing is supported via Authorized.net if the Payment Gateway has been configured in the **[[versago3:system_settings#Payment Gateway|Settings]]** page+The “Record/Payment Submission” page is used to configure a special type of data view that allows the user to select records for additional processing by Bizweaver. In addition, payment processing is supported via Authorized.net if the Payment Gateway has been configured in the **[[versago3:system_settings#Payment Gateway|Settings]]** page.
  
  
Line 12: Line 12:
     * Typically used for payment processing to change the amount to pay.     * Typically used for payment processing to change the amount to pay.
   * Select up to three columns to display on the Confirmation page.   * Select up to three columns to display on the Confirmation page.
-  * Select the connection and enter the table name where the user selected data will be save+  * Select the connection and enter the table name where the user selected data will be saved. 
 +    * The system will create the table with a set of columns that will match those of the data view plus **additional columns** for internal processing
   * Enable call to Bizweaver and complete fields   * Enable call to Bizweaver and complete fields
     * Workflow id     * Workflow id
     * Bizweaver Service address     * Bizweaver Service address
     * BW variable name that will receive the batch id created when the selected data is saved.     * BW variable name that will receive the batch id created when the selected data is saved.
 +
 +===== Record Submission Database Table Structure Details =====
 +<WRAP center round important 80%>
 +The record submission table is created during the initial setup of the data view. Changes to the data view's result set require the manual update of the table definition.
 +</WRAP>
 +
 +^Column Name                                       ^Type and Size^Notes                 ^
 +|User columns from data view appear first      |                                  |
 +|vgo_PaymentDate                                   |DateTime     |For payment processing|
 +|vgo_PaymentDetails                                |nvarchar(100)|For payment processing|
 +|vgo_CC_RespCode                                   |nvarchar(50) |For payment processing|
 +|vgo_TransID                                       |nvarchar(50) |For payment processing|
 +|vgo_PaymentType                                   |Int          |For payment processing|
 +|vgo_CreatedBy                                     |nvarchar(50) |Creation information  |
 +|vgo_CreateDate                                    |DateTime     |Creation information  |
 +|vgo_CreatedById                                   |Int          |Creation information  |
 +|vgo_PostingStatus                                 |Int          |Processing control    |
 +|vgo_PostingDate                                   |DateTime     |Processing control    |
 +|vgo_PostingId                                     |Int          |Processing control    |
 +|vgo_BatchId                                       |Int          |Processing control    |
 +|                                                  |                                  |
 +
 +  - **Payment Processing** items are used by the internal payment process. These values are only populated for payment transaction.
 +  - **Creation Information** items are populated for all transactions.
 +  - **vgo_CreatedBy**: Versago user ID (email) that created the transaction.
 +  - **vgo_CreateDate**: Date and time the transaction was created.
 +  - **vgo_CreatedById**: Versago internal user ID number.
 +  - **Processing Control** items can be used to manage back-end processing using tools such as Bizweaver.
 +  - **vgo_PostingStatus**: Typically used to indicate if a record has been processed by the back-end.
 +  - **vgo_PostingDate**: Typically used to capture when a record has been processed by the back-end.
 +  - **vgo_PostingId**: Typically used to capture the ID number of the record created during back-end processing.
 +  - **vgo_BatchId**: A sequential number added by the application when a set of records is added to the database. This value can be used to process a group of records together during back-end processing.
 +
  
 ---- ----
versago3/dataview_payment.1710255652.txt.gz · Last modified: 2024/03/12 11:00 by dlee