<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Suitable use of Alfresco? Job candidate tracking/workflow in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277845#M230975</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is definitely the kind of solution that Alfresco was built for. Your intuition is correct: Create a content model to capture the business-specific metadata, create a workflow to shepherd the documents through the process (you could start with simple workflow or even no workflow at all and do everything manually if you wanted to), and then create a page that queries your data and displays it in a way that makes sense to the managers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note that starting with 4.2 it is much easier to customize the document library with such a grid.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another idea would be to use data lists to represent candidates and their status, then link off to the supporting documents for folders as necessary.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Feb 2013 16:09:24 GMT</pubDate>
    <dc:creator>jpotts</dc:creator>
    <dc:date>2013-02-19T16:09:24Z</dc:date>
    <item>
      <title>Suitable use of Alfresco? Job candidate tracking/workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277844#M230974</link>
      <description>Hi,&amp;nbsp; I'm working on a proof of concept demonstration of Alfresco for my employer. So far I'm having a great time with Alfresco but I'm having trouble coming up with a solution to one requirement: employment candidate tracking.&amp;nbsp; We need to track a person from the time we receive a resume to the point</description>
      <pubDate>Wed, 13 Feb 2013 02:48:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277844#M230974</guid>
      <dc:creator>paul2</dc:creator>
      <dc:date>2013-02-13T02:48:47Z</dc:date>
    </item>
    <item>
      <title>Re: Suitable use of Alfresco? Job candidate tracking/workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277845#M230975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is definitely the kind of solution that Alfresco was built for. Your intuition is correct: Create a content model to capture the business-specific metadata, create a workflow to shepherd the documents through the process (you could start with simple workflow or even no workflow at all and do everything manually if you wanted to), and then create a page that queries your data and displays it in a way that makes sense to the managers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note that starting with 4.2 it is much easier to customize the document library with such a grid.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another idea would be to use data lists to represent candidates and their status, then link off to the supporting documents for folders as necessary.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 16:09:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277845#M230975</guid>
      <dc:creator>jpotts</dc:creator>
      <dc:date>2013-02-19T16:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: Suitable use of Alfresco? Job candidate tracking/workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277846#M230976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Paul.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You are at he right place. We have fulfilled the same requirements w/ Alfresco in a few ways for different clients and in-house:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a) Building a workflow on top of Alfresco Share as Jeff outlined in more detail - should be the easiest approach if you are fresh into Alfreso. Some knowledge of YUI might come in handy.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;b) Bulding a workflow on top of Activiti Explorer. Activiti is the BPM engine included in Alfresco and it features a UI of its own for such a purpose. - should be fairly easy, though a bit less documentation is available.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;c) Building a custom application in any rapid development technology, such as Grails, PHP, Java and UI such as ExtJs/YUI/GWT/JQuery and using Alfresco and its BPM through SOA/REST - should be the most flexible and difficulty will depend on your previous expertize.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope you have fun.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Roko&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;BTW, rule engines will not be a needed expertize, you should read a little bit into BPM as an approach to building applications.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Feb 2013 20:07:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/suitable-use-of-alfresco-job-candidate-tracking-workflow/m-p/277846#M230976</guid>
      <dc:creator>rroic</dc:creator>
      <dc:date>2013-02-21T20:07:00Z</dc:date>
    </item>
  </channel>
</rss>

