• Creator
    Topic
  • #4159
    lp_irovetz
    Participant

    Eek

    Hi, Advansys team
    Another question about Document

    Here is my code
    ‘====
    DocNewPath = LibTrouv.LibraryId +”:” & DocNewNum & “.1” ‘First version by default

    groupwise.DisplayProfile(DocNewPath)

    path = groupwise.OpenDocument(DocNewPath,199)
    ‘=====

    The document is open but DisplayProfile do nothing.
    No error, no sound, no bug,… nothing Confused

    Any idea ???
    Thanks

  • Author
    Replies
  • #7301
    Support 1a
    Participant

    We tried this token as well and couldn’t get it to do anything. It looks like this token may be broken as well, or we might be calling it with incorrect parameters. I notice the Token documentation (http://developer.novell.com/ndk/doc/gwtoken/gwtokens/data/h8h668yx.html) states

    quote:


    DocIDStr in the form Domain.PostOffice.LibraryBig Grinoc#.Ver# for ObjectAPI reference: LibraryID: Doc#.Ver#. The DocIDStr is a subset of the object DocumentVersion.ODMADocumentID in the ObjectAPI.


    I’m not sure if this means you need to use the ODMADocumentID property of the current version.

    I’ll ask Novell about this one – unfortunately it looks like it could be a bug in the GroupWise client. Which version of the client are you using?

    Regards,

    Advansys Support

    #7299
    lp_irovetz
    Participant

    Well, i had tried it with

    PO 6.5.3 and Client 6.5.4
    PO 6.5.4 and Client 6.5.4

    If bug, could you ask Novell to include correction it in 6.5.5. I hadn’t tied with the beta ! Could you ?

    Tanks

    #7298
    Support 1a
    Participant

    We’ll report this as a bug to Novell. I couldn’t say when/if they’ll fix it, though. It always helps getting a bug fixed if other reports are received, so you may want to report a bug in the DisplayProfile() token independently from us.

    Regards,

    Advansys Support

    #7306
    lp_irovetz
    Participant

    Hi advansys team

    sorry to call to mind this old subject Cool

    but do you have some news about it from Novell. I’d repport it on Novell Dev forum with no result

    Do you know a work arround, even with ‘stange/exotic’ solution Razz

    L.P. Irovetz
    ARCANE GroupWare

    #7302
    Support 1a
    Participant

    Hello LP,

    No, I’ve not heard anything back from Novell. I’ve just sent an email asking for a status update.

    Unfotrtunately I am not aware of any workarounds to this aparent token bug.

    I’ll let you know what I find out.

    Regards,

    Advansys Support

    #7304
    Support 1a
    Participant

    Novell have confirmed this as a bug and have assigned it defect # 145301.

    They were unable to say when it might be fixed, but indicated it probably would only make it into a post 6.5.6 FTF release. It may make it into GW7 SP1, but SP2 is probably more likely.

    I’ll post more here when I hear anything from them.

    Advansys Support

    #7303
    lp_irovetz
    Participant

    Many thanks for your help

    Do you know when this bug came ? Is it “by first design Wink” or after a realease.

    For my project, it doesn’t matter that the client is 5.5.1 because it’s for a special workstation
    On it, i’d like scan documents and put them in DMS by a VB applets, the user has no need to used message.


    I need to used this token because the Author property of document is RO, disagree of the documentation.
    The only way i found is to used ‘displayprofile” token

    LP Irovetz
    ARCANE GroupWare

    #7300
    Support 1a
    Participant

    I don’t know when the bug first appeared. (I doubt even Novell could tell me that). You would probably need to experient to see if you could find a version where the token worked.

    You may be able to get more information from Novell’s developer support forum.

    Advansys Support

    #7305
    Support 1a
    Participant

    It turns out that, in at least the 6.5.5 client, the DisplayProfile token is not broken.

    The defect actually lies in the Formativ GroupWise.DisplayProfile() command. When Novell duplicated the bug, they accidently used the incorrect syntax for the document ID. They today realised this and found the command does actually work. This led us back to our wrapping, which we found to be incorrect. We have fixed this in Formativ. The fix will be available in the next maintenance release.

    In the meantime, you can work around the bug by using ThrowToken as shown here:

    iSyntax = "DisplayProfile(""GWHQ.MOSMAN.MOSMAN Library:1686.1"")"
    groupwise.throwtoken(iSyntax, iReturnVal)

    I hope this helps.

    Advansys Support

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.