4. Recommendation
for DCM v5.0
4
• Controlled Document Lifecycle
• Workflow Management
• Authoring and Routing CNs & CRs
• Data Model
• DCM Application Administration
• WCM and DCM Code Extensions
Analysis
• Controlled Document Lifecycle
• Workflow Management
• Authoring and Routing CNs & CRs
• Data Model
• DCM Application Administration
• WCM and DCM Code Extensions
5. Recommendation
for DCM v5.0
5
Controlled document lifecycle
Promo_profile
- ds_name
- subclass
- state_number
- state_name
- state_type
- state_location
- state_status
- state_acl
- state_owner
- pdf
- read_understood
- make_current
Features:
• Initial (In-Progress): document is create, imported, or versioned, and then routed for approval
• Approved: document is approved and ready for users to be trained
• Effective: document is in-use and CURRENT
• Retired: document version is no longer in-use and has been supersepeded by a new effective ver
• Suspended: document version is temporarily retired, and has been suspended by a new temporary effective
version, but will be made effective again at some point
• Obsolete: all document version are no longer in use
Initial State
(e.g. In-Progress)
Effective
State
Retired
State
Suspended
State
Obsolete
State
Promote
Promote
Promote
Superceded
Subsequent
State(s)
(e.g. Approved)
Promote
Promotions
- promo__obj_id
- promo_chron_id
- promo_inprocess
- wflow_profile
- wflow_type
- cn_inprocess
Process: Object Model:
UI:
6. Recommendation
for DCM v5.0
6
Controlled document lifecycle (cont’d)
DCM
lifecycle
program
logic:
Assign next
state status
Assign state
ownership
Assign next
state ACL
Move to next
state folder
location
PDF?
Queue
request to
AutoRender
TBR?
Effective state?
Yes
No
No
Start
(Promote)
Doc specified
dist'n
Start
Specified
Distribution
Start
Assigned
Distribution
Dist'n
Assignment
Start Doc
Type Profiled
Distribution
Yes
No
Yes
Yes
No
G_Major_
version?
Increment
r_version_label
to next Major
version
doc_mode
Permanent?
Retire
CURRENT
Document
Suspend
CURRENT
Document
Yes Yes
No
No
Display
Promotion
Complete
Dialog
No
End
Yes
7. Recommendation
for DCM v5.0
7
Controlled document lifecycle (cont’d)
Initial State
(e.g.
In-Progress)
Effective
State
Retired
State
Suspended
State
Obsolete
State
Promote
Promote
Promote
Superceded
Subsequent
State(s)
(e.g. Approved)
Promote
• Since the “Obsolete” state affects the entire version tree, an
obsolete method will perform this task. 4i lifecycle is designed to
affect per version only.
Proposed DCM Lifecycle:
8. Recommendation
for DCM v5.0
8
Controlled document lifecycle (cont’n)
Promo_profile
- ds_name
- subclass
- state_number
- state_type
- state_name
- state_location
- state_status
- state_acl
- state_owner
- pdf
- make_current
- readunderstood
dm_policy
- action_object_id (R)
- alias_set_ids (R)
- allow_attach (R)
- allow_demote (R)
- allow_schedule (R)
- entry_criteria_id (R)
- exception_state (R)
- i_state_no (R)
- include_subtypes (R)
- included_type (R)
- r_definition_state (S)
- return_to_base (R)
- state_class (R)
- state_description (R)
- state_name (R)
- type_override_id (R)
- user_action_id (R)
- user_action_ver (R)
- user_criteria_id (R)
- user_criteria_ver (R)
TBR can be set here by calling a
TBR method
Add to Repeating Attribute
Add Version Label
Link to New Location
Move All links to location
Remove from
Repeating Attribute
Remove Link from
Existing Location
Remove Version Label
Request Rendition
Set Attribute
Set Owner
Set Permission
Promotions
- promo_obj_id
- promo_chron_id
- promo_inprocess
- wflow_profile
- wflow_type
- cn_inprocess
• DCM Promotion object is used to monitor promotion
instances. This will be handled by 4i.
• A lifecycle can be assigned to a primary object type and its
subtypes. For WebPublisher it is assigned to dm_document,
which permits users to create a dm_document with various
lifecycle options.
Proposed DCM Lifecycle (cont’d):
9. Recommendation
for DCM v5.0
9
Controlled Document Lifecycle
“4i lifecycle can be used to address DCM
lifecycle requirements”
Conclusion
10. Recommendation
for DCM v5.0
10
Controlled Document Lifecycle
• Workflow Management
• Authoring and Routing CNs & CRs
• Data Model
• DCM Application Administration
• WCM and DCM Code Extensions
Analysis
11. Recommendation
for DCM v5.0
11
Workflow Management
Features:
• Allow authorized users to route documents for review or approval and dynamically select a workflow
• Support for auto assignment of documents to a workflow template, available parallel reviewers, required
parallel reviewers, and distribution
• Support for parallel review
• The documents ACL should adjust to the task ACL. DCM and GMPharma uses the wflow_profile object with
custom code to perform this process.
• Promote on completion and demote when rejected
• Reviewers/Approvers have the option to Approve, Disapprove, and Reject documents or CNs
Process: Object Model:
UI:
Wflow_profile
- ds_name
- wfpro_name
- make_approved
- total_phases
- phase_number
- wfpro_status
- wfpro_owner
- wfpro_acl
- wfpro_location
- submit_pdf
To perform workflow features, DCM server methods are used -- post_promote6_ forward,
promote7_reject, post_promote7_forward, post_readunder_forward, promote_method
Review
Review
Review
Document Control
DC routes the newly revised
documents to the appropriate
users for approval
• Assigns status to “Effective”
• Assigns the Effective ACL to
all documents
Reject
Reject
Approved
State_dist
- objtype
- subclass
- state_name
- dist_name
12. Recommendation
for DCM v5.0
12
Workflow Management (cont’d)
• DCM will use dm_workflow instead of dm_router
• Managing task ACL is not currently available in WFM v4.2. Additional DCM/WP
task method can be added to the workflow to perform this task
• dm_workflow object type and associated processes will be replaced with the task
ACL solution as well as using Alias sets
• Parallel review is a new feature in WFM v4.2 called dynamic user selection (auto-
delegation & load balancing)
• state_distribution object type and associated processes can be replaced with a
distribution workflow task.
Proposed DCM Workflow:
13. Recommendation
for DCM v5.0
13
Workflow Management
“4i workflow can be used to address DCM
and CAM workflow requirements”
Conclusion
14. Recommendation
for DCM v5.0
14
Controlled Document Lifecycle
Workflow Management
• Authoring and Routing CNs & CRs
• Data Model
• DCM Application Administration
• WCM and DCM Code Extensions
Analysis
15. Recommendation
for DCM v5.0
15
Authoring and Routing CNs & CRs
SOP routed
for review
SOP versioned
and edited
SOP made
Effective
Documents
distributed to
appropriate
individuals
across plant
Change Requests
made from across
plant
Change Request
routed for review
Change Notice
routed for
approval
SOP authored
16. Recommendation
for DCM v5.0
16
Authoring and Routing CNs & CRs
Process: Authoring
Authorized User
DCM System
logic
Select Menu
Function: Create
Document or
Import Document
Select Document
Type
Defined as
Profile object?
Display
Document
Subclass
dialog
Select Document
Subclass
Enter attribute
values as required
Exit New or
Import Document
dialog
Create or
Import
Document
Object
Assign:
ACL=InProgress
Status=InProgress
Folder=InProgress
Standard WS/IC
New or Import
process
No
Yes
SOP routed
for review
SOP versioned
and edited
SOP made
Effective
Documents distributed
to appropriate
individuals across plant
Change Requests made
from across plant
Change Request routed
for review
Change Notice
routed for approval
SOP authored
Object_Profile
- ds_name
- subclass
- objtype
- manager*
- cr_wflow
- ar_wflow*
- ar_review_period*
- ar_start*
Will be managed in the
custom UI similar to WP’s
DFC Extension
Lifecycle
18. Recommendation
for DCM v5.0
18
Authoring and Routing CNs & CRs
Process: Create CN and
Route for Review
SOP routed
for review
SOP versioned
and edited
SOP made
Effective
Documents distributed
to appropriate
individuals across plant
Change Requests made
from across plant
Change Request routed
for review
Change Notice
routed for approval
SOP authored
Authorized User
DCM
logic
Select Menu
Function: Create
CN
Enter CN
attributes and
attach documents
Select Document
or CN and Menu
Function: Route
for Review
Select Workflow
and "Promote on
Completion"
Receive CN in
inbox
Initiate
Workflow
Assign:
ACL=InProgress
Status=InProgress
Folder=InProgress
Forward
notification of
rejection to
Originator
and previous
participants
Display
Application
Profile
Create CN
and assign
CN number
WF
Assignment for
Doc type/
profile?
Display
Workflow
options
No
Yes
Approve or
Reject?
Halt workflow,
delete router
Record status
of CN
Reject
Record status
of CN
Auto Promote
attached
Documents to
Reviewed
State
Approve
Lifecycle & Workflow
UI & DFC Extension
19. Recommendation
for DCM v5.0
19
Authoring and Routing CNs & CRs (cont’d)
Issue CN or
document(s)
Folder: In-Progress
ACL: dcm_in-progress_document
dcm_in-progress_folder
CN Routing for Approval
Route for
Approval
Folder: Approved
ACL: dcm_approved_document
dcm_approved
Folder: Rejected
ACL: dcm_retired_document
dcm_retired_folder
Approve
Reject
Disapprove
Proposed DCM Lifecycle and Workflow:
Start In-Progress Approved
Rejected
• Set ACL
• Set folder location
• Render PDF or TBR
• Set CN attributes
• Promote to Approved
20. Recommendation
for DCM v5.0
20
Authoring and Routing CNs & CRs
Process: Create CN and
Route for Approval
SOP routed
for review
SOP versioned
and edited
SOP made
Effective
Documents distributed
to appropriate
individuals across plant
Change Requests made
from across plant
Change Request routed
for review
Change Notice
routed for approval
SOP authored
Lifecycle & Workflow
Authorized User
DCM
logic
Select Document
or CN and Menu
Function: Route
for Approval
Select Workflow
and "Promote on
Completion"
Receive CN in
inbox
Initiate
Workflow
Forward
notification of
rejection to
Originator
and previous
participants
WF
Assignment for
Doc type/
profile?
Display
Workflow
options
No
Yes
Approve or
Reject?
Halt workflow,
delete router
Record status
of CN
Reject
Record status
of CN
Auto Promote
attached
Documents to
Reviewed
State
Approve
Forward
notification of
rejection to
Originator
and previous
participants
Disapprove
Demote
Documents to
InProgress
State
21. Recommendation
for DCM v5.0
21
Authoring and Routing CNs & CRs (cont’d)
Issue CN or
document(s)
Folder: In-Progress
ACL: dcm_in-progress_document
dcm_in-progress_folder
CN Routing for Review
Route for
Review
Folder: Approved
ACL: dcm_approved_document
dcm_approved
Folder: Rejected
ACL: dcm_rejected_document
dcm_rejected_folder
Approve
Reject
Proposed DCM Lifecycle and Workflow:
Start In-Progress Approved
Rejected
• Set ACL
• Set folder location
• Render PDF or TBR
• Set CN attributes
• Promote to Approved
22. Recommendation
for DCM v5.0
22
Authoring and Routing CNs & CRs
Process: Route CR for
Review
SOP routed
for review
SOP versioned
and edited
SOP made
Effective
Documents distributed
to appropriate
individuals across plant
Change Requests made
from across plant
Change Request routed
for review
Change Notice
routed for approval
SOP authored
Authorized User
DCM
logic
Select Menu
Function: Create
CR
Enter CR
attributes and
attach documents
Select CR and
Menu Function:
Route for Review
Select Workflow
Receive CR in
inbox
Initiate
Workflow
Assign:
ACL=InProgress
Status=InProgress
Folder=InProgress
Forward
notification of
rejection to
Originator
and previous
participants
Display
Application
Profile
Create CR
and assign
CR number
WF
Assignment for
Doc type/
profile?
Display
Workflow
options
No
Yes
Approve or
Reject?
Halt workflow,
delete router
Record status
of CR
Reject
Record status
of CR
Auto Promote
attached
Documents to
Reviewed
State
Approve
UI & DFC Extension
Lifecycle & Workflow
23. Recommendation
for DCM v5.0
23
Authoring and Routing CNs & CRs (cont’d)
Issue CR Folder: In-Progress
ACL: dcm_in-progress_document
dcm_in-progress_folder
Change Request Lifecycle
Route for
Review
Folder: Approved
ACL: dcm_approved_document
dcm_approved
Folder: Rejected
ACL: dcm_rejected_document
dcm_rejected_folder
Approve
Reject
Proposed DCM CR Lifecycle & Workflow:
Start CRIn-Progress CRApproved
CRRejected
• Set ACL
• Set folder location
• Render PDF or TBR
• Set CR attributes
• Promote to CR Approved
24. Recommendation
for DCM v5.0
24
Authoring and Routing CNs & CRs
4i workflow & lifecycle can be used to
address DCM CN and CR routing
requirements
Authoring process can be handled through
the new UI and DFC extension
Conclusion
25. Recommendation
for DCM v5.0
25
Controlled Document Lifecycle
Workflow Management
Authoring and Routing CNs & CRs
• Data Model
• DCM Application Administration
• WCM and DCM Code Extensions
Analysis
26. Recommendation
for DCM v5.0
26
Data Model
Contributor or
Coordinator
Contributor
• Creates/imports a new controlled
document from a template or from
an existing document or modifies
an existing controlled document.
• Selects the lifecycle if there is more
than 1 lifecycle. The appropriate
document number and prefix is
automatically populated if it was
configured.
• Populates attributes assigned per
document or takes the default from
the document class.
• Creates a new Change Notice and
attaches the new or modfied
document(s). Optional step.
• Routes the document or CN for
review or approval. Selects a WF,
if not assigned.
Reviewer /
Approver
• The workflow ACLs
are adjusted based on
the workflow profile
• Notification is sent to
the appropriate users
assigned to the
document
• Assigns status to
“Effective”
• Assigns the Effective
ACL to all documents
• Closes the CN if one exist
• Sends documents TBR
Process:
DCM System
Distribution A Distribution B
• Notified via e-mail
• Views the documents via
Acrobat reader
• Replies to TBR notification
by entering password
• Print a hard copy
27. Recommendation
for DCM v5.0
27
Data Model (cont’d)
Understanding DCM documents, CNs, and CRs
Application <ds_config & ds_config_base>, <promo_profile>, <object_profile>
Document Class <object_profile>
<controlled document>,
<promotions>
<distribution>
Document
CN
• Picklist values
• Workflow
• Lifecycle
• Default values
• Business rules
CR
• Picklist values
• Workflow
• Lifecycle
• Default values
• Business rules
Doc Types
• Picklist values
• Workflow
• Lifecycle
• Default values
• Business rules
Application
Doc Type
Lifecycle
(subclass)
Doc Types
• Manager
• CR
• Auto review
workflow
• Auto review
period
• Auto review
days
Doc Types
• Manager
• Auto review
period
• Auto review
days
28. Recommendation
for DCM v5.0
28
Data Model (cont’d)
DCM Object Model:
dm_document
SOP, Plant Drawing
- ds_name
- revision
- effect_start
- effect_end
- next_review*
- creator
- doc_state
- doc_mode
- effect_now
- doc_state_type
- manager*
- dist_name
- ar_start*
- ar_review_period*
- discipline
- plant_section
- system_level
- r_object_type
- subclass
- area
- operation
<controlled document>
support_document
auto_assign
- assigned_id
- assign_name
- ds_name
- assign_type
- objtype
- subclass
- area
- operation
distribution
- dist_name
- user_group
- r_object_type
dm_router
- r_object_type
wflow_profile
- r_object_type
Object_Profile
- ds_name
- subclass
- objtype
- manager*
- cr_wflow
- ar_wflow*
- ar_review_period*
- ar_start*
Features:
• Object_profile (a.k.a document class): groups
document types based on manager, lifecycle, CR
workflow, autoreview workflow, number of days to
start the autoreview process, and the number of
days until the next required review. These attributes
will be used as default values to a DCM document.
• DCM controlled documents have the same
object_profile attributes such as manager, ar_start,
ar_review_period for document specific attributes.
When a document or Change notice is routed for
review or approval, DCM checks the document
specific attributes, if the values are null, it checks
the object_profile for default values.
• State_dist: groups distribution lists based on object
type, lifecycle, and lifecycle state name.
• Auto_assign: groups distribution list, router, and
workflow profile. This information is mapped against
a DCM document through its subclass, area,
operation, and object_type attributes.
• DCM uses the controlled document’s “creator”
attribute as the person to send email notifications
on specific events.
• Autonumber: contains the prefix and number
information for document assignment.
Change Notice
- ds_name
- reason_code
- description
- date_sent
- date_due
- effect_proposed
- action
- notes
- creator
read_understood
- randu_user
- randu_date
- randu_obj_id
- randu_obj_name
- randu_obj_version
- randu_obj_title
- randu_sent
autonumber
- objtype
- subclass
- prefix
- last_number
- max_range
- min_range
State_dist
- objtype
- subclass
- state_name
- dist_name
29. Recommendation
for DCM v5.0
29
Data Model (cont’d)
Proposed WCM & DCM Object Model:
dm_document
SOP, Plant Drawing
- revision
- effect_start
- effect_end
- next_review*
- creator
- dist_name
- doc_state
- doc_mode
- effect_now
- doc_state_type
- manager*
- ar_start*
- ar_review_period*
- r_object_type
- subclass
- area
- operation
- discipline
- plant_section
- system_level
- r_object_id
<controlled document>support_document
dm_sysobject
- a_has_relations
- a_category
- a_effective_label (R)
- a_effective_date (R)
- a_expiration_date (R)
- a_effective_flag (R)
- a_publish_formats (R)
auto_assign
- assigned_id
- assign_name
- ds_name
- assign_type
- objtype
- subclass
- area
- operation
distribution
- dist_name
- user_group
- r_object_type
dm_workflow
- r_object_type
- r_creatpr_name
- group_name
- r_current_state
- r_component_label
- r_current_state (last state)
- r_current_state
- authors
autonumber
- objtype
- subclass
- prefix
read_understood
- randu_user
- randu_date
- randu_obj_name
- randu_obj_version
- randu_obj_id
- randu_obj_title
- randu_sent
- last_number
- max_range
- min_range
CAS requires the following attributes:
- appid
- rentention_start
- no_purgeCan we manage the
relationship between
document, dist’n, and WF
in a different manner?
• Can we eliminate required attributes?
• Can “area” and “operation” be added in
sysobject?
30. Recommendation
for DCM v5.0
30
Data Model (cont’d)
Proposed WCM & DCM Object Model:
dm_document
Change Notice
- reason_code
- description
- date_sent
- date_due
- effect_proposed
- action
- notes
- creator
dm_sysobject
- priority
- lifecycle_states (R)
- auto_ind
wcm_change_set
dm_folder
r_creator_name
description
Change Request
- ds_name
- reason_code
- description
- creator
CAS requires the following attributes
in CR & CN:
- appid
- rentention_start
- no_purge
Can CN and CR be children
of wcm_change_set?
Is there a need to version
CNs and CRs if childern of
dm_document?
CNs do not have to be
versioned. However CRs
require some form of
version control
38. Recommendation
for DCM v5.0
38
DCM Application Administration
DCM Application Administration can be
handled in the 4i environment
There is a need for a lightweight
Administration UI for Managers
Conclusion
39. Recommendation
for DCM v5.0
39
Controlled Document Lifecycle
Workflow Management
Authoring Routing CNs & CRs
Data Model
DCM Application Administration
• WCM and DCM Code Extensions
Analysis
40. Recommendation
for DCM v5.0
40
WCM & DCM Code Extensions
DCM
(new customizations)
DCM Customizations in
Workspace
DCM Customizations in IC
WDK
&
IC2
DFC
DCM dm_procedures, dm_jobs, & dm_methods
41. Recommendation
for DCM v5.0
41
WCM & DCM Code Extensions (cont’d)
WP
WCM Extensions
com.documentum.wcm
com.documentum.wcm.xml
com.documentum.wcm.zip
com.documentum.webclient
com.documentum.webclient.listitem
com.documentum.webclient.operations
com.documentum.webclient.views
com.documentum.webclient.xml
com.documentum.webclient.rightsite
DFC
Analysis of WCM DFC extension classes
Contains WebPublisher business logic. Contains
methods to perform controlled operations such
as how to checkout in WebPublisher.
Contains methods to handle XML parsing based
on xcerces APIs
Contains the document compression methods.
Contains WebPublisher UI methods .
Contains WebPublisher’s link to Righsite methods .
View
code
43. Recommendation
for DCM v5.0
43
WCM & DCM Code Extensions (cont’d)
Option#1:
• Combine WP and DCM data models
• Separate WP and DCM DFC extensions
• Separate WP and DCM WDK UI extensions
Pros:
• DCM will not be dependent on WP
Con:
• More development work
• More training & ramp time required
Proposed WDK & DFC extensions
Option#2:
• Separate WP and DCM data models
• Build separate DCM business logic as a DFC extension - com.documentum.DCM
• Reuse WCM’s DFC layer utilities - com.documentum.xml & com.documentum.zip
• Share UI framework for controlled documents
Pros:
• Less development & less ramp time
Con:
• Interoperability issues may arise such as conflicts
• Larger data model overhead if both products are installed
• Similar attributes will exist in both data models
44. Recommendation
for DCM v5.0
44
WCM & DCM Code Extensions (cont’d)
Option#3:
• Combine WP and DCM data models
• Build separate DCM business logic as a DFC extension
• Reuse WCM’s DFC layer utilities
• Share UI framework for controlled documents
Pros:
• Less development & less ramp time
• Interoperability issues will my under control
• Lesser data model overhead if both products are installed
Con:
• Controll object model enhancement for WP & CSS to avoid conflicts
Proposed WDK & DFC extensions
46. Recommendation
for DCM v5.0
46
WCM & DCM Code Extensions (cont’d)
DCM and WP are based on distinct functionality with 4 levels of usage:
DCM Consumer (Viewers)
• View “effective” documents
• Search controlled documents
• Submit Change Request
• Generate Reports
• TBR notification & signoff
DCM Contributor (Author)
• Create or import new controlled docs.
• Modify ‘effective’ documents
• Review and approval signoff
• Submit documents for review/approval
• Create & submit Change Notices
DCM Coordinator (manager)
• Perform all Contributor functions
• Configure document types
• Configure promotion profiles
• Configure workflow and distributions
• Change status & promotion state
WP Author
• Create or import new controlled docs.
• Modify ‘active’ documents
• Review and approval signoff
• Submit documents for review/approval
WP Developer
• Perform all Manager functions
• Configure folders
• Generate reports
• Setup cabinets and folders
• Create & submit Change Sets
DCM Administrator
• Install and configure
• Create document types & attributes
• Create ACLs
• Create Users and Groups
• Setup cabinets and folders
WP Administrator
• Install & configure
• Create document types & attributes
• Create ACLs
• Create Users and Groups
• Create lifecycles
• Create worfklows
WP Manager
• Perform all Author functions
• Review/audit workflow activities
Common
UI Framework
47. Recommendation
for DCM v5.0
47
WCM & DCM Code Extensions (cont’d)
DCM Distinct features
DCM Business Process DCM Business Logic Code Extensions
• TBR process • DCM read_understood object can be added to the WCM
data model
• Create DCM DFC extension to manage TBRs
• Create or integrate printing functionality
• Create a job to run TBR server method
• Additional attributes in Change Notices such as
reason_code, date_sent, date_due, effect_proposed,
action, and note
• DCM CN object can be added as a child to dm_document
• Create additional CN logic to DCM extension
or
• Add attributes to wcm_change_set object and enhance CS
business logic, if necessary
• Object_profile (a.k.a document class) that groups
document types based on manager, lifecycle, CR
workflow, autoreview workflow, number of days to
start the autoreview process, and the number of days
until the next required review. These attributes will be
used as default values to a DCM document.
• Create a DCM_config object as a child of wcm_config object
• Create additional business logic classes or methods to
handle default values
• Annotations • Include necessary DocViewer integrations
• Assigning controlled documents to 1 or more
workflow and distribution objects
• DCM auto_assign and distribution objects can be added to
the WCM data model
• Additional business logic will be created to manage
document association
• CAS integration • Include necessary CAS integrations
48. Recommendation
for DCM v5.0
48
WCM & DCM Code Extensions (cont’d)
WP
IC2
WDK
WCM Extensions
com.documentum.wcm
com.documentum.wcm.xml
com.documentum.wcm.zip
DFC
DCM
DCM Extensions
com.documentum.DCM Option#2:
•Separate WP and DCM data models
•Build separate DCM business logic as
a DFC extension
•Reuse WCM’s DFC layer utilities
•Share UI framework for controlled
documents
WCM WP UI
(jsp, html, xml,
wcm classes)
DCM UI (jsp, html,
xml, DCM classes)
Option#2:
Framework
49. Recommendation
for DCM v5.0
49
WCM & DCM Code Extensions (cont’d)
WP
WCM Extensions
com.documentum.wcm
com.documentum.wcm.xml
com.documentum.wcm.zip
DFC
DCM
DCM Extensions
com.documentum.DCM Option#3:
•Combine WP and DCM data
models
•Build separate DCM business logic
as a DFC extension
•Reuse WCM’s DFC layer utilities
•Share UI framework for controlled
documents
Option#3:
IC2
WDK
WCM WP UI
(jsp, html, xml,
wcm classes)
DCM UI (jsp, html,
xml, DCM classes)
Framework
50. Recommendation
for DCM v5.0
50
WCM and DCM Code Extensions
Build separate DCM business logic as a
DFC extension
Reuse WCM’s DFC layer utilities
Share UI framework for controlled
documents
Conclusion
51. Recommendation
for DCM v5.0
51
Controlled Document Lifecycle
Use 4i lifecyle
Workflow Management
Use 4i workflow
Authoring and Routing CNs & CRs
Use combination of 4i lifecycle and workflow
Data Model
Merge WCM and DCM data model
DCM Application Administration
Use 4i lifecylce, data dictionary, and DCM_config
to address this requirement
WCM and DCM Code Extensions
Build separate DCM code extension, reuse WCM
utility DFC extensions, and share UI framework
DCM Recommendation
