<?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: Validity of an aspect esp. mandatory fields in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/validity-of-an-aspect-esp-mandatory-fields/m-p/62578#M39066</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;After much digging, it looks as though the only way to do this, declaratively at least, is to define 2 copies of the aspect in question. One that has the so-called mandatory fields set to enforced="False", so that these fields are no longer actually mandatory and the aspect can be added to content w/o an exception being thrown. The other copy of the aspect has the properties set to enforced="True" and is manually created and populated by a script when the content is moved.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As this sort of detail does not appear to be documented anywhere, I would very much appreciate some confirmation from the Alfresco devs that this is indeed the best (only?) way to go.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Mar 2007 22:41:38 GMT</pubDate>
    <dc:creator>rtl</dc:creator>
    <dc:date>2007-03-19T22:41:38Z</dc:date>
    <item>
      <title>Validity of an aspect esp. mandatory fields</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/validity-of-an-aspect-esp-mandatory-fields/m-p/62577#M39065</link>
      <description>Is it possible to check that an aspect has all its mandatory data filled in and is valid?The reason I ask is that I'd like to setup a simple workflow that checks, for example, if the summarizable aspect is filled in, or all the Dublin Core mandatory properties are present, before it moves the conten</description>
      <pubDate>Fri, 16 Mar 2007 04:07:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/validity-of-an-aspect-esp-mandatory-fields/m-p/62577#M39065</guid>
      <dc:creator>rtl</dc:creator>
      <dc:date>2007-03-16T04:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Validity of an aspect esp. mandatory fields</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/validity-of-an-aspect-esp-mandatory-fields/m-p/62578#M39066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;After much digging, it looks as though the only way to do this, declaratively at least, is to define 2 copies of the aspect in question. One that has the so-called mandatory fields set to enforced="False", so that these fields are no longer actually mandatory and the aspect can be added to content w/o an exception being thrown. The other copy of the aspect has the properties set to enforced="True" and is manually created and populated by a script when the content is moved.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As this sort of detail does not appear to be documented anywhere, I would very much appreciate some confirmation from the Alfresco devs that this is indeed the best (only?) way to go.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2007 22:41:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/validity-of-an-aspect-esp-mandatory-fields/m-p/62578#M39066</guid>
      <dc:creator>rtl</dc:creator>
      <dc:date>2007-03-19T22:41:38Z</dc:date>
    </item>
  </channel>
</rss>

