dcm next gen
TRANSCRIPT
WebPublisher 4.3
1Recommendation for DCM v5.0
Erwin Chiong03/15/2001v 3.2
Recommendation for DCM v5.01
2Current DCM Situation (contn)Current DCM development schedule:Q0(01) Q1 Q2 Q3 Q4 Q1(02) |-----------------------|------------------|------------------|-----------------|-----------------|DCM 1.3.1 DCM 1.4 DCM 4.3 DCM 5.0- Web Consumer -Web Consumer -Remove Workspace- Web Contributor -Web Coordinator -Interoperability & Installation (Review/Approve) (+Create, Import, Edit -Bug fixes- WS Coordinator Annotate, Route) CAS 4.3 -WS Coordinator -200 character support for audit trail -localization supportGMPharma 1.0 GMPharma 1.1- Web Consumer - Built on DCM 1.4 - WS Coordinator - Additional enhancements- WS Business Owner
Recommendation for DCM v5.03ObjectivesReview the technical details for building DCM on WP modelProvide the appropriate recommendation for DCM v5.0
Recommendation for DCM v5.04Controlled Document LifecycleWorkflow ManagementAuthoring and Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code ExtensionsAnalysisControlled Document LifecycleWorkflow ManagementAuthoring and Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code Extensions
Recommendation for DCM v5.05Controlled 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 approvalApproved: document is approved and ready for users to be trainedEffective: document is in-use and CURRENTRetired: document version is no longer in-use and has been supersepeded by a new effective verSuspended: document version is temporarily retired, and has been suspended by a new temporary effective version, but will be made effective again at some pointObsolete: all document version are no longer in use
Initial State(e.g. In-Progress)
EffectiveState
RetiredState
SuspendedState
ObsoleteState
PromotePromotePromoteSuperceded
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:
Recommendation for DCM v5.06Controlled document lifecycle (contd)DCM lifecycle program logic:
Recommendation for DCM v5.07Controlled document lifecycle (contd)
Initial State(e.g. In-Progress)
EffectiveState
RetiredState
SuspendedState
ObsoleteState
PromotePromotePromoteSuperceded
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:
Recommendation for DCM v5.08Controlled document lifecycle (contn)
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 AttributeAdd Version LabelLink to New LocationMove All links to locationRemove from Repeating AttributeRemove Link from Existing LocationRemove Version LabelRequest RenditionSet AttributeSet OwnerSet 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 (contd):
Recommendation for DCM v5.09Controlled Document Lifecycle
4i lifecycle can be used to address DCM lifecycle requirementsConclusion
Recommendation for DCM v5.010Controlled Document LifecycleWorkflow ManagementAuthoring and Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code ExtensionsAnalysis
Recommendation for DCM v5.011Workflow ManagementFeatures:Allow authorized users to route documents for review or approval and dynamically select a workflowSupport for auto assignment of documents to a workflow template, available parallel reviewers, required parallel reviewers, and distributionSupport for parallel reviewThe 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 rejectedReviewers/Approvers have the option to Approve, Disapprove, and Reject documents or CNsProcess:
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
ReviewReviewReview
Document ControlDC routes the newly revised documents to the appropriate users for approval
Assigns status to EffectiveAssigns the Effective ACL to all documents
RejectRejectApproved
State_dist- objtype- subclass- state_name- dist_name
Recommendation for DCM v5.012Workflow Management (contd)
DCM will use dm_workflow instead of dm_routerManaging task ACL is not currently available in WFM v4.2. Additional DCM/WP task method can be added to the workflow to perform this taskdm_workflow object type and associated processes will be replaced with the task ACL solution as well as using Alias setsParallel 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:
Recommendation for DCM v5.013Workflow Management
4i workflow can be used to address DCM and CAM workflow requirementsConclusion
Recommendation for DCM v5.014Controlled Document LifecycleWorkflow ManagementAuthoring and Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code ExtensionsAnalysis
Recommendation for DCM v5.015Authoring and Routing CNs & CRs
SOP routedfor review
SOP versioned and editedSOP made EffectiveDocuments distributed to appropriate individuals across plant
Change Requests made from across plant
Change Request routed for reviewChange Noticerouted for approval
SOP authored
Recommendation for DCM v5.016Authoring and Routing CNs & CRsProcess: Authoring
SOP routedfor review
SOP versioned and editedSOP made EffectiveDocuments distributed to appropriate individuals across plant
Change Requests made from across plant
Change Request routed for reviewChange Noticerouted 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 WPs
DFC Extension
Lifecycle
Recommendation for DCM v5.017Authoring and Routing CNs & CRs (contd)Issue CN or document(s)
Folder: In-ProgressACL: dcm_in-progress_document dcm_in-progress_folderCN Routing for Review
Route for Review
Folder: ApprovedACL: dcm_approved_document dcm_approved
Folder: RejectedACL: dcm_rejected_document dcm_rejected_folder
ApproveRejectIssue CR
Folder: In-ProgressACL: dcm_in-progress_document dcm_in-progress_folderChange Request Lifecycle
Route for Review
Folder: ApprovedACL: dcm_approved_document dcm_approved
Folder: RejectedACL: dcm_rejected_document dcm_rejected_folder
ApproveRejectIssue CN or document(s)
Folder: In-ProgressACL: dcm_in-progress_document dcm_in-progress_folderCN Routing for Approval
Route for Approval
Folder: ApprovedACL: dcm_approved_document dcm_approved
Folder: RejectedACL: dcm_retired_document dcm_retired_folder
ApproveRejectDisapprove
Recommendation for DCM v5.018Authoring and Routing CNs & CRsProcess: Create CN and Route for Review
SOP routedfor review
SOP versioned and editedSOP made EffectiveDocuments distributed to appropriate individuals across plant
Change Requests made from across plant
Change Request routed for reviewChange Noticerouted for approval
SOP authored
Lifecycle & Workflow
UI & DFC Extension
Recommendation for DCM v5.019Authoring and Routing CNs & CRs (contd)Issue CN or document(s)
Folder: In-ProgressACL: dcm_in-progress_document dcm_in-progress_folderCN Routing for Approval
Route for Approval
Folder: ApprovedACL: dcm_approved_document dcm_approved
Folder: RejectedACL: dcm_retired_document dcm_retired_folder
ApproveRejectDisapproveProposed DCM Lifecycle and Workflow:
Start
In-Progress
Approved
Rejected
Set ACL Set folder location Render PDF or TBR Set CN attributes
Promote to Approved
Recommendation for DCM v5.020Authoring and Routing CNs & CRsProcess: Create CN and Route for Approval
SOP routedfor review
SOP versioned and editedSOP made EffectiveDocuments distributed to appropriate individuals across plant
Change Requests made from across plant
Change Request routed for reviewChange Noticerouted for approval
SOP authored
Lifecycle & Workflow
Recommendation for DCM v5.021Authoring and Routing CNs & CRs (contd)Issue CN or document(s)
Folder: In-ProgressACL: dcm_in-progress_document dcm_in-progress_folderCN Routing for Review
Route for Review
Folder: ApprovedACL: dcm_approved_document dcm_approved
Folder: RejectedACL: dcm_rejected_document dcm_rejected_folder
ApproveRejectProposed DCM Lifecycle and Workflow:
Start
In-Progress
Approved
Rejected
Set ACL Set folder location Render PDF or TBR Set CN attributes
Promote to Approved
Recommendation for DCM v5.022Authoring and Routing CNs & CRsProcess: Route CR for Review
SOP routedfor review
SOP versioned and editedSOP made EffectiveDocuments distributed to appropriate individuals across plant
Change Requests made from across plant
Change Request routed for reviewChange Noticerouted for approval
SOP authored
UI & DFC Extension
Lifecycle & Workflow
Recommendation for DCM v5.023Authoring and Routing CNs & CRs (contd)Issue CR
Folder: In-ProgressACL: dcm_in-progress_document dcm_in-progress_folderChange Request Lifecycle
Route for Review
Folder: ApprovedACL: dcm_approved_document dcm_approved
Folder: RejectedACL: dcm_rejected_document dcm_rejected_folder
ApproveRejectProposed 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
Recommendation for DCM v5.024Authoring and Routing CNs & CRs
4i workflow & lifecycle can be used to address DCM CN and CR routing requirementsAuthoring process can be handled through the new UI and DFC extensionConclusion
Recommendation for DCM v5.025Controlled Document LifecycleWorkflow ManagementAuthoring and Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code ExtensionsAnalysis
Recommendation for DCM v5.026Data Model
Contributor or CoordinatorContributorCreates/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 / ApproverThe workflow ACLs are adjusted based on the workflow profileNotification is sent to the appropriate users assigned to the document
Assigns status to EffectiveAssigns the Effective ACL to all documentsCloses the CN if one existSends documents TBR
Process:DCM System
Distribution ADistribution B
Notified via e-mailViews the documents via Acrobat readerReplies to TBR notification by entering password Print a hard copy
Recommendation for DCM v5.027Data Model (contd)Understanding DCM documents, CNs, and CRs
Application, ,
Document Class
,
DocumentCN Picklist valuesWorkflowLifecycleDefault valuesBusiness rulesCR Picklist valuesWorkflowLifecycleDefault valuesBusiness rulesDoc Types Picklist valuesWorkflowLifecycleDefault valuesBusiness rules
ApplicationDoc TypeLifecycle (subclass)Doc Types ManagerCRAuto review workflowAuto review periodAuto review daysDoc Types ManagerAuto review periodAuto review days
Recommendation for DCM v5.028Data Model (contd)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
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 documents 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
Recommendation for DCM v5.029Data Model (contd)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
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, distn, and WF in a different manner?
Can we eliminate required attributes? Can area and operation be added in sysobject?
Recommendation for DCM v5.030Data Model (contd)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_purgeCan 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
Recommendation for DCM v5.031Data Model (contd)Proposed WCM & DCM Object Model:- subclass- objtype- manager*- cr_wflow- ar_wflow*- ar_review_period*- ar_start*
dm_sysobject
wcm_config
- review_notif- wip_symbol- staging_symbol- approved_symbol- active_symbol- expired_symbol- valid_web_formats - default_channel- doc_lifecycle- default_page- expiration_increment- default_workflow- thumbnail_v_size- thumbnail_h_size- edition_cache- cps_host_addr- cps_node_name- cps_formats (R)- text_formats (R)- graphic_formats (R)- wd_version_ind- display_comments_ind- comments_req_ind- available_events (R)- start_page- allow_author_import- delay_publish_active
DCM_config (object_profile & ds_config)
- unique_nameCan object_profile and other configuration attributes be a child of wcm_config?
Recommendation for DCM v5.032Data Model (contd)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
support_document- subclass- objtype- manager*- cr_wflow- ar_wflow*- ar_review_period*- ar_start*
Change Notice- reason_code- description- date_sent- date_due- effect_proposed- action- notes- creator
dm_sysobject
wcm_user_pref
- checkout_dir- default_channel- display_pref- wip_cache_config- diff_cmd_str- diff_directory- intelligent_viewer- alt_formats- alt_format_viewers
wcm_config
- review_notif- wip_symbol- staging_symbol- approved_symbol- active_symbol- expired_symbol- valid_web_formats - default_channel- doc_lifecycle- default_page- expiration_increment- default_workflow- thumbnail_v_size- thumbnail_h_size- edition_cache- 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)- cps_host_addr- cps_node_name- cps_formats (R)- text_formats (R)- graphic_formats (R)- wd_version_ind- display_comments_ind- comments_req_ind- available_events (R)- start_page- allow_author_import- delay_publish_active
DCM_config (object_profile & ds_config)
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
- priority- lifecycle_states (R)- auto_ind
wcm_change_set
dm_folder
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
r_creatpr_name
description
Change Request- unique_name
Recommendation for DCM v5.033Data Model (contd)Separate WCM & DCM Object Models:
dm_sysobject
dm_folder
wcm_edition
dm_cabinet
wcm_user_pref
wcm_channel_fld
wcm_config
wcm_channel
wcm_edition_fld
wcm_change_set
wcm_favorites
wcm_category
wcm_supporting_doc_folder
dm_sysobject
dm_document
DCM_config
DCM_support_doc
DCM_auto_assign
dm_persistent
DCM_readunderstood
DCM_change_request
dm_folder
DCM_autonumber
DCM_change_notice
Recommendation for DCM v5.034Data Model (contd)Proposed combined WCM & DCM Object Model:
dm_sysobject
dm_folder
wcm_edition
dm_cabinet
wcm_user_pref
wcm_channel_fld
wcm_config
wcm_channel
wcm_edition_fld
wcm_change_set
wcm_favorites
wcm_category
wcm_supporting_doc_folder
dm_document
DCM_support_doc
DCM_change_notice
DCM_config
DCM_auto_assign
DCM_autonumber
DCM_readunderstood
DCM_change_request
Recommendation for DCM v5.035Data Model
Merging WCM and DCM object types simplifies the data model and utilizes common attributesConclusion
Recommendation for DCM v5.036Controlled Document LifecycleWorkflow ManagementAuthoring and Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code ExtensionsAnalysis
Recommendation for DCM v5.037DCM Application Administration
- obj_plant_section- obj_discipline- obj_system_level- obj_area- obj_operation- wflow_temp_path- wflow_inst_path- wflow_status- obj_status- cn_reason_code
- server_methods
- rfr_promote- one_ip
ds_config
ds_config
ds_config_base- cr_reason_code
ds_config_base- unique_name
- ip_cn_status- app_cn_status- rej_cn-status- ip_cn_owner- app_cn_owner- rej_cn_owner- ip_cn_acl- app_cn_acl- rej_cn_acl
ds_config
ds_config_base- obj_profile_types- cr_type- ip_cr_location- app_cr_location- rej_cr_location- ip_cr_status- app_cr_status- rej_cr_status- ip_cr_owner- app_cr_owner- rej_cr_owner- ip_cr_acl- app_cr_acl- rej_cr_acl- cn_type- ip_cn_location- ip_cn_status- app_cn_status- rej_cn_status
DCM:
Lifecycle information
DCM Configuration folder
Not needed
Data dictionary
Move to DCM_config
Lifecycle information
Recommendation for DCM v5.038DCM Application Administration
DCM Application Administration can be handled in the 4i environmentThere is a need for a lightweight Administration UI for Managers Conclusion
Recommendation for DCM v5.039Controlled Document LifecycleWorkflow ManagementAuthoring Routing CNs & CRsData ModelDCM Application AdministrationWCM and DCM Code ExtensionsAnalysis
Recommendation for DCM v5.040WCM & DCM Code ExtensionsDCM (new customizations)DCM Customizations in Workspace DCM Customizations in IC
WDK& IC2 DFC
DCM dm_procedures, dm_jobs, & dm_methods
Recommendation for DCM v5.041WCM & DCM Code Extensions (contd)
WP
WCM Extensionscom.documentum.wcmcom.documentum.wcm.xmlcom.documentum.wcm.zipcom.documentum.webclientcom.documentum.webclient.listitemcom.documentum.webclient.operationscom.documentum.webclient.viewscom.documentum.webclient.xmlcom.documentum.webclient.rightsite
DFCAnalysis 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 basedon xcerces APIsContains the document compression methods.Contains WebPublisher UI methods .Contains WebPublishers link to Righsite methods .
View code
Recommendation for DCM v5.042WCM & DCM Code Extensions (contd)
WP
IC2
WDK
WCM Extensionscom.documentum.wcmcom.documentum.wcm.xmlcom.documentum.wcm.zipcom.documentum.webclientcom.documentum.webclient.listitemcom.documentum.webclient.operationscom.documentum.webclient.rightsitecom.documentum.webclient.viewscom.documentum.webclient.xml
DFC
Analysis of WCM DFC extension classes
WCM WP UI (jsp, html,xml, wcm classes)
Recommendation for DCM v5.043WCM & DCM Code Extensions (contd)Option#1: Combine WP and DCM data modelsSeparate WP and DCM DFC extensionsSeparate WP and DCM WDK UI extensionsPros: DCM will not be dependent on WPCon: More development workMore training & ramp time required Proposed WDK & DFC extensionsOption#2: Separate WP and DCM data modelsBuild separate DCM business logic as a DFC extension - com.documentum.DCMReuse WCMs DFC layer utilities - com.documentum.xml & com.documentum.zipShare UI framework for controlled documentsPros: Less development & less ramp timeCon: Interoperability issues may arise such as conflictsLarger data model overhead if both products are installedSimilar attributes will exist in both data models
Recommendation for DCM v5.044WCM & DCM Code Extensions (contd)Option#3: Combine WP and DCM data modelsBuild separate DCM business logic as a DFC extension Reuse WCMs DFC layer utilities Share UI framework for controlled documents Pros: Less development & less ramp timeInteroperability issues will my under control Lesser data model overhead if both products are installedCon: Controll object model enhancement for WP & CSS to avoid conflictsProposed WDK & DFC extensions
Recommendation for DCM v5.045WCM & DCM Code Extensions (contd)
WP
IC2
WDK
WCM Extensionscom.documentum.wcmcom.documentum.wcm.xmlcom.documentum.wcm.zip
DFC
DCM
WCM WP UI (jsp, html, xml, wcm classes)
DCM UI (jsp, html, xml, DCM classes)
Option#1: Combine WP and DCM data modelsSeparate WP and DCM DFC extensionsSeparate WP and DCM WDK UI extensions
com.documentum.DCMcom.documentum.DCM.xmlcom.documentum.DCM.zipDCM ExtensionsOption#1:
Recommendation for DCM v5.046WCM & DCM Code Extensions (contd)DCM and WP are based on distinct functionality with 4 levels of usage:
DCM Consumer (Viewers)View effective documentsSearch controlled documentsSubmit Change RequestGenerate ReportsTBR notification & signoff
DCM Contributor (Author)Create or import new controlled docs.Modify effective documentsReview and approval signoffSubmit documents for review/approvalCreate & submit Change Notices
DCM Coordinator (manager)Perform all Contributor functionsConfigure document typesConfigure promotion profilesConfigure workflow and distributionsChange status & promotion state WP AuthorCreate or import new controlled docs.Modify active documentsReview and approval signoffSubmit documents for review/approval
WP DeveloperPerform all Manager functionsConfigure foldersGenerate reportsSetup cabinets and foldersCreate & submit Change Sets
DCM AdministratorInstall and configureCreate document types & attributesCreate ACLsCreate Users and GroupsSetup cabinets and folders
WP AdministratorInstall & configureCreate document types & attributesCreate ACLsCreate Users and GroupsCreate lifecyclesCreate worfklows
WP ManagerPerform all Author functionsReview/audit workflow activitiesCommon UI Framework
Recommendation for DCM v5.047WCM & DCM Code Extensions (contd) DCM Distinct features
DCM Business Process
DCM Business Logic Code Extensions
TBR process
DCM read_understood object can be added to the WCM data modelCreate DCM DFC extension to manage TBRsCreate or integrate printing functionalityCreate 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_documentCreate additional CN logic to DCM extensionorAdd 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 objectCreate 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 modelAdditional business logic will be created to manage document association
CAS integration
Include necessary CAS integrations
Recommendation for DCM v5.048WCM & DCM Code Extensions (contd)
WP
IC2
WDK
WCM Extensionscom.documentum.wcmcom.documentum.wcm.xmlcom.documentum.wcm.zip
DFC
DCM
DCM Extensionscom.documentum.DCM
Option#2: Separate WP and DCM data modelsBuild separate DCM business logic as a DFC extensionReuse WCMs 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
Recommendation for DCM v5.049WCM & DCM Code Extensions (contd)
WP
WCM Extensionscom.documentum.wcmcom.documentum.wcm.xmlcom.documentum.wcm.zip
DFC
DCM
DCM Extensionscom.documentum.DCM
Option#3: Combine WP and DCM data modelsBuild separate DCM business logic as a DFC extensionReuse WCMs 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
Recommendation for DCM v5.050WCM and DCM Code Extensions
Build separate DCM business logic as a DFC extensionReuse WCMs DFC layer utilities Share UI framework for controlled documentsConclusion
Recommendation for DCM v5.051Controlled Document LifecycleUse 4i lifecyleWorkflow ManagementUse 4i workflowAuthoring and Routing CNs & CRsUse combination of 4i lifecycle and workflowData ModelMerge WCM and DCM data modelDCM Application AdministrationUse 4i lifecylce, data dictionary, and DCM_config to address this requirementWCM and DCM Code ExtensionsBuild separate DCM code extension, reuse WCM utility DFC extensions, and share UI frameworkDCM Recommendation
Recommendation for DCM v5.052
Next Steps
Recommendation for DCM v5.053
WebPublisherViper
UI Framework
WDK
Business Object Layer
WCM Extensions
DFC / xFiles
4i eContent ServerViper Extensions
IC2
Recommendation for DCM v5.0