Forum Replies Created
-
AuthorReplies
-
October 3, 2006 at 3:53 am in reply to: Upgrade to GW7 – Archive unable to access certain mailboxes #9317
Unfortunately the explanation is probably very simple. As Archive To Go uses the client APIs in both Local or Enterprise mode, it is likely the standard limitation where a newer GroupWise client is not being able to access an earlier version of the Post Office.
This means the only work-around during the Post Office transition is to use a GroupWise 6.5 client, which is compatible with both GroupWise 6.5 and 7.
Regards,
Advansys Support
quote:
Would it help if your installer warns if the .net framework isn’t present, and aborts the install?
Thanks for the feedback and I’ll pass your suggestion onto the project team.
Regards,
Advansys Support
We are not aware of any problems with our software which would explain the problem. However, there are various issues which can cause this symptom.
Firstly, it is normal for GroupWise to send an HTML formatted message with a TEXT.htm and IMAGE.GIF or .JPG attachments. This is how GroupWise parses the HTML components within the MIME.822 file which is created upon saving as draft or sending the message via the client.
Rendering the received HTML message can depend on the email client the recipient is using. For example, certain clients will not allow rendering of HTML due to optional settings (GW has this option too). It may also depend on the formatting of your HTML within your stationery file.
There is a chance it may also depend on the version of GroupWise that you are running. Which version of the GroupWise Client do you have?
In any case, the best way to eliminate our software from the equation is to simply create a new (empty) GroupWise HTML message and then manually add text and images. Send this to the same recipients who are experiencing the problems. If the same results occur, then it is a GroupWise or the recipient’s email client issue.
Regards,
Advansys Support
Thanks for the update. You do need .NET installed for the Formativ Framework for .NET 1.0, which is installed with Message Saver 2.0.3.
We will be interested to learn if you have solved the menu problem.
Regards,
Advansys Support
As this is the first time we’ve heard of this issue, we do not know what is causing the problem. As such, it is probable that it is something specific to your environment. Does it happen on more than one workstation?
Have you tried uninstalling/reinstalling:
1. Formativ Runtime and Formativ Message Saver; and
2. the GroupWise Client?Can you think of any other potential factors, such as Windows Registry rights/access?
Regards,
Advansys Support
quote:
Another approach… if we were to enable the standard GroupWise classifications, would it be possible to change the GroupWise classification strings or add to the list?
Unfortunately custom classifications only work at the client end. Rules are executed at by the Post Office Agent and it doesn’t support client side custom classifications, only the GroupWise standard classifications.
Regards,
Advansys Support
To edit rules, you can refer to the Token API (http://developer.novell.com/documentation/gwtoken/index.html?gwtokens/data/hj8ej8g5.html) and the Formativ Language Guide to edit rules.
The sample Formativ line of code below displays the GroupWise rule list dialog.
‘ Displays the Rules dialog box to list, create, edit, copy, delete and run rules.
GroupWise.RuleListDlgRegards,
Advansys Support
Great news, thanks for the feedback.
Regards,
Advansys Support
You can’t use events to do what you need because rules are executed and the responses created at the post office level.
There may be a couple of possibilities. If the standard GroupWise classifications (not custom ones) are suitable for your needs, then you can set the default GroupWise classification (using the Client or an applet) for the account which has the vacation rule enabled. Every rule generated reply would then include the selected GroupWise classification within its body text.
The other option is to create a custom ‘out of the office rule’ applet which inserts classification text within the reply action.
Regards,
Advansys Support
Great news, thanks for the update.
Regards,
Advansys Support
The Formativ Applet Focus multiple signatures applet was a very early example of what could be done with Formativ. It was provided as an unsupported open source solution to offer developers insight into techiques which could be used to develop GroupWise solutions.
If you are not a developer it is recommended that you have a look at our commercial solution for Multiple Signatures, available separately and which is also included in the Presentation Pack.
Regards,
Advansys Support
Thanks for your post. The next major release of Archive To Go will include full filtering capabilities, including the ability to filter on message type, which includes document references. The next major version is targeted for release in time for BrainShare 2007.
If you wish to test this feature, we could notify you when an early release may be ready. Please write to support@advansyscorp.com to let us know.
Regards,
Advansys Support
There could be a number of explanations. How did you distribute the Templates applet? Did you use the solution installer?
If you did use the installer, it may be it was installed twice, once for the current user and once for all users. This can result in the solution becoming disabled. The solution is to uninstall one of the applets.
If you did not use the installer, did you distribute the manifest file into the Formativ System folder?
Often the best source of information is the Formativ Configuration Information. You can obtain the configuration by selecting Help | About Formativ… from the GroupWise main menu. When the About Formativ dialog appears, go to the Configuration tab and click the button Copy to clipboard. Then paste the text into an email (or save it to a plain-text file and include it as an attachment) and send it to support@advansyscorp.com.
Regards,
Advansys Support
You are correct that Formativ 2.0.1 does not disable the VBS association by default. This is in contrast to previous versions (earlier than 2.0.1), which did disable the associations by default.
Please let us know if you confirm that no user has this feature set to disable the VBS associations.
Regards,
Advansys Support
Unfortunately we can’t offer any immediate answers as to the cause. Theoretically, as Archive To Go uses the same code and GroupWise APIs to access each mailbox, our software should either work or fail consistently across all mailboxes, especially within the same Post Office.
Are you able to use Archive To Go against the troublesome mailboxes using Local Access (which requires a mailbox password)?
To help us understand your current system configuration used with Archive To Go, can you email to support@advansyscorp.com the systems.xml file from the local folder:
C:Documents and Settings[Windows User]Application DataAdvansysArchive To Go
Regards,
Advansys Support
-
AuthorReplies