Best Practices: Custom JSPs with Workbrain
- Steve Ahn
- Jul 25, 2017
- 1 min read
While utilizing core Workbrain functionality is the most cost effective business solution, it is sometimes necessary to build custom JSPs to streamline user inputs or provide feature-rich screens without breaking core. Utilize the following best practices when integrating custom JSPs into your Workbrain solution.
JSPs should broker data records, most typically overrides.
Always build a new JSP or copy an existing JSP. Modifying core JSPs will have problems during hotfix or version upgrades.
Build for consistency. While Workbrain may not have the most responsive UI, matching the look and feel of the existing application will help user adoption. Use DBLookups, DatePickers, and Load/Save buttons.
Enrich where necessary. Ajax calls are great for real-time data validations, but doesn't fit into the Workbrain action pattern of loading and saving.
Do use localization and field configuration tags. You never know when a read-only user may need access to the screen, or if your business expands to other languages!
Do wireframe a solution. Seeing the UI can help articulate business logic. More on this later!
- S
תגובות