Use Case Design Considerations
When designing applications in Archer, administrators should be aware of the impact design decisions can have on the end-user experience. Rather than limit the user, Archer can support highly complicated use case designs, keeping in mind there may be a trade-off in terms of end-user experience.
The following choices may lead to degraded performance:
- Allowing N-tier searches over 5 or more levels
- Returning or exporting over 10,000 records
- Using more than 7 filters in a report
- Displaying more than 500 fields in an application or questionnaire
- Displaying more than 10 root tabs, or 20 child tabs in an application or questionnaire
- Implementing more than 100 Data Driven Events (or more than 25 Apply Conditional Layout Data Driven Events) in an application or questionnaire
- Using more than 10 record permissions fields in an application or using more than 20 inherited record permission rules
- Allowing cross-reference or history log display grids to display every record slows load times in certain records
- Setting cross-reference fields on records to return more than 20 fields or more than 500 records slows the record lookup process
- Avoiding placing a history log field on the cross-reference side of any relationship containing large numbers of records; a better choice is on the related record side
- Adding Text Area Fields to application or questionnaire slows page load times
In isolation, any of these options may be the right approach, but administrators should be aware of the implications.
