Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
Created page with "= Overview = This document forms part of the bxp Release 10 Service Enhancement Release 2 suite of changes found here Bxp_Release_10_SER_2_prerelease_notes == Form Mana..."
= Overview =
This document forms part of the bxp Release 10 Service Enhancement Release 2 suite of changes found here [[Bxp_Release_10_SER_2_prerelease_notes]]
== Form Management [[File:038.png]] ==
=== 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.
This document forms part of the bxp Release 10 Service Enhancement Release 2 suite of changes found here [[Bxp_Release_10_SER_2_prerelease_notes]]
== Form Management [[File:038.png]] ==
=== 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.
