Article Details
| Id: | 18819 |
| Product: | finPOWER Connect |
| Type: | FIX |
| Version: | 3.04.03 |
| Opened: | 06/12/2021 |
| Closed: | 07/12/2021 |
| Released: | 01/02/2022 |
| Job: | J027961 |
 Breaking Change |
|
Security Statement form; updated Permission Key logic
When adding a new Security Statement the following Permissions Keys should not have been applied:
* SecurityStmt.UpdateCode
* SecurityStmt.BranchUpdate
* SecurityStmt.ManagerUpdate
The "Update" in the Permission Key eludes to the fact that they are applied only when updating an existing record. In addition, if the default value is blank and it is mandatory, e.g. Branch, the User would never be able to add a Security Statement.
In addition the Code field should not be mandatory if there is an auto-sequence defined in Global Settings.
This has been noted as a breaking change because of the effect in the User Interface.