Planning for performance

WFM has performance requirements for its features. These performance requirements describe supported use cases that ensure acceptable performance of the application. Exceeding the performance requirements can cause performance issues such as drastic increases to load times when users access screens or perform actions. Performance concerns caused when exceeding these performance requirements are not considered defects, but customers can submit enhancement requests through ERS if they have business requirements that require going above the documented usage levels.

These are examples of performance requirements types that are described below:
  • The maximum amount of data that can be rendered in a specific screen
  • The maximum number of records of a particular type that can exist in the database
  • The maximum number of transactions over a given time period

You must review the performance requirements prior to the implementation phase of projects to determine if the features of the application are appropriate for a particular use case. You must also consult these requirements when organizing the structure of data elements in WFM to ensure that business requirements can be satisfied while providing the best possible performance. The performance requirements assume that all components of the WFM deployment, such as client workstations and application servers, meet the specified minimum hardware and software requirements.

See Hardware and software platforms for details on these requirements.

Performance requirements are only included for a subset of the features and modules of the WFM application. Performance requirements for additional features and modules will be added in future versions of this guide.