Fusion: Upload Document Module (New Version) not working!

[wesleydenaro]

Is there anyone out there using Fusion and the new Upload Document module (not the one marked Legacy) to upload a new version of a Document?

In a heavily used Fusion Scenario, I recently replaced the Upload Document (Legacy) module with the new, non-legacy module called Upload Document, thinking this was a smart thing to do. I have found that it will not upload a Document as a new Document Version (DOCV).

I have simplified to perform a test (see screenshot)

[1] Assign a valid, static document id to a system variable

[2] Download the document into Fusion

[3] Immediately upload that document as a new document version of the original document.

This does not work either. The scenario runs, does not error and does not save the document as a new version. This is infuriating!

I have reached out to Adobe Support, but they are ignoring me. Any suggestions or even confirmation that this BUG exists on any of your instances??

Thanks,

Wes Denaro

[wesleydenaro]

I did receive a reply from Adobe that suggested that I revert my update back to using the (Legacy) module, because "that one works".

Which prompts me to pose this question: Why doesn't Adobe mark their new modules (beta) until all the bugs are worked out? This is not the first time I have swapped out a Legacy module for a "new" module and found a BUG. AITAH for assuming that new is preferred and (Legacy) means deprecated?

If it's not fully working and fully tested, DON'T RELEASE IT!

End of rant, thank you,

Wes Denaro

[ChrisStephens]

I agree. I ended up testing the new module before I updated an existing code, and it can do everything else from what I can tell except for the versioning one. I submitted a bug report, but like you I got a less than helpful reply. It appears that when you do the version upload, the module doesn't make all of the api calls required to complete the upload.

[wesleydenaro]

Hi Chris,
I am going to adopt your method and fully test any and all new Fusion modules before rolling them into existing scenarios. This really should fall on Adobe development and QA, but I simply don't have the time to do my work AND test for bugs and report them back to Adobe.

Keep on rockin' in the free world Chris,

Wes-

[wesleydenaro]

Update:

Saving a document as a new Version has begun to partially work using the new Upload Document module, as Adobe deployed a fix to production... HOWEVER... if you choose the Map option and try to rename the document... that is not working yet.

Support has confirmed the behavior I have reported and observed, and is passing the info along to the development team.

Wes Denaro