Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
no edit summary
* 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.
=== 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.
=== 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.
=== “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.
=== “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.
== Communications Centre ==
=== 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.
=== 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.
=== 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.
== eCourse ==
=== 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.
==== TOC’less. ====
=== Campaign table changes ===
A number of fields will be added to the campaign table to facilitate the forth coming changes
* 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)
=== 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
=== 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.
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
=== 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.
==== 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.
==== 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.
==== Prebuild – Contacts from emails ====
Using outlook, export all the emails to a data file.
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.
==== 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.
* 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)
==== 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.
==== 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.
=== 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
=== 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.
=== 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.
=== 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.
=== 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.
=== 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.
=== 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
=== 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:
== Information Centre ==
=== 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.
=== 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.
== KeyStats ==
=== Console ===
The security and administration of KeyStats needs some addressing to optimise build and support functions.
A KeyStats console will be made available.
The mass editing security feature needs to be developed.
This will be included as a function stand alone and as part of the console.
=== 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.
== MetaData ==
=== Console ===
This console will facilitate easier management of metadata rules and their associated security and reporting.
== Project Manager ==
=== 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
=== Project API ===
This engine will allow tasks, milestones and other data to be add, edit, delete and listed for any given project.
=== 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.
* 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.
* By Work Type (allows different rates by different activities)
* By Staff (allows the rates to be different by resource used)
=== 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.
=== Exception Costs and API ===
A log engine will be provide that exceptional costs for a project can be logged. The fields will be
* 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.
=== 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 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.
=== 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.
=== 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.
=== 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.
== System Access Management ==
=== User tabs ===
Given the length of the user setup screens a more effective interface screen is being designed.
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.
=== 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.
=== 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.
=== 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.
=== Client table alterations ===
The client table will have a number of fields added to support numerous new functions
* strClient_Retired_LastDateTime to make retired reporting easier
* strClient_Retired_LastByWhom to make retired reporting easier
=== 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.
* Last Date Time will be the date that the field is implemented
* By Whom will be associated with the Admin istrator account.
=== 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.
=== 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.
