Snapshot Locked and Linked Records

We would like to provide more comprehensive versioning capabilities in the future - in particular, the ability to take a snapshot of a set of artifacts (linked processes, linked decisions & attached policies), but this is not in our short to mid-term roadmap. We will continue to monitor this requirement and re-evaluate periodically.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Smarter Process
Product - Blueworks Live

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Business Process Management
Product - Blueworks Live

IBM: What do you mean by "including a locked and linked copy of the artifacts"?

BluesClues:
If I snapshot a Process it would be useful for that snapshot to auto snapshot all linked artifacts and link them together at one point for the users. That point being the primary process snapshot. Reversing this might also be beneficial via all artifacts but at minimum the one point is requested.
The tool has auto snapshot functionality. As such when I snapshot the primary process. The idea would be the tool then auto snapshots all artifacts and links them to a single point for the user. That single point being the Process Snapshot. If the user selects the single point process snapshot all records linked to it would reload for review.
Scenario: When I reload Monday's snapshot and go to activity 1 to select a decision model. Is that decision model the one from last Monday also or the current Decision Model from today? A Record is a snapshot in time. The record to the customer and from a Quality point of view is all the associated objects of that activity at the time the record is generated.

Therefore when I open and make my Process Snapshot on Monday all associated artifacts could generate an auto snapshot on Monday linking them to the Process Snapshot created.

Therefore when I load my Process Snapshot from Monday all associated artifacts from Monday also load for review.
When a Business is doing a root cause analysis this would improve that process as well. As researching the history of an event is critical to that process. Point being this has implications to multiple processes from a business and customers point of view.

IBM: What are you referring to as "application records"?
BluesClues:
Via my Definitions:
Artifacts would be any items linked directly to the process (based on any snapshot) you're looking at or any items that should be linked like “launch a process” record (Snapshot?) generated in the background.
Application record is a reference to the “launch a process” aspect of the tool to obtain review or notification. Its end result would be considered a record that should be associated to a specific snapshot version of a process and its associated snapshot versions of artifacts. (I believe some changes were made to this point after my original request) This falls under the idea of an artifact as well but is being called out separately since it is often overlooked when artifacts are mentioned.
From the customers and quality perspective each process and its linked Artifacts would be considered one Record. Even where the database see them each as individual objects. In the database to make them one record requires proper link management between the objects snapshots versus just the objects. For a user, to remove manual errors and lean this out would require a single point for user consumption with good linking all around and all artifacts linked.
Your comment highlighted (Reminds me) of another aspect as well.
At my last review during a review of the Process approval history it was noted the items could be modified at any point of the review process. This voids the approval really immediately upon alteration. As such it would work best to require a “complete” record snapshot prior to approval and notification. At which point it would auto publish (the entire record) upon a positive conclusion to approval and notification or return the entire record back to work status. At minimum the customer really needs to be provided the option of the higher quality options noted. The idea of in work review is fine to leave in the tool obviously but we need the higher quality review option which ensures the customer is receiving approved quality content as requested.
Launch a process could also run directly from the snapshot you wish to run it on. This then could immediately link the launch a process record to the related snapshot.
It's been sometime since I've looked at all this stuff and I also realize some items might have been address or in the works. Hopefully from this you can see the concern. From a Business and customer perspective this request would be lean, provide quality records, avoid invalidating the review process, improve traceability and lower Business risk for the customers. Of course you're welcome to meet to discuss if you want and look it over together. I went through most of these items a year ago with Support and just now they are being sent again to the RFE community. Of course, I'm available to review, discuss and meet if needed. Thanks

Note: I entered this before but it did not populate. Hopefully this comment was not posted on a different ticket. If so, can you remove it there. Thanks