AseptSoft Core Documentation
AseptSoft Core Documentation
Breadcrumbs

Commits and Branches

AseptSoft uses a branching model for parallel collaboration. Each user works on their own branch, where they can have multiple modules and commits (checkpoints), all independent of other collaborators.

🌲 Branches

A branch is a parallel thread of work within a project. Branches are organized as follows:

Branch Type

Description

Main

Automatically created in every project. Used as the shared integration branch for merging all collaborators' work.

User branches

Automatically created for each user with their name. Each user works independently on their branch.

Custom branches

Additional branches you create manually for specialized workflows.

🛠️ Managing Branches

Action

How

Create

Use the Create button in the Home Ribbon → Folders panel

Rename

Close AutoCAD, navigate to the project location, and rename the branch folder

Delete

Close AutoCAD, navigate to the project location, and remove the branch folder

📦 Modules

Each branch contains one or more modules — independent units of process design work.

🛠️ Managing Modules

Action

How

Create

Use the module management window (accessible from the Home Ribbon)

Rename

Right-click the module in the Modules window

Delete

Right-click the module in the Modules window

📌 Commits

A commit is a checkpoint (snapshot) of a module at a specific point in time. Commits allow you to:

  • Preserve the state of your work at meaningful milestones

  • Restore a previous version by merging from a commit

  • Share snapshots with other collaborators

🛠️ Managing Commits

Action

How

Create

Right-click the module in the Modules window → "Create Commit..."

Rename

Navigate to the File System commit location and rename the commit file

Delete

Navigate to the File System commit location and remove the commit file

📄 Templates

You can save a module as a template for reuse across projects:

  1. Right-click the module in the Modules window → Save as Template

  2. Enter a name for the template

Templates are stored in the templates root folder (see File System). See also Import/Export Templates for details on template management.

🏭 Pharma Example: Creating a "CIP Optimization" Branch

Your team is working on a CIP (Clean-in-Place) skid design. The lead engineer has established the baseline process on the main branch with standard wash, rinse, and drain sequences. A process optimization engineer wants to experiment with reduced water consumption without affecting the approved baseline.

📖 How To: Create and Work on a Feature Branch

  1. Create a new branch — In the Home Ribbon → Folders panel, click Create and name it "CIP Optimization"

  2. Design your changes — Modify chemical dosing concentrations, adjust rinse cycle durations, and reconfigure valve sequences for water recovery

  3. Commit your milestone — Right-click the module → "Create Commit..." and name it "Reduced Water Consumption v1"

  4. Iterate and commit again — After further refinement, create another commit: "Reduced Water Consumption v2 — Final"

  5. Request review — Share the branch with your team lead for a Review Session

  6. Merge into main — Once approved, use Merging to bring the optimized process into the main branch

This workflow keeps the approved baseline safe while allowing experimentation — critical in regulated pharma environments where changes must be controlled and traceable.