I have looked at the three papers published about BizTalk Server 2006.
I have one large complaint. I feel like the WSS Adapter is incomplete. I think everything that I see there good, for the most part. I will split my complaints into two pieces.
NOTE: These complaints assume that I am not using a XML file of any kind. Assume I am using BizTalk with TIFF documents.
A. WSS Receive
Archive Filename- "the adapter can set the filename to a fixed string or to a name derived from the XML data in the document."
Why is there no option to use the actual filename?
Why cannot use the actual file and then a string and then placeholder?
B. WSS Send
FileName - - "the adapter can set the filename to a fixed string or to a name derived from the XML data in the document."
Why is there no option to use the actual filename?
Why cannot use the actual file and then a string and then placeholder?
Override - Whether an already existing WSS file should be overwritten or not. Supported values “yes”, “no”, “orchestration”
If I chose no, what happens?
Here is what I believe the behavior should be.
1. Document Library-Versioning disabled
a. Override (yes) - delete the file in SharePoint and replace with new file
b. Override (no) - put new file in the bit bucket, better yet make it a error message
2. Document Library- Versioning enabled
a. Override (yes) - delete the most current verison of the file in SharePoint and replace with new file
b. Override (no) - version the files
This is the way I would interpret the options. And if I am interpreting the options incorrectly, then I believe that the functionality should exists in the adapter.
I am writing this now in hope that my ideas will be incorporated in the adapter. I will be attending TechEd 2005 and will hopefully be able to talk to Scott Woodgate.
Related Post:
I just changed a few things which are in italics in order to make things a little clearer.