My question is related to printing an Infopath 2010 form in Sharepoint 2010.I designed an Infopath 2010 form in Infopath Designer 2010 and published it to a form library in Sharepoint 2010.The end user fill the form and store it in .xml format in the document library.Now I would like to print the form filled by the end user?
Any Ideas or suggestion about the above scenario?Please consider both browser based forms and normal forms
Thanking you in advance.
For normal forms, you have to create a print view. It will create a Word document that can be printed from user's workstations. Here is a link how to design a view for printing:
http://office.microsoft.com/en-us/infopath-help/design-a-view-that-is-optimized-for-printing-HA010151438.aspx
Unfortunately Word print views are not supported for web-based forms. Usually the only option is to create another InfoPath view and design it for "print": all controls as labels or read only; all sections are visible, etc.
[Update]
#Surendra J: Ok. There are two things to address separately.
First of all user should be able to request "Print" operation right from SharePoint view (and I don't mean "Browser->File->Print"....) This can be implemented by using a custom ECB action. Your custom action will be associated with Forms library or even specific ContentType. It will allow SharePoint users to choose "Print Form" right from SharePoint view. These links should help:
http://www.slideshare.net/gvarosky/introduction-to-developing-custom-actions-within-sharepoint
http://www.csharpest.net/?p=95
Second issue is to make print view from XML. As you can understand InfoPath XML has to be transformed to HTML or image. Preferably it should be done by InfoPath forms library. There is no easy way to navigate to given InfoPath view without mixing rules and URL parameters. I recommend you to take a look at this article:
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/156983db-5a62-498f-a3b5-96ad7f57d15f
Disclaimer: I personally like PDF forms product from http://PdfSharepoint.com. It does not have print issues as all forms are dynamic PDFs and works with Adobe Reader. I believe it is a good alternative to InfoPath if printing is necessary.
Related
I'm relatively new to javascript. But is there a way to How to transfer values from a table in Microsoft word into a Intranet webpage Text box, preferably using something simple like notepad to code? Also, is it possible to make it such that the transfer goes on even after the webpage goes on to page 2 and page 3 etc?
I am going to take Microsoft 70-486 (MVC) exam. So i am preparing for it. Came across one most important question asking in 70-486 exam but the answer is different across web, Please help to choose the correct answer.
Question
You are designing an HTML5 website. You need to design the interface to make the content of the web page viewable in all types of browsers, including voice recognition software, screen readers, and reading pens. What should you do?
Annotate HTML5 content elements with Accessible Rich Internet
Application (ARIA) attributes.
Convert HTML5 forms to XForms.
Ensure that HTML5 content elements
have valid and descriptive names.
Use HTML5 semantic markup elements
to enhance the pages.
Use Resource Description Framework (RDF) to
describe content elements throughout the entire page.
In some website it is mentioned as AD is correct answer check this enter link description here and others mentioned ABCD is correct answer check this enter link description here. I am confused between this 2 ans.
I would say that the correct answers are :
Annotate HTML5 content elements with Accessible Rich Internet Application (ARIA) attributes : It is the primary role of the aria attributes !
Use HTML5 semantic markup elements to enhance the pages : To help the screen readers to know that an element is a nav, an article...
Ensure that HTML5 content elements have valid and descriptive names : i.e. to help the screen readers to know that an input is the "FirstName", and not just a "Text input", a better approach is to use a label for the inputs, but after reading this article, it seems that only few screen readers manage the label element.
I'm gonna correct Djoul6's answer a bit.
Ensure that HTML5 content elements have valid and descriptive names.
This is not a correct answer. the name attribute can be whatever, screen readers do not read the name attribute out loud. From the source Djoul6 refered to there was this description. http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html#namedef
name
text by which software can identify a component within Web
content to the user
Note 1: The name may be hidden and only exposed by
assistive technology, whereas a label is presented to all users. In
many (but not all) cases, the label and the name are the same.
Note 2: This is unrelated to the name attribute in HTML.
The correct answer should be
Annotate HTML5 content elements with Accessible Rich Internet Application (ARIA) attributes.
Use HTML5 semantic markup elements to enhance the pages.
So, correct answers:
Annotate HTML5 content elements with Accessible Rich Internet
Application (ARIA) attributes.
Use Resource Description Framework (RDF) to describe content elements
throughout the entire page.
Please note that the correct answer should be a complete solution for Accessible web application. HTML5 semantic markup cannot be complete solution, this only enhance the pages, also XForms cannot, and even not valid and descriptive names..
I think no question about ARIA attributes, but you can read about RDF - https://www.w3.org/TR/wai-aria/roles
For futher investigation please reffer W3C WAI-ARIA.
My understanding of HTML5 is that its semantic markup is meant to make it readable across browsers and readers. That would point to the 4th answer.
I have the need to generate a report using ActiveReports with links inserted on the text. There may be more than one link on the text, they could be anywhere, and only a specific part of the full text needs to be marked as a link. Is there a way to do this?
E.G.:
Visit my homepage or the company's web site!
I've tried with the Rich Text Control but it does not show links even if I load an html page. And the Hyperlink property of textboxes is no good because they only handle one single hyperlink and cannot mark where on the text is that link.
Any ideas will be much appreciated!
As of now the support for hyperlinks in Richtextbox is not supported in AR7. However, the feature might get added in added.
Regards,
Mohita
A web developer created our new intranet in Sharepoint 2007, none of the pages have metadata titles or descriptions (or any metadata tags) also the page has no semantic structure, divs are used instead of H1, H2, H3 etc.
He said this was a quickie out of the box creation but i'm really concerned about the quality of the page structure and the impact this will have on the effectiveness of the internal search engine.
Does a Sharepoint 2007 website come out of the box in this condition and am I right or wrong to be concerned about this?
Any advice would be appreciated as I would not accept the build of an external site like but he said "sharepoint is just like this" and I have no idea.
Many thanks
John
Edit the default master page. Add your meta tags there if the site is going to have same meta keywords and descriptions. If you want to customize the meta tags for each and every page then you will have to find the contentplaceholder ID that will hold the head section of the page and put all your meta tags there in each and every page.
I have a need to render content from another page using a content query web part. I've found several examples on how to accomplish custom fields using common-view-fields but nothing specific on how to query page content from another page.
Is this possible?
Thanks,
Eric
"Content Query Webpart" is typically used for aggregation - you have a lot of pages in your portal and you want to create a page which summarizes the headlines or some other properties that every item in your portal has.
In your scenario, as far as I understand, you have a page in your portal and you want to create another page, which displays the same content. In this case the "List form webpart" or a "data view webpart" would sound more reasonable.