Support 3

[Support 3]

Great, thanks for letting us know and glad it was of assistance.

Regards,
Advansys Support

[Support 3]

Thanks for your post.

This behaviour most likely related to GroupWise 2012 Object API (OAPI).

http://www.novell.com/document…i/data/h3r0rhi6.html

quote:

Addresses Find(String Condition)

Returns a new Addresses collection containing the addresses from this collection that match the filter expression given by the Condition parameter (see Section 5.0, Filter Expressions). This Find method differs from the Find methods for messages in that it accepts a restricted syntax and does not accept a saved Filter. Each address book may support a different set of filtering operations. Filtering on an address book that supports a limited set of operations will throw an exception when handed a filter expression beyond the address book’s capabilities. This method does not support BEGINSWITH, but it does support MATCHES and CONTAINS.

You can search only on First Name and Last Name in the System Address Book. If you try searching on Name, this method fails.

According to OAPI, “E-Mail Address” field not supported in System Address book, only support “First Name” & “Last Name”. However, “E-Mail Address” field still works in GroupWise 8 client but in limited situation. For example:

Works: Set objEntries = objAddressBook.AddressBookEntries.Find(“(<E-Mail Address> MATCHES “”Test@xyz.com””)”)
Does not work: Set objEntries = objAddressBook.AddressBookEntries.Find(“(<E-Mail Address> MATCHES “”Bill.Smith@xyz.com””)”)

Looks like email address where “.” exists in name does not work. We will recommend not to use the “E-Mail Address”, instead use First Name or Last Name. Example:

Set objEntries = objAddressBook.AddressBookEntries.Find(“(<First Name> CONTAINS “”” & strSearchItem & “””)”)

Other option could be cache the System Address book entries (xml file), where each entry can store the name, email address and other details then use the cache xml file to search entry. You will need to update the cache file to take into account for the new Address Book entry or modified existing entry.

Best regards,

Advansys Support

[Support 3]

Thanks for your post, we have emailed you the applet source.

Regards,
Advansys Support

[Support 3]

Thanks for sending us the configuration information. Considering other applets execute which indicate the issue could be in that particular applet.

We have sent you an email about steps to get to gather diagnostic information from the applet, which also discussed in post below:

http://www.advansyscorp.com/forums/topic/9151084651/

Regards,

Advansys Support

[Support 3]

Hi L.P.,

Thanks for your post. Unfortunately we haven’t had any report about this issue.

quote:

A form with a button name tst and the only script line : Tst.ShowModal

You should call FormName.ShowModal not the ButtonName.ShowModal. Example: MainForm.ShowModal, where Form name is ‘MainForm’ which can have button name as ‘tst’.

Are you able to run any existing applet (i.e. Stationery, Filing Assistant, etc)? Can you reproduce the behaviour on another machine?

If the problem persists, could you please email the Formativ Configuration information and the applet to support (support@advansyscorp.com).

You can access Formativ Configuration 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 email or save as text file and attach to your email.

Best Regards,

Advansys Support

[Support 3]

Thanks for your post. Sorry to hear about the issue.

If you are running any anti-virus software, you may need to disable it during indexing process.

Could you please send the archive detail log (UserName.log) which you will find in the target archive folder and indexer log (index.log) in target archive media folder (..media-01_indexinf) to Support (support@advansyscorp.com).

Regards,

Advansys Support

[Support 3]

quote:

set oAddressBook = GroupWise.Account.AddressBooks.Item(“Novell GroupWise Addressbook”)

Generally System Address Book name is “Novell GroupWise Address Book” but we can see in your system “Novell GroupWise Addressbook” [without space in Addressbook]. Don’t think it could be an issue.

Does the code works in another Address Book?

We had to update your above sample code for Address Book name then it works in here. We used GroupWise 12.0.1 (build date 07/09/2012).

See below slightly modified code, which shows Address Book name & Type (2 for System Address Book) and prefix wildcard character in name.

 
  set oAddressBook = GroupWise.Account.AddressBooks.Item("Novell GroupWise Address Book")

  if (not oAddressBook is nothing) then
    msgbox "Name: " & oAddressBook.Name  & ", Type: " & oAddressBook.ObjType
    iFilter = "(<First Name> CONTAINS ""*John*"")"
    set oEntries = oAddressBook.AddressBookEntries.Find(iFilter)

    if oEntries is nothing then
      msgbox "oEntries is nothing. Quitting"
    elseif (oEntries.count > 0) then
      msgbox oEntries.item(1).DisplayName
    end if
  end if

