Change Control Pro - Revision history

Mikrosha2000: Updated Change Control Pro documentation for version 1.1.3, including the new module ID, redesigned interface, upgrade instructions and updated screenshots.

2026-10-18T09:59:28Z

Updated Change Control Pro documentation for version 1.1.3, including the new module ID, redesigned interface, upgrade instructions and updated screenshots.

← Older revision		Revision as of 09:59, 18 October 2026
Line 1:		Line 1:


	[[File:01_change_control_pro_cover.png\|center\|900px\|Change Control Pro]]		[[File:01_change_control_pro_cover.png\|center\|900px\|Change Control Pro]]
Line 30:		Line 29:
	*Responsive desktop and mobile interface		*Responsive desktop and mobile interface
	*English and Romanian translations		*English and Romanian translations

			==What's new in version 1.1.3==

			Version 1.1.3 introduces a redesigned and more responsive Change Control interface while preserving the complete workflow and auditability of previous releases.

			[[File:02_dashboard_and_change_register.png\|center\|900px\|Change Control Pro Dashboard]]

			Main improvements:

			*Module ID updated to the reserved PanciucSoft ID '''210135'''
			*Redesigned dashboard with KPI cards and workflow overview
			*Improved Change Register with responsive filters and status indicators
			*Modernized Change Request creation and detail pages
			*Improved Impact Assessment and Risk Assessment presentation
			*Modernized Approval Workflow and Implementation / Action Plan
			*Improved Effectiveness Check presentation
			*Redesigned read-only Audit Trail
			*Consistent priority, risk and status badges
			*Improved desktop and mobile responsiveness
			*Complete regression testing of the workflow from Draft to Closed
			*PDF Change Control report verified with the complete Audit Trail

			===Upgrade from version 1.0.0===

			Because the module ID was changed to '''210135''', users upgrading from version 1.0.0 should:

			#Deactivate the previous Change Control Pro module.
			#Replace the module files with version 1.1.3.
			#Reactivate Change Control Pro.
			#Review permissions for non-administrator users if necessary.

			Existing Change Control records remain stored in the same database tables.

	==Workflow==		==Workflow==
Line 43:		Line 74:
	==Creating and Tracking Change Requests==		==Creating and Tracking Change Requests==

	[[File:~~02_create_and_track_change_requests~~.png\|center\|900px\|~~Create and Track~~ Change ~~Requests~~]]		[[File:03_responsive_change_request.png\|center\|900px\|Responsive Change Request]]

	A new Change Request can be created directly from the Change Control Pro menu.		A new Change Request can be created directly from the Change Control Pro menu.
Line 68:		Line 99:
	==Impact Assessment==		==Impact Assessment==

	[[File:~~03_impact_and_risk_assessment~~.png\|center\|900px\|Impact ~~Assessment~~ and Risk Assessment]]		[[File:04_impact_and_risk_assessment.png\|center\|900px\|Impact and Risk Assessment]]

	The Impact Assessment stage identifies the elements that may be affected by the proposed change.		The Impact Assessment stage identifies the elements that may be affected by the proposed change.
Line 134:		Line 165:
	==Approval Workflow==		==Approval Workflow==

	[[File:~~04_approval_workflow_and_implementation_plan~~.png\|center\|900px\|Approval ~~Workflow~~ and ~~Implementation Plan~~]]		[[File:05_approval_implementation_effectiveness.png\|center\|900px\|Approval Implementation and Effectiveness]]

	After the Risk Assessment has been completed, the Change Request can be submitted for approval.		After the Risk Assessment has been completed, the Change Request can be submitted for approval.
Line 180:		Line 211:

	==Effectiveness Check==		==Effectiveness Check==

	~~[[File:05_effectiveness_check_and_controlled_closure.png\|center\|900px\|Effectiveness Check and Controlled Closure]]~~

	The Effectiveness Check verifies that the implemented change achieved the intended result.		The Effectiveness Check verifies that the implemented change achieved the intended result.
Line 206:		Line 235:
	==Audit Trail==		==Audit Trail==

	[[File:~~06_audit_trail_and_pdf_report~~.png\|center\|900px\|Audit Trail ~~and PDF Report~~]]		[[File:06_audit_trail_desktop_mobile.png\|center\|900px\|Audit Trail]]

	Change Control Pro includes an automatic read-only Audit Trail.		Change Control Pro includes an automatic read-only Audit Trail.
Line 242:		Line 271:

	Change Control Pro can generate a complete PDF report for a Change Request.		Change Control Pro can generate a complete PDF report for a Change Request.

			[[File:07_complete_pdf_report.png\|center\|900px\|Complete PDF Change Control Report]]

	The PDF report may contain:		The PDF report may contain:
