Support 3

[Support 3]

Use the groupwise.CancelGroupWiseEvent and set this property value to TRUE. This method will cancel any GroupWise event that caused an applet to execute. See the Formativ Language Guide for more information.

Hope this helps.

Regards,
Advansys Support

[Support 3]

Seems like the Messages.Remove() method do not work if you use the Move method. Interesting to see, the Move method create a link for the Sent items messages. May be the index of the messages collection not refresh once the Move method called. You can use the Message.Delete() method to remove the message. See the sample code below:

set oMsg = client.clientstate.commandmessage
call groupwise.account.SentItems.messages.move(oMsg.messageid, groupwise.account.cabinet.messages)
oMsg.delete
set oMsg = nothing

Regards,
Advansys Support

[Support 3]

See the Object API Message.Move() method to move a message to a destination folder. You can only move the message from the owner Folder.Messages collection. If you don’t have access to the folder object of the message then you need to get the message object using the Account.GetMessage(messageid) method and use the EnclosingFolders properties to get the owner folder.

The sample code below move the selected message from the Mailbox folder to Cabinet.

set oMsg = client.clientstate.commandmessage
call groupwise.account.mailbox.messages.move(oMsg.messageid, groupwise.account.cabinet.messages)
set oMsg = nothing

Hope this helps.

Regards,
Advansys Support

[Support 3]

Another thought, may be you can store the database to a FTP site. The applet will download the DB from the FTP site and store into user’s computer. The applet can check the date stamp for the DB and download once each day to avoid download per execution. You can also automate the process to upload the file to FTP. See below a sample code to download from web.

  
iFileName = "http://www.mycompany.com/data/mydb.db"
set oHTTPConnection = Utilities.HTTPConnection
iBuffer = oHTTPConnection.Get(iFileName)
call utilities.SaveStringToFile(iBuffer, "c:tempmydb.db", true)
set oHTTPConnection = nothing

Hope this helps.

Regards,
Advansys Support

[Support 3]

Please see the forum post about the Formativ API.

Hope this helps.

Regards,
Advansys Support

[Support 3]

Memory leak on the GroupWise client can arise due to the applet calling the Object API in a sequence which leads to the API state becoming unstable.

Our experience with the GroupWise APIs has taught us that sometimes an obvious or intuitive approach is not feasible; that an applet must be redesigned to work around an API defect or to manage internal API resources.

The difficulty is usually in figuring out which API is responsible for the problem. Using the process of elimination, however, you can usually narrow the problem down rather quickly by making small logical changes and observing the impact on the problem. The key is to make only one change at a time and then see if the problem goes away. You can use the Trace commands to your source code to get a real-time picture of the execution sequence. See the Developers Guide section Error Handling and Debugging for details.

Hope this helps.

Regards,
Advansys Support

[Support 3]

Great news, thanks for the update.

Regards,
Advansys Support

[Support 3]

Could you please email your Formativ Configuration Information to Support (support@advansyscorp.com). You can access this via the main GroupWise menus: Help | About Formativ. When the “About Box” appears, select the “Configuration” tab. Press the “Copy to clipboard” button, then paste the contents of the clipboard into your reply.

Regards,
Advansys Support

[Support 3]

Iterate through all files in the target folder and delete the file. See below the sample code.

 set oFSO = Utilities.FileSystem
 set oIterator = oFSO.FileIterator
 oIterator.FileSpec = "c:temptest*.*"
 oIterator.load()

 for x = 0 to oIterator.Files.Count -1
   oFSO.DeleteFileOnDisk(oIterator.Files.strings(x))
 next

 set oFSO = nothing

Hope this helps.

Regards,
Advansys Support

[Support 3]

Thanks for your comments.

Regards,
Advansys Support

[Support 3]

We have recently test this applet on latest version of GW 7 and it works fine. I remember, earlier version of GW 7 causes few problems for this applet (i.e duplicate Mime.822 file, etc). We have reported these issues to Novell and they fixed on the latest version of GW 7. I have to check with the engineers about the build date of GW 7 we used. In the meantime please answer the following questions and send us any additional information to help us solve this issue.

– What is the build date of your GW 7 (see Help – about GroupWise)?
– How do you execute the applet (i.e from message toolbar / GroupWise toolbar)?
– Do you have a valid composing message available?
– Can you reproduce the error if you manually save the message (CTRL+S) and try the applet?
– Can you reproduce the same error on another account?

Regards,
Advansys Support

[Support 3]

Use the keyword call to execute a method with parentheses. See below an example:

call groupwise.RunProgram(Executable, Parameters)  

I haven’t heard any executable program called “CloseGW.exe”. Do you have any additional information about this EXE (i.e folder location)?

As I said earlier, you can use Windows Script Host to sends one or more keystrokes to the active window. One of the keystrokes you can send is close window. The example below should close the current window. You need to make sure when executing the code only GroupWise window is active. Once again we don’t know the impact of the SendKeys method or closing the GroupWise from C3PO so be aware of unpredictable behavior.

Set oShell = CreateObject("WScript.Shell")
oShell.Sendkeys "%{F4}"
set oShell = nothing

Hope this helps.

Regards,
Advansys Support

[Support 3]

Hi dgerisch,

While replying to your last post, accidently we have deleted your last posting. We’re extremely sorry for this inconvenience.

Regards,
Advansys Support

[Support 3]

In theory, you can use the Windows Script Host to sends one or more keystrokes (close window) to the active window. You should be able to find some sample code in web about the Sendkeys method.

We don’t know the impact of the SendKeys method or closing the GroupWise from C3PO. Please be aware of unpredictable behavior.

Hope this helps.

Regards,
Advansys Support

[Support 3]

Hi rdryan,

We are not sure why the ItemSetText token works differently in your GroupWise client if (),{} are in the message body. This Token works fine in here with or without (),{} in the message body. The sample applet works fine from the message toolbar and Tools menu.

We will recommend to upgrade your GroupWise client. Please do not hesitate to contact us with further comments or requests.

Regards,
Advansys Support

[Author]

Replies