bxp Release 10 Service Enhancement Release 1 has no set date for release yet. Cooperation and collaboration with clients is currently in progress.

1 Existing Module Changes

1.1 Appointment Manager

1.1.1 Interface

bxp has two different interfaces for dealing with the Appointment Manager engine. Appointment_Management_-_Interface

The first is a pure HTML backwards compliant engine.
The second is the open source fullcaldendar.io engine https://fullcalendar.io/

FullCalendar.io has a more limited support base. https://fullcalendar.io/support/

The bxp engine is going to embrace further the fullcalendar.io engine but provide a selectable option to allow clients revert to the pure HTML version if their browsers are incompatible.

This option will be selectable on the Diary Add / Edit screens

The calendar version has been upgraded from the previous 2.3.1 to 3.4.0

The scheduler engine is not included in the release but is under review.

1.1.2 Linking facility

A facility to add a form record, eCourse reference and a Meeting Manager reference will be included in the data structures.

The linking options will be enabled at a Diary Add / Edit level using the Features field. Appointment_Management_-_Features

1.1.3 Filtering

The interfaces will be provided with a filtering engine which will allow filtering by

Person
Category
Duration
Subject keyword
Body keyword
Form link
eCourse link
Meeting Manager link

The filtering bar will be an option configured at the Diary Add / Edit level.

The filtering will also be available as a data report listing type, as well as the interactive calendar view.

1.1.4 Appointment API

A dedicated API will be developed to facilitate add, edit, delete and listing of events.

Responses will be provide in XML and / or JSON depending on FullCalendar.io’s compatibility requirements.

1.1.5 Data listing method

The current approach for the diary system using FullCalendar.io is a listing for a 6 month historical and 6 month advance listing of events. Outside this window the data doesn’t list.

With the addition of the API, this will allow event data to be loaded in real time, making the window of reportable events universal.

1.1.6 “Drag to edit” facility

FullCalendar.io supports drag and drop editing. This facility will be enabled by Diary Add / Edit option and also limited by QueryString capability.

1.1.7 “Email on edit” facility

This change will allow an email to be sent automatically those associated with the event. This facility will be based on Category.

1.2 Communications Centre

1.2.1 Attachments

The bxp email engine is to be expanded to facilitate the sending of attachments with emails. This change will require file management capabilities to be added to the module.

The primary attachments will allow files from the Report Library module to be added to the emails. Delivery rates will be reduced but the facility is sought by numerous clients.

This facility will also provide the basis for outcomes in a form being able to attach documents directly.

1.2.2 Communications Report enhancement

The current communications reports include a total amount of communications based on the total recipients. If a wrong data source field is chosen by mistake no communications are made but the report identifies that X attempts were made. The reports will be modified to list both values, obvious blank / incorrect data counts and attempted recipient counts.

Using an SMS example : Whilst not validation can be provided on “looks kinda right data”... no values or text in values will result in that attempt not being counted.

1.2.3 Mail Merge issues

The engine of bxp had a direct integrated link with Word. Create.Object(“Word.Application”)

This used Microsoft Office XP which is no longer supported by Microsoft. As a result the engine has been disabled for security reasons.

An alternate using RTF is being investigated and applied and will be available in this release.

1.3 eCourse

1.3.1 New Table of Contents layout options

The table of contents will be given the option for new styles and approaches. These options are set at a Book level.

1.3.1.1 TOC’less.

This approach is for short training courses where it is linear in nature.  The pages will be provided with a dot bar system, each dot representing a page.  The system will provide a next previous button set as well.  This is for getting straight into training.  When the user selects the book, they are taken straight to the first page of material of the book, or the last page viewed if the book has been read before.

1.3.1.2 The Moodle’esqe view.

This is a university based, drag and drop type interface where material is secondary to the layout. i.e. links to word docs, PowerPoint is more the focus than the presentation of them.

1.3.1.3 The styled table of contents.

As page can be styled, so the ToC can be styled using an asset and key repeating tags within the code.

