16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1058 Part X: <strong>Microsoft</strong> Office 2003 Integration with SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

Note The relink feature will not work for forms that were created with a different<br />

form template than that of the form library.<br />

F39XR14<br />

Figure 39-14 Relink Forms page<br />

Deploying Fully Trusted Forms<br />

By default, InfoPath forms published to SharePoint form libraries are restricted from<br />

accessing system resources <strong>and</strong> are not allowed to use any software components<br />

that are not marked as safe for scripting. Such forms (<strong>and</strong> their templates) are said<br />

to be s<strong>and</strong>boxed. A s<strong>and</strong>boxed form template is cached for offline use, is automatically<br />

updated, <strong>and</strong> has restricted access to system resources. When a user fills a<br />

s<strong>and</strong>boxed form out, the form is placed in a local cache <strong>and</strong> denied access to system<br />

resources. Up until now in this chapter, we have been discussing the s<strong>and</strong>boxed<br />

forms. This type of form is sometimes referred to as st<strong>and</strong>ard forms; they inherit<br />

their permissions from the domain in which it is opened.<br />

You can avoid these limitations by creating a fully trusted form. Fully trusted<br />

forms have more permissions than s<strong>and</strong>boxed forms do. For example, they can contain<br />

code that uses external objects for accessing system resources; they can use software<br />

components or <strong>Microsoft</strong> ActiveX controls that are not marked as safe for<br />

scripting; <strong>and</strong> they can use custom business logic provided by COM components. In<br />

addition, some members of the InfoPath object model are set to security level 3,<br />

which means that they can only be used in a fully trusted form. For example, to<br />

access the <strong>Microsoft</strong> Office Comm<strong>and</strong>Bars object, you use the Comm<strong>and</strong>Bars property<br />

of the InfoPath object to set a reference to it. Because this property is set to<br />

security level 3, it cannot be used in a form that is not fully trusted.<br />

Unlike s<strong>and</strong>boxed forms, fully trusted forms must be installed on the client<br />

computer. That is why they are sometimes referred to as custom installed forms.<br />

Deploying a fully trusted form involves deploying form files in two locations.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!