Support 1a

[Support 1a]

Could you please email your Formativ Configuration information from the machine where you cannot see any applets to support@advansyscorp.com.

To access the configuration information:

1) Start GroupWise
2) From the main GroupWise menu, select ‘Help|About Formativ’
3) When the about dialog appears, select the ‘Configuration’ tab.
4) Press the ‘Copy to Clipboard’ button.
5) Close the about dialog
6) Compose a new email message to support@advansyscorp.com and paste the contents of the Clipboard to the message body.

Regards,

Advansys Support

[Support 1a]

Thank you for the tip. We haven’t received any other reports of this nature, so it makes sense that the problem might be related to a specific machines configuration.

Advansys Support

[Support 1a]

Hello Ralf,

I created an applet the same as yours and integrated it on the task ‘On Send’ event. I received the message box when I both created a new task and sent it to myself, and when I created a posted, personal task and pressed the post button. I did have to re-start the GroupWise client to get the event to work. Did you re-start the client? I’m using GroupWise 6.5 and Formativ 1.6, but I don’t think anything has changed in either component that would be an issue. Try re-starting the client to see if you receive the events. If not, could you please let me know the exact steps you go through when creating and posting the task.

In terms of the two On Complete events firing when the task view is opened, I have been able to replicate what you describe. The Formativ event system sits over the top of the GroupWise event system, which is firing the On Complete event twice when task view are open. I don’t know why GroupWise is doing this. It sounds like a bug to me, which I’ll report to Novell today.

Depending on what you need to do, there are generally was around this, but they can be a little messy. You may need to save out to the message ID of the task if the view is visible to a temp file. Your applet would also check for the existence of this file on the On Complete event. If it finds it, and the message ID matches the message ID of the current task, you know this is the second event, which should be ignored. Your applet then deletes the temporary file. Messy I know, but something like this should work until we can get Novell to fix the double event.

Regards,

Advansys Support

[Support 1a]

You are welcome Ralf!

Advansys Support

[Support 1a]

ItemGetType returns the following integer values:

1 Appointment
2 Mail
3 Note
4 Phone Message
5 Task

Regards,

Advansys Support

[Support 1a]

1.6 is due for release in the next couple of days. Most of the major issues appeared to have been ironed out in the GW6.5 SP1 client, so we are confident of a stable platform which we can run under.

Advansys Support

[Support 1a]

Hi Ralf,

If I understand correctly, you need to determine if the message returned by the Client.ClientState.CommandMessage is currently opened, or close (i.e. just selected in the message list).

If this is correct, then I think you need to use some variation on the code from our previous post to determine if the command message ID is the same as the ID returned from ItemMessageIDFromView().

In other words, in addition to obtaining the CommandMessage object, call ItemMessageIDFromView(), and check that the command succeeds. If it does (which means a message view is opened), compare the message ID returned against the message ID from the CommandMessage as a double check you are using the correct message. Alternatively, you could just use the ItemGetText() methods using the message ID returned from ItemMessageIDFromView() to extract the subject and body from the currently opened view.

I hope this helps.

Advansys Support

[Support 1a]

Alex has been contacted directly regarding this issue.

Advansys Support

[Support 1a]

This Cool Solutions applet is not offically supported (none of the Cool Solutions applets are), so it is probably not optimized for speed.

Nonetheless, I am suprised it takes several hours to import 1000 records. If you are happy to email the Excel spreadsheet to support@advansyscorp.com, I can organize to have Engineering take a look at it to see if any quick improvements can be made.

Advansys Support

[Support 1a]

I should be able to provide some sample code. However, if the message you wish to query is not the selected message, what technique are you using to identify the message you wish to query the status of? Do you have the message ID?

Here’s some sample code, but I’m not sure if this does what you need:

dim iMsgID
  
  ' Returns the message ID of the active view. 
  iMsgID = GroupWise.ItemMessageIDFromView()
  
  ' Make sure the token didn't fail
  if (instr(1, iMsgID, "Token failed execution", 1) <> 0) or (len(iMsgID) = 0) then
    call msgbox("Unable to find a message view.  Please execute this applet from a message toolbar.")  
    exit sub
  end if      
      
  ' Returns an item's type. 
  if (groupwise.ItemGetType(iMsgID) = 2) then
    msgbox "Mail message view open."
  end if

If this doesn’t help, please provide a little more information.

Thanks,

Advansys Support

[Support 1a]

We don’t have any applets currently available that automate the process you describe. We do have the personlized mass email applet that creates messages based on a template and the contents of an address book.

It sounds like it would be straightforward to write an applet to automate this process. Depending on the resources available to you, you might be able to do this yourself, or we could develop something for you.

If you chose to develop a solution in house, you can obtain free technical support via these forums. If you would prefer to have the solution developed externally, please us know and I’ll get in contact with you directly.

Regards,

Advansys Support

[Support 1a]

GroupWise 6.5 SP1 Beta fix – Formativ 1.5.9.5 update for Admin, Developer and Runtime

As part of the forthcoming GroupWise 6.5 SP1 client, Novell fixed a long-standing problem relating to way third parties interact with the main GroupWise toolbar and menu system. Previous versions of Formativ contained code to workaround the original client problem. The fix introduced in 6.5 SP1 invalidated the original Formativ code, preventing Formativ toolbar buttons and menu items from being added to main GroupWise window. This update ensures Formativ buttons and menu items are added when used with the 6.5 SP1 client.

The updated installation files are available from the Formativ Download Page

[Support 1a]

GroupWise 6.5 SP1 Beta fix – Formativ 1.5.9.5 update for Admin, Developer and Runtime

As part of the forthcoming GroupWise 6.5 SP1 client, Novell fixed a long-standing problem relating to way third parties interact with the main GroupWise toolbar and menu system. Previous versions of Formativ contained code to workaround the original client problem. The fix introduced in 6.5 SP1 invalidated the original Formativ code, preventing Formativ toolbar buttons and menu items from being added to main GroupWise window. This update ensures Formativ buttons and menu items are added when used with the 6.5 SP1 client.

The updated installation files are available from the Formativ Download Page

[Support 1a]

Later today we will be making available 1.5.9.5, which addresses this GW 6.5 SP1 toolbar/menu issue. Please watch this thread and the main support page for details.

Advansys Support

[Support 1a]

It sounds like you have not defined yourself as an administrator of your libraries.

Select the applet library in ConsoleOne and display it’s properties. The Applet Library object’s Library Administrators Page allows you to specify which users are authorized to create, edit and delete applets within the library. Use the Add and Remove buttons to add and remove users as Applet Library administrators, who must also be assigned to the FormativAdministrator Organizational Role.

Regards,

Advansys Support

[Author]

Replies