UKoom » WDK Application http://www.ukoom.com Documentum, SharePoint, Alfresco, ECM... Thu, 13 May 2010 00:21:48 +0000 http://wordpress.org/?v=2.8.5 en hourly 1 Check in v.s. Save http://www.ukoom.com/check-in-v-s-save.htm http://www.ukoom.com/check-in-v-s-save.htm#comments Sun, 02 May 2010 13:53:26 +0000 ukoom http://www.ukoom.com/?p=1065

Webtop lets you check in a document as the same (existing) version. However, when you do this the Content Server never sees a checkin call or event. Webtop simply sets the new file as content, updates any changed attributes, and saves the object. So a dm_save event occurs rather than dm_checkin.

It becomes more obvious if we look at the corresponding API call descriptions.

  • checkin – creates a new version of an object in the repository and removes the lock from the previous version.
  • save – writes the object to the repository without creating a new version of the object.

Both of these methods have an optional argument to retain lock on the resulting object (new version for checkin and existing version for save). This argument defaults to FALSE – the lock is gone after the operation.

So why do we care? Normally we don’t need to. However, if we turn notification on for a document we need to remember this difference between checkin and save. By default, notifications are sent only for checkin event occurrences. So we won’t get a notification if the document was “checked in as same version”.

Similarly, other behavior (such as auditing) tied to events may be affected.

This article is from http://doquent.wordpress.com/2008/08/20/check-in-as-same-version/

Related Posts

]]> http://www.ukoom.com/check-in-v-s-save.htm/feed 0 Webtop 6.5SP2 Fixed Problems – MAXLENGTH http://www.ukoom.com/webtop-65sp2-fixed-problems-maxlength.htm http://www.ukoom.com/webtop-65sp2-fixed-problems-maxlength.htm#comments Thu, 23 Jul 2009 22:28:40 +0000 ukoom http://www.ukoom.com/?p=659 Missing MAXLENGTH support for string type of attributes (WEBTOP4521)
Text input controls (dmf:text and derived controls) in Documentum do not support the MAXLENGTH
attribute available in the HTML standard, an attribute that limits the number of characters a user
can enter in a text field.
Text input controls have been enhanced to support the MAXLENGTH attribute that can be defined
for string type of attributes. If MAXLENGTH has been defined for a string type of attribute, the value
of MAXLENGTH will determine the maximum number of characters that the user can enter in a text
field. For example, the MAXLENGTH attribute can be defined for a text control as follows:
<dmf:text name=”txtSearch” id=”txtSearch” size=”35″ maxlength=”40″
defaultonenter=”true” tooltipnlsid=’MSG_GO’ autocompleteid=
“ac_simplesearch”/>
Data dictionary bound controls such as dmfx:docbaseattributevalue, dmf:docbaseattribute, and
dmfx:docbaseattributelist set the maximum input length of the text control to the length defined for
the string type of attribute in the data dictionary.

Related Posts

]]> http://www.ukoom.com/webtop-65sp2-fixed-problems-maxlength.htm/feed 0 Webtop 6.5SP2 Fixed Problems – 1 http://www.ukoom.com/webtop-65sp2-fixed-problems-1.htm http://www.ukoom.com/webtop-65sp2-fixed-problems-1.htm#comments Thu, 23 Jul 2009 22:27:41 +0000 ukoom http://www.ukoom.com/?p=657 An error occurs when Webtop users with the Version permission create a new document(161635/WEBTOP3945, WEBTOP7159)
The “No write access” error occurs when a user with the Version permission creates a new document (dm_document object) in Webtop. However, a blank document is created successfully.
You can enable Webtop users with the Version permission to create dm_document objects by customizing the newdocument_component.xml file and setting the value of the <enabled> tag to “true”.
Modify the newdocument_component.xml file by adding the following code below the code for combo_defaults:
<wdk_new_doc_aspect>
<enabled>false</enabled>
<exclusion_list></exclusion_list>
</wdk_new_doc_aspect>
1. This configuration enables users who do not have the Delete permission on the object being created, to create a new document as the object owner. For example, if you enable this behavior,users with the Version permission can create new documents.
2. When this option is enabled, the application attaches a temporary permission by attaching a new aspect and removes the aspect on the first version.
3. If you specify any custom types for dm_document, this behavior does not apply for these types even if the option is enabled in step 2.
Note: This configuration is supported from Documentum 6.5 SP2 and requires the Documentum 6.5 SP2 Webtop.dar to be compatible with the Content Server.

Related Posts

]]> http://www.ukoom.com/webtop-65sp2-fixed-problems-1.htm/feed 0 New Features in WDK6 http://www.ukoom.com/new-features-in-wdk6.htm http://www.ukoom.com/new-features-in-wdk6.htm#comments Fri, 10 Jul 2009 00:05:02 +0000 ukoom http://www.ukoom.com/?p=633

