Support 1a

[Support 1a]

Thank you for your post. The magnitute of the component documentation for Formativ 2.0 dictated we had to release the product prior to component documentation amalgamation. Prior to official documentation becoming available, component information can be accessed from the following sources:

The components on the Standard, Additional, Win32, System and Dialogs tabs of the component palette are documented in the Borland Delphi VCL help file. This can be downloaded from:
ftp://ftpc.borland.com/pub/delphi/techpubs/delphi6/d62pro.zip

The components of the Enhanced tab of the component palette are documented in the Raize Components Trial Help files. This can be downloaded from:
http://www.raize.com/DevTools/RzComps/DemoTrial/RC3Trial.zip

The components on the Netware, LDAP and NDAP tabs of the component palette are Novell’s ‘ActiveX Controls for Novell Services’. Documentation for these components can be found at: http://developer.novell.com/ndk/activex-index.htm.

The components on the GroupWise tabs of the component palette are Novell’s ‘GroupWise Controls for ActiveX’. Documentation for these controls can be found at: http://developer.novell.com/ndk/gwactive.htm.

Regards,

Advansys Support

[Support 1a]

Thank you for your posting above.

In terms of items 1) and 2), if I understand your comments correctly, you are running into limitations of the GroupWise Address Book application. Unfortunately, we are not able to address these issues as they are inherent in GroupWise.

The contact import process can potentially take some time. This is due to the design of the GroupWise Address Book access API, which can slow down considerably as contacts are added. Again, this is something we are unable to address as third party developers.

Sorry I could not provide a more positive response.

Regards,

Advansys Support

[Support 1a]

Thank you for your question. By ‘new items’, do you mean new messages that arrive in the mailbox, or do you mean items that the user creates?

In order to set a category, you first need to grab an instance of the category object from the category definitions collection in the account:

for each oCategoryDef in GroupWise.Account.CategoryDefinitions
    if (iCategoryName = ucase(oCategoryDef.Name)) then
      set aCategory = oCategoryDef
      exit function
    end if
  next

Then, given an instance of a message object, you add the category object as shown here:

oMsg.Categories.add(aCategory)

As I alluded to above, the devil is in the detail regarding the scenario under which you want to add the category.

I hope this helps.

Advansys Support

[Support 1a]

I’m not sure if messages being added to a shared folder are treated the same way as messages that are delivered to your mailbox – GroupWise may see that as being two different things. You would have to try and see if the message arrival event is fired.

In any case, the on message arrival is the only event that triggers when a message is delivered to your mailbox. If it doesn’t fire, you might need to look at another approach.

Advansys Support

[Support 1a]

There are two components that need to be installed in order to be available for all users: Formativ Runtime and the Message Saver Pack.

Formativ Runtime 2.0

I am not aware of any problems with the installation of Formativ Runtime on a multi-user workstation. I just installed Runtime on XP as a user with Admin Rights, then logged into the same machine as a different standard user. I was able to access Runtime logged in as the second user.

I would suggest you uninstall Runtime from the problem machine, then re-install as a Admin-level user. (Prior to the re-install you might want to check that all files are gone from ‘C:Program FilesAdvansysFormativ’). Log into the machine as another user. You should be able to see the ‘About Formativ’ menu item on the main GroupWise Help menu.

Message Saver Pack

We today detected an issue with the Message Saver Pack installation that would cause it to create shortcuts to the Viewer on the Start menu for the current user only. Is this the problem you saw? We have uploaded an update that should fix this problem. Please download it again and see if it fixes the problem for you. Remember to select the ‘all users’ options when installing.

I hope this helps.

Regards,

Advansys Support

[Support 1a]

Thanks for the suggestion. You could also modify this code to run on the ‘Message Arrival’ event. Instead of the selected folder, you could provide a hard coded folder object. This might be appropriate if you have a rule that moves messages to a folder on arrival.

Advansys Support

[Support 1a]

Thank you – we have received the files. We’ll respond via email and post the eventual resolution back in this thread.

Regards,

Advansys Support

[Support 1a]

Thank you for your posting above. I can’t duplicate this problem in-house. I am using Formativ 2.0.0.17 and Stationery 2.0.0.19 (You can see the version of stationery you have installed by displaying the ‘About Formativ’ box, then displaying the Applets tab.) Given you have SmartFields assistant installed, I suspect you also have 2.0.0.19 installed.

Could you please configure stationery the way you want in terms of the default stationery and the mode, exit GroupWise, then send me (support@advansyscorp.com) the following file:

C:Documents and SettingsLocal SettingsApplication DataAdvansysFormativ1.0Configstationery.ini

Thank you,

Advansys Support

[Support 1a]

Dear David,

Thank you for your questions above. You can use the mailto: formatting convention to launch GroupWise. However, tests reveal the OnCompose event (configured to fire after the event) fires _before_ GroupWise has finished completing the body of the message. As this is the only event I think would be useful in this case, automating the process would be problematic.

My initial suggestion would be to write an applet that places a button on the mail toolbar. Pressing this button checks the body of the message to see if it contains a pre-defined marker, and replaces the body if a marker is found.

In terms of the send event, yes, you could do this. We have posted some applets on Novell CoolSolutions that should give you a head start:

http://www.novell.com/coolsolutions/feature/9485.html

* 20 Jun 2002 – Find records in Access database
* 24 Sep 2002 – Save Message and Attachments
* 28 Jul 2003 – Export to Disk

I hope this helps. Please let me know if you require any further assistance.

Regards,

Advansys Support

[Support 1a]

Thank you for your questions above.

quote:

---

1. Do you support your ConsoleOne 1.2 snap-in with ConsoleOne 1.3.5? We are concerned as we had issues with ConsoleOne 1.2 as it corrupted the eDirectory schema.

---

Yes. The snapins work fine with 1.3.5. We are currently using 1.3.6 in-house.

quote:

---

2. We cannot see on your website that you have a Novell tested and approved certificate for Netware 6.5. This is what we will be using. Do you support this?

---

Yes – you shouldn’t have any problems with Netware 6.5.

quote:

---

3. Do you support eDirectory 8.7.3?

---

Yes. We use 8.7.3 on one of our demonstration systems in-house without any known problems.

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your report. It appears that the version on the web site is corrupt. We are uploading again now. Please download again shortly (clearing your browser cache if required).

Please accept our apologies for the inconvenience this has caused.

Regards,

Advansys Support

[Support 1a]

Generally speaking, you should select the ‘Copy Settings as Default’ option when installing Runtime and the Message Saver Pack. This should make the function available for all users of the machine.

Regards,

Advansys Support

[Support 1a]

If you are referring to the registry key, then yes, it should work in a WTS/Citrix environment.

Regards,

Advansys Support

[Support 1a]

Thank you for the confirmation.

Regards,

Advansys Support

[Support 1a]

Insert the Flexalock marker in your source at the point you wish to encrypt the applet:

‘–>Flexalock

Everything below this marker will be encrypted – everything above it will be exposed.

The area above the Flexalock marker can only contain:

a) Blank Lines
b) Comments
c) Constants

Anything else will cause the Flexalock process to fail. This is a security feature.

I hope this helps.

Advansys Support

[Author]

Replies