Archive for document generation

PSC Webinar - Nintex Processfest 2019 Recap on 10.10.2019 at 10:30 AM CDT

October 8 2019

PSC is a proud partner of Nintex, the leader in process automation. Four of us from PSC went to ProcessFest 2019 to learn all about what Nintex is working on - and we decided to share our top insights from the event with Nintex in a webinar. Learn all about the news on workflow, forms, RPA ( Robot Process Automation), document generation, digital signatures, and process discovery and mapping. Info about the webinar and a link to register is below: Did you attend Nintex ProcessFest 2019? If so, let's compare notes. Missed the event? Don't worry, we have you covered. PSC Group's Jeff Crowell & Dave Plasencia join Nintex's Michael Schutz (VP Product, Channel and Field Marketing) to provide a 30-minute overview of this year's conference. Interested to hear the top news and highlights from ProcessFest 2019? Register below! Thursday, October 10, 2019 10:30 am Central | 11:30 am Eastern Register Now

JMP208 The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus Symphony

January 30 2011

JMP208 The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus SymphonyView more presentations from John Head. Downloads coming shortly

OOXML Drama ... No-Duh!

April 5 2010

Last week, Alex Brown wrote a pretty scathing blog entry about how Microsoft has not followed thru on implementing and supporting the OOXML ISO Standard. We have seen Ars Technica pick up the story. Even Ed blogged about it. Today, Nathan Freeman asked me this in IM: "so, I'm wondering if Alex's (Brown) blog post puts you in MSFT apologist-mode or "no-duh" mode" My answer was a resounding "no-duh" Here are some thoughts why. Microsoft said in late 2008 that there was no way ISO/IEC 29500 Strict was going to make Office 2010. I find this interesting because (I believe) Alex Brown was in the room when they said that. As far as I can tell, Office is on a 4 year development cycle. The first year is when the previous version is in testing, two years of development, and a year of testing. The specification was accepting mid way thru a development cycle. You don't add something like that midway in a product cycle like this. As much as the team I work with at Microsoft, led by Doug Mahugh

It’s time Microsoft decide how serious they are about real people using OOXML

February 16 2010

As many of my readers know, one of the areas that PSC has invested quite a bit of time in the past 24 months is around Document Generation. Document Generation is defined (by myself) as the ability to generate a document, based on a format, without having any software installed to generate or render the document. This can be done client or server side. I have done quite a bit of blogging on the topic - and taken both Microsoft and IBM to task. We have done some real world client projects, including the Research Director, Inc. project that was highlighted in this case study. While PSC does not participate in the ODF or OOXML standards process, I think our team is one of the deepest on the technical side. I have been working with the PSC team to get our technical knowledge out into the world to share our experiences and engage in the conversations. The first piece of this engagement is a new blog called Coding the Document. Tim Murphy, a .NET guru in our Microsoft practice and one of t

OOXML - What Microsoft should be doing going forward

May 26 2009

So I have taken ODF to task in the past couple of weeks, and since I have stated that my position is to work with both ODF and OOXML, I thought it was time for a bit of tough love for Microsoft. Before I do that, a bit of a current state observation. When someone says OOXML today, they can mean many things. For most, they are not talking about ECMA-376 or IS29500, the specifically mean Office 2007 file formats for Word, Excel, and PowerPoint. We can argue what the technical term used by the standards community uses, but let's get real. The average person has no clue what either standard is or what they are called or how they are different. They need to work with Office 2007 file formats - reading them and saving changes back to them. If you look at other software vendors; Apple, Google, IBM, etc; when they add OOXML support, they always call it 'adding Office 2007 file format' - and frankly, nothing has really changed for them since adding Office 2003 support. Sure, they might have b