-
Key: CR-9
-
Legacy Issue Number: 19479
-
Status: closed
-
Source: hidera.nl ( Thijs Petter)
-
Summary:
Quote: "The difference between using a CaseTask and a Stage is that a CaseTask calls a Case that has its own context, i.e., it
is based on its own CaseFile, whereas a Stage represents behavior that shares the same context with the Stage, i.e., it
is based on the same CaseFile and is “embedded” in the same Case."It says "... a Stage represents behavior that share the same context with the Stage ..." Perhaps the second occurrence of the word Stage should have been Case?
-
Reported: CMMN 1.0 — Tue, 17 Jun 2014 04:00 GMT
-
Disposition: Resolved — CMMN 1.1
-
Disposition Summary:
Clarify difference between case task and stage
Section 5.4.10.6 CaseTask (page 38), second paragraph reads,
The difference between using a CaseTask and a Stage is that a CaseTask calls a Case that has its own context, i.e. it is based on its own CaseFile, whereas a Stage represents behavior that shares the same context with the Stage, i.e. it is based on the same CaseFile and is “embedded” in the same Case.
Which is redundant.
5.4.10.6 CaseTask (page 38), second paragraph reads,
The difference between using a CaseTask and a Stage is that a CaseTask calls a Case that has its own context, i.e. it is based on its own CaseFile, whereas a Stage represents behavior that shares the same context with the Stage, i.e. it is based on the same CaseFile and is “embedded” in the same Case.
Rewrite as follows
The difference between using a CaseTask and a Stage is that a CaseTask
calls ainvokes a new Case that has its own context, i.e. it is based on its own CaseFile (implements reuse), whereas a Stageexecutesis in the context of the current caserepresents behavior that shares the same context with the Stage, i.e. it is based on the same CaseFile and is “embedded” in thesamecurrent current Case (implements composition). -
Updated: Tue, 29 Mar 2016 15:06 GMT