Support 3

[Support 3]

quote:

---

Also please note that I was also not able to install on the limited accounts.

---

This is known behaviour of the Windows limited user account. Administrators can install software for the entire computer (i.e. “c:program files”). Standard users cannot perform these tasks and you have to run it through a privliged account or “Run as” option.

quote:

---

When I installed it on the admin account, I didn’t get the link from inside GW to launch the creator. I had to give the limited account admin rights, install it, and then remove the admin rights from the limited account.

---

Could you please clarify the behaviour. Does the “Archive To Go” creator – GroupWise toolbar exists in admin/standard account?

Regards,
Advansys Support

[Support 3]

We have sent the email.

Regards,
Advansys Support

[Support 3]

We sent the information to your email address in the Advansys Support Forums members database, but we received a notification of “Permanent Delivery Failure”.

Could you email your request to “support@advansyscorp.com”?

Regards,
Advansys Support

[Support 3]

Our engineers will review this issue and we will get back to you once we have an answer.

Regards,
Advansys Support

[Support 3]

We haven’t installed Formativ internally in Windows Server. However, in the forum post some users appear to installed successfully.

We have sent the work-around by email.

Regards,
Advansys Support

[Support 3]

Thanks for your post.

We haven’t had any report about this issue. Could you please tell us which auditing option you have selected (see below) during the archiving process?

In Archive To Go, you have the following auditing option:
– Use a text file for auditing.
– Use Redline for auditing. If Redline is/becomes unavailable, audit to a text file.
– Use Redline for auditing. If Redline is /becomes unavailable, stop archiving.

Regards,
Advansys Support

[Support 3]

Good to hear that you are making progress. If you have any further questions, please do not hesitate to contact us.

Regards,
Advansys Support

[Support 3]

We have seen the GroupWise API behave ‘strangely’ when processing a larger folder (4,960 or more messages). We recommend to split the larger folder to smaller folders. In your case, you may consider to create a find results folder with less then 4960 messages. Alternatively, you may try to save messages by smaller brunch from the large find results.

Hope this helps. If you have any further questions, please do not hesitate to contact us.

Regards,
Advansys Support

[Support 3]

We are extremely sorry about editing your post. On replying your post, by mistake our engineers have choosed the wrong option which edited your post.

Regards,
Advansys Support

[Support 3]

FYI, the example code above worked fine in 2 out of 3 GroupWise accounts. We are not sure why it failed to return the proper message ID in one account, it could be the message not yet synchronize with the GroupWise system. Although, the applet failed to return proper message id but the message actually saved to the Work-In-Progress folder. Note that, all of the 3 accounts tested are running in caching mode.

Regards,
Advansys Support

[Support 3]

Your code review shows that you did not call the GetWIPFolderPath from the main subroutine prior to save the message. The following code works fine in our environment. Let us know if we missed anything…

