﻿<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <atom:link href="http://www.hersheytech.com/Default.aspx?TabId=196&amp;rssid=0" rel="self" type="application/rss+xml" />
    <title>Most recent blog entries</title>
    <link>http://www.hersheytech.com/Blog.aspx</link>
    <description>The latest news in the ECM Industry about Document Imaging and Data Capture for SharePoint from Hershey Technologies</description>
    <ttl>60</ttl>
    <language>en-US</language>
    <generator>SunBlogNuke RSS Generator Version 3.7.9.0</generator>
    <pubDate>Fri, 18 May 2012 09:45:06 GMT</pubDate>
    <lastBuildDate>Fri, 18 May 2012 09:45:06 GMT</lastBuildDate>
    <item>
      <title>Planning for a MOSS2007 to SharePoint 2010 Upgrade</title>
      <link>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/31/Default.aspx</link>
      <description><![CDATA[This blog post is based on a white paper that I authored last year after assisting my team with a few SharePoint 2010 upgrades.  For some reason, I forgot to post this last year, and just came across this document again, so I decided to post it now. I realize that many organizations have already completed upgrades to SharePoint 2010.  However, many companies are still running on MOSS (or even SharePoint 2003) and planning an upgrade to SharePoint 2010, so I believe this information will be helpful to some you.     SharePoint is really not a “product”, but rather a sophisticated platform for building and hosting a variety of complex business applications. This makes SharePoint a powerful and flexible system that organizations rely upon as a mission-critical part of their IT infrastructure.  It also makes the process of upgrading an existing MOSS or WSS farm to SharePoint 2010 more complex than most applications or other server products from Microsoft.   Purpose The purpose of this ...]]></description>
      <dc:creator>Tom Castiglia</dc:creator>
      <comments>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/31/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/31/Default.aspx</guid>
      <pubDate>Sat, 03 Mar 2012 07:43:59 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=31</trackback:ping>
    </item>
    <item>
      <title>Changing the Item-Level Permissions Settings for a Document Library requires PowerShell</title>
      <link>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/28/Default.aspx</link>
      <description><![CDATA[Today I decided that I needed to change the Item-Level Permissions settings for a document library so that users could only read the items that they had created.  For SharePoint lists, the Item-Level Permissions setting is easily configured under the list’s Advanced Settings section, like this:      However, when I went to the Advanced Settings section for my document library, there was no section for Item-Level Permissions.  I checked a few other lists and document libraries and confirmed that apparently most list types support this configuration, except for document libraries!   So my next question was whether Item-Level Permissions settings could not be changed in a document library at all, or whether these options were simply not displayed in the browser for the Advanced Settings in a library.  I figured the easiest way to determine this would be to attempt it with PowerShell in a test environment… if it was not supported, the PowerShell commands would simply fail to execute  ...]]></description>
      <dc:creator>Tom Castiglia</dc:creator>
      <comments>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/28/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/28/Default.aspx</guid>
      <pubDate>Thu, 02 Feb 2012 08:36:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=28</trackback:ping>
    </item>
    <item>
      <title>Newsletter for Kofax Users</title>
      <link>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/27/Default.aspx</link>
      <description><![CDATA[<p>Hershey Technologies welcomes the New Year with several exciting new features for users and managers affiliated with Kofax Capture software. We understand that change is a constant in our industry, with new operating systems,   software product releases, evolving use of mobile devices and enterprise security issues are some to the topics Hershey Technologies technical support team is prepared to address!</p>]]></description>
      <dc:creator>Neal Fischer</dc:creator>
      <comments>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/27/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/27/Default.aspx</guid>
      <pubDate>Tue, 31 Jan 2012 19:40:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=27</trackback:ping>
    </item>
    <item>
      <title>How can I speed up the export of my custom export script?</title>
      <link>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/24/Default.aspx</link>
      <description><![CDATA[<p>Your custom export is saving image files out to a folder and performs well when exporting to a local folder but is much slower when exporting to network storage.  This problem increases dramatically as the number of pages in the multipage image file increase.</p>]]></description>
      <dc:creator>Arjay Dohring</dc:creator>
      <comments>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/24/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/24/Default.aspx</guid>
      <pubDate>Fri, 19 Nov 2010 04:07:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=24</trackback:ping>
    </item>
    <item>
      <title>My batch class needs to support eDocs and use KTM but it won’t publish, what do I do?</title>
      <link>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/23/Default.aspx</link>
      <description><![CDATA[<p>I have run into several scenarios where I needed my batch class to support eDocs and I needed to use Kofax Transformation Module.  For example, I wanted to use the Kofax Capture Import Connector – Email, this requires that you set your batch class to allow import of eDocs.  By default Kofax Capture will throw an error during publish if you set the batch class to allow eDocs and you include the KTM queues.  This is for good reason as KTM will error if you try and run an eDoc through it.</p>]]></description>
      <dc:creator>Arjay Dohring</dc:creator>
      <comments>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/23/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/23/Default.aspx</guid>
      <pubDate>Thu, 18 Nov 2010 00:16:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=23</trackback:ping>
    </item>
    <item>
      <title>Can I access index fields from Recognition Script?</title>
      <link>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/22/Default.aspx</link>
      <description><![CDATA[<p>Not long ago I had a client that was using a barcoded coversheet to replace a previous version that required OCR.  The client placed several values into the barcode with a delimiter and wanted them parsed out and placed into the appropriate index fields.</p>
<p>Recognition Script seemed like the most likely place to implement this little tidbit of code.  Unfortunately I quickly found out that while I could parse the barcode into its separate values, Recognition Script only provides access to the index field its applied to.  Therefore I had no access to the other index fields and could not set them.</p>]]></description>
      <dc:creator>Arjay Dohring</dc:creator>
      <comments>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/22/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/22/Default.aspx</guid>
      <pubDate>Thu, 18 Nov 2010 00:03:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=22</trackback:ping>
    </item>
    <item>
      <title>Why do I have to install my workflow agent on every station?</title>
      <link>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/21/Default.aspx</link>
      <description><![CDATA[<p>When using workflow agents with Kofax Capture it is best practice to deploy your workflow agent on every station in your Kofax Capture environment.  This ensures that the workflow agent will be present and able to perform its function whenever needed.  To enforce this best practice, Kofax Capture by default will through an exception and route your batch to Quality Control with an error status if it cannot load the workflow agent dll.</p>]]></description>
      <dc:creator>Arjay Dohring</dc:creator>
      <comments>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/21/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/21/Default.aspx</guid>
      <pubDate>Wed, 17 Nov 2010 23:55:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=21</trackback:ping>
    </item>
    <item>
      <title>The right way and wrong way to use the “Rating (0-5)” field in a SharePoint list or library</title>
      <link>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/20/Default.aspx</link>
      <description><![CDATA[<p>If you wish to utilize Ratings on a SharePoint list or library, you might think that you can do so by simply adding the “Rating (0-5)” site column to your existing list, library or content type.  In fact, SharePoint will allow you to do that, however doing so may or may not provide the intended results.</p>]]></description>
      <dc:creator>Tom Castiglia</dc:creator>
      <comments>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/20/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/20/Default.aspx</guid>
      <pubDate>Mon, 15 Nov 2010 11:47:00 GMT</pubDate>
      <slash:comments>3</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=20</trackback:ping>
    </item>
    <item>
      <title>Problem with Web Service URL for SSRS 2008 R2 deployed in SharePoint Integrated Mode</title>
      <link>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/19/Default.aspx</link>
      <description><![CDATA[<p>I recently solved a seemingly obscure problem configuring SQL Server Report Services (SSRS) 2008 R2 using SharePoint Integrated Mode.  However, perhaps this problem isn't as obscure as it seems and maybe this article will help others.</p>]]></description>
      <dc:creator>Tom Castiglia</dc:creator>
      <comments>http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/19/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/SharePoint/tabid/197/entryid/19/Default.aspx</guid>
      <pubDate>Wed, 27 Oct 2010 03:29:00 GMT</pubDate>
      <slash:comments>2</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=19</trackback:ping>
    </item>
    <item>
      <title>SharePoint Export Connector is not compatible with Item_Added event in a SharePoint event receiver</title>
      <link>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/18/Default.aspx</link>
      <description><![CDATA[<p>Today we tested the SharePoint Export Connector with Kofax v9 with a document library in SharePoint 2010.  This particular library included use of a custom SharePoint Event Receiver. </p>]]></description>
      <dc:creator>Tom Castiglia</dc:creator>
      <comments>http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/18/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.hersheytech.com/Blog/Capture/tabid/198/entryid/18/Default.aspx</guid>
      <pubDate>Mon, 25 Oct 2010 21:47:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.hersheytech.com/DesktopModules/SunBlog/Handlers/Trackback.aspx?id=18</trackback:ping>
    </item>
  </channel>
</rss>
