Hello All,
We are using My Documentum for Microsoft Outlook version 6.6 Patch 09. We are considering our options for enhancing / improving the product behavior due to some limitations and issues we are encountering. I would like to know more about any potential customization options available for this product.
More specifically, one issue we are encountering is that object type-level constraints are not being enforced by MDO. The desired behavior is that an attribute becomes required only when one or two specific values are selected from a combo box that has Value Assisstance defined. The other clients like Webtop and DA provide a message saying that required attributes are not filled in and does not let you create the object, but MDO does not and allows you to continue processing and attempts to save the object. This scenario uses the Save to Repository dialog box within MDO. Ideally, the Save to Repository dialog box within MDO would display a message back to the user instructing him to also fill in the other attribute(s).
Any suggestions for customization options that would allow us to get around this limitation?
Notes and Questions:
- Searching through the product documentation (Admin Guide, User Guide, Release Notes, Patch ReadMe files, etc.) does not seem to be mention any any reference that would indicate how to go about this. References to customization in the docs are more like what I would consider configuration.
- The Administration Guide contains this bit when describing the MDO architecture: "The Microsoft Outlook component is the Outlook “façade”, meaning it provides unified access to Outlook data regardless of Outlook version, the type of mail transport and data field in use. The Form Manager allows for the customization of native and custom Outlook forms."
- I tried to look at the installed custom Outlook forms but did not see any indication that the client-side behavior could be changed.
- We have a TBO associated with the custom object types handled via MDO. However, we believe that by the time the TBO detects this condition, there would be no way to throw a message up the stack and back to the user.
- Would it be possible to extend / customize the MDO war / ear application on the Web Application Server (e.g., dco-smartfolder.war or ucf.war module) to intercept this condition and prevent further processing until the situation is rectified by the user?
- Could the synchronization mechanism be somehow altered to take this situation into account and record a collision if certain criteria is not met?
We are aware that an asynchronous process could be used to deal with this issue (e.g., a job that runs every X minutes).
Thank you in advance for any suggestions.
JPG.
