/ Forums / Advansys Formativ / Commercial Formativ Solutions by Advansys / Message Saver 2.0 – Integration with External DMS

  • Creator
    Topic
  • #4730
    ihertanto
    Participant

    I have a few questions about this product:

    1. Can Message Saver be integrated with an external document management systems (ex. FileNet)?

    2. Is Message Saver efficient in exporting individual messages from large inboxes (3000+)? I cannot easily test this on our test environment.

    3. Would I be able to see a sample of the code by which Message Saver saves and converts messages to FML? Ideally we would like to program this functionality into a Formativ applet that runs on every incoming message.

    Thanks.

  • Author
    Replies
  • #8888
    Support 2
    Moderator

    At this stage Message Saver 2.0 cannot be integrated into a DMS beyond what is possible with the out-of-the-box features. However, the underlying technology which forms the basis of the product, the Advansys Message Saver Component for .NET, may be licensed by Advansys to approved customers.

    The Message Saver Component is the core engine which accepts a GroupWise Message object and converts it to an Advansys Portable Message file (FML), which in turn can be displayed by the free Advansys Message Viewer. It can be used as a COM component from any COM compatible language, such as Formativ, Delphi, VB etc. or used as a native .NET assembly. As it is a developer component, it does provides core functionality and not the UI or file naming/management features which are written in the Message Saver 2.0 applet (which makes calls to the Message Saver component for .NET). This component must be licensed separately to other Advansys products on an organization-wide license basis.

    quote:


    2. Is Message Saver efficient in exporting individual messages from large inboxes (3000+)? I cannot easily test this on our test environment.


    Not really sure how to answer this question. Efficiency and performance is relative. For the functionality it offers, we have made it as efficient as possible.

    quote:


    3. Would I be able to see a sample of the code by which Message Saver saves and converts messages to FML? Ideally we would like to program this functionality into a Formativ applet that runs on every incoming message.


    We cannot provide Message Saver 2.0 code but if you think that you would like to explore the use of the Message Saver Component for .NET, we can provide a simple applet example which instantiates the component from Formativ. We have not tried implementing a solution which saves each incoming message (for a single user).

    Regards,

    Advansys Support

    #8890
    ihertanto
    Participant

    Thanks for your reply. Before I rule out any potential for using the Message Saver applet, please let me describe our objective:

    We want a Formativ solution that can automatically save and import incoming messages directly into a DMS. The applet would run on one account, on a Receive event, similar to how a Rule would work.

    In your product info for Message Saver Pack 2.0, under “Benefits” you mention:

    “Import messages into GroupWise or other document management systems.”

    Could you elaborate on this process and explain how Message Saver would be involved?

    If the applet fails to meet our needs, we might be interested in obtaining a license for the Advansys Message Saver Component for .NET.

    Your info is much appreciated.

    #8887
    Support 2
    Moderator

    Thanks for the additional background. The current Message Saver 2.0 applet does not work with the On Message Arrival event (received event). It may be possible for us to modify the solution to do so. The reason is that you must have a message selected before it will save it.

    One work-around may be to write a another applet which:

    • integrates with the On Message Arrival event
    • selects the incoming message
    • chains Message Saver

    The only problem is that in a very busy client, the GroupWise event system may ‘lose’ events, thus potentially missing a message save. There are a number of approaches to help address this type of problem. One approach would be to mark/categorize a message once it is saved successfully, then run a process at some point to check that all messages are marked. If not, save the ones which were ‘missed’. This approach would require additional custom development of Message Saver 2.0 or ancillary applets.

    quote:


    In your product info for Message Saver Pack 2.0, under “Benefits” you mention:
    “Import messages into GroupWise or other document management systems.”
    Could you elaborate on this process and explain how Message Saver would be involved?


    Message Saver is involved to the extent that in response to a user action, such as message selection and clicking the save button, it exports the GroupWise message(s) to one or more Advansys Portable Message disk files in a target output folder. This facilitates the import into external applications such as a DMS. As an example, you may define the default Message Saver output folder to be one which is periodically monitored by a DMS and imported automatically. In this simple example the DMS import would need to take care of metadata and profile generation.

    In short, the current Message Saver solution alone will not achieve your objective. Apart from the Message Saver component, which would provide the most flexibility but more development on your part, there may be other approaches. We will discuss your latest post with the engineers to see what else can be done.

    Regards,

    Advansys Support

    #8889
    ihertanto
    Participant

    Thanks for the tip. We’ll play around with the idea of building a custom applet that chains the Message Saver applet as you’ve suggested.

    In the meantime I look forward to hearing what you and the engineers have come up with.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.