header
chapters
pages
stoppointtest
supportpointtest
footer

<div class="css_eCourse_Chapter" id="eCourse_Chapter_X">--eCourse_Chapter_Title--<div>
<div class="css_eCourse_Page" id="eCourse_Page_X">--eCourse_Chapter_Page--<div>
<div class="css_eCouurse_StopPointTest" id="eCourse_Chapter_Stop_X">--eCourse_Chapter_Stop--<div>
<div class="css_eCouurse_SupportPointTest" id="eCourse_Chapter_Support_X">--eCourse_Chapter_Support--<div>

These four views (including the original) should provide exciting new options for presentation of courses.

1.4 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.4.1 Campaign table changes

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

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)

1.4.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.4.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.4.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.4.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.4.4.2 Prebuild – Outlook contacts exports

Give the engine an export of your contacts from outlook and 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.

1.4.4.3 Prebuild – Contacts from emails

Using outlook, export all the emails to a data file. Outlook > File menu > Options > Advanced > Export > Export to a file > Choose Excel > Choose what you want to export > Save the file on your desktop

The output is a file with the following headings

Subject
Body
FromName
FromAddress
FromType
ToName
ToAddress
ToType
CCName
CCAddress
CCType
BCCName
BCCAddress
BCCType
BillingInformation
Categories
Importance
Mileage
Sensitivity

These can be loaded into a form. bxp instead can use the FromName, FromAddress, ToName, ToAddress, CCName and CCAddress. From these it attempts to extract unique contacts. It then attempts to tidy up the data and store those contacts in a form. In this way previous emails from an outlook folder can be quickly processed into a useable contact list for marketing and other related interactions.

Using the smart update engine the form can allow for multiple uploads.

1.4.4.4 Prebuild – SalesForce data

When loading data from SalesForce there are a number of fields and sources of data. Exporting from SalesForce is easy and provides a number of templated files.

Not all of these files are used. It depends on how you use your SalesForce account. In size however the most common used files (ones with the most data ) are usually.

By uploading key files into bxp and specifying a number of parameters, bxp can auto-build a number of structures, link the data and import the data from SalesForce. The data is then bxp forms and can be used and manipulated as per system requirements.

Account = company
Contact = contacts (link contacts to companies)
Opportunity = sales opportunity (link to account)
Notes = attached to account (loaded as ccls or as separate form)
Task = attacked to account (loaded as ccls or as a separate form)
User = System Access Management mapping to bxp users (the Client table field will contain their SalesForceId)

1.4.4.5 Prebuild – ISO27001 SOA

This build is to allow the “Statement of Applicability”, a key requirement of bxp to be almost instantly built in bxp. The form will store documents and updates, whilst a prebuilt keystat provides the headings and numbering system to deliver the requirements of the standard.

This form and keystat can then be easily modified, if needed, to the requirements of the business.

1.4.4.6 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.4.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.4.6 Cross Linked report repair

This is identified as a bug that the reports are not working as posted in the Wixi. This will be fixed for the release.

1.4.7 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 stack”. 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. 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.

1.4.8 Create template from form

This engine will construct a blank Excel template of a form using the field mapping fields, which will match perfectly, for data to be filled into them. This should allow mass copying of data into an Excel sheet which will perfectly match and load easily into bxp.

1.4.9 Word to form fix

Identified as not working with some outputs, a number of fixes are going to be applied to the creation of a form using the text based data input process. These are fixes based off hamsters and reported incorrect logical outputs.

1.4.10 Access on Pass

This is an outcome extension that allows security permissions, specifically a UAM function and content security permissions application can occur on successful passing of an exam.

A reporting showing the linking is also to be developed, to make management easier.

This process means that career pathing is easier to implement.

1.4.11 Outcome Exception Cost

This processing engine will allow exception costs to be added by the outcome rather than through AJAX.

Exception costs are discussed in Projects section

1.4.12 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.4.13 Record deletion audit log fix

