Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Using TWBS Credit Card Processing • Introduction (ExchangeConnector)
versago:form_configuration

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
versago:form_configuration [2019/11/13 13:54]
akoehler 		versago:form_configuration [2020/07/27 11:03] (current)
dlee [User Information]
Line 239: Line 239:
 The configuration of a Dynamic DDL is more complicated than a Static DDL in that it uses a Versago report as the source for the list of values. It also allows values to be placed in other controls as needed. The configuration of a Dynamic DDL is more complicated than a Static DDL in that it uses a Versago report as the source for the list of values. It also allows values to be placed in other controls as needed.
  
-<WRAP center round info>+<WRAP center round tip>
 Even though this DDL uses a report as its source for the list of values, the list of values should be relatively short. Having too many values in a DDL makes it difficult for the user to find the value they need. Even though this DDL uses a report as its source for the list of values, the list of values should be relatively short. Having too many values in a DDL makes it difficult for the user to find the value they need.
  
-In many cases, using a Lookup report instead of a Dynamic DDL is a better approach. The Lookup report provides some functionality, such as “search”, that the Dynamic DDL does not.+In most cases, using a Lookup report instead of a Dynamic DDL is a better approach. The Lookup report provides some functionality, such as “search”, that the Dynamic DDL does not.
 </WRAP> </WRAP>
 +
 +
 +
  
  
Line 364: Line 367:
 ===== System Information as Defaults ===== ===== System Information as Defaults =====
  
-<WRAP center round info>+<WRAP center round tip>
 **Note that** **the format and case of the User Information, Date, and header-to-row commands is critical**. **Note that** **the format and case of the User Information, Date, and header-to-row commands is critical**.
 </WRAP> </WRAP>
Line 370: Line 373:
 ==== User Information ==== ==== User Information ====
  
-"UserProfile" values are related to the current user. “Id” and “UserName” are typically captured to identify which user created the record.+"UserProfile" values are related to the current user's Versago profile. “Id” and “UserName” are typically captured to identify which user created the record.
  
   * {UserProfile**.**$Id} – returns the internal user ID code (integer)   * {UserProfile**.**$Id} – returns the internal user ID code (integer)
Line 376: Line 379:
   * {UserProfile**.**$FirstName} – returns the user’s first name   * {UserProfile**.**$FirstName} – returns the user’s first name
   * {UserProfile**.**$LastName} – returns the user’s last name   * {UserProfile**.**$LastName} – returns the user’s last name
 +  * {UserProfile**.**$CopmpanyName} – returns the user’s Company name
  
 ==== Date Information ==== ==== Date Information ====
Line 399: Line 403:
 **Bizweaver** is a companion product to Versago that is used for data management and integration.  The processes that execute the work to be done are called **workflows**.  A Bizweaver workflow can be initiated using a Versago form button action. This process uses a web service (API) provided by Bizweaver. The button can either be a standard form button (Save & Close, Save & New, Save, Delete) or a custom button. **Bizweaver** is a companion product to Versago that is used for data management and integration.  The processes that execute the work to be done are called **workflows**.  A Bizweaver workflow can be initiated using a Versago form button action. This process uses a web service (API) provided by Bizweaver. The button can either be a standard form button (Save & Close, Save & New, Save, Delete) or a custom button.
  
-There are two methods available to initiate a Bizweaver workflow, **POST** and **GET**. +A Bizweaver workflow is initiated using a **POST** transaction. Information on using this method is found **//[[Invoke Bizweaver Using POST|here]]//**.
- +
-The **POST** method is introduced in v2.3.  It provides authentication for the request and is the preferred method.  Information on using this method is found **//[[Invoke Bizweaver Using POST|here]]//**. +
- +
-The **GET** method was introduced in v2.2.  It provides similar functionality to the POST method, but does not provide authentication.+
  
-<WRAP center round important 60%> +<WRAP center round important 80%> 
-Any forms using the GET method will continue to function, but changing to the POST method is strongly recommended.+Any forms that were created using the v1 Form Builder tool will need to be rebuilt using the v2 Form Builder tool in order to use the POST functionality.  v1 forms only allow use of the GET transaction, which is no longer supported.
 </WRAP> </WRAP>
  
-Information on using this method is found **//[[Invoke Bizweaver Using GET|here]]//**. 
  
 ====== Read-Only Forms ====== ====== Read-Only Forms ======
versago/form_configuration.1573671264.txt.gz · Last modified: 2019/11/13 13:54 by akoehler

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