Treat FlowType=AbandonCurrentMoveToNext
as reject
action
#117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Due to a patch in Altinn/altinn-storage#414, ProcessController treats
FlowType=AbandonCurrentMoveToNext
identically toFlowType=CompleteCurrentMoveToNext
. This has now proven to be problematic, as described in Altinn/app-lib-dotnet#818.This PR intercepts
AbandonCurrentMoveToNext
and treats it asreject
instead of whateveraltinn:taskType
from the current step was.NOTE: This functionality must be implemented in altinn-storage as well. This will be the next step, after we have confirmed functionality and reached agreement on how it should look in localtest.
Related Issue(s)
action=reject
requires incorrect permissions app-lib-dotnet#818Verification
Documentation