Currently grouped record deletion requires a reason to be provided. It has been highlighted that these reasons are not instantly available to users to review. This fix will see the comments and the record Ids being properly logged into the system audit trail for review through System Access Management.

1.4.14 Data Profiling - Instant Data Analysis

A new report and search tool will be available through Main Menu > Data Profiling > Instant – Data > Data – Instant Data Analytics with the ability to export the data results to Excel or Instantly Visualise the data.

For more information please read Data_-_Instant_Data_Analysis

1.5 Information Centre

1.5.1 Scrolling Information Centre

The current information centre for backwards compatibility does not scroll.

This configurable option will be enabled to allow a system setting to choose whether scrolling or not is employed.

Browser detection will also be employed so if the scroller is turned on, but the browser doesn’t support it, the info centre will be static.

1.5.2 Access by Security Groups

Currently the limiting security engine for messages is based off access to forms. This engine is to be changed to use Security Groups from the Organogram instead.

For historical messages, the security will be maintained but going forward Security Groups will only be available.

For limited access user sends, the user can only send to security groups they are in.

1.6 KeyStats

1.6.1 Console

The security and administration of KeyStats needs some addressing to optimise build and support functions.

A KeyStats console will be made available.

1.6.2 Mass Edit Security

The mass editing security feature needs to be developed.

This will be included as a function stand alone and as part of the console.

1.6.3 Hide Tabs

The tabs will be modified to have Ids. The KeyStat itself will have a flag to show / don’t show the tabs. By default “show tabs” will be selected.

1.7 MetaData

1.7.1 Console

This console will facilitate easier management of metadata rules and their associated security and reporting.

1.8 Project Manager

1.8.1 Gantt Chart interface

FusionCharts supplies a Gantt chart as part of their reporting suite. http://www.fusioncharts.com/dev/gauge-and-widgets-guide/gantt-chart/introduction.html

bxp will use the Gantt chart tool to render the Gantt with the data being stored in a form.

A link field will be provided to link the Form to the Project.

The bxp form will need a Project Header block, as discussed in the Form Management section. https://www.bxpsoftware.com/wixi/index.php/Form_Project_Header

1.8.2 Project API

This engine will allow tasks, milestones and other data to be add, edit, delete and listed for any given project.

1.8.3 Costing

The time tracker engine is being expanded to support the application of costs against the various units logged.

The solution will allow three primary data additions to be done per time tracker entry.

Unit cost
Sales price
Margin

The billable flag will also be used for tracking sales price. The engine will also accommodate confirmation / approval, to sense check numbers before reporting.

The costing will allow group to specific unit cost application. Costs for

By Time Unit (1 hour, 30 mins, etc)
By Project (Different rates per unit by project are possible)
By Day (By day allows weekend and bank holiday rates to be applied)
By Work Type (allows different rates by different activities)
By Staff (allows the rates to be different by resource used)

1.8.4 Scheduling

The output of the scheduling engine will manifest that the hours in Time Tracker will be prefilled with a user having the ability to edit as their day progresses.

Actual scheduling will be done by a new module called Scheduler and the interaction of the output will be supported by Time Tracker.

1.8.5 Exception Costs and API

A log engine will be provide that exceptional costs for a project can be logged. The fields will be

intExceptionCost_Id
intExceptionCost_ProjectId
strExceptionCost_Type
intExceptionCost_FromCampaignId
intExceptionCost_FromCDAId
intExceptionCost_FromCCLId
strExceptionCost_Title
strExceptionCost_Details
strExceptionCost_FileLink
strExceptionCost_FutureCost_YesNo
fltExceptionCost_Cost_AmountExVAT
fltExceptionCost_Cost_AmountIncVAT
strExceptionCost_Cost_VATCode
fltExceptionCost_Billable_AmountExVAT
fltExceptionCost_Billable_AmountIncVAT
strExceptionCost_Billable_VATCode
dteExceptionCost_DateTime
intExceptionCost_LoggedBy
strExceptionCost_Approved_YesNo
dteExceptionCost_Approved_DateTime
intExceptionCost_Approved_LoggedBy
strExceptionCost_Paid_YesNo
dteExceptionCost_Paid_DateTime
intExceptionCost_Paid_LoggedBy
strExceptionCost_Paid_Reference
strExceptionCost_Billed_YesNo
dteExceptionCost_Billed_DateTime
intExceptionCost_Billed_LoggedBy
strExceptionCost_Billed_Reference

