1. GOSS iCM 10.0.0.0 Gary Ratcliffe

2. 2 Agenda Webinar Programme V10 Overview Version Information Supported Browsers Architectural Changes New Features

3. 3 Webinar Programme User –1 st October – What’s New in iCM V10 –2 nd October – Article Editing, Media Upload, etc –3 rd October – Preferences, Help Text, Shortcuts Technical –9 th October – iCM V10 Overview –16 th October – Forms –6 th November – API Server Workshops –We are considering running a forms workshop, probably in London

4. 4 V10 Overview A major iCM release with significant changes: –API Server* –New user interface –Shortcuts –New Article Editor –Forms Designer – Groups –Forms Designer – Visual Script Editor* –Forms Designer – Scripted Actions* –Media tree restructured –Security changes –Sub-site Configuration –Help text site –Miscellaneous *Covered in detail in later webinars Updates to core components

5. 5 Version Information iCM is version 10.0.0.0 APIs –Cold Fusion10.0.0.0 –.NET10.0.0.1 –Java10.0.0.1 Any additional API releases that work with 10.0.0.0 will be –10.0.0.2, 10.0.0.3 etc The first iCM v10 patch will be –10.0.1.0 –The APIs will start at 10.0.1.0

6. 6 Supported Browsers Microsoft Internet Explorer 8 on Windows Desktop Microsoft Internet Explorer 9 on Windows Desktop Microsoft Internet Explorer 10 on Windows Desktop Mozilla Firefox on Windows Desktop. Version tested is V24 –V24 is an Extended Support Release from Mozilla Google Chrome on Windows Desktop. Version tested is 29.0.1547.76m Apple Safari on Max OS X Note: Some browsers may require configuration settings to enable clipboard access from within the article editor. This is outside of iCM’s control.

7. 7 Supported Browsers – Internet Explorer Issues Internet Explorer must NOT be in ‘Compatibility Mode’ Internet Explorer will default to ‘Compatibility Mode’ for Intranet sites –Intranet sites are detected as anything on a local network Setting changed from ‘Tools’ menu under ‘Compatibility View Settings’

8. 8 Supported Browsers – Internet Explorer Issues IncorrectCorrect

9. 9 Architectural Changes Tomcat RailoSolr ‘iCM’ Java Runtime Java Libraries ‘iCM’ Java Libraries Database Search Collections ‘API’ Windows Linux SQL Server PostgreSQL (not.NET) Oracle Cold Fusion Java.NET ‘API Server’ 1.7 4.0.3 4.4.0 NodeJS 0.10.12 Java 1.7.0_25 7.0.14

10. 10 Architectural Changes – API Server API Server biggest change Responsible for all site form rendering regardless of API Also responsible for iCM article extra, user profile and subsite config forms. Each iCM and delivery server must have a local API Server Each server must be defined in iCM iCM sends the configuration information to the AP Server iCM can also send updates to the API Server –Supplied as part of iCM patches or hot fixes.

11. 11 Architectural Changes – API Server

12. 12 Architectural Changes – API Server

13. 13 Architectural Changes – API Server

14. 14 Architectural Changes – API Server

15. 15 Architectural Changes – API Server

16. 16 Architectural Changes – API Server

17. 17 User Interface DEMO

18. 18 Standard iCM features –Same as V9 A URL to another site –New Browser window –Popup window Auto size or fixed initial size –Main iCM window Apps –Create by GOSS at the moment for specific purposes Forms –Display a public form and process its actions Shortcuts DEMO

19. 19 WYSIWYG on all browsers Greater range of configuration and HTML compliance options Article Editor DEMO

20. 20 It is important that editor configuration is updated to match site –Most clients have standard editor.css This will be done as part of the upgrade performed by GOSS –Script supplied to automate generation of configuration files HTML compliance defined in the editor configuration is enforced –Invalid content will be removed. Compliance also enforced by article changes made via APIs See iCM v10 Configuration of the HTML Editor.docx Article Editor - Configuration

21. 21 Article Editor - Configuration The iCM HTML Text Editor relies on the presence of certain files within the iCM installation and the associated site(s) to function correctly. The visual appearance of content displayed within the editor is dictated by the Editor Style Sheet. The functionality and behaviour of the editor is governed by a combination of the Editor Configuration File settings and the Editor Content Rules. These settings and rules are also used to determine the html elements and attributes which are supported within article content, whether submitted within iCM via the editor, or externally via one of the APIs. It is important that the editing of articles is tested after the editor has been fully configured. iCM checks for the existence of the relevant configuration and content rules, and will prevent any changes if they are missing. Once present, however, it is important that existing content in particular is loaded into the article editor and is checked for unexpected clean-up of content

22. 22 Article Editor - Configuration Editor Configuration File –Dialog customisation for compliance and accessibility –Editor toolbar customisation Editor Content Rules –How and where styles can be applied –Defines compliance rules HTML 4/XHTML 1.1 is default Editor Style Sheet –Actual style formatting Webinar will be considered if this level of customisation is used.

23. 23 Forms Designer - Groups DEMO Covered in detail during Forms webinar on 16 th October

24. 24 Forms Designer – Visual Script Editor DEMO This is not supported on any current version of Internet Explorer –This is because of incomplete or non-existent SVG support Covered in detail during Forms webinar on 16 th October

25. 25 Forms Designer – Scripted Actions DEMO Covered in detail during Forms webinar on 16 th October Use of API Server covered in webinar on 6 th November

26. 26 Media Tree DEMO

27. 27 iCM user passwords are stored in a different format –Bcrypt They can be made case-sensitive if required – autoconfig –The won’t become case sensitive until the password changed New password reset approach –Security questions –Token emailed to user attempting a reset Use demonstrated in webinar recording1 st October Security questions can be changed via a file in custom –securityquestions.txt –http://goodsecurityquestions.com/examples.htm iCM User Security

28. 28 More granular –Particularly for Management features. Eg. File Manager Diagnostics privilege –Used to enable additional logging and debug –Should never given unless needed for support Security Privileges DEMO

29. 29 Sub-site Configuration Forms.NET and Java sites only Contents of Subsite.ini and icm4j.xml in a form Form created in forms designer Specified in autoconfig

30. 30 Sub-site Configuration Forms

31. 31 Sub-site Configuration Forms

32. 32 Help Text DEMO

33. 33 Autoconfig –No password reset –No control over iCM sections. Use privileges Pre-V9 Forms –No edit and add capability. –Forms will still work but can’t be modified Form Family Editor –Can’t modify DEFAULT and DEFAULTV2 directly. Reports –Unused external link report added Miscellaneous

34. Questions?