How to print bulk document from sharepoint site - browser

How can we print bulk documents from sharepoint site through browser. We have to print the documents through browser means at client side not at server side. The printer is not in the server network. User will select multiple projects (that carries various documents) and click on print button. We have to silently print all the documents in client's printer.
Using this code we can print the document:
<link rel="Alternate" media="print" href="TextFile2.doc" />
print
But the problem with this is it will ask to click on print again and again.

Related

How can I prevent an iframe displaying an email to load images and other email trackers?

We have a web admin panel in which the agents can see conversations with customers.
Those conversations are the result of importing normal emails thru an IMAP connection. We grab the "untouched" mailbox files and we store them in a database. Then we post-process the files to index by "from", "to", "date" and so on and so forth.
Up to here, okey. We can seek all the emails involved with a client and render them at will.
Then when the agent looks for a customer in the web admin panel and opens it, the full email conversation appears. And we display the HTML version of the email within an iframe (or the text version if the html version is not there). 90% of the customers send HTML.
What happens? Upon the agent opening the email in our web, the iframe loads the "full html" and renders it. This makes "remote loading" (images, sounds, styles if so, and whatever) to be downloaded. This allows customers to "track" if we opened the email by appending tracking id's to the assets (typical http://track.example.com/image.jpg?id=123456789)
I've tried the "sandbox" attribute of the iframe html tag with no luck (it still downloads the images).
Question
How can I programmatically tell the iframe to not load ANY remote content, and just render the initial HTML without any remote call?
Mozilla's iframe documentation listing all available attributes for the is here: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe
If you look at "sandbox" there is no restriction specific to image or other includes, just restrictions on things like running JavaScript. There are no other attributes that would restrict images and includes.
To solve the problem of images and includes in your HTML you will need to filter the HTML either at the server before sending it or in the client after it arrives.
Server:
Before storing it into the database.
In the code that retrieves the HTML and returns it to the iframe.
Client:
Use AJAX to fill the iframe with the HTML, with code that filters a
response. With this approach you could also use a div instead of an
iframe if that works better for your layout.
If all of your users will use Chrome or Firefox, you could look at writing a browser extension

Disable show response document in hierarchy for browser

I have a view of lotus notes and web browser. I have enabled show response documents and both notes and web browser showing response documents. Notes are for Admin view while web browser for employee view. So I want to create Admin can view all response document on notes but the employee cannot view response document on a web browser.
Below here my view for notes.
Below here my view for a web browser.
My question is, can I disable show response document just for a web browser?
It means, my notes still showing response document but my browser will not showing response document. Thanks for any help!
You can create two views: one for Notes users (hidden for web users ) and response hierarchy disabled and vice versa one for the web users which is hidden for notes Users with response hierarchy enabled.

Enforce print-only document on the web

I need to provide printable documents without any ability (or a very minimized ability) of the user to view or download them.
I don't even have to render the document. They could just click a text link and have it blindly print to a printer.
This can be done using native applications, but it would be far better to provide this feature from a web interface.
Some points:
I can encrypt the document on the server so the HTTP GET response is garbled. The client could fetch a dynamic key from the server just before print to re-assemble the data. This would prevent snooping through a web inspector.
I could demand the use of a browser extension that sends print jobs without presenting print preview windows.
What other ways could a user get the document? What else should I be thinking with preventing?

Is there a way to have Domino show file DB path instead of replica ID for DocLinks on the web?

We are converting an application that was built in R6 to xpages. In this application, the content was created through the Notes client and viewed on the web. There are a lot of doc links in the documents. Some of the documents have readers fields and that's where theproblem arises.
When looking at a page that contains links to "secured" documents, the URL is something like:
http://servername/dbpath/db.nsf/whaterverdoclinkhere
The links that this page contains all show a URL that looks like this:
http://servername/__REPLICAID/ViewUNID/DocUNID
The problem that we have is that this seems to be considered different DBs from a securitypoint of view and even though the user is logged in when accessing the first page, he gets the login page when he clicks on a link that uses the replica ID of the database instead of its path.
Is there a way to force Domino to use the database path all the time in URLs built with doc links, not the URL with the replica ID?

How to open a document in Xpages mobile controls from an URL

How do I open a document in XPages mobile controls from a URL?
My application notifies users about pending review using an embedded URL link in an email. The requirement is to open the document in mobile controls (SinglePage/App Page). As of now I get a grey page on ipad when the link is clicked from the email.
However I am able to edit the same document using a button and <moveTo> tag. The following is a sample URL when loaded to a browser renders a grey page.
http://175.x.y.z/db.nsf/MN.xsp#newRequest&docId=123761231653&action=openDocument
The #newRequest part of the URL needs to be moved to the END of the url string. Nothing after the # symbol in a URL is transfered to the server so the server never gets the docId or action parameters.

Resources