Line 315:		Line 346:
	==Compatibility==		==Compatibility==

	'''Module version:''' 1.0.0		'''Module version:''' 1.1.3

			'''Module ID:''' 210135

	'''Dolibarr compatibility:'''		'''Dolibarr compatibility:'''

Mikrosha2000: Created documentation page for Change Control Pro v1.0.0, including features, workflow, installation, configuration, audit trail and PDF reporting.

2026-10-04T00:53:36Z

Created documentation page for Change Control Pro v1.0.0, including features, workflow, installation, configuration, audit trail and PDF reporting.

← Older revision		Revision as of 00:53, 4 October 2026
Line 1:		Line 1:
	~~=Change Control Pro=~~

	[[File:01_change_control_pro_cover.png\|center\|900px\|Change Control Pro]]		[[File:01_change_control_pro_cover.png\|center\|900px\|Change Control Pro]]

Mikrosha2000: Created documentation page for Change Control Pro v1.0.0, including features, workflow, installation, configuration, audit trail and PDF reporting.

2026-10-04T00:53:00Z

Created documentation page for Change Control Pro v1.0.0, including features, workflow, installation, configuration, audit trail and PDF reporting.

New page

=Change Control Pro=

[[File:01_change_control_pro_cover.png|center|900px|Change Control Pro]]

'''Change Control Pro''' is a professional Change Control module for Dolibarr designed to manage the complete lifecycle of controlled changes.

The module provides a structured workflow covering change request creation, impact assessment, risk assessment, approval, implementation, effectiveness verification and controlled closure.

It is particularly suitable for organizations that need structured quality processes, traceability and accountability within Dolibarr.

==Main Features==

*Automatic Change Request references in the format '''CHG-YYYY-####'''
*Change Request creation and tracking
*Priority, owner and target date management
*Impact Assessment
*Multiple affected items per Change Request
*Risk Assessment
*Automatic risk score calculation
*Approval and rejection workflow
*Approval history
*Implementation / Action Plan
*Responsible users and due dates
*Implementation progress tracking
*Effectiveness Check
*Controlled closure
*Automatic Audit Trail
*Previous and new values recorded for important modifications
*PDF Change Control report
*Responsive desktop and mobile interface
*English and Romanian translations

==Workflow==

The standard workflow is:

'''Draft → Impact Assessment → Risk Assessment → Pending Approval → Approved → Implementation → Effectiveness Check → Closed'''

Each stage must be completed before the Change Request can proceed to the next stage.

A closed Change Request becomes read-only.

==Creating and Tracking Change Requests==

[[File:02_create_and_track_change_requests.png|center|900px|Create and Track Change Requests]]

A new Change Request can be created directly from the Change Control Pro menu.

Each Change Request includes:

*Automatic reference
*Title
*Change type
*Priority
*Owner
*Target date
*Description
*Reason for change
*Current status
*Risk level

The reference is generated automatically using the format:

'''CHG-YYYY-####'''

The Change Request list provides search and filtering capabilities and gives users a quick overview of all active and completed changes.

==Impact Assessment==

[[File:03_impact_and_risk_assessment.png|center|900px|Impact Assessment and Risk Assessment]]

The Impact Assessment stage identifies the elements that may be affected by the proposed change.

Supported impact types include:

*Document / SOP
*Product
*Specification
*Equipment
*Supplier
*Training
*CAPA / Deviation
*Software
*Other

Each Impact Item can contain:

*Impact type
*Affected item
*Assessment
*Responsible user
*Due date
*Status
*Comment / justification

Multiple Impact Items may be added to the same Change Request.

All required Impact Items must be completed before the workflow can proceed to the Risk Assessment stage.

==Risk Assessment==

The Risk Assessment stage evaluates the risk associated with the proposed change.

The module records:

*Risk description
*Severity
*Probability
*Detectability
*Risk score
*Risk level
*Mitigation / controls
*Responsible user
*Due date
*Status

The calculated risk score is based on:

'''Severity × Probability'''

Risk levels are classified automatically.

Typical ranges are:

*Low: 1–4
*Medium: 5–9
*High: 10–16
*Critical: 17–25

Detectability is recorded separately and is available as additional risk information.

The Risk Assessment must be completed before the Change Request can be submitted for approval.

==Approval Workflow==

[[File:04_approval_workflow_and_implementation_plan.png|center|900px|Approval Workflow and Implementation Plan]]

After the Risk Assessment has been completed, the Change Request can be submitted for approval.

The approver can:

*Approve the change
*Reject the change
*Add an approval comment or justification

A rejection requires a justification.

Every decision is recorded in the Approval History with:

*Decision
*Approver
*Decision date
*Approval comment / justification

