Documentation

Administration Guide

The PDF Converter for SharePoint Administration Guide contains information on how to deploy the software as well as how to troubleshoot potential problems.

 
Latest release

 
Old release (7.3)

 

Case Study - EIB

While setting up proofs-of-concept for other divisions within the European Investment Bank to begin using the PDF converter for SharePoint, we caught up with Chris Alman, Technical Project Manager at EIB. It’s always fascinating to find out the specific details regarding projects our clients are involved with as we don’t necessarily discuss them in detail while they are busy evaluating our products and we’re assuring them the best product support we can offer. We knew the EIB was going “paperless” but didn’t know they were physically changing their entire office-scape! (A brief video of this case study is available here).

Muhimbi: Tell us about European Investment Bank (EIB):    

Chris:  The European Investment Bank is the European Union's long-term lending institution established in 1958 under the Treaty of Rome.  A policy-driven bank, the EIB supports the EU’s priority objectives, especially boosting sustainable growth and job creation.  It aims to provide long-term lending in order to mobilise funding from the private and public sectors.  These projects usually involve building infrastructure such as bridges or roads.  One notable project is the Channel Tunnel (aka, “The Chunnel”) connecting England to France.  We borrow money from the capital markets and then lend it out for projects within the EU, but we have also lent money for projects outside it.  Because our credit rating is Triple-A, we can borrow money at a much lesser rate than through other institutions. 

We say that the EIB is “the biggest bank in the world that you’ve never heard of.”  While the World Bank will lend about 30 Billion dollarsi annually, we’ll lend 60 Billion eurosii.  It’s not a proper financial way of comparing banks but you get the idea of our size.  Another part of the bank is the European Investment Fund that will do venture capital.  For instance the funding for Skype came from the EIF as did the funding for Rovio, if you’re familiar with “Angry Birds”

Muhimbi: How did Muhimbi’s PDF Converter for SharePoint make its way into EIB?

Chris: About two years ago the EIB decided it wanted to under-go a massive cultural shift, that ended up also including great physical changes to the EIB headquarters such as a new atrium for socializing, the removal of phone consoles from desktops, hot desking, a multi-million dollar teleconference room, etc.  In a nut-shell the aim of the shift was to greatly increase the ability for employees to work remotely and be more “green.” 

Previous to this, the physical lay-out of the EIB offices was similar to those of many corporations; everyone had their own cubicle and the environment felt very insular.  The EIB wanted to create an environment and culture more similar to what you see at Google or Microsoft.

One of the first steps in this process was to go as paperless as possible, exchanging manual processes for electronic processes (thus making for a more “green” way of working and easier for remote solutions, per EIB’s objectives).  From this realization, a 9 month exploration and analysis phase lead to adopting SharePoint wherein Nintex Workflows would also be utilized.  The adoption of Muhimbi’s PDF Converter for SharePoint came not long after in realizing we wanted to convert different document types to PDF.

Muhimbi: What sorts of processes were you attempting to make electronic?

Chris: “Signature work-flow.”  Naturally in our industry documents need to be signed all the time for different reasons.  The producer of these documents is generally not the person that needs to sign them so these documents would be created usually in Word or Excel documents, printed, taken to the person for approval (signature), signed, and then needed to be scanned and archived.  It was quite a long process. 

Furthermore, in the bank’s archiving system, there’s a lot of meta-data to fill in: the name of the document, the date, etc. When this process was manual, one had to fill out an entirely separate form than the document with this meta-data.  In addition to documents, one had to print these meta-data forms, and send to scanning team to be scanned along with documents as well.  The manual process was very manual.  It was very laborious to go through each step.

Muhimbi: What made you choose Muhimbi's PDF Converter for SharePoint? 

Chris: We heard through the Nintex community online that Muhimbi’s PDF Converter for SharePoint integrates very well with Nintex Workflows so it seemed automatic to start using it.  Furthermore, our experiences with Muhimbi’s support were very good so it was an easy choice. 

Muhimbi: How do you use the tool?  

Chris: After installing SharePoint, we replaced the manual processes with Nintex Workflow.  Documents could be created then electronically transmitted for approval, and upon signature, approved for PDF conversion.  On the topic of meta-data we can now simply type the meta-data, send through Nintex Workflow and onto Muhimbi, where it all transfers when being archived.  It’s all much more convenient and efficient this way. 

This method has been tested with a small team of 16 people and since December of 2011 the team has produced 150 documents.  These documents are roughly 5-10 pages each and may combine different document types such as Word, Excel, other PDF’s, emails, etc. as well as be written in different languages.  The languages in play on documents around here aren’t limited to just the most popular of the EU (English, French, German).  It’s common to have annexes in any of the 27 languages of the EU.

We then use the merge feature within Muhimbi’s PDF Converter for SharePoint to decide on the order we’d like, and then convert ultimately to a PDF.  The ability to set the order in which you want the different contributing documents to appear in the PDF is extremely valuable to us as is creating a single PDF from all these documents.

Muhimbi: What sort of results have you seen?

Chris: Because the PDF Converter has worked so well and Muhimbi’s support has been wonderful, this test has been labelled a big success and the other departments such as, the archiving system and the EAI team (Enterprise Architecture Integration) will also begin using the PDF Converter for SharePoint.  We are working on the proofs of concepts for those departments as we speak. 

Muhimbi: Have you noticed any cultural or workflow changes since installing Muhimbi’s tool? 

Chris: In addition to quite a few hours of administration saved monthly, there is much more visibility to the status of different documents.  One can just log in and view a dashboard, so there is significant value in that.  In addition, having a converted PDF is much better than a scanned document, as was previously the practice.  

Muhimbi: When did you start using Muhimbi tools? 

Chris: We started using Muhimbi’s PDF Converter for SharePoint in March or April of 2011.  We started looking for a tool, found Muhimbi’s as mentioned, and it was a very easy software package to install and use. It did everything that we needed it to do.

