0

Document Reclassify

Dears:

Can we reclassify even minor versions of document through custom tool built using .net and Vault API. When I'm reclassifying the document with this tool, it only reclassify latest version not the other minor versions associated with it. Is It correct behavior?

Document Type change from A to B while reclassify but Vault not looking for mandatory fields for document type B. It still reclassify the document..Is It correct behavior?

 

Thanks & Regards,

Manish

6 comments

  • Avatar
    Adam McMillan

    Hey Manish,

    Reclassification should only be possible on the latest version of the document, so it sounds like that's working as designed. If reclassifying using the API, I would expect required fields to be enforced, but I suspect in your case the fields are only made required through field dependencies (which are UI constraints only, and doesn't make the fields mandatory in the API).

  • Avatar
    Manish Kumar

    Hey Adam:- That makes sense. Also, when document is checked out and is in steady state one should not be able to reclassify using API, but I'm still able to do. is it expected behavior? Please advise.

    Regards,

    Manish

  • Avatar
    Adam McMillan

    We should probably block that one, but I don't believe it is explicitly blocked today.

    We should also block state change and create draft when the document is checked out; these are all on our radar.

    Thank you for the feedback, very helpful

  • Avatar
    Manish Kumar

    Hi Adam:

    I hope you could help me on this. If my understanding is correct then in order to retain document status while reclassifying via custom code, migration mode has to be enabled. I opened a ticket with Veeva Support and they told that it's already enabled in the vault on which I'm testing. But still it's not retaining status.

    Has there been any change lately which is causing this. I tested the same thing in start of month and after enabling migration mode, i was able to reclassify and retain document status as well. But unfortunately not today :(

    Thanks & Regards,

    Manish

  • Avatar
    Adam McMillan

    If reclassifying in the UI, a document will retain its lifecycle state if:

    • Your vault has the "Retain Document Status and Number if applicable" feature enabled (ask your CSM, or file a support ticket)
    • The same lifecycle state exists in the lifecycle associated with the new document type you're reclassifying to

    I'd expect that to be the same behavior in the API call as well, but perhaps not. I can check with my team.

  • Avatar
    Manish Kumar

    Hi Adam - Thanks for your response. This setting is already enabled on the vault on which I'm testing. Also, when i was testing on April 22nd, 2019 it was retaining status but now it's not. I am not sure if something has changed in back end in Veeva settings which is causing this. Do you have any idea on this.

     

    Thanks & Regards,

    Manish

Please sign in to leave a comment.