SharePoint
Digital signatures can be used in Office InfoPath 2007 browser forms to sign sections of data. However, the certificate that you use must be installed on both the client and SharePoint server machines...
posted @ Monday, March 24, 2008 4:50 PM | Feedback (0)
The XmlFormView is a common way to display Office InfoPath 2007 browser forms on a custom ASPX page. One thing to keep in mind though is that the InfoPath form template that is to be displayed in the XmlFormView control must reside in the same site collection as the custom ASPX page...
posted @ Wednesday, February 20, 2008 11:47 AM | Feedback (2)
If you have ever encountered the "Error updating a list item: Document checked out" issue in a SharePoint workflow, it appears that there is a resolution...
posted @ Thursday, October 18, 2007 3:34 PM | Feedback (6)
This is the final installment in a four-part series about the time-off request solution, an end-to-end Microsoft Office SharePoint Server 2007 solution that uses Microsoft Office Word 2007 as a form application. In the previous post I added a custom document information panel to the Time-Off Request site content type. This post focuses on the development of Microsoft Office SharePoint Designer 2007 workflows that will route task assignments and update time-off balances accordingly...
posted @ Tuesday, June 12, 2007 1:46 PM | Feedback (7)
This is the third installment in a four-part series about the time-off request solution, an end-to-end Microsoft Office SharePoint Server 2007 solution that uses Microsoft Office Word 2007 as a form application. In the previous post I built an Office Word 2007 document template using content controls and associated it with the Time-Off Request site content type. This post focuses on the document information panel and its ability to drive business logic in the form without any custom code...
posted @ Thursday, June 07, 2007 8:33 AM | Feedback (12)
This is the second installment in a four-part series about the time-off request solution, an end-to-end Microsoft Office SharePoint Server 2007 solution that uses Microsoft Office Word 2007 as a form application. In the previous post I created the site columns for the solution and included them in a site content type. This post focuses on the Office Word 2007 document template and the binding of content controls to those site columns...
posted @ Friday, June 01, 2007 8:18 AM | Feedback (6)
In my last post I alluded to a time-off request solution that uses Microsoft Office Word 2007 as a form application. Here, I will begin the process of documenting how that solution was built. This post, the first in a four-part series, will focus on the creation of a Microsoft Office SharePoint Server (MOSS) 2007 content type...
posted @ Tuesday, May 29, 2007 4:51 PM | Feedback (5)
A few people have asked if it is possible to create a SharePoint Designer workflow variable that includes references to other variables. Indeed, it is possible. The Build Dynamic String action in the Workflow Designer allows you to define any combination of static text, list field data, and workflow data in a single variable...
posted @ Wednesday, February 28, 2007 11:03 AM | Feedback (16)
When you create a new MOSS 2007 wiki page library, there are always two pages added by default: "Welcome to your wiki library" and "How to use this wiki library". The former is assigned the ./Home.aspx URL and is the default home page for the library. Changing this default home page is not as intuitive as you might think...
posted @ Wednesday, February 14, 2007 9:26 AM | Feedback (0)
When designing Microsoft Office InfoPath form templates, filtering can be used to limit the options that are displayed to users in certain controls. However, if you are designing an Office InfoPath 2007 form template for a browser scenario, it should be noted that filtering is not supported. In this post, I offer a workaround for the unsupported filtering feature...
posted @ Tuesday, January 16, 2007 5:39 PM | Feedback (2)
A number of good questions have been raised about the building permit application solution that we built. One question in particular that I see frequently relates to the SharePoint columns that were promoted from the InfoPath form template. How did we enable some of those columns to be editable so that they could be modified by a SharePoint Designer workflow? The answer to the question is actually quite simple...
posted @ Friday, October 27, 2006 10:32 AM | Feedback (3)
A few months ago I wrote about how a Microsoft Office SharePoint Designer 2007 workflow can be used to update SharePoint list items. In that post the workflow logic that was described was attached to a specific document library, and the Update List Item action was used to set field values for files in that library. I have since found out that Office SharePoint Designer 2007 workflow functionality can extend to other SharePoint lists...
posted @ Thursday, October 26, 2006 10:39 AM | Feedback (27)
The 2007 Microsoft Office release has built-in support for running InfoPath forms in a mobile Web browser. Granted, there are limitations to the form behavior. For instance, all formatting and layout in views are ignored, and controls such as the rich text box, option button, and section are not supported. Still, the fact that InfoPath form data can be submitted from mobile devices opens up a broad range of user scenarios...
posted @ Tuesday, August 22, 2006 2:16 PM | Feedback (5)
Microsoft Office InfoPath 2007 supports parameters for browser forms. This functionality can make form solutions more dynamic and requires only a small amount of code. Within the Loading event of the form template, the TryGetValue method is needed for each parameter value that is being passed. Then, the appropriate fields in the form file can be set accordingly...
posted @ Monday, July 24, 2006 11:35 AM | Feedback (6)
The much-hyped building permit application solution, which was featured in John Peltonen's Tech•Ed 2006 demo and will be presented as an instructor-led lab later this month at TechReady3, includes a feature that has not been discussed in great length but has been sought after by developers for a long time. The feature, having a Microsoft Office InfoPath 2007 form hosted in a custom Web page, is used at the beginning of the demo—when the applicant first provides building project information...
posted @ Friday, July 14, 2006 10:22 AM | Feedback (0)
This is the sixth and final installment in a series about the building permit application, an end-to-end solution built entirely with the 2007 Microsoft Office release. The previous post described how to enable form conversion for archiving in a SharePoint document library. This post focuses on key performance indicators (KPIs)…
posted @ Wednesday, July 05, 2006 10:19 AM | Feedback (7)
This is the fifth installment in a series about the building permit application, an end-to-end solution built entirely with the 2007 Microsoft Office release. The previous post described how routing logic was developed with SharePoint Designer. This post focuses on the creation of an archival policy...
posted @ Friday, June 30, 2006 9:17 AM | Feedback (1)
This is the fourth installment in a series about the building permit application, an end-to-end solution built entirely with the 2007 Microsoft Office release. The previous post identified the new InfoPath e-mail attachment options. This post focuses on workflow logic…
posted @ Tuesday, June 27, 2006 12:44 PM | Feedback (10)
This is the third installment in a series about the building permit application, an end-to-end solution built entirely with the 2007 Microsoft Office release. The previous post described the implementation of user role functionality. This post focuses on InfoPath e-mail attachments…
posted @ Wednesday, June 21, 2006 12:46 PM | Feedback (0)
This is the second installment in a series about the building permit application, an end-to-end solution built entirely with the 2007 Microsoft Office release. The last post provided an overview of the solution and explained the "design once" concept of Microsoft Office InfoPath 2007. This post focuses on how user roles are implemented in the solution…
posted @ Friday, June 16, 2006 10:38 AM | Feedback (3)
Recently, I have touted how the 2007 Microsoft Office release simplifies the overall development effort for end-to-end solutions. Currently, I have been developing different variations of a building permit application solution, for which I promised in my last post to share some details. In this post, I will provide an overview of that solution and highlight one key feature: the "design once" concept of Microsoft Office InfoPath 2007…
posted @ Monday, June 12, 2006 12:01 PM | Feedback (10)