Exception costs allow a form to log a survey complete, or a mystery shop complete directly to a project. This logging means one of purchases or logs can be directly associated with a project for billing purposes.

This engine will also include an API to allow add, edit, delete and list capabilities. This will be delivered through AJAX.

1.8.6 Project Costs report

The project costs report will have 4 sections and delivered by time period

There will be options on the two preceding options selection pages.

Page 1: Time period and project
Page 2: Section selection and include costing reporting information

The report itself will be in 6 sections

Section 1: Project overview
Section 2: Tasks by period
Section 3: Time Tracker report
Section 4: Expenses report (mileage and subsistence report)
Section 5: PO report (for large preapproved purchases)
Section 6: Exception costs report

The report will have security to those with project access only. The report generation will be logged in the System Audit log for security reasons.

1.8.7 Project profile

This report is a text and listing based report to output the contents of a task and details for the project and provide summative amounts rather than detailed breakdowns.

This report will begin as an onscreen and with client feedback be transition into an RTF / PDF output format. Client feedback required after initial build.

1.8.8 Project Management console

Given the extensive module options and selection choices a project console will be developed to put all the project management tools in a single interface for easy user management of the options and navigating the modules.

1.8.9 User by project profile

This will facilitate a by user profile report which allows expenses and owed charges by project to be reported on by user.

1.9 System Access Management

1.9.1 User tabs

Given the length of the user setup screens a more effective interface screen is being designed.

Borrowing from the tabs capability of forms the interface will look follow this format.

The tab bar will contain the sections currently available but only show the fields when that tab is clicked

The Module title and counts bar will use module icons (with name and count of ticks on hover over) Then upon clicking the module, the sections for the module appear for selection.

The module access tick box (overall access to the module) will be removed in favour of intelligent access if you have access to 1 or more sections in the module.

1.9.2 UAM “function” support engine

Since the launch of UAM it’s speed, accuracy and popularity amongst clients and security specialists has shown that a UAM approach is far more effective for administrators to manage a business. https://www.bxpsoftware.com/wixi/index.php/UAM_-_User_Access_Management

A system setting flagging “Using UAM” will be added to system settings.

When turned on in a system, add and edit a user will only provide a list of UAM buttons. The buttons will self-generate based on accounts flagged as templates.

UAM template users will have flags available allowing them to be easily managed, using the new enhanced layout above.

Any modifications of the UAM accounts will be logged in the audit trails.

The user management console will be moved to prominently appear in the user administration section of SAM.

Each user account if based on a UAM will now have a flag listing on which UAM template user account it is based. This will help reporting and group user updates.

1.9.3 UAM and SAM wixis

After all these changes a significant amount of wixi material will need to be updated to reflect the new user interfaces.

This documentation will see a gap between go live and testing where documentation may exist on the wixi before the functionality is in place.

1.9.4 Password blacklist engine

This facility will allow clients and the bxp administration team to apply a list of weak known hack attempted passwords which may validate as strong. These password combinations are designed to reduce risk of security break-ins even if the password strength is flagged as strong.

A global list will be maintained by All n One, with clients able to control their own lists from inside System Settings.

1.9.5 Client table alterations

The client table will have a number of fields added to support numerous new functions

strClient_SalesForceId to allow mapping to SalesForce data
strClient_UAMTitle to allow reporting and grouping of UAM permissions
strClient_IsUAM to flag account is a UAM template
strClient_LimitTimeTrackerCosting to influence Time Tracker option display on day view.
strClient_Retired_LastDateTime to make retired reporting easier
strClient_Retired_LastByWhom to make retired reporting easier