Sub Main(Client, GWEvent)

  dim iWIPFolderPath
  dim oMsg
  dim iMsgID
  dim iWIPPath
  Dim iBreakCount

 ' Save the draft message to the Work in Progress folder
  Call Groupwise.ItemSetText("X00", itfSubject, " COMPLETED", TRUE) ' TRUE = Append

  call GetWIPFolderPath(groupwise.account.workfolder, iWIPPath)

  msgbox "Work In Progress folder path: " & iWIPPath

  Call Groupwise.throwtoken("ItemSaveMessageDraft(""" & iWIPPath & """)", iReturnVal)

  ' Calling ItemMessageIDFromView immediately after GroupWise.ItemSaveMessageDraft
  ' can result in an X00 ID.
  iMsgID = GroupWise.ItemMessageIDFromView

  iBreakCount = 0
  while (iMsgID = "Token failed execution!") or (iMsgID = "X00")
     Application.ProcessMessages
     utilities.Timer(1)
     Application.ProcessMessages
     iMsgID = GroupWise.ItemMessageIDFromView
     iBreakCount = iBreakCount + 1
     Utilities.Trace iBreakCount & ": " & iMsgID
     if (iBreakCount > 10) then
       exit sub
     end if
  wend

  set oMsg = GroupWise.Account.GetMessage(iMsgID)
  msgbox "Subject: " & oMsg.subject.plaintext

End Sub



'-------------------------------------------------------------------------------
' Get full path of the Work-In-Progress folder where Drafts are saved
'-------------------------------------------------------------------------------
Function GetWIPFolderPath(aGWFolder, byref aPath)
  Dim sHome
  sHome = ""
  Utilities.Trace "aGWFolder.Name=" & aGWFolder.Name & " aPath=" & aPath
  If (Cint(Left(GroupWise.EnvVersionName,1)) >= 7) Then
    If aGWFolder.Name = GroupWise.Account.Owner.DisplayName Then
      sHome = " Home"
    End If
  End If
  If aGWFolder Is Nothing Then
    Exit Function
  End If
  If (aPath <> "") Then
    aPath = aGWFolder.name & sHome & "" & aPath
  Else
    aPath = aGWFolder.name
  End If
  If (aGWFolder.objtype = fgwRoot) Then
    Exit Function
  Else
    Call GetWIPFolderPath(aGWFolder.ParentFolder, aPath)
  End if
End Function  

BTW, you can use the custom fields to store data or insert the data to the message body. If the data is sensitive then you can consider to encrypt and decrypt at the other end by your solution.

Most probably in GroupWise 8 (Bonsai) will have the X-Fields where you can add additional data and viewable by other non GroupWise clients.

Hope this helps.

Regards,
Advansys Support

[Support 3]

Does the messages saved to the folder? You can use the Groupwise.ThrowToken() method to call the native Token(), alternative you can use our Token wrapper. See the Formativ Language Guide for more information. The code below execute the ItemSaveMessageDraft() token and return boolean value which indicate the token execution.

  msgbox Groupwise.throwtoken("ItemSaveMessageDraft(""" & iWIPPath & """)", iReturnVal)     

Could you also post the updated source so that we have review.

Regards,
Advansys support

[Support 3]

GroupWise 7 client contains a localized word ‘Home’ after the account name. You will need to modify the code to add the localized ‘Home’ word after the account name. See the code below:

  
  dim oMsg
  dim iMsgID
  dim iWIPPath
  Dim iBreakCount


  ' GroupWise 7+ onwards contains a localized word 'Home' after the account name.
  ' You will need to add the localized 'Home' after the name
  if (groupwise.EnvVersionName > "7") then
    iWIPPath = GroupWise.Account.Owner.DisplayName & " Home" & GroupWise.Account.WorkFolder.Name
  else
    iWIPPath = GroupWise.Account.Owner.DisplayName & "" & GroupWise.Account.WorkFolder.Name
  end if


 ' Save the draft message to the Work in Progress folder
  Utilities.Trace "iWIPPath=" & iWIPPath
  Groupwise.ItemSaveMessageDraft(iWIPPath)

  ' Calling ItemMessageIDFromView immediately after GroupWise.ItemSaveMessageDraft
  ' can result in an X00 ID.
  iMsgID = GroupWise.ItemMessageIDFromView
  iBreakCount = 0
  while (iMsgID = "Token failed execution!") or (iMsgID = "X00")
     Application.ProcessMessages
     utilities.Timer(1)
     Application.ProcessMessages
     iMsgID = GroupWise.ItemMessageIDFromView
     iBreakCount = iBreakCount + 1
     Utilities.Trace iBreakCount & ": " & iMsgID
     if (iBreakCount > 10) then
       exit sub
     end if
  wend

  set oMsg = GroupWise.Account.GetMessage(iMsgID)
  msgbox oMsg.subject.plaintext

Hope this helps.

Regards,
Advansys Support

[Support 3]

We have sent you email about the “PST Creator” beta, we look forward to receiving your feedback and suggestions.

If you want to know about the compression method then feel free to let us know.

Regards,
Advansys Support

[Support 3]

This enquiry has been handled by direct email.

Regards,
Advansys Support

[Author]

Replies