Anonymous, bureaucrat, administrator
7,528
edits
Changes
no edit summary
Planned updates moved from SER1 to SER2
= Existing Module Updates =
== 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.
=== 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.
== Form Management ==
=== 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.
=== 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
=== 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.
=== 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.
== System Access Management ==
=== 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.
== Time Tracker enhancements ==
=== Scheduling ===
= New Modules =
== 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]]
== 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]]
https://en.wikipedia.org/wiki/Enterprise_resource_planning
{| class="wikitable"
! Module
! Icon
! Total Changes
! Link
|-
| Project Manager || [[File:050.png]] || 8 Changes || [[Bxp_R10SER1_-_Project_Manager]]
|-
| Time Tracker || [[File:000.png]] || 2 Changes || [[Bxp_R10SER1_-_Time_Tracker]]
|-
| KeyStats || [[File:036.png]] || 5 Changes || [[Bxp_R10SER1_-_KeyStats]]
|-
|}
= General =
== Scheduled reports plan ==
Scheduled reporting will be moved to W3 and Db2 to reduce operational load on W1, W2 and Db1
This tool also will help to reset testing environments where experimentation or training is required.
== 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.
== 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