1.9.6 Security - Retired date time

Whilst this information is available through the audit logs it is not easily reported upon.

When was a user retired?
Who retired the user?

There will be the addition of two summary data fields to the Client table

strClient_Retired_LastDateTime
strClient_Retired_LastByWhom

The reason they have last is that the information will only be the last time an account was retired. So if it was retired multiple times, this field will only hold the last data. This also compensates for the fact that logs are only held for 6 months.

So if you go over the 6 months without manually backing up the logs the information is no longer auditable.

So the fields will be added for future record changes only
The columns of information will be made available in the retired functions search abilities
A dedicated report in SAM will be provided to allow reporting on these fields.

The fields if a user is already retired will be initialised to.

Last Date Time will be the date that the field is implemented
By Whom will be associated with the Admin istrator account.

1.9.7 System Settings - Tabbed view

To reduce space on screen for very long screens with lots of settings, tabs, as used in KeyStats are being implemented system wide. The layout will change for the System Settings page with all the same sections and fields just tabbed.

A new filed for "Table Styling" discussed later will be made available on this screen.

1.9.8 System Keywords - Tabbed view

To reduce space on screen for very long screens with lots of settings, tabs, as used in KeyStats are being implemented system wide.

The layout will change for the System Keywords page with all the same sections and fields just tabbed.

There are no new fields on this page.

1.10 Time Tracker

1.10.1 Confirmation Engine

A number of extensions are being added to the time tracker module.

One of these is, by project, if hours have to be confirmed by a manager. This allows a safety check before billable hours are applied to clients.

Mass confirmation ability will be part of this engine.

Confirmation can be applied on a project by project basis.

1.10.2 Limit project and work type by Costing

This engine will add intelligence by user, to only allow users to log data for projects they have access to AND where they have had pricing set up for them against the activity.

This allows greater control of project by work type by billing control for reporting purposes.

This setting will be centrally controlled in Project. There will be a flag by user to allow specific user only limitation.

2 New Modules

2.1 Dashboards

The Dashboards module allows for prebuilt, predesigned panes of information to be collated into a single operational dashboard.

A user can have access to multiple dashboards. Module_-_Dashboards

A number of predesigned dashboards will be launched with the module.

2.2 Expenses Management

The Expenses module in bxp jargon is the logging of costs incurred as part of the delivery or a project. An expense is logged to an individual and requires that individual to be reimbursed by the business.

Expenses are associated with a project.

Expense items include entries such as mileage, subsistence and operational day to day costs of smaller one off purchases for the business.

Expenses will also support an administrator approval engine

Module_-_Expenses_Management

2.3 PO Module

The Purchase Order (PO) Management module allows for the management of Purchase Order requests, approvals and tracking. Where significant purchases are to be made by a business a purchase order management approach allows for sense checking of purchases by management.

Module_-_Purchase_Order

2.4 Scheduler

The scheduler module will deliver in conjunction with Time Tacker and Appointment Manager the ability to plan staff hours and allocate them in advance.

The module is in concept stage and is being worked through with a client to deliver specific requirements.

The primary challenge in the development of this module is the development and application of the resource allocation algorithms

As bxp moves towards being able to offer ERP solutions, the schedule features as a key stepping stone in this development https://en.wikipedia.org/wiki/Enterprise_resource_planning

3 Engine

3.1 KeyStats plan

In order to better manage the potential slow down issues with incorrectly built KeyStats, the render page of the keystat is going to be given it’s own server W3 to process it. If W3 becomes unavailable a fall back to W1 and W2 will be implemented.

This action is considered a priority and is being worked on with Sungard at this time.

3.2 Scheduled reports plan

Scheduled reporting will be moved to W3 and Db2 to reduce operational load on W1, W2 and Db1

3.3 Big reports plan

