[[File:advanced_settings_001.png|800px]]
== Basic Details ==
* Type : [[Bxp_Form_Types]]= Sections =
* Name : This is your name for the form
* Available From : The date and time when users will be able to interact with the form * Available Until : The date and time when users will no longer be able to interact with the form== Basic Details ==
== Advanced Options ==
{| class="wikitable"
! Heading
! Description
! Link
|-
| Type || || [[Bxp_Form_Types]]
|-
| Name || This is your name for the form ||
|-
|}
* Active : This is a simple true / false to allow users to interact with the form. False overrides the date options above.
* External Reference Code : When interacting with a phone system this field allows a form to respond to something different than the Id or Name of the form. In code is referred to as the campaign_code [[Scenario_-_bxp_Integration_with_a_Phone_System]]
* Contact History - Sort Order : The is the sort order of how the contacts are presented in the Contact History window.== Access ==
* Public Outcome : When the form is used in a public way an outcome is automatically applied. This is the default outcome applied to public form record logging.
* Externally {| class="wikitable"! Heading! Description! Link|-| Active || This is a simple true / false to allow users to interact with the form. False overrides the date options above. || |-| Available : When From || The date and time when users will be able to interact with the form || |-| Available Until || The date and time when users will no longer be able to interact with the form is || |-| Cross User Lookup || When set to be made accessible through True, a user can only interact with a record IF the bxp_API this value CDA_StaffId is that of the user, or the user has an entry in the Contact History. Within Inbound Contact "My Data - Admin View", allows you to be set to Publicoverride this limitation. || |-| Use Outcome security || Outcome Security is turned on (true) or off (false) || [[bxp_APIForm_-_Outcome_Access]] By default all forms are Private.|-|}
* Use Outcome security : Outcome Security is turned on (true) or off (false) [[Form_-_Outcome_Access]]
* Cross User Lookup : When set to True, a user can only interact with a record IF the CDA_StaffId is that of the user, or the user has an entry in the Contact History. Within Inbound Contact "My Data - Admin View", allows you to override this limitation.== Search ==
* Record Move Next Bar : This adds a bar at the top of the screen to allow easy navigation of records. This is ideal for testing but not suitable for most live production forms.
* Enable Offline Usage : {| class="wikitable"! Heading! Description! Link|-| Record Move Next Bar || This option allows adds a form bar at the top of the screen to create an RSA encrypted snapshot allow easy navigation of records. This is ideal for testing but not suitable for most live production forms. || |-| Enable Search Export || Allows for search results page to be exported to a xls file || |-| Search Screen Export Fields || Alternate fields to be used in the data within the formsearch export. Fields seperated by ,'s || |-| Precision Search Fields || For more info [[Using_Forms_Offline]]effective searching boolean matching can be employed. Listing the fields here, force boolean matching and can greatly speed up queries. || |-|}
* Page Header Replacement : Can be used to put extra header HTML data directly into the script.
* Keyword Replacement : Allows engine keywords to be replaced as needed.
* Report - All Campaigns Fields : When cross campaign listings are employed, this allows the custom fields to be chosen.== Advanced Options ==
* In-Module Reporting Fields : The columns displayed in the My and Team report data reports.
* {| class="wikitable"! Heading! Description! Link|-| Enable Integrated Warehousing || Integrated Warehousing actives automatically but can be manually activated. || |-| Use Workflow || || [[Outcome_-_Workflow]]| Contact History - Sort Order || The is the sort order of how the contacts are presented in the Contact History window. || |-| Page Header Replacement || Can be used to put extra header HTML data directly into the script. || |-| Keyword Replacement || Allows engine keywords to be replaced as needed. || |-| Report - All Campaigns Fields || When cross campaign listings are employed, this allows the custom fields to be chosen. || |-| In-Module Reporting Fields || The columns displayed in the My and Team report data reports. || |-| CCL Column Replacements : || When generating the reporting, the CCL column names can be replaced.|| |-|}
* Precision Search Fields : For more effective searching boolean matching can be employed. Listing the fields here, force boolean matching and can greatly speed up queries.
* Enable Integrated Warehousing : Integrated Warehousing actives automatically but can be manually activated.
* Dashboard - Contact Source : When using the Dashboard - Contact Source report, this field is the report that is reported against.
== Case Management ==
* {| class="wikitable"! Heading! Description! Link|-| Exception : Track Reopen|| || |-| Exception : Time || || |-| Exception : Contacts || || |-| Service Level Agreement || || |-|}
* Exception : Time
* Exception : Contacts
* Service Level Agreement== Communications ==
{| class="wikitable"
! Heading
! Description
! Link
|-
| Email From || ||
|-
| SMS From || ||
|-
|}
== Communications ==
* Email From== Dashboard Defaults ==
* SMS From
{| class="wikitable"
! Heading
! Description
! Link
|-
| Dashboard - Contact Source || When using the Dashboard - Contact Source report, this field is the report that is reported against. ||
|-
| Working Days || ||
|-
| Working Hours - Start || ||
|-
| Working Hours - End || ||
|-
| Non Working Days || ||
|-
| Sales Outcomes || ||
|-
|}
== Dashboard and Reporting Defaults ==
== eCourse Prerequisites ==
* Working Days
* Working Hours {| class="wikitable"! Heading! Description! Link|- Start| eCourse Prerequisites enabled || User Must complete an eCourse or a number of eCourse before accessing the form || |-| eCourse Book Id || eCourse Book Id's seperated by a , || |-|}
* Working Hours - End
* Non Working Days
* Sales Outcomes== Dimensions ==
{| class="wikitable"
! Heading
! Description
! Link
|-
| Table || ||
|-
| Info Button || ||
|-
| Question || ||
|-
| Lookup Button || ||
|-
| Item || ||
|-
| Weighting || ||
|-
| Max Weighting || ||
|-
| Row Height || ||
|-
|}
== Dimensions ==
* Table== External ==
* Info Button
* Question{| class="wikitable"! Heading! Description! Link|-| Externally Available || When the form is to be made accessible through the bxp_API this value is to be set to Public. [[bxp_API]] By default all forms are Private. |||-| Public Outcome || When the form is used in a public way an outcome is automatically applied. This is the default outcome applied to public form record logging. || |-| Enable Offline Usage || This option allows a form to create an RSA encrypted snapshot of the data within the form. For more info || [[Using_Forms_Offline]]|-| Allow External CCL file download || Allow external download of CCL files || |-|}
* Lookup Button
* Item
* Weighting== Inbox - Management ==
* Max Weighting
* Row Height{| class="wikitable"! Heading! Description! Link|-| BEmail Account || The mailbox to log into || |-| Attachments as CCLs || True means attachments will be stored in the CCL history || |-| Notify on Receipt || When an email is loaded into the system, should an email be sent? || |-| Process as Outcome || What outcome should each email be processed as? || |-| Scheduling Enabled || Auto retrieve emails periodically which is managed by bxp || |- | Scheduling Refresh Rate || The rate to check for new mails. || |-|}
== Inbox Management - Storage ==
* BEmail Account{| class="wikitable"! Heading! Description! Link|-| DateTime field || || |-| From field || || |-| To field || || |-| CC field || || |-| Subject field || || |-| Body Field || || |-|}
* DateTime field
* From field
* To field== Inbox - Content ==
* CC field
* Subject {| class="wikitable"! Heading! Description! Link|-| Attempt matching? || True will attempt to append to an existing record on a pattern || |-| Field to match on || Which fieldcontains the code to match on || |-| Match pattern || What pattern is used for matching on? eg ###--ID--# || |-| Content retrieval || || [[BEmail_Content_Retrieval]]|-| Content replacement || || [[BEmail_Content_Replacement]]|-|}
* Body Field
* Attachments as CCLs
* Notify on Receipt== Inbox - SPAM ==
* Process as Outcome
* Attempt matching?{| class="wikitable"! Heading! Description! Link|-|-|}
* Field to match on
* Match pattern
* Content retrieval== Inbox - onArrival ==
* Content replacement
{| class="wikitable"
! Heading
! Description
! Link
|-
|-
|}
