Sage CRM Developers Course Using the Component Manager

Sage CRM Developers Course Using the Component Manager

Looking ahead to the classes DP 01: Introduction to the Development Partner Program DP 02: Entities and the Data Model (Part 1 of 2) DP 03: Entities and the Data Model (Part 2 of 2) DP 04: Implementing Screen Based Rules (Part 1 of 2) DP 05: Implementing Screen Based Rules (Part 2 of 2) DP 06: Screen and User Independent Business Rules DP 07: Workflow (Part 1 of 2) DP 08: Workflow (Part 2 of 2) DP 09: Using the API Objects in ASP Pages (Part 1 of 2) DP 10 : Using the API Objects in ASP Pages (Part 2 of 2) DP 11: Using the Component Manager DP 12: Programming for the Advanced Email Manager DP 13: Using the Web Services API DP 14: Using the Web Services API (Part 2 of 2) DP 15: Coding the Web Self Service COM API (Part 1 of 2) DP 16: Coding the Web Self Service COM API (Part 2 of 2) DP 17: Using the. NET API (Part 1 of 2) DP 18: Using the. NET API (Part 2 of 2)

Agenda What is the Component Manager? How the Component Manager Interacts with Meta Data Tables What is Included in the Component Manager Exceptions Editing Component Files The Component Manager as a Coding Environment. Delivering Components

Use of Extensibility Features Standard License Extensibility License Developer License Import & Export Customisation: New Screen, New List, New Tab, Table Connect, Ext DB, Custom Page Actions, Edit New Blocks O P P Customisation Standard - New Field, Translations, Selections, Re-order fields P P P Can Run ASP Application Extensions P P P Component Manager ASP pages will only run in Standard Install with correct. js files. Can Run. NET Application Extensions P Only DPP Members can create. NET App Extensions

“DPP” Files Received when DP joins program. sagecrmdpp. js sagecrmnolangdpp. js sagecrmdpp. vbs accpaccrmdpp. js accpaccrmnolangdpp. js accpaccrmdpp. vbs Include the appropriate files in your third-party products/installs. These files are supplied to CRM Development Partners only. They will enable your product to run on the CRM installs that do not have the Enterprise Integration Server (EIS). Products using the standard accpaccrm. js will not run on systems without EIS.

‘Record and Edit’ installer Sage CRM’s “install shield” API Do customizations using front end Automatically generate scripting to re-create customizations Allow for editing of script files Allow for install parameters Component Packages contain New objects (e. g. Menus, Tabs, Screens, Database, Workflow) Customized objects ASP & Other Files

Prompting of Component Name and Changed Item

Component Manager

View Details

Apply all Component Changes

Preview installation success checks

Apply all Changes? : Yes

Post Installation Log file: OK, Fail, Overwritten

Data Diagram of Meta Data Dependencies

Component Manager Generated Code Generated code is commented The order of sections is important. Referential Integrity Add. Custom_Tables Add. View Add. Custom_Screen. Objects Add. Custom_Edits Add. Custom_Screens Add. Custom_Tabs Add. Custom_Lists Note: Add. Custom_Data and Run. SQL statements need to be tested thoroughly if they are inserting or deleting on the above tables because of Referential Integrity.

Entity Wizard as Component. Make sure version is correct.

Points to Watch Changing Screens, Lists, Tabgroups If something added to a grouped object Component manager scripts out entire group Edit script to remove changes not required. When a component installed, Views are Rebuilt and Metadata is refreshed when views are rebuilt they are dropped and then recreated because views are dropped potentially any structure like lists and screens that use views would return an error if accessed before the view is recreated therefore when installing a component all users should be excluded from the system. There is no uninstall before carrying out an install of a component you should backup a production system. the best recovery is to restore the database before the component was run. If you are already excluding users from the system - this then is an ideal time to take a backup.

Dos and Don’t’s Component Dos Start a new component for new customisations – Consider a new component a day. You can merge them afterwards Create customizations in small unit components – (e. g. all the Company related customizations, all the Cases related changes and then all the new Project entity related changes) – but these would not be the final deliverable – The final deliverable 'component' would be made by amalgamating the small units. Give components meaningful names – Easier to manage. – The Description not the file name is shown when loading. Make use of the ecf file parameters to control your components – E. g. 'Multiple. Installs=Y' allows component to be run more than once on the same install. Component Don’ts Don't forget to stop recording when you are finished. – You will have to edit the component Don't forget the component manager includes: – Reports – Saved searches – Workflow Don't forget to comment your component. – Comments in es file – Parameters in the ecf file – More user friendly to run

Q&A

Looking ahead to the classes DP 01: Introduction to the Development Partner Program DP 02: Entities and the Data Model (Part 1 of 2) DP 03: Entities and the Data Model (Part 2 of 2) DP 04: Implementing Screen Based Rules (Part 1 of 2) DP 05: Implementing Screen Based Rules (Part 2 of 2) DP 06: Screen and User Independent Business Rules DP 07: Workflow (Part 1 of 2) DP 08: Workflow (Part 2 of 2) DP 09: Using the API Objects in ASP Pages (Part 1 of 2) DP 10 : Using the API Objects in ASP Pages (Part 2 of 2) DP 11: Using the Component Manager DP 12: Programming for the Advanced Email Manager DP 13: Using the Web Services API DP 14: Using the Web Services API (Part 2 of 2) DP 15: Coding the Web Self Service COM API (Part 1 of 2) DP 16: Coding the Web Self Service COM API (Part 2 of 2) DP 17: Using the. NET API (Part 1 of 2) DP 18: Using the. NET API (Part 2 of 2)