<?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: Interaction with PostgreSQL using Share-workflow form. in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272812#M225942</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd advise against using direct database queries / access for most use cases, and yours - as far as I know it from the post - would be one of them. Based on your description, you have a hierarchial set of data, e.g. players by type of sport. Depending on what other data you want to have associated, this sounds like a use case for a category tree in Alfresco data model. This would allow you to use a standard category control and save you the development effort (and maintenance issues) associated with a custom database access layer / operation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 03 Feb 2013 14:54:03 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2013-02-03T14:54:03Z</dc:date>
    <item>
      <title>Interaction with PostgreSQL using Share-workflow form.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272811#M225941</link>
      <description>Hi,Is there any possibility to provide some action on share-workflow-form.xml so that it can directly interact with PostgreSQL provided in Alfresco?Let me explain with the help of a scenario:I have a dropdown list of Games. e.g. Football, Cricket, Golf etc. and I have another dropdown which is based</description>
      <pubDate>Thu, 31 Jan 2013 10:50:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272811#M225941</guid>
      <dc:creator>anand6105</dc:creator>
      <dc:date>2013-01-31T10:50:12Z</dc:date>
    </item>
    <item>
      <title>Re: Interaction with PostgreSQL using Share-workflow form.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272812#M225942</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd advise against using direct database queries / access for most use cases, and yours - as far as I know it from the post - would be one of them. Based on your description, you have a hierarchial set of data, e.g. players by type of sport. Depending on what other data you want to have associated, this sounds like a use case for a category tree in Alfresco data model. This would allow you to use a standard category control and save you the development effort (and maintenance issues) associated with a custom database access layer / operation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Feb 2013 14:54:03 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272812#M225942</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2013-02-03T14:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: Interaction with PostgreSQL using Share-workflow form.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272813#M225943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello AFaust,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for your reply. You are right i have to create a category tree in Alfresco data model. But how can I create action based category tree in my data model. can you explain with the help of an example?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Anand.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2013 08:48:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272813#M225943</guid>
      <dc:creator>anand6105</dc:creator>
      <dc:date>2013-02-04T08:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: Interaction with PostgreSQL using Share-workflow form.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272814#M225944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm afraid I don't fully understand the last question. You can create your category tree simply by using the Category Manager in Alfresco 4.x Share UI (or Explorer UI equivalent if you are up for a blast from the past), or by providing a bootstrap ACP / view XML. You can also create a category tree by using the &amp;lt;a href="&lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/wiki/4.0_JavaScript_API#Classification_API" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/4.0_JavaScript_API#Classification_API&lt;/A&gt;&lt;SPAN&gt;"&amp;gt;Classification JavaScript API&amp;lt;/a&amp;gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Feb 2013 16:45:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interaction-with-postgresql-using-share-workflow-form/m-p/272814#M225944</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2013-02-21T16:45:17Z</dc:date>
    </item>
  </channel>
</rss>

