Bxp R10SER1 - Form Management

Contents

1 Overview

This document forms part of the bxp Release 10 Service Enhancement Release 1 suite of changes found here Bxp_Release_10_SER_1_prerelease_notes

1.1 Form Management

This area covers all changes to forms and their respective supporting modules, Inbound, Outbound, Case, Quality, Testing, Survey and a new area of management Project

1.1.1 Campaign table changes

A number of fields will be added to the campaign table to facilitate the forth coming changes

Field	Reason	Link
strCampaign_Prebuild_Type	Which of the below prebuilds it is)
strCampaign_Prebuild_Ids	Related ids of forms in the prebuild)
strCampaign_Prebuild_Role	If there are multiple forms, which form in the relationship is this)
strCampaign_BEMail_MatchContact_Flag	onArrival engine	BEMail_onArrival_matching_engine
strCampaign_BEMail_MatchCompany_Flag	onArrival engine
strCampaign_BEMail_MatchOwner_Flag	onArrival engine
intCampaign_BEMail_Match_CampaignId	onArrival engine
strCampaign_BEMail_MatchContact_Field	onArrival engine
strCampaign_BEMail_MatchCompany_Field	onArrival engine
strCampaign_BEMail_MatchOwner_Field	onArrival engine
strCampaign_BEMail_MatchContact_ResultField	onArrival engine
strCampaign_BEMail_MatchCompany_ResultField	onArrival engine
strCampaign_BEMail_MatchOwner_ResultField	onArrival engine
strCampaign_BEMail_Match_ResultFlagsField	onArrival engine
strCampaign_Project_HeaderBlock	Project Header	Form_Project_Header
strCamapign_Revenue_Model	Revenue management	Form_Revenue_Header
strCamapign_Revenue_CDAConfig	Revenue management
strCamapign_Revenue_CCLConfig	Revenue management
strCamapign_Revenue_Outcomes	Revenue management
strCamapign_Revenue_MarginReport	Revenue management
strCamapign_Revenue_Prods_Values	Revenue management
strCamapign_Revenue_Price_Values	Revenue management
strCamapign_Revenue_VAT_Values	Revenue management
strCamapign_Revenue_PriceCurrency_Values	Revenue management
strCamapign_Revenue_Costs_Values	Revenue management
strCamapign_Revenue_CostCurrency_Values	Revenue management
strCamapign_Revenue_Store_CDAPriceField	Revenue management
strCamapign_Revenue_Store_CDAVATField	Revenue management
strCamapign_Revenue_Store_CDATotalField	Revenue management
strCamapign_Revenue_Store_CDACostField	Revenue management
strCamapign_Revenue_Store_CDANETMarginField	Revenue management
strCamapign_Revenue_Store_CDAGrossMarginField	Revenue management
strCamapign_Revenue_Store_CDAPriceCurrencyField	Revenue management
strCamapign_Revenue_Store_CDACostCurrencyField	Revenue management
strCamapign_Revenue_Prods_Field	Revenue management
strCampaign_BEmail_SPAM_Active	BEmail SPAM management	BEmail_SPAM_Management
strCampaign_BEmail_SPAM_Addresses	BEmail SPAM management
strCampaign_BEmail_SPAM_Keywords	BEmail SPAM management
strCampaign_BEmail_SPAM_FieldId	BEmail SPAM management
strCampaign_BEmail_SPAM_OutcomeId	BEmail SPAM management
strCampaign_Lookup_OpeningHTML	Lookup screen extra HTML field
strCampaign_IncludeMaps	Google Maps enhanced question support
strCampaign_ContentRetrieval_SuppressRules	BEmail Content Retrieval enhancement	BEmail_Content_Retrieval
strCampaign_UseViewer	Inline attachment viewer	Form_-_Attached_File_Viewer

1.1.2 Project Header

For people who’ve ever used Microsoft Project the concept of work items, tasks, milestones, etc. will be very familiar. Each entry in a record could be considered a line in a spreadsheet, or in our case a record in a form (CDA).

We’re adding a new prebuilt form header question type called Project, to allow a form to become the data storage for a MS Project style amount of data. The interface will be delivered through the Project Management module but the data stored in a form.

