Sunday, July 16, 2006

Possible bug in workflow schema?

I am playing around with workflows, and I have stumbled on what is either a possible bug or a mistake in documentation.

The SDK clearly states that "Microsoft Windows SharePoint Services (version 3) supports absolute or server-relative paths in the workflow template definition. All form path URLs must be expressed in one of these formats. For example, an absolute path, such as "http://site/library/page.aspx"; or a server-relative path, such as "/layouts/page.aspx". Microsoft Windows SharePoint Services (version 3) does not support link fix-up in workflow template definitions."

So from this I understand that a link like "http://sharepoint/_layouts/formserver/.../form.aspx" is as valid as "/layouts/formserver/.../form.aspx".

Well, either I misunderstood, or the documentation is wrong or there is a bug. I tried the full absolute URL ("http://sharepoint...") and when I set the workflow settings for a forms library, it tried to open the link as if it was relative ("http://sharepoint/http://sharepoint...").

I can only hope this is a minor bug, and microsoft are planning to fix this.

Side Note
By the way, am I the only one who, when he writes fast on the keyboard writes "sharepoing" instead of "sharepoint"? I guess its because my fingers are used to writing "ping" and also because I am used to an agronomic keyboard, and I dont have one here at work. )-:


ARJ said...

Actually, I do that SharePoing thing all the time. You aren't alone.

Raghu Iyer said...

Well am in "Sharepoing" grp now:-) .This fact got me excited to hunt for more "Sharepoing" users so i did a simple google with "sharepoing". SharePoint and the result was beyond my expectation .

Neal said...

This bug just came up for me as well -- in one of the prefab workflows (the "approvals" workflow), the email that is sent to the approvers has three steps, two of which include hyperlinks: to (1) review the document and to (2) approve/reject it.

The hyperlink for #1 is malformed b/c of this relative path error. The second hyperlink works just fine. I'm trying to dig through all related pages to find where to fix this email code. Any ideas???