You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add configuration setting to prevent field agents from submitting partially completed forms
(Describe the problem you're trying to solve by doing this work)
Tech design fundamentals
User scopes need to be as granular as possible. User scope is the smallest unit of the system,
User scopes need to be documented comprehensively so that all behaviours are known
For wider permission sets (for instance functionality based) we define "permission sets"
For us to be able to introduce more scopes that are more granular than the earlier ones, we should always consider the existing, old scope as a "permission set". So as an example, we could consider the current day "declare" scope to be an alias for all of the following:
In commons, implement a hasScope(userScopesOrPermissionSets: string[], scope: Scope): boolean function that knows how to expand permission sets. Hardcode the first permission set to this file: declare. Notice that you might need to create other sets as part of this task, like create-birth-declaration.
Research where the declare scope is being checked and replace those code points with more granular scope requirements.
Implement a new user scope submit-incomplete-declaration. Make this scope control if a declaration can be sent incomplete or not
The text was updated successfully, but these errors were encountered:
jpye-finch
changed the title
Configuration: FA should not submit incomplete Notifications
Configure FA permissions to send incomplete declarations
Jan 19, 2023
@jpye-finch if this is covered in Custom Users & Scopes, can you check? If so, please close the issue and remove it from the project. I removed it from 1.7 backlog
Problem statement
Add configuration setting to prevent field agents from submitting partially completed forms
(Describe the problem you're trying to solve by doing this work)
Tech design fundamentals
Tech design
The full scopes definition can be found here.
For us to be able to introduce more scopes that are more granular than the earlier ones, we should always consider the existing, old scope as a "permission set". So as an example, we could consider the current day
"declare"
scope to be an alias for all of the following:We support this permission set at least for a few versions until our new scope definitions have stabilised a little.
commons
, implement ahasScope(userScopesOrPermissionSets: string[], scope: Scope): boolean
function that knows how to expand permission sets. Hardcode the first permission set to this file:declare
. Notice that you might need to create other sets as part of this task, likecreate-birth-declaration
.declare
scope is being checked and replace those code points with more granular scope requirements.submit-incomplete-declaration
. Make this scope control if a declaration can be sent incomplete or notThe text was updated successfully, but these errors were encountered: