Support 1

[Support 1]

Here is an example applet to delete a message from a shared folder. The key to this solution is the Token GroupWise.Refresh, used instead of the Object API method Account.Refresh.

Sub Main(Client, GWEvent)
 
  dim oMsg
 
  if Client.ClientState.SelectedMessages.Count = 0 then
    exit sub
  end if
 
  set oMsg = Client.ClientState.SelectedMessages.Item(1)
  msgbox oMsg.Subject
  oMsg.Delete
  set oMsg = nothing
 
  Groupwise.Refresh

End Sub

I hope this helps.

Advansys Support

[This message was edited by Support 3 on February 17, 2004 at 03:10 PM.]

[Support 1]

It is possible to write a Formativ applet that creates a GroupWise rule. See the GroupWise online Tokens Reference (A – Z) here.

Unfortunately, there does not seem to be way to set up a rule that automatically prints a message.

Alternatively, you could write an applet that executes on message arrival, checks for the required conditions, and prints the message data. For this you could use the ItemPrint() routine in the GroupWise Token API, or else develop your own printing method and format.

Advansys Support

[Support 1]

We are pleased to hear that the Message Saver solution is valuable to you. Equally, your feedback is very valuable to us in refining the quality of products that we provide. Thank you for your comments.

Stay tuned for the next update.

Advansys Support

[Support 1]

An alternative approach you could try is based on the GroupWise token ItemGetSource:

const SRC_MAILBOX = 1
const SRC_SENT_ITEMS = 2
const SRC_PERSONAL = 3

Sub Main(Client, GWEvent)

  dim iPersonal
  dim oMsg

  set oMsg = GroupWise.ComposingItem
  if not (oMsg is nothing) then
    iPersonal = (oMsg.ClassName = "GW.MESSAGE.TASK") _
      and (GroupWise.ItemGetSource("X00") = SRC_PERSONAL)

    msgbox "ClassName: " & oMsg.ClassName & ", Personal: " & iPersonal
  end if

End Sub

It may be that there is a defect in the GroupWise client (or in your co-worker’s installation), causing it to report the box type/message source in error.

In addition, it may be that your co-worker’s local copy of the relevant view has been edited in some way that alters the type reported by GroupWise. Perhaps you can experiment with replacing that view with your own ‘working’ view file. If you wish, send us the view file to analyze, at support@advansyscorp.com.

Advansys Support

[Support 1]

Thank you for your question.

Unfortunately what you require does not seem to be possible. We have done some testing of this issue here at Advansys, using both:

• Notify Options, to select a Shared folder;
• The event ‘On message arrival’ for the GroupWise Application (on the Integrations tab in Formativ Central).

The latter approach is associated with a Formativ applet, which is launched when the event fires.

In our tests, neither approach had any effect when a message arrived, or was moved into, in a Shared folder.

We are not sure whether this is a defect in GroupWise/Notify. Therefore we will look into having Novell add this issue to their enhancement database for GroupWise and/or GroupWise Notify.

Advansys Support

[Support 1]

This issue has been added to our enhancement database for Message Saver.

You can expect to see an update to the Message Saver pack, including several enhancements, by the end of March 2004.

Advansys Support

[Support 1]

Thank you for your query.

It is important that a saved message file has an extension of .fml because the Message Viewer only looks for such files in the selected folder.

If you use the mouse to click on the filename box, or use the keyboard to Tab to the filename box, all text in the box will be highlighted. If you then type text, you will replace the original filename. But if you use the mouse to click again (or press left-arrow/right-arrow on the keyboard), you can edit the original filename – thus retaining the .fml file extension.

This inconvenience is probably a limitation of the software. I will send your feedback to Engineering for review; we may add this to our enhancement database for Message Saver.

Advansys Support

[Support 1]

Thank you for the clarification.

It is possible to write a Formativ applet that proxies to the Admin account by using the AccountRights object in the GroupWise Object API. If you wish to develop such a solution, please refer to the online Object API documentation here.

Alternatively, if you prefer to have a solution custom-developed, please contact Advansys for specification and pricing at support@advansyscorp.com.

I hope this helps.

Advansys Support

[Support 1]

This issue will be handled by direct email. When we have determined a resolution, an update will be posted here for general viewing.

Advansys Support

[Support 1]

To clarify your requirement, here is what I think you want. A toolbutton that will:

• Grant Admin account proxy rights to an otherwise excluded (normal) GroupWise user account;
• Proxy to the Admin account.

The only way to do this is to use multilogin, which will require the Admin password.

Alternatively, you could write an applet that runs from the Admin account. The applet would automate the granting of proxy rights for each user account involved. Then each user would simply use the GroupWise Proxy menu (at the top of the Folder List pane) to proxy to Admin when required.

I hope this helps.

Advansys Support

[Support 1]

Looks like we both learned something. Thank you for sharing your simple discovery!

Advansys Support

[Support 1]

This issue is best dealt with by direct email. Please contact us at support@advansyscorp.com. In addition, please include your identity and organization in your message, as well as the details of this problem.

We look forward to hearing from you.

Advansys Support

[Support 1]

I do not know of a way to suppress the Send/Retrieve dialog.

You may wish to experiment with recording in an applet the steps taken by GroupWise itself in Remote mode, as follows.

• Go to Applets on the GroupWise main menu, and select Start Recording.
• Send a test message via the GroupWise user interface.
• Go to Applets on the GroupWise main menu, and select Stop Recording.

The recorded applet may expose GroupWise Object or Token API methods that you need for Remote mode.

I hope this helps.

Advansys Support

[Support 1]

I believe that in Remote mode, you will need to explicitly Send and Receive before the new message appears in your inbox.

To automate this you could try either of the following code snippets (to be executed after sending your message). Note that this code is untested.

  ' Send and Retrieve #1
  if GroupWise.Account.Remote then
    call GroupWise.CachingRefresh
  end if

  ' Send and Retrieve #2
  if GroupWise.Account.Remote then
    call GroupWise.RemoteSendRetrieveDlg
  end if

I hope this helps.

Advansys Support

[Support 1]

I am glad to hear this works for you.

Advansys Support

[Author]

Replies