We actually had to use the trial version for a good 5 months because our purchase process is pretty complicated, so it was great that it doesn’t expire- we got to continue working with the tool and learning it better during that period of time we were waiting to have the purchase approved.

Muhimbi: What is it about your business that makes Muhimbi’s PDF Converter for SharePoint important for you? 

Chris: There have been moments in this process where if we weren’t going to be able to convert a document to PDF or if the PDF Converter for SharePoint’s functionality wouldn’t work with EIB’s requirement, the whole project wouldn’t work so we’ve relied on it pretty heavily.  The product, with occasional clarification from Muhimbi’s support has delivered and made this project a reality. 

Muhimbi: Would you recommend PDF Converter for SharePoint to other SharePoint users?

Chris: Yes, and I’d recommend anyone using Nintex use Muhimbi’s PDF Converter for SharePoint.  The product is excellent as is the support service.  Also, Muhimbi’s blog with its scenarios/use cases is extremely useful.  I’ve sat in meetings and been able to say “hey, we can do that!” having seen the examples in the blog. 

i http://siteresources.worldbank.org/EXTABOUTUS/Resources/29707-1280852909811/IBRD_Jun_11.pdf

iihttp://www.eib.org/infocentre/publications/all/financial-report-2011.htm

Case Study - itgroove

Back in early 2012 we knew from our conversations with itgroove, a Microsoft consultancy specializing in SharePoint, that our PDF Converter for SharePoint was going to play an integral role in the major project they conducted for their client, BC Ferries.  In June we were incredibly pleased to see this project become nominated for the first annual Nintex awards!

Since the nomination, we recently sat down for a chat with Sean Wallbridge, owner of itgroove, and Keith Tuomi, SharePoint consultant, to find out more about the project, how the PDF Converter for SharePoint played a role, and their thoughts on working with the PDF Converter for SharePoint in general.

A PDF Version of this case study is available here.

Muhimbi: Well for starters, major congratulations on being nominated for the Nintex awards.  How did that come up?  

Sean: Thank you, this is the first year for the award, we’ve been a Nintex partner for about 2 years now.   Our Nintex rep suggested that we should submit for the awards since the project was fairly interesting and high profile, at least for our region.  The client, BC Ferries is a pretty big outfit in British Columbia.  We don’t know if we’ll win, but hopefully! We were pretty happy to be nominated. 

Muhimbi: Thanks for including us prominently in the submission as part of “the recipe.”

Sean: Well sure, it was worth while doing and Muhimbi was a big part of it. 

Muhimbi: Can you tell us a bit about yourselves, itgroove and the client, BC Ferries?

Sean: We started out as Microsoft consulting company but I’ve been involved in SharePoint since the first digital dashboards in Outlook ’98, but nobody was on board with that (SharePoint) back then.  With SharePoint itself becoming more prominent, we (daily) now show businesses how to get more out of it.  I think SharePoint consultants are a new breed: we’re part business analyst, part developer, part ITPro, part Project Manager, part political activist, part trainer, and part Dion Warwick psychic network (laughs).  With a platform like SharePoint, there never stops being *something* to work on.  We don’t normally go looking for big clients like a BC Ferries, but the demand for SharePoint expertise is definitely on the rise. Currently we’re a team of 8 with around 90 clients total, 24 of which we work with on a daily basis with SharePoint. 

Editor's Note: BC Ferries (BCF) is one of the largest ferry operators in the world, providing year-round vehicle and passenger service on 25 routes to 47 terminals, with a fleet of 35 vessels. BC Ferries is headquartered in Victoria, BC Canada and has operations over the length and breadth of the BC coast. To see more details regarding the project, read the Nintex awards submission here and the Nintex case study here

Muhimbi: As one can see from the awards submission, BC Ferries had actually purchased our PDF Converter for SharePoint previous to your coming on board for the project.  Were there any particular notes provided by BC Ferry staff as to why they had decided to purchase Muhimbi’s PDF Converter for SharePoint? 

Sean: Essentially because the main objective of the project was to assemble PDF’s from the huge number of files previously distributed, Muhimbi seemed the clear choice.  I actually knew of Muhimbi previous to this project for that same reason.  Nintex does have some basic PDF assembly, but it didn’t provide the capabilities we needed. We needed far more than that. 

Keith: If I can jump in, the project started out working with native SharePoint workflows and the complexity of what needed to be accomplished was so astronomical compared to what you can do with native SharePoint workflows. Initially they were converting basic file types to PDF but couldn’t do much else. That’s where Nintex and Muhimbi came in.  Watermarking in particular was a needed feature.

Muhimbi: When it comes to getting new tools up and running in a project, there’s always a chance it’ll take a moment to get everything working. You guys ending up needing to exchange a few messages with Muhimbi’s support, how would you rate that experience?  

Sean: It was almost scary how fast it was.  We are aware that Muhimbi’s response time is officially 24 hours, but most of the time we received a reply within minutes, which is pretty unheard of in the software industry we are used to. 

Muhimbi: What was your initial impression of the tool?

Keith: The Installation was well-documented- clear and straight forward.  Licensing and activation was painless.  Integration with Nintex, which is our big focus as a firm was also pretty straightforward.  The product is better documented than a lot of similar (ISV) software products out there. 

Muhimbi: How did you feel about its performance? 

KEITH: It definitely does the job it claims to.

Sean: It makes the complex simple.  There’s a lot it’s capable of doing and as SharePoint vendors, we can definitely appreciate all the options it provides its users in terms of functionality.    

Muhimbi: Was there anything pleasantly surprising about using the tool? 

Keith: I guess that it has that much functionality.  I was not expecting it to work with all the different file types, or watermark. The functionality is well above the name or description. I thought it was just going to be a solid tool for PDF Conversion but there’s a lot more happening, like Sean said.

Sean: Yeah, I could see it being an under-appreciated tool, because a lot of people aren’t going to look under the hood and see all that it’s doing.  It’s the quiet hero that plays a big role in projects similar to ours.

Muhimbi: The Nintex awards submission goes into great details as to what you guys did and the role of the PDF Converter for SharePoint in the project, but can you summarize the use of Muhimbi’s PDF for Converter in the BC Ferry project? 

