360 likes | 487 Views
What’s New SDL Tridion R5.3. What’s new in R5.3. Globalization Workflow Content compliance Modular Templating Enterprise readiness Platform support. Globalization. Visual BluePrinting™ Japanese language support. BluePrinted process definitions. BluePrinted workflow definitions
E N D
What’s new in R5.3 • Globalization • Workflow • Content compliance • Modular Templating • Enterprise readiness • Platform support
Globalization • Visual BluePrinting™ • Japanese language support
BluePrinted process definitions • BluePrinted workflow definitions • Can be localized to adapt processes to local needs
Configuration • Enable workflow inheritance in BluePrint (minimize upgrade impact)
Agenda • Globalization • Workflow • Content compliance • Modular Templating • Enterprise readiness • Platform support
Process definitions stored inside R5 • Process definition is item in R5 • CP-able • Versioned • Et cetera • Single-sign-on
Finish multiple activities • Multiple activities can be selected and finished • Error handling
Agenda • Globalization • Workflow • Content compliance • Modular Templating • Enterprise readiness • Platform support
New workflow triggers • Workflow on rollback/roll forward • For compatibility it is switched off by default
Workflow auditing • WF can be auditable: changes are tracked for each activity within a workflow instance
Workflow auditing: compare or preview • Auditing for all activities per workflow instance • Preview and compare content as it was ‘half-way’ a workflow
Workflow auditing: configuration • Snapshots of content are stored • Even when schema changes, content can still be viewed • Separate templates for visualization of snapshots
Agenda • Globalization • Workflow • Content compliance • Modular Templating • Enterprise readiness • Platform support
Modular Templating • Templates consist of multiple individual modules • Each module has its own role in delivering the end result • Modules can be for visual design or code • Modules can be written in HTML, XSLT, JavaScript, VBScript or any .NET language (in any combination) • Modules can be made using Dreamweaver or Visual Studio • Modules are reusable across templates • R5 delivered with modules out-of-the-box • Existing templates will still work in R5.3
Template Builder • Template Builder allows you to assemble and debug templates • Run & measure
Template Builder builds a ‘package’ • Package: all data that is needed to build the Web page • Data includes URI’s, JPEG, XML,HTML, binary, CSS, array, text, ... • Every module adds to the package
Parametrized building blocks • Parameters:to definebehavior of themodule • Examples: • Accessibility level • Binary location
Debugging templates • Debugger:all standardoperations • Output view:output of modules is shown
Visual design: Dreamweaver • Dreamweaver can be used to edit the design part of templates • Standard Dreamweaver functionality • No R5 knowledge needed
.NET assembly: Visual Studio • Visual Studio can be used to modify the code part of temlates • Any .NET language • IntelliSense TOM.NET • Remote debugging • Post-build step to store assemblies in R5
Modular Templating options • Page Templates, Component Templates and Template Building Blocks can all be modular • Template Building Blocks can now be: • A .NET assembly… • …or written in • C# • Dreamweaver • XSLT • VBScript • JavaScript
Modular Templating benefits • Modular Templating fulfills enterprise level requirements • Modular design: separate visual design, content and code • Reusable building blocks • Choose, combine and extend technologies • BluePrinting & brand management • Support for industry-standard tools • Shorter time to market
Agenda • Globalization • Workflow • Content compliance • Modular Templating • Enterprise readiness • Platform support
Application monitoring • Application Monitoring • Up/hang/downSNMP traps • Logfile scanning • Polling • Heartbeats
SSH-FTP • SSH-FTP has been added to the list of transport protocols (used between CMS and websites) • Transport protocol overview • FTP • ‘SFTP’(really FTP over SSH) • SSH-FTP • HTTP(S) CMS FTP CMS SSH FTP CMS SSH CMS Web Server
Enterprise readiness • Support JMS for the communication of cache events • IBM standard for cache synchronization across servers • Replacement of Cache Channel Service • ‘Tridion Content Delivery Language’, intermediate language to prevent target language dependent constructs in published data 5.2 5.3
AddBinary • Replacement of PublishBinary • Improvements • No more http://www.tridion.com/Images/logo-SDL-tridion_tcm15-201.gif • Allow target location (structure group) of binaries to be specified • Allow original filename to be used as target file name • Allow for ‘variants’/ managed binaries • PublishBinary still works.AddBinary/ AddBinaryData API calls need to be used in templates to use new functionalityWriteOut AddBinary(lObjComp,lObjComp.Publication.RootStructureGroup)
Agenda • Globalization • Workflow • Content compliance • Modular Templating • Enterprise readiness • Platform support
Microsoft .NET support • Content Management • TOM.NET • Publishing (extensions) in .NET • Content Delivery • Improved CD.NET • Improved code generation support for ASP.NET
Other platforms • Windows Vista • Windows 2003 r2 • Windows Internet Explorer 7