Archive for the ‘MS InfoPath’ Category

How to create and use CA with InfoPath 2007

August 31, 2011

Building an Enterprise Root Certification Authority in Small and Medium Businesses:

http://technet.microsoft.com/en-us/library/cc700804.aspx

Installing and configuring a certification authority: Public Key:

http://technet.microsoft.com/en-us/library/cc756120(WS.10).aspx

Certificates How To …: Public Key:

http://technet.microsoft.com/en-us/library/cc785226(WS.10).aspx

Advertisements

How to use Infopath 2007 with Digital Certificates

August 30, 2011

About digital signatures – InfoPath – Microsoft Office Online:

http://office.microsoft.com/en-us/infopath/HP010967151033.aspx

Introduction to digital signatures – InfoPath – Microsoft Office Online:

http://office.microsoft.com/en-us/infopath/HA101574281033.aspx

Lab 4: Enabling Digital Signatures in InfoPath 2007 Form Templates:

http://msdn.microsoft.com/en-us/library/bb251748.aspx

Digitally Signing Data in InfoPath 2003:

http://msdn.microsoft.com/en-us/library/aa168019(office.11).aspx

Request a digital certificate – InfoPath – Microsoft Office Online:

http://office.microsoft.com/en-us/infopath/HP101574261033.aspx

Importing Excel data into InfoPath

November 29, 2010

There is always a need to create a InfoPath forms from Excel. Now this can be bit more trickier. Again there are be couple of different approaches:

1) Using workflow activities to copy List data to InfoPath forms: First part of this exercise is to create a SharePoint List from a Spreadsheet. Second part of the process is to generate and update the InfoPath forms in a form library. You can accomplish this by following steps:

a) You will have to prepare the form library to take data. Specifically you will have to promote all the fields in the form that needs to be updated as site columns. This has some serious performance issues.

b) Create a black InfoPath by hitting new button on the form library.

c) Download it on your local machine by choosing “Download a Copy” option in the listitem menu.

d) Make multiple copies of this form (one per record in your spreadsheet).

e) Rename and upload the forms. This is most effectively done with the “Explorer view” of form library. Other options is to use “Upload Multiple Files” from list menu or in SharePoint Designer.

f) Now Write a SPD workflow for the SharePoint list which was created by getting data from spreadsheet and coping it over to the corresponding column in the Form Library (that is the reason to expose the column). You can use “Update List Item” activity to do this.

g) Trigger the update on each row of SP list so it copies the data in the InfoPath form.

Now there can be some serious issue if you can more than 40 columns in the sheet. Limitation occurs with Form Library promoted columns. As you promote more and more columns it will take more time to publish the form template. The web service that publishes the Form Templates starts to timeout and you will not be able to publish the forms.

There is a CodePlex Activity “Set InfoPath field inner text” available to get around this issue. This activity basically allows you to copy text directly into the form.

2) I have not tested this approach but this can be every simple thing to do. I came across Qdabra’s Excel to InfoPath Migration Tool . This tool looks quit promising to me as it uses very simple approach to generate the xml per record in the Spreadsheet. Mapping also looks easy it uses one xml file to map excel sheet columns to Form fields.

InfoPath 2007 Server Upgrade and Migration Tool

February 9, 2010

Ci sono dei grossi problemi nell’ upgrade a MOSS 2010 di Form InfoPah pubblicati su MOSS 2007 .

I problemi sono legati al fatto che al termine dell’upgrade gli URL sono cambiati, e nei vari form InfoPath 2007 i percorsi sono hard-coded… e quindi generano errore.

Scaricare ed utilizzare il tool IPWSSupg.exe che consente questo genere di modifiche. Il tool è disponibile anche a 64 bit.

Domain Certificate Authority Signing InfoPath 2007 Forms

October 28, 2009

InfoPath forms with custom code and those that have their Security Level set to Full Trust must be signed so that they can be run by the client.  That’s fine but who wants to pay for a code signing certificate for internally developed applications?  If we string together a couple of facts we can quickly realize that we shouldn’t have to pay for code signing certificate if we are developing code that will only ever be used by internal users.

