https://github.com/manduco/truvistaxpraxedo_integration
Automated data integration between TruVista’s ERP/CRM and Praxedo WorkOrder system using .NET ETL processes.
https://github.com/manduco/truvistaxpraxedo_integration
automation business-process-automation crm dotnet enterprise-integration erp etl-process field-service-management manduco praxedo scheduled-task
Last synced: 2 months ago
JSON representation
Automated data integration between TruVista’s ERP/CRM and Praxedo WorkOrder system using .NET ETL processes.
- Host: GitHub
- URL: https://github.com/manduco/truvistaxpraxedo_integration
- Owner: Manduco
- Created: 2025-02-01T23:59:15.000Z (4 months ago)
- Default Branch: master
- Last Pushed: 2025-03-23T22:16:19.000Z (2 months ago)
- Last Synced: 2025-03-23T23:23:51.648Z (2 months ago)
- Topics: automation, business-process-automation, crm, dotnet, enterprise-integration, erp, etl-process, field-service-management, manduco, praxedo, scheduled-task
- Language: C#
- Homepage:
- Size: 376 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# TruVista & Praxedo Integration
## Table of Contents
1. [Overview](#overview)
- [Solution Architecture](#solution-architecture)
- [Wireframes (Draft)](#wireframes-draft)
2. [User Stories](#user-stories)
3. [Use Cases](#use-cases)
- [Use Case Diagram](#use-case-diagram)
4. [Requirements](#requirements)
5. [Repository Contents](#repository-contents)
6. [Next Steps](#next-steps)
7. [Requirements Table](#requirements-table)
8. [Entity Relationship Diagram](#Entity-Relationship-Diagram)
9. [UML Class Diagram](#UML-Class-Diagram)
## Overview
This project provides basic data integration between **TruVista’s CHR_Omnia360 ERP/CRM** application and **Praxedo’s WorkOrder and Dispatch application**. The solution is an **OnPremise .NET Application** that extracts, transforms, and loads (ETL) data between the two systems, ensuring accurate synchronization.
### Solution Architecture
*This diagram outlines the major components of the system integration.*
### Wireframes (Draft)
*Preliminary wireframe sketch of the application UI workflow.*
### User Stories
1. **System Administrator**
*As a system administrator, I want the integration to handle API authentication automatically using secure credentials so that I don’t have to configure it manually.*
2. **Operations Manager**
*As an operations manager, I need work orders from CHR to be automatically synced to Praxedo and vice versa so that my team can focus on field operations instead of data entry.*
3. **Data Analyst**
*As a data analyst, I want account and contact information to be consistently updated between CHR and Praxedo so that reporting and customer records remain accurate.*
4. **Field Technician**
*As a field technician, I need completed work orders in Praxedo to reflect updates in CHR in real time so that my job completion status is accurately recorded.*
5. **DevOps Engineer**
*As a DevOps engineer, I need comprehensive logging and error-handling for each data sync so that I can quickly diagnose and resolve any integration failures.*
## Use Cases
[📄 View Detailed Use Cases](docs/use-cases.md)
## Use Case Diagram
*This diagram visualizes the actors and system interactions.*
## Requirements
- **Programming Language:** C# .NET
- **Database:** SQL Server
- **API Integration:** REST/SOAP (depending on Praxedo’s API)
- **Authentication:** Secure API token-based authentication
- **Logging & Error Handling:** Event logs, retry mechanisms
## Repository Contents
- `README.md` (This file)
- `docs/` (Design documents, including user stories, use cases, and architecture diagrams)
- `images/` (Diagrams for architecture, wireframes, and use case models)
- `src/` (Project source code)
- `logs/` (Error and execution logs)
---
## **Next Steps**
- [ ] Finalize wireframe sketches using **Draw.io** or **Pencil Project**.
- [ ] Create architecture and use-case diagrams.
- [ ] Populate repository with initial `.NET` project structure.
- [ ] Set up API credentials and data mapping in CHR and Praxedo.
---
## Requirements Table
| ID | Requirement Description |
|---------|--------------------------|
| RQ-001 | The system shall synchronize accounts and contacts from CHR to Praxedo in real-time to ensure accurate customer records. |
| RQ-002 | The system shall allow work orders to flow from CHR to Praxedo and back with status updates occurring within 5 minutes. |
| RQ-003 | The integration shall verify the existence of product records in both systems using a common key. |
| RQ-004 | The system shall generate error logs for failed synchronizations and notify administrators via email within 10 minutes of failure detection. |
| RQ-005 | The integration shall support scheduled task execution, running automatically at predefined intervals without manual intervention. |
| RQ-006 | The system shall provide a logging mechanism to track all data changes and transactions between CHR and Praxedo for audit purposes. |
| RQ-007 | The system shall implement retry logic for failed synchronizations, ensuring data consistency and reducing manual intervention. |
| RQ-008 | The integration shall support role-based access control (RBAC) to restrict access to configuration settings and logs to authorized users only. |
| RQ-009 | The system shall include debugging functionality to test and validate integration behavior within the evaluation instance of Praxedo, allowing developers to simulate data flows and detect issues before deployment. |
### Entity Relationship Diagram
---
### UML Class Diagram
---
We are off!🚀