Sean: 20,000 paper files have been condensed into 90 unique PDFs that can easily be electronically transmitted, updated, etc. and Muhimbi’s tool is the one converting them.  They’re going to add even more files now as well because this process has worked out so well. It’s very green, it means improved safety and will save a lot of money. 

Keith: They’re also using Html to PDF for the change log when changes in the brochure/documents occurs. Again, using the product for more than just SharePoint to PDF.    

Muhimbi: On the client side, have you noticed changes in workflow and culture since deploying Muhimbi?

Sean: In a nutshell, the project has showed BC Ferries how much more than can be done with SharePoint and folks are excited about it.  Again, it’s played an integral role in a project that’s green, has saved BC Ferries money, administrative head-ache, and increased the quality of information exchange. 

Muhimbi: Would you recommend PDF Converter for SharePoint to other SharePoint users?

Sean: Yeah, if it’s a fit for the client or project, then definitely we would.  The topic of PDF hasn’t come up a lot in our line of work but we suspect that will increase and with some of the new features rolling out on the Muhimbi product, there will likely be other reasons to consider it for a project.  A lot of companies are just starting to realize the power of SharePoint in the document management space, so the future looks bright.

Case Study - Process Fusion

June 2012: We were extremely pleased to hear that not only was the implementation of the PDF Converter for SharePoint a huge success in Process Fusion’s client project, but that they would then be recommending it to their client base with a write-up in their July 2012 newsletter. We recently spoke with Brooke Martin, SharePoint Practice Lead to prep for this newsletter and thought we’d re-cap the details of this very successful project.

Muhimbi: Tell us about Process Fusion.

Brooke: Process Fusion Inc. is a Microsoft gold and managed solution partner specialized in Transactional Document Management. We are a technology and thought leader in the advancement of the Enterprise Content Management (ECM) capabilities of Windows SharePoint Services and Microsoft Office SharePoint Server. Our goal is to reduce, and ultimately eliminate the inefficiency and errors associated with manual document handling.

We have over 200 active clients across the country in a wide variety of industries ranging from some of the largest financial institutions in Canada to very small non-profit organizations. As of now we have a team of 25. I’ve been with Process Fusion for 2 years and am the SharePoint Practice lead. My background is document management.

Muhimbi: Can you tell me a little bit about the client project that brought Muhimbi’s PDF Converter into the mix?

Brooke: Our client was a major regional hospital in Central Ontario with a 137 beds. The hospital administrative department had document “troubles”, to put it lightly. They had a collaborative problem and would send multiple versions of policy documents to different stakeholders, collaborated, then tried to re-create document with changes. This was pertaining to over 600 policies that need to be reviewed annually or bi-annually. All told there were over 600+ forms and with 7-10 contributors per policy, and their varying versions in play, it’s quite a bit of document management. Naturally, these policy documents were also a central aspect of running a hospital.

This process was hugely inefficient. It was a very big burden on the policy or procedure holder/owner. A lot of times they would end up being late on delivering critical document to staff that were responsible for utilizing them, especially like those involved in first hand patient care. Time is of the essence and hospitals tend to not have huge administrative staffs.

In a nutshell, we built an on-line collaborative tool with SharePoint and Microsoft Office on the hospital’s intranet where owners of the documents can publish the documents for the different stakeholders and those stakeholders can go online and edit that document once the edits are done the workflow status can be changed to publish and that’s when and then kicks off and converts to PDF.

Muhimbi: How did Muhimbi’s PDF Converter for SharePoint make its way into the project?

Brooke: When we went through our discovery process and ultimately decided this was all going to be taking place on the hospital’s intranet we realized we needed a tool that could convert different document types to PDF and work with Nintex work-flows. Specifically pertaining to Muhimbi, first and foremost, it was the top recommendation from Nintex and we also saw quite a few recommendations from other Nintex users on forums and such. For the sake of due diligence we did look at a few options but the price for Muhimbi’s tool was incredibly reasonable for the functionality if offers. In the competitive landscape it’s very different from others.

In previous cases we’ve actually created our own PDF conversion tool for a client but with the different document types Muhimbi’s tool can convert such as excel or images, Muhimbi’s tool is much more involved and a better fit for this project.

Muhimbi: Were there any specific features about the PDF Converter for SharePoint that lead to your adopting it?

Brooke: Integration with Nintex Workflow was a must. From there the ability to convert different document types was also very important. Finally, the actual experience of doing the trial of Muhimbi’s software and working with Muhimbi staff was a major reason for recommending the tool. In those regards I’d say there are 2 key elements for us that were really relevant:

  • Fast communication- we were in a rush to demo it as we were on a short timeline. Muhimbi staff responded to us very quickly when we had questions. Some of Muhimbi’s competition took 3 weeks to get a hold of someone.
  • Ease of use from a development perspective- our developers started the trial very quickly and easily and that was a huge benefit to us. The topic of “Bench time” on a project is a big concern; spending hours learning a tool or training can be a hindrance toward selecting a given tool.

That both of these elements really worked in our favor in terms of evaluating Muhimbi’s PDF Converter was a big bonus for us and made it an easy choice.

Muhimbi: What benefits does the outcome of this project ensure for end-users (the administrative staff of the hospital)?

Brooke: It’s a huge times-saver. They’re going to be able to get this part of their job done, which is only one of many, that much faster. In the past there were a lot of technical challenges around the issue of when and these documents were published that these staff members will no longer have to worry about now that Nintex Workflows and Muhimbi PDF Converter for SharePoint will do all of that for them behind the scenes and seamlessly.

As I mentioned most hospitals are pretty light on administrative staff but there’s a huge amount of administration to be done, meaning the small staff has a lot on their plate. Reducing this burden on them means less stress for them (it’s already a high stress environment), they can do other things, and as you can imagine lends to benefits hospital-wide.

Muhimbi: What have you done with the tool on this project?

Brooke: After going through the discovery process of seeing how the hospital’s administration collaborated on documents, we took a look at how SharePoint allows for such collaboration. In trying to stay within the SharePoint framework, we realized that the check-in, check-out would not be an option here. It’s a nice feature for the average SharePoint user but it can be quite cumbersome. In addition to the fact that there could be 7-10 contributors, the requirement was for everyone to be able to sign in and work on the document at the same time. So we have the ability to allow everyone to work simultaneously on a word document by highlighting a certain paragraph they’re working on, making this more like an interactive online tool. From there the owner changes the meta-data guiding the document along the different statuses: initiation is stage one, stage two when it’s in review, stage three is the final, and then stage 4 is converted to PDF and published.

There are two main document types in which we’re using Muhimbi’s PDF Converter for SharePoint. One is “Policies and procedures workflows” moving the policies through the varying stages of collaboration and the second one is that we’re building a contract management similar to the word document: it’s open, edited, and collaborated upon. There aren’t as many users compared to Policies and Procedures but go through the specific stages and then get converted to PDF to be signed.

Muhimbi: Are people using it ways you hadn’t expected?

Brooke: We didn’t expect that the process could be automated. Our original thought was that it was more of a manual selection; we’d convert the editing collaboration process then hospital staff would have to manually convert to PDF, but with the integration with Nintex it’s more automated at the last stages. That’s a big bonus for us and users.

The whole process is behind the scenes for the client so they just change the stages of the workflow. It’s a huge value to them that they just click once and the Muhimbi tool does the rest from there. It’s almost unfortunate for Muhimbi, their tool makes things so convenient one might not even know or be able to appreciate how much is being done behind the scenes. Of course, that’s a quality of a good work-flow; the user gets to enjoy simplicity and efficiency without having to know all that’s being done to make that possible for him. Again, that’s a huge value for the customer.

Muhimbi: To re-cap, what is it about this process that is so important to the client?

Brooke: In working with their policies and procedures documents, there are over 600 policies that need to be reviewed annually or bi-annually. All told there were over 1000 forms and with 7-10 contributors per policy, and their varying versions in play, it’s quite a bit of document management to streamline and these documents are highly critical to the hospital’s operation.

Muhimbi: Do you have advice for others considering Muhimbi?

Brooke: If you’re already familiar with Muhimbi and are considering recommending their tool or using it yourself, I can just say that ease of doing business with Muhimbi as well as ease of use of their software is paramount if you’re an integrator or a consultant. From start to finish we were about a week between downloading the trial, asking questions, and ultimately making our recommendations to the client. It’s just amazing we were able to do that. There’s just not enough time in the day to evaluate new tools and the experience working with Muhimbi was a huge value to us. Finally, the product works; it does exactly what it says it will and those are all fabulous attributes to have.

Muhimbi: Thank you very much. Would you recommend PDF Converter for SharePoint to other SharePoint users?

Brooke: Yes, definitely. 100%. We plan on recommending it to our entire customer base and are going to do a write-up in our next newsletter that will be out next month (July 2012).

Case Study - SharePoint Gurus

Between itgroove’s nomination, and the victories of Provoke and SharePoint Gurus, we are ecstatic that our PDF Converter for SharePoint was so heavily represented in projects at the first annual Nintex Partner Awards this year! After hearing the winning announcement we caught up with Ivan Wilson, founder of SharePoint Gurus, to hear more about the massive project his team worked on with their client Hansen Yuncken, entitled the HYway Project.

(For a nice overview of the business (less technical) end of the HYway project we’d strongly recommend you read Bill Dawes’ article in Image and Data Manager, "Constructing a digital future with SharePoint at Hansen Yuncken")

Muhimbi: Tell us about SharePoint Gurus and your client, Hansen Yuncken.  

Ivan: We started back in 2007 and obviously from the name we’re focused on SharePoint.  I personally was a SharePoint MVP for 5 years.  We’ve been working with a number of medium-sized organizations in Australia and are now a team of 6 people.  We mostly work with clients on business management processes and helping organizations get the best out of their SharePoint environment. 

At any given time we work with about 5 clients monthly.

Hansen Yuncken is the largest privately-held construction company in Australia.  With over 800 employees Hansen Yuncken has offices all over the country and over $1.2B (AUD) in revenue annually.

Muhimbi: Tell us a little bit about the HYway Project:

Ivan: In 2010 Hansen Yuncken worked on huge project with the Australian government- the Building the Education Revolution Stimulus Package- that involved managing over 200 project sites and serving as liaison between the state education department, the project sites, as well as a myriad of other professionals such as architects, engineers, and suppliers.  This project proved to be a big success wherein Hansen Yuncken created some pretty innovative solutions involving real-time communication and project management.  Some of the techniques they developed in the project really inspired them to improve their own business processes. 

To provide a bit of background as to what internal business processes looked like internally at Hansen Yuncken previous to this, there’s no better description than from Bill Dawes’ article about the project in Image & Data Manager:

"Like any company that has evolved its operational systems over many years, Hansen Yuncken had staff in different regions using disconnected applications including spreadsheets to prepare tenders, track construction progress and monitor performance.  Consistency and accuracy of the information becomes a constant challenge in this environment, and there is lot of effort required to correlate the results each reporting cycle."

Their initial research phase lead them to adopt SharePoint and then bring in our expertise in terms of implementation.  We coordinated with Scalable Solutions whom already worked with Hansen Yuncken and was familiar with their systems and way of operating.

Muhimbi: How did Muhimbi's PDF Converter for Sharepoint make its way into the project?

Ivan: As you may have seen in the IDM article, one objective was to work with existing programs and systems as much as possible and that being said, InfoPath was a key part of the work.  We wanted to automate business processes and gather information by way of team members filling out electronic forms.  The challenge then was to be able to show what a particular form looked like at particular point in the process, particularly during "sign-off".  

We wanted to be able to capture exactly what a form looked like the moment someone approved it, because documents tend to change quite a bit as they move along the process; the construction industry is a dynamic one and there was a lot of dynamic information in differing versions of these forms.  In that we thought of converting to PDF and a quick search of available tools indicated Muhimbi’s PDF Converter had exactly what we were looking for.