Where are a report is identified as working on a very large data set, e.g. > 10,000 CDA records, the report will be generated on W3 and Db2 in a scheduled fashion. When the report has generated it will be available in the Report Library module for collection. An email notification will also be sent to the user that the report is ready to collect.

3.4 Analytics

R is a free statistical computing tool available from https://www.r-project.org/

bxp will generate data in a format compatible with R to facilitate the implementation of a number of data mining algorithms.

Algorithms currently considered

kMeans Clustering algorithm
k Nearest Neighbour algorithm
Apriori algorithm
CART 4.5 algorithm

3.5 Custom folder via sftp

Access to the custom folder via the current web interface requires a “one by one” file approach. Where a client needs numerous file management access, sftp access will be provided to the file storage engine of bxp. This will in turn be managed on a scheduled or click request basis to kick off an audited and antivirus scanned transfer of the file storage to the live web infrastructure.

This should provide easier access for system administrators to mass manage their custom folder.

The_Custom_folder_through_sFTP_management

3.6 API Tester Engine

Currently testing the API engine requires an external solution to poll the bxp servers. To make testing the interface more controlled and generate consistent repeatable results, an API testing interface will be developed.

This interface will be developed using PHP and live on the www.bxpsoftware.com public webserver. The interface will be available to all to use and provide sample code.

3.7 API Hamster Report (Moss and others)

To make API support easier hamsters generated by the API engine will be interrogate-able and searchable. This interface will initially only be available to internal All n One staff with the interface on refinement being rolled out the System Access Management module.

A new section for API support will be provided in the System Access Management module.

3.8 Table styling

We’ve been asked more than once to allow tables to “pop” or look more stylish.

bxp can adopt a look from other known office tools and using a well-known package to suggest some HTML interpretations.

In order to implement these styles the tables will have to have new CSS tags applied.

css_Table_New_Table
css_Table_First_Cell
css_Table_First_Row
css_Table_Data_FirstCell
css_Table_Data_DataCell
css_Table_Data_LastCell
css_Table_Data_Alt_FirstCell
css_Table_Data_Alt_DataCell
css_Table_Data_Alt_LastCell
css_Table_Last_FirstCell
css_Table_Last_Row
css_Table_Last_LastCell

These tags are then set with appropriate styles and makes styling really easy to apply.

This change will affect where clients might have customisations or expect data to appear in particular layouts.

A default style matching current styles will be created BUT the HTML will have the new css Headers added.

Application of styling will vary throughout the system. i.e. there will be a master default but only some reports will allow “selective” styling.

3.9 System Wipe function

This tool will purge all data and accounts from the ww5 or live environments as required. The tool will require a special code only supplied by All n One staff to allow a client enact the removal of all their data.

This tool also will help to reset testing environments where experimentation or training is required.

3.10 System notification emails

A number of email and reports from bxp come from a variety of email addresses currently. These are to be unified under the bxpsoftware.com domain.

security@bxpsoftware.com
hamsters@bxpsoftware.com
notification@bxpsoftware.com
alerts@bxpsoftware.com
compliance@bxpsoftware.com

3.11 Client daily picture engine

This small change will allow clients to have their own 365 daily images run from the clients custom folder.

Currently using the keyword dailyPic in the background image of a user or a system will use the daily pic engine as their background.

By changing the word to customDailyPic, the engine will use the path folder. X is the name of the system currently being used and YYY is the 3 digit code for the day of the year, ie. 001 is 1st January of that year.

For more information The_dailyPic_engine

3.12 Login page - Username autocomplete

As part of security the password field has a feature which removes the auto-complete of the password. This is a reasonable security measure.

In order to further improve security the username field will now also have autocomplete removed. The reason being that if a machine is used in a public environment, the username is left in the box providing a valid account which could be attacked to force unwanted lock outs. This change means a user will need to type their name in regularly.

3.13 AJAX engine - Title when no records

Currently the text displays

This will be changed to "No records found."

Bxp Release 10 SER 1 release notes

Contents