Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
YouTube Security VideosVisual Studio Code: VS Code Learn: Extending Agents(24.09.2026 um 21:00 Uhr)
•
YouTube Security VideosGoogle Cloud Tech: Turn Audio into Action with Gemini 3.5 Transcribe(24.09.2026 um 21:00 Uhr)
••••
Unix & Linux ServerUSN-8815-1: libass vulnerabilities(24.09.2026 um 16:57 Uhr)
•••••
YouTube Security VideosVisual Studio Code: VS Code Learn: Extending Agents(24.09.2026 um 21:00 Uhr)
•
YouTube Security VideosGoogle Cloud Tech: Turn Audio into Action with Gemini 3.5 Transcribe(24.09.2026 um 21:00 Uhr)
••••
Unix & Linux ServerUSN-8815-1: libass vulnerabilities(24.09.2026 um 16:57 Uhr)
•••••
Intelligence View
⚡ tsecurity.de Intelligence

Implementing Quotation from Materials and Scheduled Maintenance in Riviera Industrial ERP

Implementing Quotation from Materials and Scheduled Maintenance in Riviera Industrial ERP   TL;DR: I added features to generate quotes from materials and scheduled maintenance to the Riviera Industrial ERP. This involved updating the …

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!




Implementing Quotation from Materials and Scheduled Maintenance in Riviera Industrial ERP



 



TL;DR: I added features to generate quotes from materials and scheduled maintenance to the Riviera Industrial ERP. This involved updating the Prisma schema, implementing new API routes, and modifying existing components.






The Problem



The Riviera Industrial ERP lacked the functionality to generate quotes directly from materials and to manage scheduled maintenance. This resulted in manual workarounds and inefficiencies in the quoting process and maintenance planning.






What I Tried First



Initially, I attempted to extend the existing quote functionality to include material-based quoting. However, this approach led to complexities in handling the relationships between materials, quotes, and production processes. I then decided to refactor the Prisma schema to better support these new features.






The Implementation






Updating the Prisma Schema



I modified the prisma/schema.prisma file to include new models and relationships for materials and maintenance:




model QuoteItem {
unitPrice Decimal @default(0) @db.Decimal(12, 2)
total Decimal @default(0) @db.Decimal(12, 2)
process ProductionProcess? @relation(fields: [processId], references: [id])
// ...
}

model MaintenanceOrder {
id String @id @default(cuid())
description String
scheduledAt DateTime
// ...
}









New API Routes



I created a new API route for generating quotes from materials in src/app/api/quotes/route.ts:




export async function POST(req: NextRequest) {
const { materialId, quantity } = await req.json();
const material = await getMaterial(materialId);
const unitPrice = material.unitPrice;
const total = unitPrice * quantity;

// Create a new quote item
const quoteItem = await prisma.quoteItem.create({
data: {
description: material.description,
unitPrice,
total,
// ...
},
});

return NextResponse.json({ quoteItem });
}









Maintenance Pages



I added new pages for managing maintenance orders in src/app/operations/maintenance/[id]/page.tsx, src/app/operations/maintenance/new/page.tsx, and src/app/operations/maintenance/page.tsx.






Component Updates



I updated the src/components/shared/NewQuoteForm.tsx component to include material-based quoting:




import { listMaterials } from "@/server/repositories/materials";

export default function NewQuoteForm() {
const [materials, setMaterials] = useState([]);

useEffect(() => {
listMaterials().then((data) => setMaterials(data));
}, []);

// ...
}









Key Takeaway



The key takeaway from this implementation is the importance of carefully planning and executing schema changes and API routes when adding new features to an existing application.






What's Next



Next, I plan to integrate WhatsApp notifications for quote requests and maintenance orders. This will involve setting up a WhatsApp API and modifying the existing notification system.






vibecoding #buildinpublic #rivera-industrial-erp #quotation-system #maintenance-management






Part of my Build in Public series — sharing the real process of building Building Riviera Industrial ERP from Playa del Carmen, México.



Repo: zaerohell/riviera-industrial-erp · 2026-07-01



#playadev #buildinpublic

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - Implementing Quotation from Materials and Scheduled Maintenance in Riviera Industrial ERP
id: a32c5b85-7877-4a17-b800-431282c11e37
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "Implementing Quotation from Ma" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Implementing Quotation from Materials an")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Implementing Quotation from Materials an*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Implementing Quotation from Materials an"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Implementing Quotation from Materials an.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Implementing Quotation from Materials and Scheduled Maintenance in Riviera Industrial ERP

Thematisch verwandte Begriffe: Implementing, Quotation, from, Materials · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-61782 | Rsdoctor is a build analyzer tailored for projects built with Rspack. Pr…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel • Rechts: nächster Artikel • unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel TTP ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...
↗ Original-Quelle