Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Solution Description
3rd
Advanced Features
Content Features
Workspace support Approval workflow Preview, Attachments Publish, contentSpot Catalog Tooling Marketing Tooling Attachment Tooling Integration services Workspace enablement Workspace enabled bulk load capability
Business Tooling
Commerce Workspaces
Workspaces
Provide separation of data for business users Changes/preview are visibly scoped a workspace Business users in other workspaces do not see other workspace changes
Task Groups
Group tasks within a workspace that need to share data but have different approval or scheduling needs Approve work directly to production
Tasks
Unit of assigned work within a task group Content contributors are assigned to tasks Tasks appear on the content contributor's task list within accelerator until they mark them complete
Commerce Attachments
Attachments are any file assets
Images Reference documents (pdfs, doc etc.) Engineering diagrams URLs
Workspace1
Workspace2
WorkspaceN
WC Read Schem a
WC Read Schem a
...
WC Read Schem a WC Write Schem a (WS)
Workspace Preview
read-only
WC Read Schema
WC Write Schema
A B
A B
Content update
Loader
Store/config update
Workspace Preview
read-only
WC Read Schema
WC Write Schema
A B
A B
Content update
Loader
Product Managers
Attachment Commit
File Syndication
WC File System
Commerce Content Workspace Enabled Workspac e Context Attachments Service Data Model
Workflow Engine
Product Management Tasks
Attachment Commit
Workspac
File Syndication
Schema Management
Workspace schema creation is done during instance creation via Ant task. (In Toolkit there is an additional enableWorkspace.bat). Fixed number of reusable workspaces managed in CMWSSCHEMA table. Schemas are mapped to workspace through identifiers and allocated during Workspace activation and must be released explicitly when WS is complete. Each Workspace contains read/write schemas
Under Darwyn a new persistent model exists for maintaining session information contained under ActivityToken. Content Context and Preview Context are
Default implementation of Resource Managers based on Access Beans (specify in the XML file) Resource Managers uses ActivityToken to switch schemas Resource Manager actions:
createResource expects an EntityData object.
Based on the class name provided it will pass
deleteResource
Default implementation performs the following:
If row does not exist in base / but in WS delete the row from WS Schema sql copy the record if not exists into the Workspace Schema and update the row to add WS info.