-
Key: SYSMOAS-6
-
Status: closed
-
Source: University of Arizona ( Mr. Rick Steiner)
-
Summary:
In the PIM, ProjectDataVersioningService.getCommitChange(...) operation returns a set of changes in a given commit compared to the previous commit(s). This includes elements added, updated, or deleted in the given commit. The set of changes returned from the getCommitChange(...) operations can be large, even though served using pagination. In many scenarios, consumers of the API may only be interested in specific types of changes, e.g. elements added, or updated, or deleted.
Can we add an additional argument to the getCommitChange(...) operation that returns a filtered set of changes based on a change type versus all the changes? -
Reported: SystemsModelingAPI 1.0a1 — Sun, 14 May 2023 22:37 GMT
-
Disposition: Resolved — SystemsModelingAPI 1.0b2
-
Disposition Summary:
Adding changeTypes argument to getCommitChange operation of ProjectDataVersioningService
This is the proposal to resolve
SYSMOAS-6. See the Revised Text for details. -
Updated: Tue, 1 Jul 2025 15:08 GMT
-
Attachments:
- Commit_Change_Type_Graphic.png 198 kB (image/png)
SYSMOAS — Filtering commit changes by change type
- Key: SYSMOAS-6
- OMG Task Force: Systems Modeling API and Services (SystemsModelingAPI) 1.0 FTF