Welcome to the FOLIO Wiki
Spaces
Apps
Templates
Create
Technical Designs and Decisions
All content
Space settings
Shortcuts
Decision log
Decision log
This trigger is hidden
Content
Results will update as you type.
Architectural Designs and Proposals
Decision log
Feature Level Designs and Decision Logs
Acquisitions and Finance Designs
Acquisition Units
•
Acquisitions API migration enhancements
•
Attaching Documents to Invoices
•
Batch Voucher Exports
Business Use Cases
•
Cross-module migration solution design
Data consistency and message driven approach
Edge-orders: Configuration Based Routing
•
Export Orders to csv
Finance Data Model
Fiscal year rollover
Gobi integration
Inventory and Receiving Designs
•
Order Alerts
•
Orders - Custom fields
•
Orders Event Log
•
Orders search performance improvements
Perfomance testing
•
EBSCONET order renewal integration testing
•
EDIFACT order export performance testing
•
Fiscal year rollover testing
•
Prorated Invoice Adjustments
•
Quartz Scheduling Implementation in mod-data-export-spring
•
SPIKE: Investigate using style sheet for printing vs convert to PDF on backend
•
Supporting Package Orders
•
Central Ordering For a Consortium
Apache Kafka Messaging System
Authentication and Authorization
Authority control
Cataloging
Circulation
Configuration
Cross-functional
Data Export
Data Import
•
ERM
Fees/fines
Folio logging solution
Inn-Reach Integration
Inventory
OAI-PMH
Platform
PubSub
Remote storages integration
RTAC
Search
Users
Guidelines and Best Practices
Migrated Decisions
•
Stripes v4 migration guide
Apps
draw.io Diagrams
Technical Designs and Decisions
/
/
Acquisitions and Finance Designs
/
Perfomance testing
Summarize
Perfomance testing
Dennis Bridges
Owned by
Dennis Bridges
Jul 18, 2022
Loading data...
Pages outlining a plan for performance testing for specific features or sets of features.
{"serverDuration": 30, "requestCorrelationId": "43a3d7e86daf4e61a1f35e5e428bb397"}