Approved Change Requests move to the Implementation stage.

==Implementation / Action Plan==

The Implementation / Action Plan allows users to define and track all activities required to implement the approved change.

Each implementation action includes:

*Action / task
*Responsible user
*Due date
*Status
*Completion date
*Evidence / result
*Comment

The module displays implementation progress automatically, for example:

'''0 / 1 actions completed – 0%'''

or:

'''1 / 1 actions completed – 100%'''

All implementation actions must be completed before the Effectiveness Check can begin.

==Effectiveness Check==

[[File:05_effectiveness_check_and_controlled_closure.png|center|900px|Effectiveness Check and Controlled Closure]]

The Effectiveness Check verifies that the implemented change achieved the intended result.

The following information can be recorded:

*Effectiveness criteria
*Verification method
*Reviewer
*Planned review date
*Actual review date
*Result
*Evidence / observation
*Comment / conclusion

A typical result is:

'''Effective'''

A Change Request can only be closed after an Effective Effectiveness Check.

Once closed, the Change Request becomes read-only.

==Audit Trail==

[[File:06_audit_trail_and_pdf_report.png|center|900px|Audit Trail and PDF Report]]

Change Control Pro includes an automatic read-only Audit Trail.

Important activities are recorded automatically, including:

*Change Request creation
*Change Request update
*Impact Item creation
*Impact Item update
*Risk Assessment actions
*Approval decisions
*Implementation actions
*Effectiveness Check actions
*Workflow transitions
*Change Request closure
*Deleted records

Audit entries may contain:

*Change Request reference
*Event
*User
*Date / time
*Object
*Details
*Previous value
*New value

For important modifications, the module records both the previous and the new values to improve traceability.

The Audit Trail is read-only.

==PDF Report==

Change Control Pro can generate a complete PDF report for a Change Request.

The PDF report may contain:

*General information
*Impact Assessment
*Risk Assessment
*Approval History
*Implementation / Action Plan
*Effectiveness Check
*Audit Trail

The PDF can be used as part of the change documentation or quality records.

==Permissions==

Permissions can be assigned through the standard Dolibarr user and group permission system.

Depending on the assigned permissions, users may be allowed to:

*Read Change Requests
*Create or modify Change Requests
*Delete Change Requests
*Participate in workflow actions
*Approve or reject Change Requests
*View Audit Trail information

Administrators receive permissions automatically when the module is activated.

Permissions for other users or groups must be assigned manually when required.

==Installation==

1. Download the Change Control Pro ZIP package.
2. In Dolibarr, open:

'''Home → Setup → Modules / Applications → Deploy / Install external app/module'''

3. Upload the ZIP package.
4. Activate '''Change Control Pro'''.
5. Review the module permissions.
6. Grant permissions to the required users or groups.

No additional external service is required.

==Configuration==

After activation, the module is available from the Dolibarr menu.

Recommended configuration steps:

#Activate Change Control Pro.
#Review user and group permissions.
#Confirm that the required users can access the module.
#Create a test Change Request.
#Verify the complete workflow before using the module in production.

==Mobile and Responsive Interface==

Change Control Pro has been designed for use on both desktop and mobile devices.

The interface adapts to smaller screens and provides mobile-friendly cards for:

*Change Requests
*Impact Assessment
*Risk Assessment
*Implementation actions
*Effectiveness Checks
*Audit Trail records

This allows users to review and manage Change Control activities from mobile devices as well as desktop systems.

==Compatibility==

'''Module version:''' 1.0.0

'''Dolibarr compatibility:'''

*Dolibarr 23.x
*Dolibarr 24.x

'''PHP:'''

*PHP 7.4 or later

==Typical Use Cases==

Change Control Pro can be used for:

*SOP revisions
*Quality system changes
*Process changes
*Equipment changes
*Supplier changes
*Software changes
*Training-related changes
*Product or specification changes
*CAPA-related changes
*Laboratory procedure changes
*Other controlled organizational changes

==Benefits==

Change Control Pro helps organizations:

*Standardize Change Control activities
*Assign clear responsibilities
*Improve traceability
*Evaluate risks before implementation
*Record approval decisions
*Track implementation progress
*Verify effectiveness
*Maintain a complete audit history
*Generate structured PDF documentation
*Prevent uncontrolled modification after closure

==Support==

For support, questions or feedback:

'''Email:''' support@panciucsoft.com

'''Website:''' https://panciucsoft.com/

==License==

Change Control Pro is distributed according to the license included in the module package.

==See Also==

*[[Complementary_modules|Complementary modules]]
*[https://www.dolistore.com/ DoliStore]
*[https://panciucsoft.com/ PanciucSoft]