Forum Replies Created

Viewing 15 replies - 286 through 300 (of 913 total)
  • Author
    Replies
  • in reply to: Delete attachments with reference #8747
    Support 1a
    Participant

      Dear HRH,

      We don’t have a full version of this particular solution. To date we have not had sufficient demand to create a more fully-featured, paid version.

      How many users in your organization would be likely to require such a solution if it existed?

      Regards,

      Advansys Support

      in reply to: Delete attachments with reference #8746
      Support 1a
      Participant

        This is working as designed. The free solution you are referring to does not leave any reference to the attachments it deletes.

        Regards,

        Advansys Support

        in reply to: Problems with Calendar Pack 2.0 #8734
        Support 1a
        Participant

          Thanks for the update. Thank you also for the enhancement request regarding the Anniversaries solution, which I have entered into our product database.

          Regards,

          Advansys Support

          in reply to: Problems with Calendar Pack 2.0 #8741
          Support 1a
          Participant

            An update will be emailed to you today.

            Regards,

            Advansys Support

            in reply to: Intégration in Menu #7215
            Support 1a
            Participant

              Thank you for your question. Yes, I suspect the client language is the issue here. In order to insert a menu item at a particular position within a menu, we need to identify an ‘anchor’ menu item by caption. At this time Formativ contains only English menu caption definitions.

              To work around this, you need to edit a text file that is part of Formativ. Assuming you are using GroupWise 6.5, the file is called ‘msgclass6_5.txt’, and will be found in the Formativ program files folder (The other supported version are named based on the supported version – it should be pretty easy to see which file goes with which version).

              Open the file and look for a section that looks like this:

              [GW.CLIENT.WINDOW.BROWSER]
              Description=GroupWise Main Window
              Toolbar=1
              Popup=1
              Events=0
              Opened=5
              Closed=5
              
              #File="New","Open Archive","Open Backup","Open View...","Save As...","Import Documents...","Import POP3/IMAP...","Proxy...","Sharing...","Properties","Print...","Print Calendar...","Retrieve...","Mode","Exit"
              #Edit="Cut","Copy","Paste","Select All","Add Calendar Tab...","Delete","Delete and Empty","Retract","Retract and Delete","Delete Sent Item","Undelete","Empty Trash","Change to","Folders...","Move/Link to Folders...","Find Text...","Find Next","Find Previous"
              #View="Toolbars","Folders List","QuickViewer","Display Settings","Appointment Display","QuickView","Threads","Filter","Next Unread Item","Prev Unread Item","Go to Today","Go to Date...","Refresh"
              #Actions="Open","View","Accept","Accept with Options...","Decline","Decline with Options...","Reply...","Forward","Forward as Attachment","Delegate...","Resend","Show Appointment As","Move to Archive","Restore","Junk Mail","Version List","Copy Document...","Check Out...","Check In...","Reset Document Status","Alarm...","Mark Private","Mark Completed","Categories","Read Later","Mark Read","Move to Checlist Folder","Show in Checklist","Checklist Actions","NNTP Newsgroup Actions"
              #Tools="Address Book","Dial Sender","Junk Mail Handling...","Rules","Find...","Stop Find","Busy Search...","Date Difference...","Mass Document Operations...","Replace Document With Backup","Hit The Road...","Check Mailbox Size...","Options..."
              #Accounts="Send/Retrieve...","Retrieve Selected Items...","Pending Requests...","Connection Log...","Show Status Window","Auto Send/Retrieve","Account Options"
              #Window="Minimize GroupWise","Close Others","New Main Window","Calendar"
              #Help="Help Topics","What's New","User's Guide","Cool Solutions Web Community","Novell GroupWise Home Page","About GroupWise"
              

              The “#File=”New”,…” lines related to the main menu items. You would need to translate any of these entries you wished to use as anchors. It would not be necessary to edit all of them. For example, if you wanted to be able to add a menu to the ‘File’ menu after ‘Proxy…’, you would need to translate the “#File=”New”,…” line.

              Once the file has been edited you would need to restart the GroupWise client, then define your menu integrations. You will also need to distribute this file with your solution.

              I hope this helps.

              Advansys Support

              in reply to: Cancel event – email tracking #7211
              Support 1a
              Participant

                You are welcome.

                Advansys Support

                in reply to: Problems with Calendar Pack 2.0 #8743
                Support 1a
                Participant

                  Thank you for your post. Updates have been sent to you via email. These updates will be released publically in the near future.

                  Regards,

                  Advansys Support

                  in reply to: Setting destination fields to addresses with initials #7189
                  Support 1a
                  Participant

                    We spent some more time on this issue, and believe we have discovered two cause of the behavior. Whether or not Novell will see these as bugs I’m not sure.

                    There are two scenarios where this behavior can be seen:

                    1) Two Address Book entries with the same Display Name value, different email addresses

                    The problem occurs when you have two address book entries that share the same Display name in different Address Books. One entry is a GroupWise user in the System address book, the other is an external user in a personal address book. This address book may or may not be in the name completion order.

                    Use ItemSetText() to type the Display Name of the recipient into the TO field. Don’t set the focus to the TO field. When you try to send the message the recipient is crossed out.

                    It appears the duplicate display names in different address books causes the resolution process to fail. Manually entering the same display name would appear to invoke an internal address book resolution lookup and the send is successful.

                    2) External Email Address

                    Define an address book entry in a personal address that has an external (non-GroupWise system) email address. Use ItemSetText() to type the Display Name of the recipient into the TO field. Don’t set the focus to the TO field. When you try to send the message the recipient is crossed out.

                    In this case it appears address book entry resolution is not occurring. The send succeeds if the text you enter includes the external email address in brackets.

                    While both scenarios are slightly different, the results suggest that in both cases using the ItemSetText() token does not cause the same recipient resolution process to occur that happen when the same text is typed manually into the TO field. Using ItemSetText() doesn’t cause the individual keystroke events to fire in the same way as when you manually enter text into the recipient box. I’m not sure whether Novell are going to view this as bug.

                    Regards,

                    Advansys Support

                    in reply to: Creating Mail with an Documentreference #7205
                    Support 1a
                    Participant

                      Thank you for your question above. A Document object (i.e. a document added to a library) and a document reference are two distinct objects. Given a document object, you need to create a document reference and associate with with the document object. Once you have created a document reference, you can attach it to a message as you would any other message object.

                      Assuming you add a document to a library and obtain a reference to the Document object like this:

                      set oDocument = iDocumentLibrary.Documents.Add(iAttachment, oDocumentType)

                      You then need to create a DocumentReference object in some folder and associate it with the document like this:

                      docref = GroupWise.Account.DocumentsFolder.Messages.Add("GW.MESSAGE.DOCUMENTREFERENCE", oDocument, fgwCurrent)

                      ‘docref’ now refers to the DocumentReference object (in this case stored in the users Documents folder). You could then add this as an attachment to a message.

                      I hope this helps.

                      Regards,

                      Advansys Support

                      in reply to: Cancel event – email tracking #7212
                      Support 1a
                      Participant

                        Simon,

                        Thank you for your post above. Unfortunately GroupWise doesn’t provide us with a message-based ‘OnCancel’ event. The application level Cancel event you see refers to certain application level dialogs – not messages, unfortunately.

                        Requests have been made to Novell to add such an API. Unfotunately, to date the feature has not been added.

                        I’m sorry we could not provide a more positive response.

                        Regards,

                        Advansys Support

                        in reply to: Portal Manager dont like popups? #7202
                        Support 1a
                        Participant

                          Hello Rene,

                          Thanks for the update – I can understand your frustration. Hopefully IE 7 will address the problem.

                          Regards,

                          Advansys Support

                          in reply to: Portal Manager dont like popups? #7201
                          Support 1a
                          Participant

                            Hello Rene,

                            Thank you for your post above. Unfortunately, this is a known issue with the Internet Explorer ActiveX control (used by the portals) when used in a particular context. The sesssion security token is not passed between certain windows, resulting in multiple login requests and other side affects of session information not making it between windows.

                            The only work around (other than the ActiveX being fixed) involves changing the authentication scheme of the web site – not something that is usually possible).

                            Sorry I could not provide more positive response.

                            Regards,

                            Advansys Support

                            in reply to: Setting destination fields to addresses with initials #7195
                            Support 1a
                            Participant

                              No problems.

                              Advansys Support

                              in reply to: Setting destination fields to addresses with initials #7196
                              Support 1a
                              Participant

                                We’ll let you know via this thread and email. I have removed your email address from your post above so it doesn’t get picked up by spammers.

                                Regards,

                                Advansys Support

                                in reply to: Setting destination fields to addresses with initials #7198
                                Support 1a
                                Participant

                                  Unfortunately we were unable to identify any workarounds to the problem. It would appear the use of these GroupWise tokens breaks the standard address book resolution process that normally occurs.

                                  The only other possible way you could approach the problem would be to use the Object API to create and send the messages. This would involve the creation of a draft message in code, then setting the message properties, including recipients, using the Object API. This is a very different approach, as no user interface is involved, and may not suite your requirements.

                                  We’ve logged the token issue as a bug to be reported to Novell.

                                  Regards,

                                  Advansys Support

                                Viewing 15 replies - 286 through 300 (of 913 total)