| Table of Contents |
|---|
Date
19 Dec 2019
Previous Meeting - Next Meeting
Agenda
Item / Topic | Presenter | Description |
|---|---|---|
Discuss Long Beach OMG Meetingnaming of SDMN elements | Stephen White (Unlicensed) | Considering such discussion for KPMN |
Discuss design time data value assignments (variable initialization) Look at options and vote on approachfor topics like Order Sets | There are a number of approaches, which are basically work-arounds |
Participants
Stephen White (Unlicensed); Keith Butler; Keith Salzman; @Falko Menge; John Svirbely (Unlicensed); Denis Gagne; Sharnita Riley; Peter Haug; John Butler
Goals
List goals for this meeting (e.g., Set design priorities for FY19):
- Address any Situational Data presentation for OMG Meeting
- Update document as appropriate
- Discuss naming of SDMN elements
- Discuss design time data value assignments (variable initialization) for topics like Order Sets
- Identify next steps
Notes (raw)
Since the KPMN working group is discussing the name "Knowledge Package" and whether it should be changed, we brought up the terminology topic on this call. The general consensus was that "Situational Data" or other SDMN terms did not require any modifications. But we will monitor the KPMN discussion to see if we will need to follow suit.
Again we discussed the pre-population of data values for Data Items for things like Order Sets. there are a few options, but within SDMN and without.
Within SDMN:
- Use the UnaryTest for ItemDefinitions to put constraints
- This is not value assignment. Even if defined in SDMN, the value assignment would still need to take place in the other BPM+ models.
- This means that would would have to create a new ItemDefinition for each Data Item. This could create maintenance problems when you have to do this for many Data Items.
- Add a new value assignment capability.
- We don't currently know how to do this. We don't know if this capability exists within other OMG standards.
- This would be useful for SDMN modeling, but we would still need to figure out how the other BPM+ standards would utilize the value assignments
Within the other BPM+ Standards.
- This means that the SDMN elements would not contain the value assignments
- Using a file to store the value assignments
- A BPMN Data Object could reference an XML file with the assignment values, then there would be service Task that takes the file and updates an other Data Object with those values.
- This could be done with CMMN, but it is not clear how Case File Item would be updated with those values, since there is no Service Task in CMMN
- DMN would not have to do this, since it would be getting the data values from a Process or a Case
- Using the BPMN Data Output Associations
- A Data Object can be updated with the appropriate assignments.
- The values assigned to a Data Object or Case File Item would have to be properly passed between the processes and cases.
We need to settle on a single approach so that we can update the Field Guide with that approach.
Chat Log
No chat items this time
Action items
Add action items to close the loop on open questions or discussion topics:
- enter action item
Anchor Meeting Recording Meeting Recording
Meeting Recording
| Meeting Recording | |
| Meeting Recording |
| View file | ||||
|---|---|---|---|---|
|