Technische Dokumentation gbrma
Aus Wikizone
Umsetzung Details[Bearbeiten]
Regeln etc...
Status updates[Bearbeiten]
Import[Bearbeiten]
Identifikation der Felder[Bearbeiten]
- Stelle der Felder wird angegeben
Kontrollen[Bearbeiten]
- Kontrolle der Felderanzahl
- Erstes Feld muß Nummer mit Beginn RMA (RMAxxxxxx) sein.
Status aktualisierung[Bearbeiten]
- Neue RMA hat Status 0
- Von User gesendet Status 1 (RMA Controller)
Change Log[Bearbeiten]
1.96 - Log Files[Bearbeiten]
Im noch nicht genutzten RMA Datenbankfeld additionalInformation werden Log Informationen gespeichert. Dazu speichern wir als Text folgende Daten gespeichern, die mit den Stati zusammenhängen.
Datumsangaben im ERP File[Bearbeiten]
ERP Feld - Bezeichnung im ERP - Bezeichnung für Logfile (en) - Korrespondierender Status ---------------------------------------------------------------------------------------- 2 - Belegdatum - Date of status change - Jede Änderung 1 - Wareneingangsdatum - Date of receipt - Offen (2) 6 - KVA gedruckt am - Quotation sent - Warten (4) 7 - KVA freigegeben - Quotation approved - In Versand (5) 8 - Versanddatum - Date of return shipment - Erledigt (6)
1.95 - Neue Stati[Bearbeiten]
Neue Stati[Bearbeiten]
- Neuer Status Dateiaufbau
"Nr.";"Wareneingangsdatum";"Belegdatum";"Debitorennr.";"Name";"Bearbeitungsstatus";"KVA gedruckt am";"KVA freigegeben";"Versanddatum" "RMA31310";"08.02.2016";"21.04.2016";100333;"TES America Andina LTDA.";"Erledigt";"11.02.2016";"21.03.2016";"26.04.2016" "RMA31370";"08.02.2016";"26.04.2016";100013;"CMV Hoven GmbH";"Erledigt";"09.02.2016";"25.04.2016";"28.04.2016" ...
- Neuer Status Reihenfolge
Nr Status Beschreibung Statusname im ERP System 0 Not finished wie gehabt na 1 Request sent RMA request has been sent. Units not received na 2 On hold NEU: Units received Offen 3 In process wie gehabt In Bearbeitung 4 Waiting for approval NEU: Quotation sent, waiting for approval Warten 5 Unit(s) ready for dispatch NEU: Unit(s) are ready for dispatch In Versand 6 Unit(s) returned NEU: RMA closed Erledigt
- Alter Status Dateiaufbau:
RMA-Nummer;Eingangs-Datum (Erfassung im ERP-System);Datum der letzten Bearbeitung;Debitoren-Nummer;Debitor / VP;Status RMA2;22.01.2015;11.02.2015;100119;Air-Met Scientific Pty Ltd;Freigegeben ...
- Alte Status Reihenfolge
Nr Status Beschreibung Statusname im ERP System 0 Not finished (User muß Request senden) na(Nur im RMA System vorhanden) 1 Open (User hat request gesendet Geräte noch nicht bei Narda) na 2 In process (Eingang bestätigt) Freigegeben 3 Waiting for approval (Narda sent quotation / Kostenvoranschlag) Offen 4 Unit(s) returned Beendet
Umsetzung bis Version 1.9[Bearbeiten]
Implementation List
Device Model OK New, Show, Edit, Delete Devices (Backend) OK RMA Model OK New, Show, Edit, Delete RMAs (Backend) OK New, Show, Edit, Delete RMAs (Frontend) OK Generate RMA no. based on RMA-Type OK Find RMAs based on FE-User OK Access Checks for all actions TODO Connect Device Repository OK Selecting Devices from Device Repository and store relation (Backend) OK Selecting devices from Device Repository and store relation (Frontend) OK Prevent loss of RMA Data in case of login or connection problems OK Preselect Device Class before selecting the actual device OK If RMA contains device show only devices of same class OK Visual hint main devices (type1 devices) OK Main rule: Only one main device allowed OK Not finished rmas can be deleted by user (in case of errors) OK No access for finished rmas by user OK Add metadata (serial, error description) to device OK Finishing rma locks rma OK - Obsolete Implement RMA State OK Finishing rma sends mail to admin OK Visual hint "finished devices" (css-based) OK - Obsolete Visual hint for closed RMAs - OK Possible actions depending on finishing state OK Deleting RMAs is possible after finishing RMA but not editing - OK Deleting RMAs is locked when state 2 (Released) is reached - OK Possibility for showing additional data based on device type - OK Possibility for checking additional "device selecting rules" - OK Adding check rule for nbm550, nbm520 - OK Implementing PDF generation - OK Implementing PDF Attachment - OK Additional action for ACC Checklist - OK Di vide Device Selector into main devices and auxiliary devices via tabs - OK Add modification field to devices - OK Add ACC possible field to devices - OK Add repair discontinued field to devices - OK Preselect 2nd Device Selector Tab after first device for better user experience - OK Extend devicefamily model to hold fegroup for access control - OK Extend deviceclass to hold devicefamily for access control - OK Add ts option to turn on devicefamily access - OK Implement devicefamily access
Feuser is only allowed to create RMAs from families belonging to specific deviceclasses - OK
Previously generated RMAs can be seen anyway - OK
Add check for express rma request - OK Add rules for IDA/Radman - OK ERP synchronisation - OK Extend fe_users to hold clientid - OK add ts option to use clientid for rma identification (default is userid) - TODO Implement user selection clues for special devices (NBM,IDA) - OK show hints if repair / calibration is not possible for this device - OK only show acc device classes possible for acc - OK don't show service checkboxes for acc - OK Preselect 1st Device Selector Tab when SRM after 1st device - OK Admin Mail when rma has been deleted by user - OK