Philip Lacey at 14:51, 6 February 2018

2018-02-06T14:51:56Z

Philip Lacey: Created page with "= Overview = Public forms allow data entry into bxp without the need to log into bxp or grant security access to a form. Public forms have one set outcome and have no user..."

2018-02-06T14:49:36Z

Created page with "= Overview = Public forms allow data entry into bxp without the need to log into bxp or grant security access to a form. Public forms have one set outcome and have no user..."

New page

= Overview =

Public forms allow data entry into bxp without the need to log into bxp or grant security access to a form. Public forms have one set outcome and have no user tracking for the first entry made. Once the record is in the form all management and tracking is available as normal.

Every entry in a form is a unique record.

= Public Forms =

There are two locations for Public forms, where XXX is the name of your system

* Internal : https://ww3.allnone.ie/client/client_XXX/main/userForms.asp
* External : https://ww3.allnone.ie/client/client_XXX/cti/userPublic_Forms.asp

The internal one requires you to be logged into bxp but '''does not''' require you to have access to the form. This process uses the currently logged in users credentials to work out what user to log the initial record under.

If you use the CTI version it requires an API user account to be set up, configured and the credentials supplied to the form so that it knows which user account to use.

== Internal ==

A drop down list allows a simple listing of all forms potentially available to the user to fill in. This makes for simple supply of company standard forms without the need to provide access to all of the forms.

Examples of useful forms include:
* Fire risk log
* Health and safety risk log
* Competition / business feedback form
* Helpdesk / request form

== External ==

A bxp API user account needs to be created. A description of the process starts here [[Form_External_Options]]

The major steps are:
* Create the user with no functional access at all
* Ensure that the user's external API details are set
* Grant the user access to the form that will be public
* Set the External Outcome to allow proper recording / process management as a record arrives.

The page is expecting to recieve the following fields of information
* query : will have the value from the lsit forms ~ body ~ store.
** Forms provides an xml listing
** Body provides the form in an externally useable format
** Store will draw the form to screen

* campaignid : the Id of the form
* user_id : the bxp api user id
* user_key : the bxp api user key
* alt_url : when the record stores where would you like the system to bounce you

= Customisation of the form =

Each form is managed the same as a form inside bxp is managed.

If the form receives information in the form of QueryString parameters, the userForms.asp page will dynamically change to provide slightly different experiences.

= Making a form public =

To make a form public, it requires a Form setting to be changed. ''Main Menu > Form Management > Form - Advanced Settings > Choose the form > External >''

* Set "Externally Available" to "Public"
* Choose the Outcome to be processed when the form is filled in in "Public Outcome"

[[Category:Module Specific:Form Management]]
[[Category:Topic:bxp API]]

@@ Line 64: / Line 64: @@
 = Customisation of the form =
@@ Line 75: / Line 77: @@
-= Making a form public =
+== Making a form public ==
@@ Line 82: / Line 84: @@
 * Set "Externally Available" to "Public"
 * Choose the Outcome to be processed when the form is filled in in "Public Outcome"
 [[Category:Module Specific:Form Management]]
 [[Category:Topic:bxp API]]

Form - Public Forms - Revision history

Philip Lacey at 14:51, 6 February 2018

Philip Lacey: Created page with "= Overview = Public forms allow data entry into bxp without the need to log into bxp or grant security access to a form. Public forms have one set outcome and have no user..."