QAD Integrated Customization Toolkit (ICT)

1. QAD Integrated Customization Toolkit (ICT) Romeo Sequeira QAD

2. Agenda • Challenges • Non-Intrusive Principles • Demo • Solution • Key Features • Deliverables • Case Study • Benefits

3. Challenges - Statements “We can only create customizations if we have the full source code” “Customizations are too expensive and take too long to deliver” “Can’t migrate (upgrade), too many (intrusive) customizations” “Due to intrusive customizations, adding ECO’s (QAD Support patches) takes too much time”

4. Why Customize? alternate user interfaces analysis gathering many reasons extended attributes extended validation simplification default values business rules

5. What if you could customize QAD applications that: • Were not intrusive to QAD source code • Followed a set of development standards • Were easy to migrate to the latest release of QAD Enterprise Applications • Allowed for quick modifications as your business needs change • Included automatic tracking, tracing and debugging features

6. Custom Software QAD Integrated Customization Toolkit Non-Intrusive Development QAD Enterprise Applications (Character/Desktop/.NetUI & GUI)

7. User Interface Business Logic Database Security / Role Model QAD Standards Tracking & Tracing Control & Debugging QAD ICT Components QAD Integrated Customization Toolkit

8. DEMO

9. ICT Main Menu All ICT screens are available under 90 menu. Note 90.12 is a collection menu of all developer screens that can be fired up from anywhere (in terminal mode) using a hot key (ctrl-O)

10. ICT Tasks You can create and select a task when you start a new customization . As soon as its tested and ready for production, you can then dump all the data for that Taskid.

11. Examples of Different Types of ICT Triggers • Frame & Field Properties • User Interface • Default Values • Validate fields • Database Triggers • ICT Custom Programs

12. ICT Frame & Field Properties Using this screen you can modify the add, delete & modify field characteristics

13. ICT User Interface Custom business logic can be invoked from the UI maintenance screen.

14. ICT Validate Field Validation is set up in this screen. Note there are 3 ways to define validations with a wild character string, using gen codes or call a custom program. Hard or soft validation is specified using the type and message number similar to pxmsg.i

15. ICT Default Default value for a field is defined this screen. The default value can be forced (or when empty only) with constant value or derived from a custom program.

16. ICT Database triggers Database triggers are defined using the Table and Field Trigger screens. Each of the triggers can intercepted in the Subscriber Screen (Next Page)

17. ICT Subscribe Database triggers are intercepted in the Subscriber Screen (Next Page) and a Custom Program is called. A template is automatically provided .

18. ICT Custom Programs ICT generously provides templates for each type of screen where custom code can be called. With minimal effort, an existing custom program can be called from ICT

19. .NET versus ICT • .NET • Simplified screens • Hide and disable fields • Set Default values • Make any field required • Skip through frame • Add user defined fields • Create a new frame (for user defined fields) • ICT • More complex changes • Works on all screens, if you can see a field/frame you can modify it • Add screens / change business logic • Trigger based enhancements/ turn on or off standard processing logic during run-time • Upward compatible non-intrusive and intrusive customizations • Tracking and tracing

20. The Solution • The ICT deployment includes: • A methodology for non-invasive custom development • A structured design strategy • A set of development standards • And the Toolkit (ICT) • It eliminates or significantly reduces the need to change standard source code • Additionally… • No changes are required in any propath definition • Monitor, track and trace features are built in

21. Key Features – ICT Release 3.0 • User Interface • Option to change position, re-format, re-label & disable standard fields without coding • Define custom validation rules, defaults and global values • Ability to intercept on UI triggers and execute custom code. • Database • Ability to intercept on any database table, field events and execute custom code. • Define & manage all session triggers without having to bring down the database • Business Logic • Domain dependency embedded in ICT • Run any custom program before/after gprun.i • Option to de-activate standard source code • Option to switch on/off intrusive tags • Supports CIM processing • Development features • Copy ICT trigger set to other function/frames/groups • ICT menu via Ctrl key • Managed by Task ID: Work In Process/Complete status ICT trigger development • Others • Security on named developer – by User Name, Groups or Roles • Support ORACLE database • Extended export/import options of ICT Data • Source code (Templates) • Any changes made in character version is instantly visible in .Net

22. Deliverables of the QAD ICT Implementation • Runtime version for ICT • Enables users to run customizations developed by ICT • Required for each user running QAD Core Enterprise Applications (Base Bundle) • Development Toolkit (ICT) • Enables you or your service partner to develop customizations • Annual maintenance • Installation Services consisting of • Installing the ICT on a server • Training custom developers (2 day training) • Remote coaching & support during first 3 months • Documentation & templates

23. Case Study – Arthrex Inc Original development • Standard customizations • Intrusive changes to QAD maintenance programs • 50+ programs Re-designed using ICT • Time Spent on ICT Migration: less than 2 weeks Benefits achieved • Fully Non-Intrusive • Visibility: Custom programs now easily accounted for with ICT • Manageable: All customization documented and managed in ICT • Consistent behavior with .NET User Interface • No Hassle future patch installation and upgrades to new service pack and release • Easier implementation of future business rules and customizations using ICT methodology

24. Case Study – Lincoln Red Storno Original development (localization): • Red Storno functionality with QAD MFG/PRO 9.0 (35 functions) • Extremely intrusive development • Time Spent on Development and Migration • Original development time - 200 days • Migration to QAD MFG/PRO eB2 - 120 days Re-designed Red Storno functionality in QAD applications using ICT: • Time Spent on Development and Migration • New development time - 20 days • Migration to QAD eB2.1 - 5 days Reduction achieved: • Re-Design solution ~ 90% • Migration ~ 96%

25. Key Benefits • Reduce initial development costs of customizations by 15-20% • Reduce costs of migrating customizations by 50-70% • Apply QAD support patches when required • Increase portability to new releases • Quickly and easily adapt applications to changing business requirements • Enable changes to applications while running standard unmodified applications

26. To Learn More… • Contact your Sales Representative or send a request to services@qad.com • See www.qad.com / Global Services / Consulting / QAD Integrated Customization Toolkit data sheet

27. Questions and Answers Thank You