Forum Replies Created
-
AuthorReplies
-
We’ll attempt to obtain an update this week at BrainShare. However, I doubt they will have any news given the defect was reported so recently.
Regards,
Advansys Support
Dear Dav,
Thank you for your message above. Two quick questions: Are you athenticated to eDirectory when you see this error? Do you have the Novell eDirectory/NDS ActiveX controls installed (see the docs for additional information).
As a first step, I would try authenticating to NDS and see if the problem persists. I’ll also forward this to our engneering staff for comment.
Regards
Advansys Support
Thank you for your question above. Unfortunately, GroupWise does not offer a way for third parties to add menu list buttons to the GroupWise client.
We have addressed this type of problem in the past by creating an applet that displays a form listing all the available forms/view/options. The user then selects the appropriate option, at which time the secondary applet is chained by the first. (This assumes you are using Formativ 2.0 – 1.6 dosn’t support applet chaining). In this way you only have one button on the toolbar, but your UI can present any number of secondary options.
For information on applet chaining, see the ‘Applet Chaining’ topic in the Developers Guide.
I hope this helps.
Advansys Support
Thank you for the update. I suspect modifying the solution to work with proxy authentication would be non-trivial but a worthwhile feature. I’ll add this to our enhancement database.
Thank you for your feedback.
Advansys Support
As MA mentioned, this message will appear if the image at the given URL is not accessible via a standard HTTP GET command. This normally happens if you enter an incorrect URL (Don’t forget to include ‘http://’ at the start of the URL).
Advansys Support
As Novell have created a defect number for this problem, the issue is now subject to Novell’s normal defect rectification process. Unfortunately, as a third party, we can’t tell you when Novell will address this issue. As they recently released the 6.5.4 client, I’m not sure when the next maintenance release is scheduled.
Regards,
Advansys Support
The solution depends on what this applet does. Where did you obtain it? Do you have the source code version available?
We should be able to assist once we have more information.
Regards,
Advansys Support
Unfortunately, the OnSend event occurs at a point in time before the final message ID of the outgoing message is available. This means you cannot easily identify the outgoing message’s message ID, which you would need in order to customize the Personal Subject. This problem has been present for many years, and is one we have asked Novell to address many times.
The only workaround is to collect key information about the message being sent (i.e. subject, date, etc), wait a short period, then locate the message in the sent items folder that matches the criteria. Once located, use the object API to update the PersonalSubject.
I hope this helps.
Advansys Support
The packet trace won’t be necessary at this time. The next step is probably getting you to run a version of Studio which outputs trace information. I’ll prepare that today. Could you please send an email to support@advansyscorp.com with your details.
In the meantime, could you please make one final check for me. In ConsoleOne, open your user object (CN=MSHIMONEK.OU=ADM.OU=MO.O=US) and select the ‘See Also’ page. Can you confirm you see an entry referencing the ‘FormativAdministrator’ object, and that the name of that object is indeed ‘FormativAdministrator’ (including case).
Thank you.
Advansys Support
Thank you for your message. I would suggest you check the following:
1) Ensure name of the ‘FormativAdministrator’ role is spelt correctly. The process won’t work if the role name differs in any way from that shown above.
2) Ensure you have added your own User object to the ‘Security Equal To Me’ list of the FormativAdministrator object.
3) Ensure you added your user object to the list of library administrators as shown on the Library Administrators property page of the Applet Library object.
4) In the Formativ Applet Library object, ensure you have configured the property page ‘Trustees of this Object’ to include the FormativAdministrator Organizational Role object as a trustee of the library. Assign the following rights to the library object: [Entry Rights] Browse, Create, Rename, Delete, Inheritable; and [All Attributes Rights] Compare, Read, Write, Inheritable.
5) In your Formativ Configuration Object, ensure you have added the Applet library to the Applet library list.
6) Check the topic entitled ‘Step 5 – Assign eDirectory Rights’ in the Studio Users Guide to ensure you have assigned the appropriate rights to all the objects.
I hope this helps. Please let me know if you still encounter problems after working through this checklist.
Regards,
Advansys Support
No – it shouldn’t really matter. Feel free to move it to after the ThrowToken calls if the tokens appear to be failing.
Regards,
Advansys Support
Tim,
We have resent the applet to the alternate email address as requested.
You’ll find us at booth 160 in the Sponsors Hall at BrainShare. We look forward to meeting you.
Regards,
Advansys Support
We have been able to duplicate this behaviour. The most likely cause is a bug in GroupWise. We will investigate further and get back to you as soon as possible.
Advansys Support
Engineering identified an issue that may cause the behavior you describe. The sample message doesn’t contain any date information for the two attachments. You can see this if you look at the properties page for the message. The applet was rejecting any attachments that did not expose date properties.
I have sent you an updated version of the applet that will accept undated attachments. We will also post an update in Cool Solutions.
(I noticed the email address you supplied bounced. I have tried re-sending the applet to you today).
Regards,
Advansys Support
Isabelle,
An engineer looked at the code, and had the following suggestions:
– Are all the calls to ‘Groupwise.EnvCurrentViewName()’ actually required? Presumably the applet is integrated with the appropriate message types (i.e. email, tasks, notes, etc), so the applet will only be run in response to known message types. If, for a reason we have missed, you do need to query the view name, we suggest you call Groupwise.EnvCurrentViewName() only once and assign the view name to a variable. Carry out your view name evaluation using this variable. The current code calls ‘Groupwise.EnvCurrentViewName()’ 12 times within each run of the loop. I can’t say what impact this might have on the state of the view.
– You can check to see if the calls to FocusSet() and PosTextTop() are actually working by using the ThowToken technique. This approach calls the native GroupWise token directly, and returns a boolean indicating if the token actually worked. As the FocusSet() and/or PosTextTop() are the most likely candidates for failure, we have re-written the code to use this technique. Although the code below doesn’t show this, you could check the return value from the
if groupwise.ThrowToken("focusSet(10;)", iReturnVal)
lines to see if the appropriate token actually worked.
Sub Main(Client, GWEvent) dim x dim query dim headerText dim iReturnVal query = true headerText = "This is the header text to be inserted at the top of each message" for x = 1 to 20 Utilities.DoEvents if groupwise.ThrowToken("focusSet(10;)", iReturnVal) then if groupwise.ThrowToken("PosTextTop()", iReturnVal) then Call Groupwise.fontbold(true) Call Groupwise.TypeText(headerText) Call Groupwise.fontbold(false) query = false exit for end if end if next If query = true Then MsgBox "Error: PA Macro Line 271 - Query focus timed out! Message will be sent without header." End If End Sub
We hope this helps.
Advansys Support
-
AuthorReplies