Post-Artifact Editing Workflow
Creating a Checkpoint of Changes
After working with artifacts, such as building rules for decision table artifacts or editing model artifacts, users can create a checkpoint to save and capture the current state of their changes. A checkpoint acts as a snapshot of the sandbox at a specific moment, preserving the modifications made so far. Checkpoints are uniquely named and described by users, ensuring clarity and traceability.
Checkpoint Flow
Saving Changes Locally
Users first save the changes to their sandbox. These changes remain local and are not visible to other users until published.
Creating a Checkpoint
Checkpoints are for the whole sandbox and not associated with projects. To create a checkpoint, proceed as follows.
- Right-click anywhere in the Project Explorer view and select Checkpoint>Create
OR
In the Checkpoints view, click the Create Checkpoint toolbar button
.
- Enter the Name of the checkpoint.
- Enter the Description (optional) which contains the purpose or details of the changes.
The checkpoint is saved in the sandbox, capturing the current state of the artifacts and projects.
Viewing Checkpoints
To view the list of created checkpoints, select Window>Show View>Checkpoints in the top-level menubar.
The Checkpoints view displays the following details:
Date
: Creation date of the checkpoint.Name
: Name of the checkpoint.Description
: Description of the checkpoint.Author
: Creator of the checkpoint.
Making Additional Changes
If users make further changes after creating a checkpoint, such as updating the project version, they can create additional checkpoints to save the progress. Each checkpoint is independently named and described, ensuring incremental tracking of modifications.
Reverting Changes
When working on a project, users may need to revert the sandbox to a previous state or remove unwanted modifications. The Checkpoint context menu provides options for reverting changes, including:
- Discarding the modifications.
- Resetting the sandbox.
- Resetting to a checkpoint.
Discarding the Modifications
To discard all pending modifications in the sandbox, right-click anywhere in the Project Explorer view and select Checkpoint>Discard modifications.
Purpose: Remove all modifications since the last checkpoint.
Behavior: All unsaved changes are permanently discarded. Changes captured in the last checkpoint or previously published versions remain unaffected.
Usage: Use this option for quick cleanup when modifications are no longer required.
Warning: This action cannot be undone. Ensure that the changes are no longer needed before discarding.
Resetting the Sandbox
To reset the sandbox, right-click on the project in the Project Explorer view and select Checkpoint>Reset Sandbox.
Purpose: Revert the sandbox to its original state before any checkpoints were created, syncing it with the backing space.
Behavior: Deletes all checkpoints in the sandbox and synchronizes the sandbox with the current state of the backing space. Any unsaved changes are preserved as pending changes unless explicitly discarded.
Usage: Useful for clearing all progress and aligning the sandbox with the latest version in the backing space.
Warning: Checkpoints cannot be recovered once deleted during this operation.
Reset to Checkpoint
To reset to a specific checkpoint, right-click on the project in the Project Explorer view and select Checkpoint>Reset to Checkpoint.
Purpose: Allows to reset to a specific checkpoint, the latest checkpoint, or the initial checkpoint.
Behavior: Only the changes made after the selected checkpoint are discarded. The sandbox is restored to the exact state of the chosen checkpoint.
Usage: Choose the desired checkpoint from the list and confirm the reset operation. Useful for rolling back to a specific stable state while retaining earlier progress.
Warning: Ensure that the selected checkpoint represents the desired state, as changes after that point are lost.
These options allow users to manage their workspace, ensuring flexibility and control while maintaining the integrity of their project workflows.
Publishing a Checkpoint
Publishing a checkpoint ensures that the changes in the sandbox are available in the backing space. This allows other users to access and collaborate on one or more updated projects.
Preconditions
The user requires publish permission to the backing space or else it fails.
Update the Project Version
Before creating a checkpoint, ensure that all projects' versions have been updated. A project that is published to the backing space must have a unique version.
No Modified Files
Ensure that all changes are saved and included in the checkpoint. There should be no modified files left in the sandbox to avoid conflicts or incomplete publishing.
Steps to Publish a Checkpoint
Using the Context Menu
To publish the latest checkpoint, proceed as follows.
- Right-click anywhere in the Project Explorer view and select Checkpoint>Publish.
- Confirm the publish operation in the Publish Checkpoint dialog.
Using the Checkpoints View
To publish a specific checkpoint, proceed as follows.
- On the top-level menubar, select Window>Show View>Checkpoints to open the Checkpoints View.
- Locate the desired checkpoint in the Checkpoints View list. Right-click on the checkpoint and select Publish
OR
Select the checkpoint in the Checkpoints View and click the Publish toolbar button
.
Deleting Artifacts from the Project Explorer View
Model Management Server (hereafter referred to as MMS) allows individual artifacts to be deleted directly from the Project Explorer view.
Local Deletion
When an artifact is deleted, the operation remains local to the sandbox unless published. The artifact is removed from the local project not yet reflected in the backing space.
Publishing the Deletion
To delete the artifact globally, the deletion must be included in a checkpoint and published to the backing space. Until published, users can withdraw or discard the deletion operation as described in previous sections.
Duplicate Name Restrictions
Once an artifact is deleted, you can create a new one with the same name.
Deleting a Project
Deleting a project removes the project from the sandbox. If the Delete project from the backed space option is checked, it deletes the project from the sandbox and the backing space.
If the Delete project from the backed space option is NOT checked, then whenever a checkpoint is created and published, the project is not removed from the backing space.
Steps to Delete a Project
- To delete a project, right-click on the project in the Project Explorer view and select Delete.
- A confirmation dialog appears, with an option to Delete project from the backed space. To delete the project globally, check the Delete project from the backed space checkbox before confirming the deletion. Please note that this change is not reflected in the backing space until a checkpoint is published.
Checkpoint and Publish Requirements
After confirming the deletion by selecting the Delete project from the backed space option, the user must create a checkpoint to capture the deletion. The checkpoint must then be published to the backing space to make the deletion permanent.
Impact of Deletion
Deleting a project by selecting the Delete project from the backed space option removes all the artifacts associated with the project from the backing space. Always verify that the correct project or artifact is selected for deletion to avoid accidental data loss.
Permissions
Deleting a project requires appropriate permissions. Users without the necessary roles or privileges cannot perform this operation.
Deploying Artifacts
If your user role includes the deploy privileges, you can deploy artifacts in the repository to a running Streaming cluster. For more information, see MMS Artifact Administration.