The fact that we could render the forms into PDF at the same moment they launched the document with Muhimbi’s PDF Converter was the key driver.

Muhimbi: Were there any specific features about the PDF Converter for SharePoint that lead to your adopting it? 

Ivan: We chose Muhimbi’s PDF Converter because it rendered a very faithful PDF of what had previously appeared on the screen. 

Furthermore, while InfoPath was a key-driver in this project, we were already working with Nintex as well and the easy-integration was very attractive to us.

Muhimbi: How do you use PDF Converter for SharePoint?  

Ivan: As the forms go through the various signoffs we generate PDF "snapshots".  The SharePoint user interface we created allows a person to select an InfoPath form and see a list of the snapshots that were created over it's in a way that they can click through the history of that form and see a timeline perspective.  One can view multiple PDF versions of the "same" document and see the information as it's changed over time.

Muhimbi: What was it about the project that you think won you guys the Nintex award? 

Ivan: It's tough to say exactly but we think it might be that we were working across a large number of SharePoint sites.  "Templatizing" the workflow functionality and making sure we had a workspace for every project and when a workspace kicks off it needs to have the same workflows as every other project.  For example, when the workflow to create a PDF snapshot runs, it should store the PDF in the current project’s workspace, but we still want to be able to make global changes workflows without having to modify hundreds of workflow definitions.  We worked with Nintex and made sure that changes to functionality are easy to roll out to the existing workspaces. 

Muhimbi: How has this project improved or change the way the Hansen Yuncken team works? 

Ivan: It benefits on multiple levels: for the project manager it means they’re guided through the process a lot better than they were in the past with paper-based forms.  They don’t have to re-key information they were already provided because such information is now centrally stored.  Furthermore, as there were several offices doing similar tasks differently in the past, centrally located information has led to better consistency of information that’s been gathered across the organization. 

On the board/upper management level it's now easier to aggregate information across the organization.  Upper management now has its finger more on the pulse.  Once that information is submitted it’s available, whereas in the past there was a lag time of weeks before they could receive such updates.

From an audit trail perspective, with use of Muhimbi's PDF Converer for Sharepoint, it's much more visible.  Anyone can log in and can see a form, the history of changes it’s undergone, as well as the contributors, and the specific things they added to the document.  For instance, if there’s any sort of discrepancy between what one claims they approved and the document at the moment this claim is made, Hansen Yuncken now has the ability to go back and check the document at the exact moment it was approved.  There’s no ambiguity between what people have agreed to at any point in time.

Muhimbi:  Have you noticed changes in culture since deploying the Muhimbi PDF Converter? 

Ivan: There's a quote in the IDM article that's direct from Hansen Yuncken's CEO, that answers this question perfectly: 

“The cultural change across the company is immense with the requirement for staff to stop submitting paper or maintaining local spreadsheets but instead enter everything via web-based forms.  The pleasing aspect is that this project is changing behaviour in the organisation and goals are being achieved.  The HYway project is continuing to add value to the way Hansen Yuncken manage their business.”- Joe Barr

Muhimbi: What is it about your business that makes Muhimbi's PDF Converter for SharePoint important for you?

Ivan: The HYway project was a pro-active move that stems from Hansen Yuncken's desire to constantly be improving, taking advantage of technology to ensure the organization is in a good position for the future.  This wasn't a "me too" project to keep up with others, it puts them ahead of the pack…and Muhimbi's tool has played an important role in that.  

Muhimbi: Do you have advice for others considering the Muhimbi PDF Converter?

Ivan: One thing we’ve always been really impressed with is the quality of the support.  There's a palpable desire to help.  It's not automated.  A person speaks to you and follows through.  That doesn't happen with every vendor we work with.

Muhimbi: Would you recommend PDF Converter for SharePoint to other SharePoint users?

Ivan: Yes I certainly would.

Case Study - Xylos

In discussing the release of version 6.0 of the PDF Converter for SharePoint with long-time client Steven Moens at Xylos, we also talked about our history of working together, a partnership that started when Xylos recommended the PDF Converter for SharePoint for their end-client, Umicore. (A brief video of this case study is available here).

Muhimbi: Tell us about Xylos, your client, Umicore, and what you do.    

Steven: Xylos is an ICT service company.   We have three main business units specializing in systems integration, systems management, and business solutions focused on increasing the productivity of end users.  We’re headquartered in Antwerp, Belgium with offices in Brussels and Moscow.  Our firm has around 180 employees. Our SharePoint consulting team is about 15-20 members.  

Umicore, our client, is a global materials technology group.  It focuses on application areas where its expertise in materials science, chemistry and metallurgy makes a real difference.  Umicore has over 14,000 employees total and has business units all over the world.  Because of this, they have SharePoint farms in Europe, Brazil, North America, Asia, and South Africa.  Umicore uses both SharePoint 2007 and 2010 and the corresponding workflows from Nintex.  I have worked with Umicore exclusively for 3 and a half years now on their SharePoint implementations.  For many of those implementations we now use Muhimbi’s PDF Converter for SharePoint.

At Xylos, I believe we have a pretty clear view of how to work on SharePoint projects.  Our philosophy is that we first work with the out of the box functionality of SharePoint, train end users, and get them used to working with it.  If there is a client requirement for which the out of the box features of SharePoint aren’t sufficient, we look for 3rd party tools that will meet the requirement.  If there are no 3rd party tools that have functionality to meet the requirement, we’ll build one.

Muhimbi: How did Muhimbi’s PDF Converter for SharePoint make its way into the project?

Steven: Xylos came in initially to train the Umicore team in SharePoint’s out of the box functionality.  The second step of our methodology is how we came to use Muhimbi’s PDF Converter for SharePoint: we used it for the first time with Umicore because we needed the functionality it provides for an application we were building. This initial application involved InfoPath and Nintex workflows where at the end, the document needed to be converted to PDF.

Out of several tools we evaluated, we recommended Muhimbi because of ease of installation, ease of user adoption, and low cost. In addition, our contact with Muhimbi staff made it an easy decision to make; the response was always quick and the information was very high quality.

Muhimbi: So this was your first time working with a Muhimbi tool?

Steven: Yes.   We had such a great experience with the tool, every new SharePoint application at Umicore uses the PDF Converter for SharePoint and we’ve recommended and implemented Muhimbi’s PDF Converter for SharePoint at other Xylos clients, such as Terminal Investment Limited and KBC Securities.

Muhimbi: When was this?

Steven: About two and a half years ago.   We started the trial in November of 2009 and purchased in December 2009.

Muhimbi: We’ve updated and released several versions since over the past two and a half years.  Do you keep up to date on the versions and utilize new features?

Steven: Yes, every version has something new and useful for us.  We’re excited to update to version 6.0 as it enables conversion from InfoPath to Word and this is something we’d like to take advantage of.  We have on occasion put in feature requests and Muhimbi seems to respond within the next release or so, which is great.

Muhimbi: We try to make sure the tool evolves with users’ desired functionality.  It’s great to hear your use of the PDF Converter for SharePoint has evolved with the tool as well.  What is it about Umicore that makes Muhimbi’s PDF Converter for SharePoint important for you?

Steven:At natural mile-markers managers need to approve InfoPath forms before the team can continue work on a project, but Umicore is a global business with management all over the world.  Before Muhimbi’s solution was installed, the approving managers needed to be physically in the office or return to the office to approve documents.

With Muhimbi’s PDF Converter for SharePoint's capability to convert InfoPath forms into secure PDFs, we can send secure PDFs via email (a Nintex capability) to manager’s mobile devices for approval.  This is incredibly convenient and increases efficiency and productivity by a magnitude.  A lot of approvals now happen in real time when previously this would have been impossible.

Since the initial group within Umicore started using the PDF Converter for SharePoint over 2 years ago, many others began using it as well because it has been so useful.  Now, over 70% of SharePoint applications within Umicore use the PDF Converter for SharePoint.

Muhimbi: Do you have advice for others considering Muhimbi?

Steven: If you have a question, don’t feel it is hopeless to ask support as it is with many ISV’s.  You will receive a good response quickly from Muhimbi.

Muhimbi: Would you recommend PDF Converter for SharePoint to other SharePoint users?

Steven: Absolutely, as I’ve previously mentioned, we’ve already recommended and installed Muhimbi’s PDF Converter for SharePoint for several Xylos clients and more and more groups within Umicore have started using the tool since we started using it.

Case Study - Nviron

As you may have already read in our blog post, Converting Formotus mobile forms to PDF using the PDF converter for SharePoint, Formotus is one of the third party products Microsoft's InfoPath team recommend as a replacement, in light of InfoPath’s formal retirement back in 2014. As converting InfoPath forms to PDF via our PDF Converter for SharePoint (either on-premise or online) has always been a popular use case, converting Formotus forms to PDF using our software is also becoming increasingly popular.

The following case study is with our consulting partner, Nviron, who is already seeing success introducing the combination of Formotus and our PDF Converter for SharePoint to their clients in SharePoint projects. In this case, we’ll be focusing on their projects with Havmain, a building services contractor firm in the south of England, and Semperian, a PPP (public–private partnership) investment firm based in London.

In April 2016 we spoke with Howard Kelly, SharePoint Specialist at Nviron, about these successful projects.

Muhimbi: Hi Howard, thanks for taking some time to chat with us today. Can you tell us a bit about Nviron and your clients, Havmain and Semperian?     

HOWARD: At Nviron we create end-to-end solutions in SharePoint, most often building our solutions with integrations from available best-of-breed tools. You could say this is in contrast to some of our competitors that try to code solutions end-to-end in SharePoint. While available tools indeed cost money, generally coding the functionality that an existing tool provides, in our opinion, is an attempt at running up the hours and bill on a project. We especially like to purchase products from companies that have well-supported products / great support teams so we leave our clients in very capable hands once our labor/project is concluded. Muhimbi is one of those tool companies with a well-supported tool / great support team. 

Muhimbi: Can you tell me about the challenges your clients were facing that lead to you working with them (and recommending Formotus and Mumimbi’s PDF Converter for SharePoint)? 

HOWARD: Both Havmain and Semperian have in common that a number of their team members are out in the field, so to speak, capturing different forms of data for reports, estimates, and approvals. They both already had SharePoint installed when we started working with them, and their pain-point was very much the same; that uploading the Word docs, Excel spreadsheets, photographs, sometimes even hand-written notes into SharePoint to consolidate and complete their necessary reports was time-consuming, laborious, and error-prone by virtue of being time-consuming and laborious. A Semperian teammate, for instance, might have 100 photos on his/her phone from projects they needed to manually move from their phone, into SharePoint via the laptop they also had out in the field, and then link individual photos to related Word Docs or Excel sheets, iteratively. Havmain teammates run performance tests on boilers or other pieces of equipment via iPad, report findings, along with schedules of maintenance, etc. When you’re dealing with aspects of construction and building maintenance, mistakes or accidents can be lethal, if not very expensive to fix, so capturing and maintaining data like service requests and reports is critical.  After collecting the data in the field, the employee understandably wanted to move on to their next appointment, not spend another hour (or more) on digital paperwork.  

Muhimbi: Presumably, this is where Formotus comes in? 

HOWARD: Absolutely.  Going back to my comment regarding the preference for best-of-breed tools as preference when available, Formotus also fits in this category and has become the field tool du jour.  Team members at both companies now use Formotus / InfoPath via iPads / tablets. Formotus is not just like having a triplicate book in the field, except digitally, it can also serve as task management.  If there is a missing field or error in a form someone is filling out, a notification or message will be sent in real-time.  Using Formotus as a standard, unified form and method for capturing data on iPad or tablet has greatly reduced the stress and errors of creating these reports.  

