|
|
| (34 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | bxp Release 10 Service Enhancement Release 1 has no set date for release yet. Cooperation and collaboration with clients is currently in progress. | + | bxp Release 10 Service Enhancement Release (SER) 1 was released at 04:00 on 27th February 2018. |
| − | | |
| | | | |
| | = Existing Module Changes = | | = Existing Module Changes = |
| Line 11: |
Line 10: |
| | ! Link | | ! Link |
| | |- | | |- |
| − | | Appointment Manager || [[File:000.png]] || 7 Changes || [[Bxp_R10SER1_-_Appointment_Management]] | + | | Appointment Manager || [[File:027.png]] || 7 Changes || [[Bxp_R10SER1_-_Appointment_Management]] |
| | |- | | |- |
| − | | Communications Centre || [[File:000.png]] || 1 Change || [[Bxp_R10SER1_-_Communications_Centre]] | + | | Data Profiling || [[File:061.png]] || 1 Change || [[Bxp_R10SER1_-_Data_Profiling]] |
| − | |-
| |
| − | | eCourse || [[File:000.png]] || 3 Changes || [[Bxp_R10SER1_-_eCourse]]
| |
| − | |-
| |
| − | | Form Management || [[File:000.png]] || 19 Changes || [[Bxp_R10SER1_-_Form_Management]]
| |
| | |- | | |- |
| − | | Information Centre [[File:000.png]] || 3 Changes || [[Bxp_R10SER1_-_Information_Centre]] | + | | eCourse || [[File:047.png]] || 3 Changes || [[Bxp_R10SER1_-_eCourse]] |
| | |- | | |- |
| − | | KeyStats || [[File:000.png]] || 4 Changes || [[Bxp_R10SER1_-_KeyStats]] | + | | Form Management || [[File:038.png]] || 19 Changes || [[Bxp_R10SER1_-_Form_Management]] |
| | |- | | |- |
| − | | MetaData || [[File:002.png]] || 1 Changes || Available from [[Bxp_R10SER1_-_MetaData]] | + | | Information Centre || [[File:011.png]] || 3 Changes || [[Bxp_R10SER1_-_Information_Centre]] |
| | |- | | |- |
| − | | Project Manager || [[File:050.png]] || 8 Changes || [[Bxp_R10SER1_-_Project_Manager]] | + | | MetaData || [[File:002.png]] || 1 Changes || [[Bxp_R10SER1_-_MetaData]] |
| | |- | | |- |
| − | | System Access Management || [[File:016.png]] || 14 Changes || [[Bxp_R10SER1_-_System_Access_Management]] | + | | System Access Management || [[File:016.png]] || 15 Changes || [[Bxp_R10SER1_-_System_Access_Management]] |
| − | |-
| |
| − | | Time Tracker || [[File:000.png]] || 2 Changes || [[Bxp_R10SER1_-_Time_Tracker]]
| |
| | |- | | |- |
| | |} | | |} |
| − |
| |
| | | | |
| | = New Modules = | | = New Modules = |
| | | | |
| | | | |
| − | == Dashboards == | + | == Dashboards [[File:049.png]] == |
| | | | |
| | | | |
| − | The Dashboards module allows for prebuilt, predesigned panes of information to be collated into a single operational dashboard. | + | The Dashboards module allows for prebuilt, pre-designed panes of information to be collated into a single operational dashboard. |
| | | | |
| | | | |
| Line 47: |
Line 39: |
| | | | |
| | | | |
| − | A number of predesigned dashboards will be launched with the module. | + | A number of pre-designed dashboards will be launched with the module. |
| − | | |
| − | | |
| − | | |
| − | == 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]]
| |
| − | | |
| − | | |
| | | | |
| | = Engine = | | = Engine = |
| − |
| |
| − |
| |
| − | == 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.
| |
| − |
| |
| − |
| |
| − | Currently the KeyStats engine for generating reports executes on Web servers 1 and 2 using Database server 1 as its data repository. This will be updated to execute on web sever 3 and use database server 2 as its data repository.
| |
| − |
| |
| − |
| |
| − |
| |
| − | == 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | == 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]]
| |
| − |
| |
| | | | |
| | | | |
| Line 118: |
Line 47: |
| | | | |
| | | | |
| − | We’ve been asked more than once to allow tables to “pop” or look more stylish.
| + | This change allows custom table styling in various areas throughout the bxp system [[Table_Styling]] |
| − | | |
| − | | |
| − | bxp can adopt a look from other known office tools and using a well-known package to suggest some HTML interpretations.
| |
| − | | |
| − | | |
| − | [[File:bxpR10SER1_015.png | 800px]]
| |
| − | | |
| − | | |
| − | 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.
| |
| − | | |
| − | | |
| − | | |
| − | == 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
| |
| − | | |
| − | | |
| − | | |
| − | == 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 https://ww3.allnone.ie/client/client_x/custom/dailypic/YYY.png 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]]
| |
| − | | |
| − | | |
| − | | |
| − | == 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.
| |
| − | | |
| − | | |
| − | == AJAX engine - Title when no records ==
| |
| − | | |
| − | | |
| − | Currently the text displays
| |
| − | | |
| − | [[File:bxpR10_AJAXTitle.png]]
| |
| − | | |
| − | | |
| − | This will be changed to "No records found."
| |
| − | | |
| − | | |
| − | | |
| − | === 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.
| |
| − | | |
| | | | |
| | | | |
bxp Release 10 Service Enhancement Release (SER) 1 was released at 04:00 on 27th February 2018.
The Dashboards module allows for prebuilt, pre-designed panes of information to be collated into a single operational dashboard.
This change allows custom table styling in various areas throughout the bxp system Table_Styling
