Forum Replies Created
-
AuthorReplies
-
December 4, 2006 at 2:51 pm in reply to: Deletion of GroupWise attachments removes To information #8354
We have updated this applet some time ago to fix this bug but unfortunately we haven’t publish this version to cool solutions. I will inform the person-in-charge to publish this version soon.
In the meantime, I have emailed you the updated applet. Please save the updated applet into default Formativ applets folder, usually c:my documentsadvansysformativapplets.
Hope this helps.
Regards,
Advansys SupportThanks for your enquiry.
I am guessing that you are referring to the “CSV Export_Example” example applet. It appear that the applet need to modify to include all fields. Unfortunately we do not support the example and cool solutions applet. Our custom development resources are assigned to other projects. I would suggest you contact a Formativ development partner, one of which should be able to assist. You can access the full list at:
http://www.advansyscorp.com/formativ_partners_developers.htm
However, if you want to edit the applet to include all fields then I will suggest you to look at the FieldDefinitions object in Address Book then access each Field of the address book entry. Please see the Object API (http://developer.novell.com/documentation/gwobjapi/index.html?gwobjenu/data/h7ikbsqg.html) for more information.
Hope this helps.
Regards,
Advansys SupportIt appears that we don’t provide any popup menu integrations for the document message type. We haven’t had any request about this integration. I will add this request into our enhancement database for future release. In the meantime, you can use the GroupWise toolbar or run menu integration. The user will need to select a document then press a GroupWise toolbar icon to execute the applet.
quote:
My goal is to create a popup and with it, the user could send a message with the document selected
I don’t think you can add a message type attachment using Token API. You probably need to use the Object and Token API to add an existing document into a message. Here is some sample code:
set oMessage = Client.clientstate.commandmessage ' Create the message using Object API set oDraftMessage = groupwise.account.workfolder.messages.add("GW.MESSAGE.MAIL", fgwDraft) utilities.doevents ' Add the selected message as an attachment (Object API) call oDraftMessage.attachments.add(oMessage, "") utilities.doevents ' Open the draft message (Token API) call groupwise.itemopen(oDraftMessage.messageid, "") utilities.doevents set oMessage = nothing set oDraftMessage = nothingHope this helps.
Regards,
Advansys SupportThanks for the heads up. We will test the integration on the latest client and let you know the results.
Regards,
Advansys SupportWe will update the documentation to fix the spelling of the createfolder.
In the meantime, you can use ThrowToken to execute a given token. The return value from the token is given in the ResultValue parameter. Please see the “Formativ Language Guide” for more information about the method. Here is an example:
dim iSyntax dim iReturnValue iSyntax = "FolderCreate(""Test AccountNewFolder"";""Folder description"";0)" msgbox groupwise.throwtoken(iSyntax, iReturnValue)See the TokenAPI (http://developer.novell.com/documentation/gwtoken/index.html?gwtokens/data/hj8ej8g5.html) for the parameters of the FolderCreate method.
Hope this helps.
Regards,
Advansys SupportPlease see Messages.Add method in the Object API to adds an existing message object to the collection.
Regards,
Advansys SupportThanks for your feedback.
Regards,
Advansys SupportNovember 16, 2006 at 2:57 pm in reply to: Publish Distribution List not exporting external references (exchange 2003 contacts) #8344We haven’t had any reports about this issue. This solution uses the GroupWise Admin API to access the members within a distribution list. For some reason the Admin API is only returning the GroupWise entities in your system. We don’t have MS Exchange in house so we are unable to test this behaviour.
We don’t formally support the Cool Solution applets. However, as this solution is provided as open source to the community, if you have programming skills in-house then you can modify the solution. You will need to install Formativ Creator or Studio to modify the source. Once you install Formativ Creator or Studio, execute the Publish Distribution List installer to install the open source version. Please let us know about your progress. If you are able to modify the source then please send us the updated version so that we can publish it back to the community.
Hope this helps.
Regards,
Advansys Support[This message was edited by Support 2 on November 16, 2006 at 04:36 PM.]
We have reported this bug to Novell and they have assigned a defect number for this bug. Hopefully this bug will be fixed on next release.
Please refer to “Formativ Language Guide”, “Formativ Developers Guide” and GroupWise Object API for more information about creating message. See below the sample code from the “Formativ Developers Guide” about creating appointment:
quote:
You can create any kind of message without a user interface. You would normally use this approach when you have all the information required to create a new item,
and there is no need for user interaction. For example, you may write an Applet to read email addresses from a database,
then create and send a customized email message to each address.
In this case there is no need for a user to see the actual messages being composed.Although there are several variations, the most common way to create a new message is this:
Call the Add method of the Messages collection owned by the folder in which you wish to store the message. For example,
the following Applet creates a new personal GroupWise Appointment in your own calendar:Sub Main(Client, GWEvent) Dim objMessage ' Create the new message Set objMessage = GroupWise.Account.Calendar.Messages.Add("GW.MESSAGE.APPOINTMENT", 3) ' Set some properties objMessage.OnCalendar = True objMessage.FromText = GroupWise.Account.Owner.DisplayName objMessage.Subject = "This was created using Formativ" ' Display the MessageID of the new message MsgBox(objMessage.MessageID) End Sub
Hope this helps.
Regards,
Advansys Support[This message was edited by Support 1 on November 13, 2006 at 03:37 PM.]
Not appropriate question for this forum, please see our response below:
http://www.advansyscorp.com/forums/topic/5061048931/Regards,
Advansys SupportIt appears account specific issue, GWCheck of the user’s account may help. Be sure you have installed all patches available for the GroupWise client.
If the problem persists, please post the Formativ configuration. 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.
Regards,
Advansys SupportWe haven’t had any report about this issue. Here are some suggestions:
- Make sure you are running the latest version of GW 7 client (not the beta version).
- Setup MAPI configuration as described in the documentaion:
There are well known MAPI configuration issues when running both the GroupWise client and Outlook on the same workstation. Prior to migration, prevent Outlook using the Novell MAPI default settings by configuring the Outlook client to prompt on startup for the MAPI profile to be used. You can configure this behavior in the Outlook client under Options | Mail Services | Prompt for a profile to be used. On Windows 2000 or above, you can also set this option by using the Windows Control Panel | Mail | Show Profiles, "When starting Microsoft Outlook, use this profile:" Prompt for a profile to be used. When Outlook starts and prompts you for the profile, select the appropriate one to connect to your Outlook data.
- Make sure the Outlook is not running prior to start GroupWise. You can start Outlook after the GroupWise started. We have noticed strange behaviour in GroupWise 7 client, if the Outlook is running prior to GroupWise. This behaviour has been reported to Novell.
Hope this helps.
Regards,
Advansys SupportYou can not modify most of the properties (To, Sender, subject, etc) of a received message. May be you need to re-create the message using the AddExistingMessage method. See the Object API for more information.
Regards,
Advansys SupportUse the Kind property and set the value to 2 for the time control. See the sample code below:
Leave Start Date: <DateTime prompt="Leave start date"></DateTime> Leave Start Time: <DateTime prompt="Leave start time" kind="2"></DateTime>
Regards,
Advansys Support -
AuthorReplies