First, certificates work because there are a set of trusted root certificate authorities.  Their responsibility is to issue certificates.  The organizations running the trusted root certificate authorities are responsible for only issuing certificates where the certificate matches the organization requesting the certificate.  They make no judgment about whether the person is good or bad – only that they are who they say they are.  The service that you pay for when you purchase a certificate from a trusted root certificate authority is that they have verified your identity.

Microsoft Windows has a list of trusted root certificate authorities – but when a computer is in a domain, it automatically trusts the Enterprise Certificate Authority for the domain.  The Enterprise certificate authority is an instance of certificate services which comes with Windows Server operating systems.  It allows an administrator to issue certificates.  There are several templates for the kinds of certificates to be issued.  The most common one is for a web server – an SSL certificate – but there are others as well.

Certificate Services has a template for code signing certificates.  If you put everything together you realize that when all of your computers are a member of a domain you can request and get granted a code signing certificate that’s valid for anyone using the certificate in the domain.

Here’s how to do it…

Install Certificate Services

If you don’t have an Enterprise Certificate Authority in your domain, go to a server and …

1)      Click Start- Control Panel-Add/Remove Programs

2)      Click Windows Components

3)      Click the checkmark to the left of Certificate Services

4)      Click Next

5)      Follow the wizard to create an Enterprise Certificate Authority.

Note: There are special precautions for protecting enterprise certificate authorities including creating sub-authorities, and taking the certificate authority offline.  If your organization is large, you should review the risks and guidelines for creating certificate authorities and manage security appropriately.  In smaller organizations it’s generally acceptable to create an enterprise CA and issue certificates from it.

Create a Copy of the Code Signing Template

The default out of box code signing certificate doesn’t allow the certificate’s private key to be exported.  This means that only the user to which the certificate is issued can use it.  Generally you don’t want to have developers to have enough permission to request the certificate themselves.  If you want to be able to move the certificate from user to another you’ll need to make a copy of the Code Signing certificate and change it so it can have exportable keys.  We’re going to show you how to do this.  If you follow these steps choose your duplicated code signing certificate in the following steps.

1)      Click Start-Run and enter certtmpl.msc.

2)      Right click the Code Signing template and select Duplicate.

3)      Enter a name for the new Template.  For instance, add your organization name in front.

4)      Click the Request Handling tab.

5)      Click the Allow private key to be exported.

6)      Click OK.

You now have your own code signing template that can be exported.

Enable the Code Signing Template

By default the  code signing certificate template isn’t available to be issued from your certificate authority.  To do that you need to enable the template which you can do by following these steps…

1)      Click Start-Administrative Tools-Certification Authority

2)      Expand the server that you installed certificate services on

3)      Click the Certificate Templates folder.

4)      Right click the Certificate Templates folder, select New, Certificate Template to Issue.

5)      Click Code Signing and click the OK button.

Now you can issue Code Signing Certificates

Issue the Certificate

Now that everything is in place you can issue the certificate.  Follow these steps to do that…

1)      Open a web browser and navigate to http://server/certsrv where server is the name of the server which you installed certificate services.

2)      Click the Request a certificate link

3)      Click the advanced certificate request link

4)      Click the Create and submit a request to this CA link

5)      In the certificate template drop down box select Code Signing.

6)      Enter a friendly name for the certificate in the friendly name textbox at the end of the page.

7)      Click Submit.  You may be prompted that the web site is requesting a certificate, click Yes.

8)      Click the Install Certificate link. Again you may be warned that you’re getting a certificate, click Yes.

You now have a certificate in your certificates store.  If you’ve not been doing this as the developer (and you probably haven’t), you’ll need to export the certificate and import it into the developer’s account.  You’ll only be able to do this if you created your own code signing template.

Exporting the Certificate

Here’s what you need to do to export the certificate:

1)      Click Start-Run enter certmgr.msc

2)      Expand the Personal Folder

3)      Expand the Certificates folder

4)      Locate the certificate that indicates that its intended purposes is Code Signing.

5)      Right click on that item and select All Tasks-Export

6)      Click Next

7)      Click Yes, export the private key.

8)      Click Next.

9)      Click Next

10)   Enter a password and confirm password.

11)   Click Next

