<?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: running exampleModel in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/running-examplemodel/m-p/30623#M15742</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is a bug that is rasied in JIRA (I can't get access at the moment though to tell you the issue number).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When a node that has mandatory properties is first created by the web client i.e. before the properties page is displayed, it is in an "incomplete" state, represented by the incomplete aspect applied to the node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once all mandatory properties have been added the incomplete aspect is removed. The integrity system will not produce warnings for missing properties when the incomplete aspect is present. The same is not currently happening for associations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This means when you first create a node that has a mandatory association (like my:sop has) the integrity system will print this warning as it is not checking for the incomplete aspect. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is not fatal however, and you can continue to use the node as normal.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Aug 2006 08:51:31 GMT</pubDate>
    <dc:creator>gavinc</dc:creator>
    <dc:date>2006-08-09T08:51:31Z</dc:date>
    <item>
      <title>running exampleModel</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/running-examplemodel/m-p/30622#M15741</link>
      <description>This warning appears:&amp;nbsp; WARN&amp;nbsp; [org.alfresco.repo.node.integrity.IntegrityChecker] Found 2 integrity violations:The association target multiplicity has been violated: &amp;nbsp;&amp;nbsp; Association: Association[ class=ClassDef [ name={my.new.model}sop], name={my.new.model}signOff, target class={http://www.alfresco.or</description>
      <pubDate>Tue, 08 Aug 2006 12:55:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/running-examplemodel/m-p/30622#M15741</guid>
      <dc:creator>tiofelix</dc:creator>
      <dc:date>2006-08-08T12:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: running exampleModel</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/running-examplemodel/m-p/30623#M15742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is a bug that is rasied in JIRA (I can't get access at the moment though to tell you the issue number).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When a node that has mandatory properties is first created by the web client i.e. before the properties page is displayed, it is in an "incomplete" state, represented by the incomplete aspect applied to the node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once all mandatory properties have been added the incomplete aspect is removed. The integrity system will not produce warnings for missing properties when the incomplete aspect is present. The same is not currently happening for associations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This means when you first create a node that has a mandatory association (like my:sop has) the integrity system will print this warning as it is not checking for the incomplete aspect. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is not fatal however, and you can continue to use the node as normal.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Aug 2006 08:51:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/running-examplemodel/m-p/30623#M15742</guid>
      <dc:creator>gavinc</dc:creator>
      <dc:date>2006-08-09T08:51:31Z</dc:date>
    </item>
  </channel>
</rss>