In D6, WDK has introduced many new features/functionalities to give rich UI/better navigation and improved performances. D6 includes the following functionalities

  1. Configuration service modifications
  2. Right-click context menus
  3. Presets
  4. Field tab-through order configuration
  5. Auto complete
  6. Keyboard shortcuts
  7. Remove checkboxes
  8. Multi-object select (ACLs, Properties, Lifecycles)
  9. Assigning relationships
  10. Emphasizing lifecycles
  11. Dynamic filters (e.g., Starts With)

Related Posts

]]> http://www.ukoom.com/new-features-in-wdk6.htm/feed 0 WDK6 – Lifecycle enhancements http://www.ukoom.com/wdk6-lifecycle-enhancements.htm http://www.ukoom.com/wdk6-lifecycle-enhancements.htm#comments Mon, 29 Jun 2009 00:25:18 +0000 ukoom http://www.ukoom.com/?p=638 Lifecycle is now displayed on the Properties Screen (part of the default attribute set). Lifecycle Users are able to apply a lifecycle on documents at creation time (and Import, Create, Checkin), or later, via the Properties screen. The process of applying a lifecycle to a document has been enhanced to include the ability to specify the initial lifecycle state and the alias set. The current success/error messages for the lifecycle‑related actions displayed on the Message Bar that involve a lifecycle state change (Apply, Detach, Promote, Demote, Suspend and Resume) will be enriched to contain pertinent information about the object lifecycle state (previous and current).

Related Posts

]]> http://www.ukoom.com/wdk6-lifecycle-enhancements.htm/feed 0 WDK Based Applications http://www.ukoom.com/wdk-based-applications.htm http://www.ukoom.com/wdk-based-applications.htm#comments Thu, 27 Nov 2008 08:29:35 +0000 Rexleed http://www.ukoom.com/?p=180 wdk-concept-dctm

What is WDK
Web Development Kit (WDK) is a developer’s toolkit, based on industry standards,
that facilitates the development of complex web-based applications that connect to
Documentum Content Server and Documentum content repositories. WDK provides
a J2EE development platform and contains a large library of reusable components
and controls that perform common Documentum content management functions and
provide a uniform user interface to applications built with WDK. The Documentum web
client applications described below were developed using WDK. These applications can
be customized using WDK.

What is WDK application

WDK applications can have four or more application layers: The WDK layer, the
webcomponent layer, a layer that extends Webtop (such as Web Publisher), the custom
layer, and an optional Webtop layer. A customized WDK application is a web client that
configures and extends the components in the WDK and webcomponent layers.

What is WDK-Based application

A WDK-based application is built on WDK (Web Development Kit) functionality. A
WDK-based application lets you access an EMC | Documentum repository over the web.

What is WebTop
Server and provides access to a content repository, formerly called a Docbase. Webtop
allows you to perform many document management tasks, from a document’s creation to
its archiving, and everything in between. Content Server automates numerous document
management tasks and provides automatic routing, renditioning, versioning, security,
and many other functions.

What is Web Publisher
Web Publisher is a browser-based application that simplifies and automates the creation
of content for web sites. Authors create and modify content without having to know how
to construct web pages. Content is automatically published to multiple sites in multiple
languages and formats. Developers use Web Publisher to maintain web page templates
and site structures. Administrators maintain the Web Publisher system settings.

Web Publisher connects to Content Server to store content in a repository and perform
content management functions. Documentum Site Caching Services (SCS) is used to
publish content from a repository to a designated location on a web site.

Note: web publisher portlet builder/web publisher page builder/ web publisher contributor

Relationship between them

Webtop and webPublisher are WDK-Based applications of WDK

Documentum Web client applications are built on WDK. Webtop is a reference
implementation of WDK. Documentum Administrator, Digital Asset Manager, Web
Publisher, and other client applications are extensions of Webtop. WDK for Portlets
is an application built on WDK.

Development on WDK

if we wanna develop a new Web application , we can extend one of the WDK clients such as WebTop or Web Publisher or it can be a new application based on WDK.

This is extended from Yuewen’s study note

Related Posts

]]> http://www.ukoom.com/wdk-based-applications.htm/feed 0 How does WDK work http://www.ukoom.com/how-does-wdk-work.htm http://www.ukoom.com/how-does-wdk-work.htm#comments Tue, 11 Nov 2008 00:21:11 +0000 admin http://www.ukoom.com/?p=9 how does WDK work

Related Posts

]]> http://www.ukoom.com/how-does-wdk-work.htm/feed 0