The Formotus forms are the raw versions of what these reports will eventually become in these projects.  We’ve introduced a new workflow where - after a form is filled out - the system converts the Formotus form / InfoPath views to PDF using Muhimbi’s PDF Converter for SharePoint. 

Muhimbi: How did Muhimbi’s PDF Converter for SharePoint make its way into this project?  

HOWARD: We’ve recommended Muhimbi’s PDF Converter for SharePoint in the past so we are well-familiar with it and thus, it was top of mind.  Some of the specific features that have been useful for this project have been the ability to email the converted pdf (even though we prefer to send SharePoint URLs, it’s still an important feature to have), and advanced features like splitting, merging and watermarking. We watermark almost every converted Formotus form and for varying reasons have merged a few together before converting. One can merge all the related forms thematically; all the forms from the same city or project type, etc. 

Muhimbi: Why convert to PDF at all though? Why not just introduce Formotus forms and use them?

HOWARD: Formotus forms are incredibly versatile and useful in the data capturing phase as a template, but we believe a final document needs to be in PDF format.  It’s the most-secure and most-trusted document type, especially for folks out in the field.  Because of the aforementioned features, we wanted to add Muhimbi’s functionality to the “last mile” of this new workflow.  

Muhimbi: To re-cap, what benefits do end-users get out of this new workflow involving Formotus and our PDF Converter for SharePoint?

HOWARD: The team members out in the field mainly benefit from Formotus;  using it as a standard method of capturing data on an iPad or tablet is far less time-consuming,  stressful, or error-prone than the previous “every man for himself” method of capturing data however one prefers and later having to compile said data into a standard form.  Fewer errors on important reports and fewer stressed-out employees also benefit the organization as a whole as well. Management, and the organization at large, benefits from having those forms (in some cases merged together), water-marked, and ultimately converted to PDFs via the Muhimbi PDF Converter for SharePoint.  Having secure, stable records is important to an enterprise in myriad of ways, although I’m sure everyone certainly knows that!  

Muhimbi: Final question- would you recommend the combination of Formotus and Muhimbi’s PDF Converter for SharePoint again? 

HOWARD: Right now we are literally in the midst of a project where we’ve already recommended both, and I’m sure there will be more projects in the future in which we’ll recommend both again!  

Muhimbi: Thanks Howard!

 

User Guide

The PDF Converter for SharePoint User Guide contains information on how to use the software on a day to day basis.
 

Code Samples

Release Notes

Listed below are the release notes for the various PDF Converter versions. If you have identified an issue that is not listed here then please check out the FAQ, Support Area or contact us directly.

Release notes are available for the following public releases:


PDF Converter for SharePoint v8.3
 

Read the announcement to see what is new in this version. An overview of breaking changes / points of caution when upgrading from a previous version can be found in this Knowledge Base article.

Known issues of this version are as follows:
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v8.2
 

Read the announcement to see what is new in 8.2. Known issues of these versions are as follows.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v8.1
 

Read the announcement to see what is new in 8.1. Known issues of these versions are as follows.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v8.0
 

Read the announcement to see what is new in 8.0. Known issues of these versions are as follows.
 

#2461 - Office 2016 is not recognised by installer

The installer carries out a number of checks to verify that MS-Office has been deployed on the server running the Conversion Service. At this moment the installer recognises Office 2007-2013 and will display a warning that Office was not found when using Office 2016. If Office 2016 is installed as per the Administration Guide, then this warning can be ignored.
 

#2555 - Unattended installation option not available

The new installer currently doesn't support unattended installation. This will be introduced as part of version 8.1
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v7.3
 

Read the announcement to see what is new in 7.3. Known issues of these versions are as follows.
 

#2020 - JPEG2000 encoded PDFs cannot be OCRed

The PDF Converter's OCR add-on has the ability to recognise text in scanned PDF files and make these files fully searchable and indexable. Scanned content can be encoded in many different ways, but PDFs that use JPEG2000 encoding cannot be OCRed. As a workaround use the PDF Converter Professional to convert the PDF to an older PDF version that doesn't support JPEG2000 before sending it for OCR processing.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v7.2 - 7.2.1
 

Read the announcement to see what is new in 7.2 and 7.2.1. Known issues of these versions are as follows.
 

#2020 - JPEG2000 encoded PDFs cannot be OCRed

The PDF Converter's OCR add-on has the ability to recognise text in scanned PDF files and make these files fully searchable and indexable. Scanned content can be encoded in many different ways, but PDFs that use JPEG2000 encoding cannot be OCRed. As a workaround use the PDF Converter Professional to convert the PDF to an older PDF version that doesn't support JPEG2000 before sending it for OCR processing.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v7.1
 

Read the announcement to see what is new in this version. Known issues of the 7.1 version are as follows.
 

#2020 - JPEG2000 encoded PDFs cannot be OCRed

The PDF Converter's OCR add-on has the ability to recognise text in scanned PDF files and make these files fully searchable and indexable. Scanned content can be encoded in many different ways, but PDFs that use JPEG2000 encoding cannot be OCRed. As a workaround use the PDF Converter Professional to convert the PDF to an older PDF version that doesn't support JPEG2000 before sending it for OCR processing.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v7.0
 

Read the announcement to see what is new in this version. Known issues of the 7.0 version are as follows.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v6.1
 

Read the announcement to see what is new in this version. Known issues of the 6.1 version are as follows.
 

#1801 - File names with multiple periods are truncated during conversion

When a file name contains multiple periods ('.') then the name may be truncated after the first period. We are working on a fix, as a temporary workaround replace periods with dashes ('-').
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v6.0
 

Read the announcement to see what is new in this version. Known issues of the 6.0 version are as follows.
 

#1384 - AuthorizedType is not deleted from web.config when uninstalling solution

When uninstalling the PDF Converter's front-end WSP SharePoint's deployment mechanism does not retract all changes to the web.config file. This may lead to problems creating new SharePoint Designer workflows if a new version of the PDF Converter is not installed after the uninstallation. To solve this problem remove all references to 'Muhimbi.SharePoint.DocumentConverter.PDF' from the 'authorizedTypes' section in the affected web.config files.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v5.2
 

