Differences

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

--- versago3:dataview_payment [2022/09/15 09:59]
dlee created
+++ versago3:dataview_payment [2024/03/12 11:14] (current)
dlee
@@ Line 1: / Line 1: @@
 ====== Record/Payment Submission ======
-**Sub-Reports** are additional data view that typically provide additional information related to a row being displayed in the main data view. The sub-record data view is displayed within the same page as the main data view and appear directly below the selected row. Sub-records are displayed when the user clicks the expand/collapse icon at the left end of the main record.
+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.
-{{ :versago3:dv_subrecord01.png |}}
+{{ :versago3:dv_payment01.png |}}
+  * **Enable** the record submission switch to activate the page.
+  * Activate the **Payment** switch if you intend payment processing.
+  * Select **Editable Column** to allow the user to edit the value of the selected column.
+    * Typically used for payment processing to change the amount to pay.
+  * 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 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
+    * Workflow id
+    * Bizweaver Service address
+    * 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.
-  * Select the data view with the sub-records
-  * Select the (first) linking column for the parent data view
-  * Select the corresponding linking column in the child data view
-    * In some cases, there may be multiple values needed to link the child report to the parent.
 ----

Wiki

User Tools

Site Tools

Differences

Page Tools