Forum Replies Created

Viewing 15 replies - 466 through 480 (of 929 total)
  • Author
    Replies
  • in reply to: How to create a reply form? #7960
    Support 3
    Participant

      You can approach it by the following two ways:

      Option 1: Cancel the GroupWise event that caused an applet to execute.
      You can include the following line which will cancel the GroupWise event (i.e. message view will not display)

      groupwise.CancelGroupWiseEvent = true

      You need to change the “OnReply” event direction to “Before the GroupWise Event”. Click the arrow next to “OnReply” event to see the available direction.

      Option 2: Close the mail window

      Following code will close the window. It make sure the mail window is opened. Incorrectly calling the “CloseWindow” can result closing the GroupWise client window.

        
        if (lcase(groupwise.EnvCurrentViewName) = "mail") then
          groupwise.CloseWindow()
        end if
      

      We will recommend to use the Option 1 because the user don’t have to see the mail window open and close. See the Formativ language Guide for more information about the available methods.

      quote:


      I really hate to ask for more handouts, however i am really struggling to find what other predefined variables I can call on
      such as: GroupWise.Account.Owner.DisplayName etc etc, where can I find more information on what variables i can call up? I have been trying the programmers chm guide (from your website.


      “GroupWise.Account” return the logged in user object. You can view the available methods/properties in the Novell Object API documentation: http://developer.novell.com/documentation/gwobjapi/index.html?gwobjenu/data/h7ikbsqg.html

      Regards,
      Advansys Support

      in reply to: How to create a reply form? #7961
      Support 3
      Participant

        The following code access the selected message subject and prompt if the special “[MARKER]” text exists in the subject.

          
        '-------------------------------------------------------------------------------
        ' Mainline processing
        '-------------------------------------------------------------------------------
        
        Sub Main(Client, GWEvent)
        
          dim oMsg
          dim iSubject
        
          set oMsg = Client.clientstate.commandmessage
        
          if (not oMsg is nothing) then
            iSubject = oMsg.subject
            msgbox "Message subject: " & iSubject
        
            ' See the "Visual Basic Script Guide" for the instr function which you can access
            ' from the Formativ IDE Help menu.
            if (instr(1, iSubject, "[MARKER]", vbTextCompare) > 0) then
              msgbox "Marker found."
            end if
        
          end if
        
          set oMsg = nothing
        
        
        End Sub
        

        You can set the Mail – “On Reply” event as explained earlier to execute the code on replying message.

        Regards,
        Advansys Support

        in reply to: How to create a reply form? #7964
        Support 3
        Participant

          quote:


          1. We wish to send users an email on GW and on their reply of THAT particular message ( perhaps we could use the subject as the identifier) we want to load a form that formats their reply that is sent to us.


          You can use the Formativ “Mail – On reply” event and can display form, etc based on the message subject. See the “Developers Guide” for more information. You can view the available integrations from the Formativ IDE (Start Formativ IDE from the GroupWise toolbar, select an applet, click the Integrations tab, see Mail – Events). Once you set an event, you will need to re-start the GroupWise client.

          quote:


          2. How can you deal with the users that do not login to Novell, but use their GroupWise clients, hence they do not get the applets?


          Formativ applets is based on the GroupWise client and need to be installed to the users machine. Applet can be executed regardless whether the user login to the Novell. Please provide more details if we misunderstood the issue.

          Regards,
          Advansys Support

          in reply to: FML Extractor utility #8390
          Support 3
          Participant

            We are in the process of releasing the utility to convert the FML to HTML.

            However, we have released the first beta of the Advansys PST Converter solution, which will convert Advansys Archive to Go archives into Microsoft® Outlook® PST format. You can also convert Archive to Go archives to existing PST. This solution makes it easy to provide an alternative format for your Archive To Go portable archives, whether it be for people leaving an organization or for applications/professional services which require the Outlook PST file format or searching across multiple archives.

            If you are interested to test the beta, please write a message to support(support@advansyscorp.com)

            Regards,
            Advansys Support

            Support 3
            Participant

              Thanks for your feedback and sample code.

              The code-completion which is in our roadmap. We also have plan to extend further to support plug-in where developer can write the solution in other platform (i.e VS, Delphi, etc). As you know, it will require extensive R&D work. Currently we are occupied with making Formativ to Vista compatibility.

              Regards,
              Advansys Support

              in reply to: Export to Disk Doesn’t Include “From” Information #8424
              Support 3
              Participant

                It could be possible to export the “from” field of the message. However, this applet was submitted by “Steven Stewart”, author of this solution is no longer available and while it is not officially supported by Advansys. If you have in-house programming experience then we may be able to provide you the source code. Otherwise you need to contact our partners (http://advansyscorp.com/resellers_formativ.htm) for custom enhancement.

                Regards,
                Advansys Support

                in reply to: Accessing Information from GroupWise.AddressBookDlg #7954
                Support 3
                Participant

                  It appears to be a bug in the GroupWise ActiveX – “Address Book Control”, TargetType returns what seems to be random values. We will report this behaviour to Novell and post any update in this thread.

                  Regards,
                  Advansys Support

                  [This message was edited by Support 2 on April 01, 2008 at 03:54 PM.]

                  Support 3
                  Participant

                    If you want to access all messages in a given folder then try the following code. Note that, you have to use bit different technique when accessing the messages in Mailbox folder. Mailbox folder usually contains the sent messages which you can not see in client.

                      
                      dim oFolder
                      dim oMessages
                    
                      set oFolder = client.clientstate.selectedfolder
                    
                      if (oFolder.ObjType = fgwMailbox) then
                        set oMessages = oFolder.messages.find("(BOX_TYPE=INCOMING)")
                        msgbox oMessages.count
                        set oMessages = nothing
                      else
                        msgbox oFolder.Messages.count
                      end if
                    
                      set oFolder = nothing
                    

                    Regards,
                    Advansys Support

                    in reply to: Accessing Information from GroupWise.AddressBookDlg #7955
                    Support 3
                    Participant

                      Please see “Address Book Control” in GroupWise ActiveX API for available methods: http://developer.novell.com/documentation/gwactive/index.html?page=/ndk/doc/gwactive/gwax_enu/data/bktitle.html

                      Follwing code will return the target type (TO, CC, BC) of the selected contacts.

                        
                        dim iText
                        dim iCounter
                      
                        iCounter = MainDlg.oGWAB.Count
                      
                        for x = 0 to iCounter - 1
                          iText = iText & MainDlg.oGWAB.EMailAddress(x) & " (target type: " & MainDlg.oGWAB.TargetType(x) & ");"
                        next
                      
                        msgbox iText
                      

                      Regards,
                      Advansys Support

                      in reply to: Accessing Information from GroupWise.AddressBookDlg #7952
                      Support 3
                      Participant

                        – Add the GWab control to your form (In Formativ Form designer, select GroupWise tab then add the GWab control). Change the name property to “oGWAB”
                        – Change the ShowButtons property to “2” which will add the “Ok” button.
                        – Double click the “OnOkClick” event and add the following code

                          
                        Sub testGWab1OkClick(Sender)
                        
                          dim iText
                          dim iCounter
                        
                          iCounter = MainDlg.oGWAB.Count
                        
                          for x = 0 to iCounter - 1
                            iText = iText & MainDlg.oGWAB.EMailAddress(x) & ";"
                          next
                        
                          msgbox iText
                        
                        End Sub
                        

                        Hope this helps.

                        Regards,
                        Advansys Support

                        in reply to: Archive to Go 1.5.1 – GW Message Metadata – Properties #9491
                        Support 3
                        Participant

                          quote:


                          The problem has been and continues to be that I don’t get the message property information on the Archived email that is migrated. I do with the live email, but not the users Archive. I need to have the message metadata (Property) information for both Live and Archived using the LOCAL method following the .pdf instruction manual.


                          Thanks for clarification.

                          Its a known GroupWise issue. Archive To Go will export the GroupWise Message Property information (Mail Envelope Properties) only for the primary or the archive mailbox (not both). If you log in to the GroupWise primary account then Archive To Go will export the message properties for the primary account. However, if you log in to the GroupWise archive then Archive To Go will export the message properties for the archive account.

                          We also hope there will be new APIs in Bonsai which will allow us to address this requirement.

                          quote:


                          Also, is there a way to add new files to an existing migration for the same user. I’m saving to the local hard disk and not breaking up the files for CD or DVD. But would like to add only new information if possible to the existing or previous run on the user.


                          Archive To Go version 2 will support this feature (We expect to release during Q3/Q4 2008).

                          Regards,
                          Advansys Support

                          [This message was edited by Support 2 on March 25, 2008 at 03:52 PM.]

                          in reply to: Viewer error: Invalid unicode character #9500
                          Support 3
                          Participant

                            Please send the file to support and we will look into the issue.

                            Regards,
                            Advansys Support

                            in reply to: Viewer error: Invalid unicode character #9496
                            Support 3
                            Participant

                              We think the problem is caused by invalid data inside the index file. It would help us to correct the problem if you could send the following file to support (support@advansyscorp.com).

                              “/media-01/_metadata/00000014.xml”

                              Please do not hesitate to contact us if you have any further questions or comments.

                              Regards,
                              Advansys Support

                              in reply to: Archive to Go 1.5.1 – GW Message Metadata – Properties #9492
                              Support 3
                              Participant

                                Please see the information below from the “Creator Users Guide” to access the message properties.

                                quote:


                                Local Access requires the archive creator to know the target account’s password. Use this mode when you require the GroupWise Message Property information (Mail Envelope Properties – see note below), where accessible, to be saved with the exported message. Message Property information is not available when using Enterprise Access.
                                Advansys® Archive To Goâ„¢ – Mailbox Exporter for GroupWise®

                                Advansys Archive To Go Creator Manual
                                If you choose to save GroupWise Message Property information the export process will be slower.

                                Note:
                                To save mail envelope properties, first log into the target account’s mailbox. You can use the GroupWise client command line options /@u-? or /@u-<UserID>.
                                Advansys®


                                Archive To Go version 2.0 will support continuous archives and many other features. We expect to release version 2.0 during Q3 2008.

                                Regards,
                                Advansys Support

                                in reply to: Viewer error: Invalid unicode character #7950
                                Support 3
                                Participant

                                  Thanks for reporting to the correct forum.

                                  Regards,
                                  Advansys Support

                                Viewing 15 replies - 466 through 480 (of 929 total)