What’s New
SDL Tridion R5.3
Copyright © 2009 by SDL Tridion. SDL Tridion®, SDL Tridion R5™, BluePrinting™, SiteEdit™ and WebForms™ are trademarks of
SDL Tridion Holding B.V. or its affiliates. All other company or product names used herein may be trademarks of its respective owners.
What’s new in R5.3
Globalization
Workflow
Content compliance
Modular Templating
Enterprise readiness
Platform support
2
Globalization
Visual BluePrinting™
Japanese language support
3
BluePrinted process definitions
BluePrinted workflow definitions
Can be localized to adapt
processes to local needs
4
Configuration
Enable workflow inheritance in BluePrint (minimize upgrade
impact)
5
Agenda
Globalization
Workflow
Content compliance
Modular Templating
Enterprise readiness
Platform support
6
Process definitions stored
inside R5
Process definition is item in R5
 CP-able
 Versioned
 Et cetera
Single-sign-on
7
Display of approval status
8
Finish multiple activities
Multiple activities can be selected and finished
Error handling
9
Hidden items
10
Agenda
Globalization
Workflow
Content compliance
Modular Templating
Enterprise readiness
Platform support
11
New workflow triggers
Workflow on rollback/roll forward
For compatibility it is switched off by default
12
Workflow auditing
WF can be auditable: changes are tracked
for each activity within a workflow instance
13
Workflow auditing: compare
or preview
Auditing for all activities per workflow instance
Preview and compare
content as it was
‘half-way’ a workflow
14
Workflow auditing: configuration
Snapshots of content are stored
 Even when schema changes, content can still be viewed
Separate templates for visualization of snapshots
15
Agenda
Globalization
Workflow
Content compliance
Modular Templating
Enterprise readiness
Platform support
16
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
17
Open template with Template
Builder
18
Template Builder
Template Builder allows you to assemble and debug
templates
Run & measure
19
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
20
Parametrized building blocks
Parameters:
to define
behavior of the
module
Examples:
 Accessibility level
 Binary location
21
Debugging templates
Debugger:
all standard
operations
Output view:
output of modules
is shown
22
Visual design: Dreamweaver
Dreamweaver
can be used
to edit the
design part of
templates
 Standard
Dreamweaver
functionality
 No R5
knowledge
needed
23
.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
24
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
25
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
26
Agenda
Globalization
Workflow
Content compliance
Modular Templating
Enterprise readiness
Platform support
27
Application monitoring
Application Monitoring
 Up/hang/down
SNMP traps
 Logfile scanning
 Polling
 Heartbeats
28
Application monitoring per
service
29
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
CMS
SSH
CMS
FTP
Web Server
30
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
Jsp
transformer
jsp
deployer
Asp
transformer
asp
deployer
Dotnet
transformer
aspx
deployer
TCDL
jsp
5.3
5.2
Publisher
Target
Language
TCDL
asp
TCDL
31
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 functionality
WriteOut AddBinary(lObjComp,lObjComp.Publication.RootStructureGroup)
32
Agenda
Globalization
Workflow
Content compliance
Modular Templating
Enterprise readiness
Platform support
33
Microsoft .NET support
Content Management
 TOM.NET
 Publishing (extensions) in .NET
Content Delivery
 Improved CD.NET
 Improved code generation support for ASP.NET
34
Other platforms
Windows Vista
Windows 2003 r2
Windows Internet Explorer 7
35