12)   Enter a file name for the exported file

13)   Click Next

14)   Click Finish

You’ve exported the certificate.

Importing the Certificate

If you’ve exported the certificate you can move that over to the user or machine that will be signing the code and follow these steps to import the certificate.

1)      Double click the file to start the Certificate Import Wizard.

2)      Click Next

3)      Click Next

4)      Enter the password you entered when you exported the file.

5)      Click Mark the key as exportable.

6)      Click Next

7)      Click Next

8)      Click Finish

9)      Click OK.

You’ve now imported the certificate file.

Configure InfoPath to Use the Certificate

The final step in this journey is to tell InfoPath to use the certificate.  Do that by following these steps…

1)      Open an InfoPath form in design view.

2)      Click Tools-Form Options

3)      In the category pane, click Security and Trust

4)      Click Sign this form template

5)      Click the Select Certificate button

6)      Select the certificate that you just issued.

7)      Click OK.

8)      Click OK.

OK, you’re done.  That’s all you need to do in order to get a code signing certificate that will sign InfoPath forms that the users of the organization will recognize.

Risorse essenziali per Infopath 2007

September 21, 2008

Per coloro che utilizzano professionalmente il programma Microsoft InfoPath 2007, possono trovare utile, il seguente post

http://blogs.msdn.com/wael/archive/2008/09/02/infopath-2007-essential-resources.aspx

nel quale sono riportati link a delle risorse molto interessanti sul programma Microsoft InfoPath 2007, ed il suo utilizzo con altri programmi, come per esempio Microsoft Office SharePoint Server 2007.
Il post è in lingua inglese, ma il materiale è molto valido.

Aggiornare i progetti su MS Office Project Server 2007 via InfoPath

July 2, 2008

Igor Macori segnala sul suo blog un interessante progetto pubblicato su MSDN Code Gallery (da tenere d’occhio ormai quanto il buon vecchio Codeplex), dove si offre un intelligente metodo di aggiornamento dei progetti pubblicati su Project Server 2007 (EPM 2007) attraverso dei moduli InfoPath 2007 di tipo web-enabled.

Il progetto si chiama EPM 2007 Project Updater InfoPath Form.

L’idea è più che intelligente, visto che a volte risulta macchinoso ed eccessivo andare a realizzare personalizzazioni all’interno del sito di Project Web Access, abituale ambiente per consentire l’aggiornamento dei progetti da parte dei team di progetto.

I moduli InfoPath aggiornano i progetti passando attraverso PSI (Project Server Interface).

Ecco qua il link al progetto, completo come sempre del codice sorgente.

I moduli InfoPath offrono piene funzionalità attraverso i Forms Services ?

May 31, 2008

I moduli realizzati attraverso InfoPath 2007 offrono piene funzionalità anche tramite browser, una volta pubblicati attraverso gli InfoPath Forms Services…

La risposta è NO !

In particolare ecco la lista delle funzionaltà che, se presenti su di un form InfoPath 2007, non saranno disponibili alla fruizione del modulo tramite browser.

Inoltre si parla di utilizzo attraverso il Web Browser… ma attenzione al browser:

Browser Windows* Unix/Linux Macintosh
Microsoft Internet Explorer 6.0 (32-bit) Full support icon No support icon No support icon
Windows Internet Explorer 7.0 (32-bit) Full support icon No support icon No support icon
Firefox 1.5 Full support icon Full support icon Full support icon
Mozilla 1.7 Full support icon No support icon No support icon
Netscape 7.2 No support icon Full support icon No support icon
Netscape 8.1 Full support icon No support icon No support icon
Safari 2.0 No support icon No support icon Full support icon

*Includes Windows Vista, Microsoft Windows Server 2003, Microsoft Windows XP, and Microsoft Windows 2000.

Pubblicare una form template come un messaggio e-mail

February 4, 2008

Vi segnalo un interessantissimo filmato su come pubblicare una form template come un messaggio e-mail al seguente link.

Creare parti di template riutilizzabili in InfoPath 2007

February 3, 2008

Vi segnalo un interessantissimo filmato su come creare parti di template riutilizzabili in InfoPath 2007 al seguente link.