Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sig#811 Split up ACTIVATE_APPLICATION Process Step and make it retrigger able #913

Closed
5 tasks
MaximilianHauer opened this issue Aug 9, 2024 · 0 comments
Closed
5 tasks
Assignees
Labels
enhancement New feature or request

Comments

@MaximilianHauer
Copy link

MaximilianHauer commented Aug 9, 2024

Description

AS A PDO
WHEN the process step ACTIVATE_APPLICATION fails
THEN i want to be able to retriger it

Goal is to split up the process step to enable retriggering on the different phases.
After the split-up is done the new process steps should be retriggerable

Acceptance Criteria

  • Split up ACTIVATE_APPLICATION into logical and retriggerable process steps
  • Update documentation regarding the split of ACTIVATE_APPLICATION
  • Define retriggering capabilities for the new process steps
  • The process worker documentation is updated regarding the new retrigger functionality
  • Status endpoints are updated with accurate retrigger endpoint mapping
@MaximilianHauer MaximilianHauer added the enhancement New feature or request label Aug 9, 2024
@MaximilianHauer MaximilianHauer changed the title sig#811 Split up ACTIVATE_APPLOCATION Process Step and make it retriggerable sig#811 Split up ACTIVATE_APPLICATION Process Step and make it retriggerable Aug 9, 2024
@MaximilianHauer MaximilianHauer changed the title sig#811 Split up ACTIVATE_APPLICATION Process Step and make it retriggerable sig#811 Split up ACTIVATE_APPLICATION Process Step and make it retrigger able Aug 9, 2024
@MaximilianHauer MaximilianHauer added this to the Release 24.12 milestone Aug 9, 2024
Phil91 added a commit that referenced this issue Sep 17, 2024
Phil91 added a commit that referenced this issue Sep 18, 2024
Phil91 added a commit that referenced this issue Sep 18, 2024
Phil91 added a commit that referenced this issue Sep 18, 2024
Phil91 added a commit that referenced this issue Sep 20, 2024
Phil91 added a commit that referenced this issue Sep 20, 2024
Phil91 added a commit that referenced this issue Sep 20, 2024
Phil91 added a commit that referenced this issue Sep 26, 2024
Phil91 added a commit that referenced this issue Oct 8, 2024
Phil91 added a commit that referenced this issue Oct 8, 2024
Phil91 added a commit that referenced this issue Oct 8, 2024
Phil91 added a commit that referenced this issue Oct 8, 2024
Phil91 added a commit that referenced this issue Oct 14, 2024
Phil91 added a commit that referenced this issue Oct 14, 2024
Phil91 added a commit that referenced this issue Oct 14, 2024
Phil91 added a commit that referenced this issue Oct 14, 2024
ntruchsess pushed a commit that referenced this issue Oct 15, 2024
ntruchsess pushed a commit that referenced this issue Oct 15, 2024
ntruchsess pushed a commit that referenced this issue Oct 15, 2024
Phil91 added a commit that referenced this issue Oct 16, 2024
Refs: #913
Co-authored-by: Norbert Truchsess <[email protected]>
Reviewed-by: Norbert Truchsess <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants