BIOVIA Structured Document Manager | Overview & What's New

BIOVIA
22 Sept 202319:18

Summary

TLDRThe session introduces structured document management, highlighting its efficiency over traditional methods. It emphasizes the ease of collaboration, centralized control over formatting, and the ability to handle data-rich documents. The presentation covers core concepts like document maps, topics, and repositories, and showcases recent updates including template management, content duplication and move support, and user notifications. The session demonstrates how these features streamline content creation, management, and publishing across multiple formats and audiences.

Takeaways

  • 📚 Structured Document Management (SDM) is a system designed to efficiently handle data-rich documents, such as CMC documents or regulatory submissions, by eliminating manual copying and pasting of data from one application to another.
  • 🔄 The traditional document production method is time-consuming and lacks data traceability, whereas SDM provides a modern, efficient approach with web-based authoring, simultaneous multi-author collaboration, and automatic data management.
  • 🌐 SDM stores content in a neutral XML format, allowing for easy publication to various output formats like PDF and HTML, and centralized control over the final output's appearance and styling.
  • 🗂 The core concepts of SDM include document maps, topics, repositories, and render formats, which help organize content, control permissions, and manage the publication process.
  • 🔧 The 22x FD04 release introduced significant updates to SDM, including powerful template management, usage analysis, content duplication, and move support to enhance content management.
  • 📋 A document map is a structured list of topics, while topics are content fragments like text paragraphs, tables, or images that can be combined with external data and reused across multiple documents.
  • 🏢 Repositories are used to organize content by team, department, or project, with different user roles and permissions, such as leader, author, and viewer, to manage access and editing rights.
  • 🔔 The 3D experience platform uses notifications to keep users informed about events and changes within repositories, with options to customize the types and methods of notifications received.
  • 📄 Templates in SDM control the structure and content of document maps, with topic templates containing instructions and examples to guide authors, ensuring consistency and quality across documents.
  • 🔄 The ability to duplicate and move document maps and topics within the system allows for efficient content reuse and management, with automatic updates to all instances of a topic when changes are made.
  • 👥 The session provided a comprehensive overview of SDM, its benefits, and recent updates, aiming to improve the understanding and application of structured document management for users.

Q & A

  • What is the main problem addressed by structured document management?

    -The main problem addressed by structured document management is the inefficiency and time-consuming process of handling data-rich documents, such as CMC documents or submission documents, where data needs to be manually copied and pasted from one application to another, and verified for each usage.

  • What are some of the challenges faced when managing large documentation sets with traditional methods?

    -Challenges include difficulty in tracing back to the originating application, managing copies of the same content in multiple documents, increased overhead of updating content in multiple locations, and difficulty in collaborating in team environments, especially when members are in different locations or time zones.

  • How does structured document management improve the authoring experience?

    -Structured document management improves the authoring experience by being web-based, requiring no software installation, allowing multiple authors to work on documents simultaneously, and managing all changes automatically. It also enables seamless combination of content and data in the same document, keeping the data up-to-date and traceable to the original source.

  • What is the significance of using a neutral XML format for storing content?

    -Using a neutral XML format allows the content to be published to various output formats such as PDF and HTML. It also provides centralized control over the format and appearance of the final output, enabling consistency and standardization across different teams and departments.

  • Can you explain the concept of a document map in structured document management?

    -A document map is similar to a document but contains a list of topics in the map. The content itself is stored in topics, which can be fragments like paragraphs, tables, images, or a combination of these. A data topic can contain data from an external system and can be combined with topics within a document map.

  • Repositories are used to organize content by team, department, or project. They allow different users to have different permissions as required. Maps and topics are organized by repository, enabling content organization and access control.

    -Repositories function by organizing related content and providing access control. They allow users to manage content in a structured manner, with different permissions for various team members.

  • What new features were introduced in the 22x FD04 release?

    -The 22x FD04 release introduced powerful template management, used analysis, duplication and move support, making content easier to manage. It also added the ability for users to create and manage their own repositories.

  • How do templates control the structure and content of document maps?

    -Templates control the structure and content of document maps by providing a predefined layout and content elements. They can contain topic templates with specific instructions and examples, guiding authors on what to include in each section. Templates ensure consistency and efficiency in document creation.

  • What happens when a topic is updated in a document map?

    -When a topic is updated in a document map, the changes are automatically reflected in all other document maps that include that topic. This ensures that the content remains consistent and up-to-date across all usages.

  • How can users be notified about changes in repository access or responsibilities?

    -Users can be notified about changes in repository access or responsibilities through 3D notifications. These notifications inform users about events of interest, such as being added, removed, or having their responsibilities changed within a repository.

  • What are the benefits of using a dedicated repository for templates?

    -Using a dedicated repository for templates allows for centralized control over who can edit and update the templates. It ensures that the templates remain consistent and standardized, which is crucial for maintaining the quality and integrity of the documents created from these templates.

Outlines

00:00

📚 Introduction to Structured Document Management

This paragraph introduces the concept of structured document management, highlighting its purpose and recent updates in the 22x fdo4 release. It emphasizes the problems solved by this approach, such as the manual and time-consuming process of handling data-rich documents, difficulty in tracing data origins, and challenges in managing large documentation sets. The paragraph also contrasts the traditional document production method with the modern, efficient structured document management method, which offers a web-based authoring experience, multi-author collaboration, data-rich documentation, and centralized control over output formats.

05:00

🗂️ Core Concepts and Repository Management

The second paragraph delves into the core concepts of structured document management, starting with the document map and topics. It explains how maps and topics are organized in a repository, which allows content organization by team, department, or project, and assigns different permissions to various users. The paragraph also discusses the creation of new repositories, the addition of users with different roles, and the use of render formats for publishing content. Furthermore, it touches on the 3D experience platform's 3D notifications, which keep users informed about repository-related events.

10:01

📈 Template Management and Creation

This paragraph focuses on the introduction of templates in the fdo4 release, which are used to control the structure and content of document maps. It describes how document map templates and topic templates function, including their capabilities and the ability to control and format content within them. The paragraph outlines the process of creating a new template, adding topic templates with instructions and sample content, and the inclusion of existing topics. It also explains how to use these templates to create new reports and the impact of changes on content reuse across multiple document maps.

15:02

🔄 Content Reuse and Document Map Management

The final paragraph examines various content reuse scenarios and the effects of changing content included in multiple document maps. It discusses the process of adding existing topics to a document map, selecting revisions, and using the 'where used' capability to track topic usage. The paragraph also explains how to duplicate and move document maps, including the considerations and outcomes of these actions, such as changes in visibility and edit permissions. The summary concludes with a recap of the structured document management overview and an appreciation for the attendees' participation in the session.

Mindmap

Keywords

💡Structured Document Management

Structured Document Management refers to a modern and efficient method for creating, editing, and managing documents, particularly those that are data-rich. It allows for the seamless combination of content and data within the same document, ensuring that the data is always up-to-date and traceable back to the original source. This approach enhances collaboration, reusability of content, and maintains consistency across different outputs and teams, as exemplified in the video by the ability to publish content in various formats like PDF and HTML while applying corporate branding and styling.

💡Document Map

A Document Map is a core concept in Structured Document Management, functioning as a framework that contains a list of topics intended for the document. Unlike traditional documents, the content in a Document Map is not copied but referenced, which means the same topic can be included in multiple documents without duplication. This approach facilitates easier management and updating of content, as changes in a single topic propagate across all documents it is included in.

💡Topics

Topics are the individual, reusable fragments of content within the Structured Document Management system, such as paragraphs, tables, images, or a combination of these elements. A topic can contain data from an external system and can be combined with other topics in a Document Map. Because topics are not duplicated when included in multiple maps, this system promotes efficiency and consistency, reducing the risk of errors and redundancy.

💡Repositories

Repositories in the context of Structured Document Management are used to organize content by team, department, or project. They allow for different users to have varying levels of access rights, ensuring that the content is controlled and secure. Repositories play a crucial role in managing permissions, version control, and the overall organization of documents and topics.

💡Templates

Templates in Structured Document Management are pre-defined structures that control the layout and content of Document Maps. They consist of one or more Topic Templates and can include instructions, sample text, and formatting guidelines to assist authors in creating consistent and standardized documents. Templates streamline the document creation process by providing a framework that can be replicated and modified as needed.

💡Content Reuse

Content Reuse is a significant feature of Structured Document Management that allows for the inclusion of existing content, such as topics, in multiple documents without duplication. This not only saves time and effort but also ensures consistency and accuracy across documents. When a change is made to a reused topic, it is automatically updated across all instances where the content is included, maintaining up-to-date information throughout the documentation set.

💡Data Traceability

Data Traceability is the ability to track the origins and changes of data within Structured Document Management. It ensures that the data used in documents is verifiable and can be traced back to its original source, promoting transparency and accountability. This feature is particularly important for data-rich documents, such as those used in regulatory submissions, where the accuracy and provenance of data are critical.

💡Collaboration

Collaboration in the context of Structured Document Management refers to the ability of multiple authors to work on documents simultaneously without the need for software installation. The system manages all changes automatically, allowing for efficient teamwork and communication, especially in team environments where members may be geographically dispersed or working in different time zones.

💡Centralized Control

Centralized Control refers to the ability to manage and enforce a consistent look and feel across all documentation, including styling, layout, and formatting. This is achieved by storing content in a neutral format like XML, which allows for easy publication to various output formats while maintaining the application of corporate branding and standards.

💡3D Notifications

3D Notifications are used within the 3D Experience Platform to inform users of events of interest or updates within various applications. These notifications can be managed through the notification center, where users can choose which types of notifications they wish to receive and how they prefer to be alerted. This feature enhances user experience by keeping them informed and in control of their notification preferences.

💡Maturity

Maturity in the context of the video refers to the readiness or completeness level of a Document Map Template or a Topic Template. The maturity can be independently changed, allowing for flexibility in the development and refinement of templates before they are finalized and used for creating actual documents. This feature ensures that only fully matured and approved templates are utilized, maintaining a high standard of quality and accuracy in the final documents.

Highlights

Introduction to structured document management, a system designed to efficiently handle data-rich documents.

Recent updates in the 22x fdo4 release include powerful template management and used analysis features.

Content management is simplified with the addition of duplication and move support.

Traditional document management issues include manual data copying and difficulty tracing back to the original data source.

Structured document management overcomes these challenges by allowing multiple authors to work simultaneously on web-based documents.

Data in structured documents is always kept up to date with full traceability back to the original data source.

The system stores content in neutral XML format, allowing for publication in various output formats like PDF and HTML.

Centralized control over format and appearance ensures consistent and standardized documentation across different formats.

Core concepts of structured document management include document maps, topics, repositories, and render formats.

Repositories allow content organization by team, department, or project with different user permissions.

3D notifications inform users of events of interest within various applications, with customizable settings.

Templates control the structure and content of document maps, with the ability to contain all available content elements.

Instructions and example content within templates provide guidance and structure for authors.

Authors can use document map templates to create new reports, with topics in the required order and instructions for guidance.

Content reuse scenarios are examined, including the impact of changing content included in multiple document maps.

The system allows for easy duplication and moving of document maps between repositories.

The session concludes with an overview of structured document management and its recent updates, aiming to improve efficiency and collaboration.

Transcripts

play00:04

welcome to the session on structure

play00:06

document manager where we are going to

play00:08

provide an overview of the capability we

play00:10

call structured document management

play00:13

we are also going to walk through some

play00:15

of the recent updates we have provided

play00:17

in our 22x fdo4 release

play00:21

we've made some significant updates

play00:23

across a number of areas as well as

play00:26

adding some brand new features

play00:29

we've added powerful template management

play00:31

and we're used analysis

play00:34

we've also made content easier to manage

play00:36

by adding duplication and move support

play00:39

so let's take a look at those and other

play00:42

features

play00:43

in our upcoming release

play00:50

let's start by understanding the problem

play00:52

we are trying to solve

play00:54

when all three documents that are data

play00:56

Rich such as CMC documents or documents

play01:00

in the submission

play01:01

these documents contain large amounts of

play01:03

data that has been generated in other

play01:06

applications

play01:08

this means the data needs to be copied

play01:10

from the originating application and

play01:12

paste it into each document

play01:15

this is a very manual and time-consuming

play01:17

approach

play01:18

and the data that is used must be

play01:20

manually verified for each and every

play01:22

usage

play01:24

when reading or approving such documents

play01:27

it is very difficult to understand what

play01:29

the date has come from as documents

play01:32

cannot easily Trace back to the

play01:34

originating application

play01:37

when managing large documentation sets

play01:39

with multiple related documents

play01:41

document copying can result in copies of

play01:44

the same content in multiple documents

play01:46

with the increased overhead of having to

play01:49

update this content in multiple

play01:51

locations

play01:53

single monolithic documents make it more

play01:56

difficult to work and collaborate on the

play01:58

content in the team environment where

play02:00

some team members may be in a different

play02:02

location or time zone

play02:06

the current approach to managing content

play02:07

means you cannot Target multiple

play02:10

audiences using the same content for

play02:13

instance creating a publication for

play02:15

consumption internally and using the

play02:18

same content to provide documentation to

play02:21

an agency or regulatory body

play02:24

you may also wish to use the same

play02:26

content and make it available on your

play02:28

internal internet or knowledge base

play02:30

where the format and the presentation is

play02:32

different

play02:34

finally controlling the appearance of

play02:37

content so that the styling layout and

play02:40

formatting are consistent and

play02:42

standardized across many teams and

play02:45

departments is very difficult as there

play02:47

is no way to enforce this with

play02:49

traditional document editing

play02:51

applications

play02:54

when we compare the traditional approach

play02:56

of document production

play02:58

to a more modern and efficient method

play03:01

which we refer to as structure document

play03:03

management

play03:04

we see that there are many differences

play03:08

firstly the authoring experience is

play03:10

web-based with no installation of

play03:12

software required

play03:14

multiple authors can work on documents

play03:17

simultaneously and the application takes

play03:19

care of managing all of their changes

play03:23

because the structure document approach

play03:25

is designed for data Rich documentation

play03:27

you can seamlessly combine your content

play03:30

and data in the same document

play03:34

data in those documents is always kept

play03:37

up to date and because we provide full

play03:40

data traceability back to the original

play03:42

data source it's always clear where the

play03:45

data came from

play03:48

with the structure document approach we

play03:50

store the underlying content in neutral

play03:53

XML format and this means we can publish

play03:56

it to many different output formats such

play03:59

as PDF and HTML

play04:02

it also means that you have centralized

play04:04

control over the format and appearance

play04:07

of the final output

play04:10

so you can apply corporate branding and

play04:12

styling and ensure that all of your

play04:14

documentation is consistent and

play04:17

standardized even when it is generated

play04:19

in multiple different formats

play04:24

let's now look at the Core Concepts in

play04:26

structure document management

play04:28

we start with a document map

play04:31

which is similar to a document but

play04:33

simply contains the list of topics in

play04:35

the map

play04:36

the content itself is stored in topics

play04:40

a topic is a fragment of content such as

play04:43

a paragraph of text or a table or an

play04:46

image or a combination of those

play04:49

a data topic can contain data from an

play04:52

external system and can be combined with

play04:54

topics within a document map

play04:57

because topics and data topics are

play05:00

simply included in a map and not copied

play05:03

this means the same topic can be created

play05:06

once and included in many different

play05:08

documents

play05:10

maps and topics are organized by

play05:12

repository which allows you to organize

play05:15

your content by team department or

play05:18

project with different users having

play05:20

different permissions as required

play05:23

finally one or more render formats are

play05:26

used to publish the content into

play05:28

multiple different output formats and

play05:31

control The Styling and layout of the

play05:34

published output

play05:43

the content and structure document

play05:44

manager consists of document maps and

play05:47

topics that are at varying stages of

play05:49

completeness

play05:51

at the top of the welcome panel is the

play05:53

list of repositories that the user has

play05:56

access to

play05:58

repositories are used to organize

play06:00

content related to a specific product or

play06:03

project or team

play06:06

users must be added to a repository in

play06:09

order to see or edit the content in the

play06:11

Repository

play06:15

with her upcoming release users can now

play06:18

create and manage their own repositories

play06:21

so to create a new repository we provide

play06:23

a title and a description

play06:25

and users can be added as a leader which

play06:28

allows them to add other users to the

play06:31

repository as well as edit the contents

play06:33

in the Repository

play06:35

adding a user as an author gives them

play06:38

full edit capability over all of the

play06:41

contents in the Repository

play06:42

and finally a viewer within the

play06:45

repository can read all of the contents

play06:47

but it's not allowed allowed to modify

play06:50

any of that content

play06:52

so the newly created repository is now

play06:55

available and appears in the list of

play06:57

repositories

play07:00

content can now be added to the

play07:03

repository using the actions on the

play07:06

welcome panel

play07:08

so we choose to create a new document

play07:11

map

play07:12

and we give that map a title

play07:16

we also provide a title for the first

play07:19

Topic in the map

play07:23

when we save that document map

play07:26

we can see that we'd have the newly

play07:28

created map and Topic in the newly

play07:32

created Repository

play07:36

within the 3D experience platform 3D

play07:39

notifications are used to inform users

play07:41

of events of interest within various

play07:43

applications

play07:45

you can use the notification center to

play07:47

control which notifications you want to

play07:49

receive as well as how you wish to

play07:51

receive them

play07:52

we've added some new notifications to

play07:54

help users understand when they have

play07:56

been added or removed or had the

play07:59

responsibility changed on a repository

play08:02

these can be enabled or disabled for

play08:04

each individual user

play08:06

now when we look at the notifications

play08:08

that we have received in our role as a

play08:10

structured document manager we can see

play08:12

that anytime we've been removed or added

play08:15

from a repository we get a notification

play08:19

so now we choose to manage the members

play08:21

of a particular Repository

play08:25

select

play08:27

to add a member

play08:29

and assign them a specific

play08:31

responsibility

play08:34

once we've found and added that member

play08:37

to the Repository They will receive a 3D

play08:40

notification

play08:50

with our fdo4 release we have introduced

play08:53

the concept of templates

play08:56

templates are used to control the

play08:59

structure and content of document Maps

play09:04

a document map template looks just like

play09:07

a normal document map

play09:09

and has all of the same capabilities

play09:14

templates can contain all of the content

play09:17

elements that are available in a normal

play09:20

map or topic

play09:22

our document map templates contain one

play09:25

or more topic templates

play09:28

and the content within templates can be

play09:32

controlled and formatted in the same way

play09:35

as in the document map

play09:38

you can also use all of the available

play09:40

content elements within a template

play09:46

each document map template and topic

play09:50

Templars

play09:51

has its own maturity that can be changed

play09:54

independently

play10:01

you can also choose to duplicate or move

play10:04

templates in the same way as other

play10:07

content items

play10:14

here we have chosen to put our templates

play10:17

into a dedicated Repository

play10:20

this allows us to control who can edit

play10:23

and update those templates

play10:25

in our templates repository we have two

play10:28

types of items

play10:30

document map templates which control the

play10:33

structure and the Order of the document

play10:36

and topic templates contain the content

play10:38

and the instructions that the author is

play10:41

provided with

play10:43

let's start by creating a new template

play10:45

using the actions on the welcome panel

play10:50

we provide a title for the document map

play10:53

template in this case it's a template

play10:55

for the process performance

play10:57

qualification report

play11:00

we also have an initial topic template

play11:03

that is set to in work

play11:05

so we can provide a title in this case

play11:09

to capture the executive summary

play11:14

we now add another topic template

play11:17

this time for the introduction content

play11:24

we continue to add more topic templates

play11:27

this time to capture the materials and

play11:31

methods content

play11:38

we continue to add more topic templates

play11:41

until the structure of the document map

play11:43

template is complete

play11:48

we can now add instructions to each

play11:51

topic template to provide guidance to

play11:54

the author on that particular section

play11:58

instructions can be used to help the

play12:01

author understand what needs to be

play12:03

provided in each topic

play12:06

sample text

play12:07

also content such as a table can be used

play12:10

to provide specific examples of the type

play12:13

of information and detail that's

play12:16

required in each topic

play12:19

foreign

play12:22

instructions to the other topics in our

play12:24

template and we can include examples of

play12:27

the content that is expected in that

play12:29

part of the document

play12:31

instructions can contain any type of

play12:34

content element

play12:35

for instance providing a table within

play12:38

the instructions provides a strong

play12:40

example of the data that is expected in

play12:44

a particular topic

play12:46

authors can also copy the content from

play12:49

the instructions and insert that into

play12:51

the relevant topic

play12:58

we have now added our instructions to

play13:00

the document map template and we can see

play13:03

from looking at the various topics how

play13:05

specific the guidance is

play13:08

detailed instructions and example

play13:10

content are provided to ensure the

play13:12

author understands exactly what they

play13:14

need to provide

play13:16

in each topic

play13:27

we are going to make one final addition

play13:29

to the template we're going to include

play13:31

an existing topic which is a generic

play13:34

supporting material topic

play13:36

we move that topic to the relevant

play13:39

location within the document map

play13:41

template

play13:43

so now all of our modifications are

play13:45

complete we have finished creating our

play13:47

template so let's look at how we can use

play13:50

that template to create a real

play13:52

qualification report

play14:03

using our document map templates to

play14:05

create a new report is really simple

play14:09

authors can only see and use the

play14:12

templates that they have permission to

play14:14

access

play14:16

using the actions menu on the template

play14:19

you choose create from

play14:22

the user chooses a Target Repository

play14:25

for the new document map that will be

play14:27

created

play14:29

we will select the DSX 90 repository as

play14:32

our Target

play14:34

and we now have a new document map

play14:37

created from our map template

play14:40

document map contains a copy of each

play14:43

topic template taken from the map

play14:45

template

play14:47

we can see as we scroll through the new

play14:49

map

play14:50

that we have all of the topics in the

play14:52

required order

play14:53

with all of the instructions to guide

play14:55

the author

play14:59

the author can choose to hide the

play15:01

instructions

play15:03

to Aid the readability of the document

play15:11

we are now going to examine a number of

play15:14

content reuse scenarios

play15:16

and understand the impact of changing

play15:19

content that is included in multiple

play15:21

document Maps

play15:24

we add an existing topic to the current

play15:28

document map

play15:31

here we choose to add the supporting

play15:33

material topic

play15:39

if there are multiple revisions of a

play15:42

topic

play15:44

we have the choice of which revision to

play15:46

use

play15:49

we can see here that we have both an

play15:52

in-work and a released revision of the

play15:54

supporting material topic

play15:57

using released revision means we know

play16:00

that the topic will not change

play16:04

on the left of the supporting material

play16:06

topic we can see a symbol that shows us

play16:09

that this topic is used elsewhere

play16:14

our where used capability

play16:17

will show us exactly where this

play16:19

particular topic is used

play16:22

we can see that it is used in four other

play16:25

locations or documents also

play16:30

so in this case the release topic is

play16:32

being included in an in-work document

play16:35

map

play16:37

that means the map is including released

play16:40

or finalized content that will not

play16:42

change

play16:46

we can choose to include the latest

play16:48

revision of the supporting material

play16:51

topic

play16:54

including the latest revision means any

play16:57

changes to that content will be

play16:59

automatically updated everywhere that

play17:02

content is used

play17:10

let's now take a look at how we

play17:12

duplicate a map

play17:13

the menu provides us with the available

play17:15

actions when we select duplicate we are

play17:19

asked for a Target Repository

play17:21

this is where the new document map will

play17:23

be placed

play17:25

so once we have selected our Target

play17:27

Repository

play17:28

we then hit duplicate

play17:30

and a copy of the document map is

play17:33

created and a copy of each Topic in the

play17:35

original document map

play17:37

is also created

play17:41

all of these items are now available in

play17:44

the selected Target Repository

play17:49

the newly created map

play17:51

has all of the content of the original

play17:53

map in that original order

play17:57

now let's take a look at what's involved

play17:59

in moving a document map

play18:02

you may move a document map for a number

play18:04

of reasons

play18:05

You may wish to put it into the

play18:06

repository that will restrict the

play18:08

authors who can edit it

play18:10

or you may wish to relocate this into a

play18:13

repository that allows a larger audience

play18:15

to view it

play18:17

when we access the actions menu

play18:20

we choose the move option

play18:25

the move dialog outlines the map

play18:28

and all of the topics within the map

play18:30

that will be moved

play18:31

if any of this top any of these topics

play18:34

has dependent items like embedded images

play18:36

these will be moved also

play18:39

so we choose our Target Repository

play18:43

and then we hit move

play18:46

this will move the map and its topics

play18:48

for the items in total

play18:51

into the target Repository

play18:54

this may also change who can view or

play18:57

edit

play18:58

the document map and its contents

play19:03

so we have just walked through an

play19:05

overview of structured document

play19:07

management as well as taking a look at

play19:10

some of our recent updates

play19:12

I hope you enjoyed the session and thank

play19:14

you for attending

Rate This

5.0 / 5 (0 votes)

Related Tags
Doc ManagementCollaboration ToolsData IntegrityTemplate ManagementVersion ControlContent CreationEfficiency BoostRegulatory ComplianceMulti-Author EditingXML Publishing