Regards,

Advansys Support

[Support 3]

Thanks for your post.

Is “Novell GroupWise Adressbuch” System Address Book?

Based on Novell documentation, you can search only “First Name” & “Last Name” in System Address Book. See below extract from Find() method documentation.

quote:

…
This Find method differs from the Find methods for messages in that it accepts a restricted syntax and does not accept a saved Filter. Each address book may support a different set of filtering operations. Filtering on an address book that supports a limited set of operations will throw an exception when handed a filter expression beyond the address book’s capabilities. This method does not support BEGINSWITH, but it does support MATCHES and CONTAINS.

You can search only on First Name and Last Name in the System Address Book. If you try searching on Name, this method fails.
…

However, our internal test shows we was able to search Email Address in System Address Book entries in GroupWise 8.0.3 (build date 15/06/2012) but not in GroupWise 2012. Following code works in GroupWise 8/2012 System Address Book.

  
set oAddressBook = GroupWise.Account.AddressBooks.Item("Novell GroupWise Address Book")
iFilter = "(<First Name> CONTAINS ""Test"")"
set oAddresses = oAddressBook.AddressBookEntries.Find(iFilter)

In your code you have used “<Email-Adresse>”, in English client its “<E-Mail Address>”. We are not sure AddressBook keywords are language-dependent.

Hope this helps.

Regards,

Advansys Support

[Support 3]

Thanks for your post.

Unfortunately we haven’t heard any report about this issue. Please see below some suggestions:

– Please make sure you are running latest version of the PST Creator. Current version is 1.0.0.9. Select Help – “Check for update” option to check for latest version.

– Did you run any anti-virus during conversion process? We recommend to disable anti-virus software temporarily for the duration of the conversion process. Please see Users Guide (Client Installation section) for more information. Please also check whether any type of virus on the system.

If the above steps unable to resolve issue then:

– Please send us the PST Creator log and screenshots of the error to Support (support@advansyscorp.com). Conversion log usually stored in:
XP: “C:Documents and SettingsUSER-NAMEApplication DataAdvansysPST Creator”
Windows 7: “C:UsersUSER-NAMEAppDataRoamingAdvansysPST Creator”

– Send us some problematic FML files to support (support@advansyscorp.com). You will need to open the Archive To Go Viewer, find and select messages, open QuickViewer and select Properties tab. You will see FML file path of the message. Locate the file in Windows Explorer and send it to us for review. Advansys treats all data provided by clients as strictly confidential.

Regards,
Advansys Support

[Support 3]

Thanks for your request.

Please see the forum post about the updated solution and download link:

http://www.advansyscorp.com/forums/topic/2807055906/

Regards,

Advansys Support

[Support 3]

Thanks for your post.

Unfortunately we haven’t had any report about the issue.

The issue could be relate to publish applet location and your local applet or library integration. Formativ may be configured to load applets where local changes not saved.

Could you open the Formativ Control Panel applet (Start – Control Panel – Advansys Formativ – Select Paths tab) then check the local applets location. You should be able to find your modified applet in that location.

In Formativ Control Panel applet, select “Local Config” tab:

– Is “Enable intelligent applet caching” checked?
– Is “Update applet cache on client start up” checked?

You can also backup your modified applet to different location. In Formativ Studio IDE, select the applet, right click and choose “Save as” context menu option.

In order for us to review, 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 email or save as text file and attach to your email.

Regards,

Advansys Support

[Support 3]

Thanks for your post.

Our engineering team has updated the “Delete Attachments from Select Messages” applet to support GroupWise 2012. Unfortunately Novell cool solution site hasn’t updated.

In the mean time, we have sent the updated applet to your email address.

Best regards,

Advansys Support

[Support 3]

Sorry for the delay.

Unfortunately we haven’t had any report about this issue, it could be environmental.

Can you reproduce the behaviour on another machine?

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 email or save as text file and attach to your email.

Regards,

Advansys Support

[Support 3]

Thanks for your feedback.

We can reproduce the bug, thank you for reporting the issue. We have emailed you the updated solution (2.0.11).

Regards,

Advansys Support

[Support 3]

Our engineering team has updated the “Calendar Dates Importer” solution (version 2.0.10) to fix the issue of AllDay.

We have emailed you the updated solution.

Regards,

Advansys Support

[Author]

Replies