手动设置 r_creation_date ？
我正在开发一个 DFS 应用程序（在 C# 上），它将文档从另一个文档管理系统导入 Documentum Server。部分地，我必须决定：如何导入“创建日期”（r_creation_date）？我的意思是：Documentum 的意识形态假设值 r_creation_date 将由服务器设置（作为当前日期/时间）。 WebTop 不允许在文档创建期间设置它；或修改它。在“另一个文档管理系统”中，思想是不同的：我们可以手动将任何日期设置为文档创建日期。因此：
如果我的软件将我自己的值设置到 r_creation_date 中，Documentum Server 意识形态是否可以接受
将会从实施的角度来看有什么问题吗？我发现创建操作会忽略我指定的“r_creation_date”。我可以将自己的值设置为 r_creation_date 的唯一方法是在创建对象后调用 Update 命令。我还没有找到 DFS 参考中描述的这种行为，所以也许这是我可以依赖的未记录的行为？也许这样的 r_creation_date 的 ivewrtiting 会导致将来出现一些问题？
I am developing a DFS application (on C#) that imports a document from another document management system into Documentum Server. Partially, I have to decide: how to import 'Creation date' (r_creation_date)? I mean: Documentum's ideology supposes that value r_creation_date will be set by the server (as current date/time). WebTop does not allow to set it during documentum creation; or to modify it. In the 'another document management system' the ideology is different: we can set any date as document Creation Date manually. So:
Will it be acceptable from Documentum Server ideology if my software sets my own value into the r_creation_date
Will be there problems from implementation point of view? I have found out that Create operation ignores 'r_creation_date' I specify. The only way I can set my own value to r_creation_date is to call Update command after the object is already created. I have not found this behaviour described in DFS Reference, so maybe it is undocumented behavior I can rely on? Maybe such ivewrtiting of r_creation_date will lead to some problems in future?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
就我个人而言，我不建议通过代码修改此日期。
我过去处理这个问题的方法是使用自定义属性，例如“my_creation_date”，并将该值用于显示目的。
您是为此应用程序创建自定义前端，还是为用户使用开箱即用的 Webtop？如果您要创建自定义前端，那么使用您自己的属性很简单。否则，您将需要进行一些 WDK 修改才能显示该日期而不是 r_creation_date。
此外，如果遇到系统中实际创建日期的问题，保留实际系统创建日期也很有用。即使是审计记录也无法保留，除非您永久保存它们。
Personally, I wouldn't recommend modifying this date via code.
The way I have dealt with this in the past is to use a custom attribute, for instance "my_creation_date" and to use that value for display purposes.
Are you creating a custom front-end for this application, or using the out-of-the-box Webtop for users? If you are creating a custom front-end then it is trivial to use your own attribute. Otherwise, you will need to do some WDK modifications to display that instead of r_creation_date.
In addition, it can be useful to preserve the actual system creation date, should it come to a question of when this was actually created in the system. Even audit records would not preserve that unless you maintained them permanently.