Translations:Schutzbedarf/76/en: Unterschied zwischen den Versionen
Weitere Optionen
Isan (Diskussion | Beiträge) Die Seite wurde neu angelegt: „===Workflow plan FAQs=== <b>What happens when the workflow plan is executed?</b><br> When the workflow plan is executed, reassessments are created for the linked protection needs analyses, and the respective interview partners are requested to respond. A reassessment evaluates the same resources and data categories for the same organizational unit or process as the original protection needs analysis. <b>When is no reassessment created and requested?</b><b…“ |
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
Zeile 7: | Zeile 7: | ||
*The protection needs analysis is not completed. | *The protection needs analysis is not completed. | ||
*The protection needs analysis has no interview partner. | *The protection needs analysis has no interview partner. | ||
*There is already another protection needs analysis for the same organizational unit or process that: | *There is already another protection needs analysis for the same organizational unit or process that evaluates at least one overlapping resource or data category that: | ||
**is not yet completed, or | **is not yet completed, or | ||
**has already been completed but has a more recent start date | **has already been completed but has a more recent start date.<p> | ||
<u>Caution:</u> The last case is especially relevant when you operate more than one management systems. If you have planned a protection needs analysis via the workflow, but a colleague in a different management system creates a protection needs analysis that meets the same criteria, that new protection needs analysis will block the workflow.<p> | <u>Caution:</u> The last case is especially relevant when you operate more than one management systems. If you have planned a protection needs analysis via the workflow, but a colleague in a different management system creates a protection needs analysis that meets the same criteria, that new protection needs analysis will block the workflow.<p> | ||
<b>What happens to paused protection needs analyses?</b><br> | <b>What happens to paused protection needs analyses?</b><br> | ||
If a protection needs analysis is paused, no reassessment will be created during the next execution. Instead, the analysis will be re-activated for the following execution cycle. | If a protection needs analysis is paused, no reassessment will be created during the next execution. Instead, the analysis will be re-activated for the following execution cycle. |
Version vom 19. August 2025, 09:54 Uhr
Workflow plan FAQs
What happens when the workflow plan is executed?
When the workflow plan is executed, reassessments are created for the linked protection needs analyses, and the respective interview partners are requested to respond. A reassessment evaluates the same resources and data categories for the same organizational unit or process as the original protection needs analysis.
When is no reassessment created and requested?
No reassessment is created and requested if any of the following conditions apply:
- The reassessment of the protection needs analysis is paused.
- The protection needs analysis is not completed.
- The protection needs analysis has no interview partner.
- There is already another protection needs analysis for the same organizational unit or process that evaluates at least one overlapping resource or data category that:
- is not yet completed, or
- has already been completed but has a more recent start date.
Caution: The last case is especially relevant when you operate more than one management systems. If you have planned a protection needs analysis via the workflow, but a colleague in a different management system creates a protection needs analysis that meets the same criteria, that new protection needs analysis will block the workflow.
What happens to paused protection needs analyses?
If a protection needs analysis is paused, no reassessment will be created during the next execution. Instead, the analysis will be re-activated for the following execution cycle.