To this end a new header type will be made available in bxp to allow any form to become the support for a project.

For details on the header click here https://www.bxpsoftware.com/wixi/index.php/Form_Project_Header

1.1.3 Inbox - onArrival matching engine

When BEMail reads an email from an inbox it can create a CDA and log the record.

As part of this mechanism matching and preprocessing can be done on the emails. BEmail_(_Email-2-Campaign_)#Configuring_the_form_to_retrieve_the_email

This engine will be expanded to provide two new levels / approaches for matching.

1. email comes in from user@something.com, a search is done on the “Contacts” form to identify which account this belongs to

This first process means that preapproved addresses can be quickly managed and emails allocated to clients for reporting purposes.

2. That contact account is managed by Aiden. Therefore that email is meant for Aiden, so automatically display it in his worklist.

This way, though emails are coming into a general email box they can be allocated to individuals for account management.

This engine can be applied to all forms using BEMail retrospectively

1.1.4 Form Prebuilds

This engine will forms in bxp to be built very quickly based on templates. These templates are industry best practice layouts as identified by the All n One team to speed up implementations.

1.1.4.1 Prebuild – Inbox manager

Give the engine an inbox and it will construct a complete case management solution with appropriate prebuilt associated reporting. Build time currently < 0.5 of a second! More details on this will be available through the wixi

The engine will also provide the onArrival matching engine.

1.1.4.2 Prebuild – Outlook create from Contacts

A way of loading contacts from Outlook in a structured way with time saving constructs.

• Give the engine an export of your contacts from outlook.
• It will build two forms. One for contacts one for companies.
• It loads all the contacts into a predesigned and tabbed contacts form.
• It then uses identification techniques to create the companies entries.
• It can then link based on email domain and company name fields to quickly build a contacts and companies populated structure.

The engine also facilitates further loads from different people.

• So user 1, creates the first list and first companies.
• User 2, like a smart load, can add to the contents and expand the data.

Prebuild - Outlook create from Contacts

1.1.4.3 Prebuild – Excel no data

• To quickly build a form, you can select the top row of a spreadsheet.
• Copy and paste this into bxp
• The columns will be separated by the “Tab” character
• bxp will read the tabs, split the fields and then create a basic text box field for each heading and set the field mapping.
• This should allow very quick form builds and enable perfect field mapping.

1.1.4.4 Prebuild - CRM & Pipeline

This prebuild provides three forms instantly.

• Companies : contains all the companies you'll deal with.
• Contacts : contains all the contacts you'll deal with.
• Opportunities : contains all the sales opportunities you'll identify with that company.

These forms are interlinked.

• Many contacts can be associated with one company
• Many opportunities can be associated with one company
• One opportunity can be associated with one Contact

Notes

1. The Contact form also comes ready to support an Inbox form / BEmail linked form.
2. The structure of Contacts is built specifically to support the easy import of contacts from Outlook

Details can be found here Form - Prebuild - CRM & Pipeline

1.1.5 Complex – Email Block change

When a BEMail question is added you get.

The challenge is the amount of space given to the subject and body of the email. There is over 50% more space to the left of the boxes.

The suggestion is to convert this from being text areas to being text wide boxes which would use the width of the screen and make it easier to read the body of received emails.

This is a layout change rather than a data change, so should only cosmetically affect clients. i.e. JavaScript will not be affected

1.1.6 Outbound Data Drill down

Currently the “Set the Current Working Outcome” engine allows a number to be displayed to allow the user set which group of records are being worked on.

An option on the screen in the form of a drop down list, will allow by default (“Set the stack”) and a new option “View Data”. This view stack when clicked will open in a new tab a report showing the records that are in that stack, using the default fields of the search engine, as per the lookup screen. The user must have access to Data Profiling > Instant - Data to see this option.

Upon click those records, they can then be opening in Inbound way (i.e. no taking the record off the stack), to allow an admin review the contents of the records. Or they can be visualised in an Instant Visualsation report for just those records.

1.1.7 Data Import timer

Main Menu > Form Management > Form - Data Import > Load Data Records – Retrieve Email 2 – Form (affects anyone using the bemail retrieval to form engine)

Currently if you select this page, it goes Form Selection > Results. There is no landing / timing page. This change will put a landing page before the downloads begin with a stop watch on it.

Main reasons for this change:

• to provide timing feedback on loading
• to provide better feedback to users that loading is going on
• to provide explanation and troubleshooting wixi links to users more appropriately (i.e. if troubleshooting then the loading page never appeared, how did a user see the links to help themselves?)

1.1.8 Revenue Header and associated capability

1.1.8.1 Revenue Header CCL changes

This engine allows for the previously conceived "Campaign Accounts" module to be implemented. Within the CCL are a number of fields to allow for an amount to be logged.

• strCCL_[i]_Amount_Price decimal (9,4)
• strCCL_[i]_Amount_VAT decimal (9,4)
• strCCL_[i]_Amount_Total decimal (9,4)

5 new fields are being added to every CCL

• strCCL_[i]_Amount_VATPC text
• strCCL_[i]_Amount_Cost decimal (9,4)
• strCCL_[i]_Amount_NetMargin decimal (9,4)
• strCCL_[i]_Amount_GrossMargin decimal (9,4)
• strCCL_[i]_Amount_CurrencyPrice varchar(3)
• strCCL_[i]_Amount_CurrencyCost varchar(3)

1.1.8.2 Revenue Header complex question type

Also being added to the engine will be a complex type called Revenue Header (these are all hidden fields on the form)

• Price
• VAT
• Total
• VATPC
• Cost
• NetMargin
• GrossMargin
• Price Currency
• Cost Currency

The full article will be available from Form_Revenue_Header

1.1.8.3 Revenue Header form settings

There are then form level settings which allow the engine to be used.

Field	Type	Use	Options
strCamapign_Revenue_Model	text	Where is the calculate stored	None,CDA,CCL,Both
strCamapign_Revenue_CDAConfig	text	For CDAs, what happens if already filled in	Replace (CDA recalculate),Ignore (CDA if filled do nothing)
strCamapign_Revenue_CCLConfig	text	What if other CCL has data	One Only (CCL Historic check),Update (CCL Historic wipe),All (CCL new)
strCamapign_Revenue_Outcomes	text	String separated commas on which the process executes
strCamapign_Revenue_MarginReport	text	Reporting Marings, which fields to use	None,Net,Gross,Both
strCamapign_Revenue_Prods_Field	text	Which field contains the product	All CDA fields
strCamapign_Revenue_Prods_Values	text	Top has to be filled out (text or list), Only consider SOME products in the field
strCamapign_Revenue_Price_Values	text	If only using SOME then, count must match. If using field then leave it to JavaScript on the page to manage
strCamapign_Revenue_VAT_Values	text	These are all percentages without the symbols.
strCamapign_Revenue_PriceCurrency_Values	text	Three letter text codes	Default to system currency of EUR to start
strCamapign_Revenue_Costs_Values	text	A straight one off price per cost
strCamapign_Revenue_CostCurrency_Values	text	Again three letter text codes.
strCamapign_Revenue_Store_CDAPriceField	text	Once the calculations are done, an update to the CDA table can be done, what to store where. Great for testing and if using the header type, then all hidden.
strCamapign_Revenue_Store_CDAVATField	text
strCamapign_Revenue_Store_CDATotalField	text
strCamapign_Revenue_Store_CDAVATPCField	text
strCamapign_Revenue_Store_CDACostField	text
strCamapign_Revenue_Store_CDANETMarginField	text
strCamapign_Revenue_Store_CDAGrossMarginField	text
strCamapign_Revenue_Store_CDAPriceCurrencyField	text
strCamapign_Revenue_Store_CDACostCurrencyField	text

1.1.9 Form - Advanced Settings

As the tabbing engine of bxp is applied system wide, there are a number of enhancements to the Advanced Settings of a form. Apart from just the tabbing a bit of tidying and sorting was done to make things more logically grouped and easier to find.

Was	Becomes

Notes