Read the announcement to see what is new in this version. Known issues of the 5.2 version are as follows.
 

#1572 / 1670 - Site and List workflows are not supported

All SharePoint Designer and Nintex Workflow activities shipped with the PDF Converter for SharePoint are primarely aimed at workflows associated with Document Libraries. Regular List and Site Level workflows are currently not officially supported.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v5.1
 

Read the announcement to see what is new in this version. Known issues of the 5.1 version are as follows.
 

#1508 - Nintex File Merge activity fails when used inside a 'For each' iterator

Using the PDF Merge activity in a Nintex workflow crashes the workflow when this activity is used inside an iterator loop. As a workaround maintain a list of files to merge in a string and carry out the merging outside of the loop.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v5.0
 

Read the announcement to see what is new in this version. Known issues of the 5.0 version are as follows.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1395 - Filtering in SP2010 doesn't take the regional settings of the current site into account

When using the new automatic watermarking functionality to only apply watermarks under certain conditions using filters, then - when using SP2010 - the filters do not take the current site's regional settings into account. It appears to use the Web Application service account's regional settings. This is not a problem in most cases as all accounts are likely to use the same settings. As a workaround either use workflows to apply filters or change the regional settings for the Web Application service's account. This is not a problem in SharePoint 2007.
 

#1016 - User facing translations for new functionality are in English only.

The new watermarking screens and merging facility are always in English. All languages will be refreshed as part of the upcoming 5.1 release.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v4.1
 

Read the announcement to see what is new in this version.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v4.0
 

Read the announcement to see what is new in this version.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1151 - Converting SharePoint pages to PDF sometimes results in a bitmap based PDFs

Under normal circumstances Muhimbi's HTML to PDF Conversion module generates 'vector based' output when converting HTML files. This has the advantage that it looks very well and all text contained in the HTML file is maintained and can be edited using normal text editing tools. However, certain SharePoint pages are converted to a single bitmap. We are looking into a solution.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#1140 - HTML to PDF Conversion of SP2010 screens is not working correctly.

Due to the large amount of JavaScript and Dynamic HTML that the SharePoint 2010 user interface relies on, some pages may not convert correctly when using the Convert Page to PDF option from the user's Personal Actions menu. SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v3.5
 

Read the announcement to see what is new in this version.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v3.4
 

Read the announcement to see what is new in this version.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v3.2.0.20 - 3.2.1.22
 

Read the announcement to see what is new in this version.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v3.0.0.11
 

Read the announcement to see what is new in this version.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v3.1.1.17 - 3.1.2.18
 

Read the announcement to see what is new in this version.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v3.0.0.11
 

Read the announcement to see what is new in this version.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v1.4.0.0 - v1.4.0.2
 

Read the announcement to see what is new in this version.
 

#628 - DocProperties containing spaces and quotes are not supported

As of version 1.4.0.0 DocProperties embedded in an MS-Word document are automatically refreshed using the values in any associated SharePoint Columns. However, this fails if the DocProperty field name contains either a space or a double quote ("). We are working on a solution, which will be released shortly.
 

#620 - Custom Formatting in DocProperties is not supported

When a DocProperty contains additional formatting information then this is not automatically applied. For example {DOCPROPERTY DateField \@ "yyyy/MM/dd"}.
 

#579 - Doc Properties inserted using MS-Word 2007 'Quick Parts' are not supported

Currently the PDF Converter only supports DocProperties that have been inserted using the 'pre MS-Word 2007' insert field -> DocProperty functionality. Please do not use MS-Word 2007's Insert -> Quick Parts -> Document Property. 
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with fully automated and friendly command line based batch scripts to deploy the solution.
 

#521 - PDF Engine - Converting Arabic documents is not supported

Documents authored in Arabic use the RTL (Right To Left) text direction, which is currently not supported.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.3.0.2
 

Read the announcement to see what is new in this version.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with fully automated and friendly command line based batch scripts to deploy the solution.
 

#521 - PDF Engine - Converting Arabic documents is not supported

Documents authored in Arabic use the RTL (Right To Left) text direction, which is currently not supported.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.2.3.41734
 

Read the announcement to see what is new in this version.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with fully automated and friendly command line based batch scripts to deploy the solution.
 

#521 - PDF Engine - Converting Arabic documents is not supported

Documents authored in Arabic use the RTL (Right To Left) text direction, which is currently not supported.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.1.1.41734
 

Read the announcement to see what is new in this version.
 

#482 - SETUP - Resources need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The customer will need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with command based batch scripts to deploy the SharePoint solution file.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.0.1.6 - BETA
 

#342 - Web applications that use Forms Based Authentication are not supported?

When users are authenticating using FBA then documents cannot be converted to PDF. It is expected that this issue will be resolved in the official release.
 

#341 - PDF Engine - Converting large 'plain text' files is slow

Converting a plain text file of 1MB, an unrealistic scenario, takes an unexpected amount of time to convert to PDF. This is due to a bug in the PDF Engine, which has been reported to the relevant team.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#335 - PDF Engine - Some 'double byte' character sets are not supported

Even though our user interface fully supports Japanese, the PDF Engine currently doesn't support some double byte character sets such as those used by the Japanese language. This is due to a bug in the PDF Engine, which has been reported to the relevant team.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

Screenshots


Listed below are a number of PDF Converter screenshots in various different languages. Several screen casts showing the product in action are available as well.

 


Convert, merge, watermark, secure and OCR files using Nintex Workflow

 

 
Select multiple file for a merge operation.

 

 
Convert files using a SharePoint Designer Workflow

 

 
Convert files using a SharePoint Designer Workflow

 


Specify which formats can be converted and run diagnostics

 


Browse for a different destination folder

 
 


Specify conversion settings (Dutch SP2007 version)

 


Conversion Results (Japanese SP2007 version)

 


Conversion Results (German SP2007 version)

Related News and Articles