1. QAD.NET UI – Tips n Tricks Stacy Elwood, BravePoint MWUG March 2010

2. Agenda  Introduction  Multiple Servers/Configurations  Return Multiple Fields from a Browse  Browse Maintenance Security  Reporting Engine  Operational Metrics  Questions and Answers  Next Steps

3. .NET UI in Multiple Environments  Challenge: In today’s world, there are often multiple QAD.NET UI environments, including test servers, development servers, and production. Installing.NET UI from a new server overwrites the initial installation.  Solution: Set up each server with a unique icon and client destination folder.

4. Change icon name  Change the icon name in /apps/tomcat/webapps/qadhome/client/options.js  By default, this file reads var Vers=“ 2009 SE” Note: Be sure to leave the space in front!

5. Change icon name (SEUG)  Change the icon name in /apps/tomcat/webapps/qadhome/client/options.js  By default, this file reads var Vers=“ 2009 SE” Note: Be sure to leave the space in front!

6. Change client working directory  Change the client working directory in /apps/tomcat/webapps/qadhome/configurations/default/ client-bootstrap.xml  By default, this is &{APPDATA}\QAD\Shell &{APPDATA} =C:\Documents and Settings\userid\Application Data

7. Change client working directory (SEUG)  Change the client working directory in /apps/tomcat/webapps/qadhome/configurations/default/ client-bootstrap.xml  By default, this is &{APPDATA}\QAD\Shell &{APPDATA} =C:\Documents and Settings\userid\Application Data

8. Run the QAD.NET UI Installation

9. Run the QAD.NET UI Installation (ctd)  Choose Install a new instance of this application

10. Run the QAD.NET UI Installation (ctd)  Finish Installation  Icon will be created with new name  Client working directory will be created with new name

11. Run the QAD.NET UI Installation (SEUG)  Finish Installation  Icon will be created with new name  Client working directory will be created with new name

12. Returning Multiple Values from a Browse  Challenge: In some areas of QAD, there is a requirement to return more than one value from a browse. For example, in Voucher Maintenance, if you do a lookup in the Receiver Matching frame, it should also return the PO line. In CHUI, this was handled by scrolling windows.  Solution: Configure.NET to return more than one value from a browse.

13. Return Multiple Fields from a Browse

14.  Configuration file for multiple values is /apps/tomcat/webapps/ /net/lookups/ lookupreturnfields.xml

15. Return Multiple Fields – Other Examples:  Inventory –Location –Lot/Serial –Reference  Work Orders –Work Order Number –Work Order ID/Lot  Routings –Routing –Operation –Start Date

16. Browse Maintenance – Table Security  Challenge: Want to be able to have “power users” create their own browses for their areas. However, once users have menu security access to Browse Maintenance, they can create browses on potentially sensitive data.  Solution: Set up table restrictions for Browse Maintenance by user or user security groups (eg “non-fin”).

17. Browse Maintenance – Table Security  Set up Restricted Tables by user or role in /apps/tomcat/webapps/qadhome/configurations/ /client-session.xml  By default, all tables are visible in Browse Maintenance

18. Operational Metrics  Constantly keep tabs on your data  Set your own criteria  Constant Improvement

19. Operational Metrics DEMO

20. Reporting Framework  Use a browse as the basis for the report  Save Report Criteria to run in a batch  Send reports directly to PDF or Excel  Schedule jobs

21. Operational Metrics DEMO

22. Questions?

23. Next Steps – The Future’s So Bright…  Today, many IT departments face challenges of down- sizing. What can you do to prove you’re worth keeping?  Set up Operational Metrics to help increase data accuracy and drive continual business improvement  Help your users be more efficient

24. Thank You! Stacy Elwood selwood@bravepoint.com