Tab	Reason
Access Tab	New tab added for security based access options
Access Tab	"Active" moved in
Access Tab	"From" and "Until" moved in
Access Tab	The two general access security questions "Cross User Lookup" and "Use Outcome Security" also moved in
Search Tab	New tab added for security of navigation around data
Search Tab	"Record Move Next Bar" moved in
Search Tab	"Enable Search Export" moved in
Search Tab	"Search Screen Export Fields" moved in
Search Tab	"Precision Search Fields" moved in
Advanced Options Tab	Just items moved out into other tabs
Dashboard Tab	Changed name from Dashboard and Reporting
Dashboard Tab	Moved in "Dashboard - Contact Source", previously from Advanced.
Inbox - Management	name changed and items moved out
Inbox - Storage	Groups all the data fields where emails are logged into
Inbox - Content	handles all the in data finding and replacing from an email
Inbox - onArrival	The new engine fields for record identification and auto assignment
JavaScript - Options	Items removed from onLoad as they're config options not for onLoad
bxp API XML Arrival Management	"BEAPI API XML Arrival Management" name need to be upgraded appropriately
bxp API XML File Options	"BEAPI XML and Excel AutoLoad File Options" name need to be upgraded appropriately
bxp API XML Processing Options	"BEAPI XML and Excel AutoLoad Processing Options" name need to be upgraded appropriately
Revenue Engine	New revenue engine options added.

1.1.10 Question Add enhancement

When new questions were added to a form their initial Field Mapping was defaulted to "New". For larger complex types this represented a challenge.

The system will now attempt to correctly name complex types with default names to make identifying fields easier.

This may lead to fields with duplicate names after addition but the same was true with the use of "New" as a field name so the benefits were considered to outweigh the challenges.

Section Group and Section Headers will include the Question in their title as well for convenience.

Simple types will become "New - Question Type" where Question Type represents the type of question added. Again this should improve identifying new items quickly added.

1.1.11 Lookup setting additions

On the lookup screen for a form it is now possible to put in a custom header. In the Advanced Settings for the form in the "Instructions" section a new field at the bottom entitled "Lookup Instructions" allows you to inject HTML or any other material directly into the Lookup page.

The logic of the lookup page has also been adjusted. In JavaScript - onLoad section the field "Lookup code execution" allows you to enter any JavaScript. This has not changed. By default the Lookup page automatically added a .focus() command to move the cursor to the Id field. Now the engine will examine your JavaScript code. if anywhere in it has a .focus() command, the system will not add the default .focus command assuming you are setting the .focus() manually.

1.1.12 Inbox - Content Retrieval engine tweaks

bxp now provides a testing engine which allows you to play with the rules on email data that’s already been loaded into a form. If you add a new rule, you can also retrospectively apply the rule to existing records. BEmail_Content_Retrieval_Rules_Testing

There is a suppression engine which means if no match is found then no update happens for that field. Making queries faster but also allowing more complicated rules set ups. In Advanced Settings > Inbox - Content > Content Retrieval - Suppress Blanks

The match pattern for vbCrLf has been expanded so the rule can have leading or trailing spaces. This allows for far more complicated patterns to be built.

The Content rules in Advanced Settings have been renamed to make them clearer and easier to follow. The wixi articles all now cross link with each other for the Inbox rules management.

1.1.13 Precision Searching in Forms

It was discovered that the intCDA_X_Id and the intCDA_X_NoOfAttempts fields were not being precision searched and need to be. The code of the system was modified to support this precision searching without the need for explicit addition into the Advanced Settings of each form.

1.2 AJAX engine - Title when no records

Currently the text displays

This will be changed to "No records found."

1.3 Outcome - Communications - Send to Security Group

The power of an outcome is that it can send to large groups via the External Communication of Intra Communication engines.

When there are large groups of users to receive an email and that group changes often this can result in a lot of changes to outcomes.

The easier solution is to use a Security Group. Form_-_Communications_-_To_Security_Groups

1.4 Inline attachment viewer

When a document is uploaded to the contact history of a record it is available to view as required. The default position of the system is to allow you to download this document and review at your leisure.

For security reasons it can become difficult to manage a users "Download" folder on their machine. it may be more desirable to just view the document and for the data to be in the browser's cache rather than in the Downloads folder.

For this reason the "Attached File Viewer" was added as an option to a form. Form_-_Attached_File_Viewer