tilbudgivern/apitest/BATCH_13_PLAN.md

Batch 13 Plan - Medium Mutations (Update Operations - Part 1)

Strategy: Update Operations

Batch 13 continues the mutation phase with 30 update operations - mutations that modify existing data but don't create or delete records.

Total Update Mutations: 78 (from analysis)

Risk Level: 🟡 MEDIUM

• Modify existing records
• Don't create new data
• Don't delete data
• Can be partially tested with valid IDs
• May affect production state

Batch 13 Focus: First 30 Update Mutations

Endpoints (30 total)

Account/Finance (2)

1. updateAccount - Update account information
2. updateFinanceAgreement - Update finance agreement

Appendix (3)

3. updateAppendix - Update appendix
4. updateAppendixLine - Update appendix line
5. updateAppendixLines - Update multiple appendix lines (bulk)

Case Management (5)

6. updateCase - Update case information
7. updateCaseConfirmationDraftLine - Update case confirmation draft line
8. updateCaseMaterial - Update case material
9. updateCaseStatus - Update case status
10. updateCaseTemplate - Update case template
11. updateCaseType - Update case type

Contact/Customer (5)

12. updateContactPerson - Update contact person
13. updateCustomer - Update customer information
14. updateCustomerCategory - Update customer category
15. updateCustomerDocument - Update customer document
16. updateCustomerEmployeeType - Update customer employee type

Creditor/Invoice (3)

17. updateCreditor - Update creditor
18. updateCreditorInvoice - Update creditor invoice
19. updateCreditorInvoiceInboundLine - Update creditor invoice inbound line
20. updateCreditorInvoiceInboundLines - Update multiple creditor invoice lines (bulk)

User/Department (2)

21. updateCurrentUser - Update current logged-in user
22. updateDepartment - Update department

Delivery/Discount (3)

23. updateDeliveryAddress - Update delivery address
24. updateDiscountGroup - Update discount group
25. updateDiscountGroupInterval - Update discount group interval

Documentation (4)

26. updateDocumentationFile - Update documentation file
27. updateDocumentationFileComment - Update file comment
28. updateDocumentationFolder - Update documentation folder
29. updateDocumentationFolderShare - Update folder sharing

Event (1)

30. updateEvent - Update event

Testing Strategy

For each mutation:

1. Introspect arguments - Get required parameters and input types
2. Create documented script - With parameter validation
3. Add safety warnings - Document what gets modified
4. Mark as placeholder - Most can't be safely tested in production
5. Note testable candidates - E.g., updateCurrentUser might be safe

Expected Pattern:

Most update mutations follow this pattern:

mutation UpdateX($id: Int!, $input: XInput!) {
  updateX(id: $id, input: $input) {
    id
    ...fields
  }
}

Testability Assessment:

• ✅ Possibly testable: updateCurrentUser (only affects test user)
• ⚠️ Requires IDs: All others need valid production IDs
• 🔴 Production impact: Most modify real business data

Success Criteria

• ✅ All 30 scripts created with documentation
• ✅ Clear parameter requirements documented
• ✅ Safety warnings included
• ✅ Testable mutations identified
• ✅ Update progress: 279 → 309/507 (61%)

Implementation Approach

Given the large number of mutations and their complexity:

1. Create placeholder scripts with consistent structure
2. Document required parameters from introspection
3. Add safety warnings based on mutation purpose
4. Mark few as testable (like updateCurrentUser)
5. Provide implementation notes for future development

Next Batches

• Batch 14: 30 more update mutations
• Batch 15: Remaining update mutations (~18)
• Batch 16-22: Create/delete mutations (dangerous)

---

Batch 13 Goal: Document all basic update operations and establish update mutation patterns.