Use dynamic list of portal types based on families (ex. node, project, ticket)...

Use dynamic list of portal types based on families (ex. node, project, ticket) instead of static list. Documents can be related to a CRM ticket.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@21815 20353a03-c40f-0410-a6d1-a30d3c3de9de

bt5/erp5_dms/SkinTemplateItem/portal_skins/erp5_dms/Document_viewFieldLibrary/my_follow_up_title_list.xml

@@ -327,7 +327,9 @@
                 </item>
                 <item>
                     <key> <string>portal_type</string> </key>
-                    <value> <string></string> </value>
+                    <value>
+                      <persistent> <string encoding="base64">AAAAAAAAAAM=</string> </persistent>
+                    </value>
                 </item>
                 <item>
                     <key> <string>relation_setter_id</string> </key>
@@ -579,4 +581,20 @@
       </dictionary>
     </pickle>
   </record>
+  <record id="3" aka="AAAAAAAAAAM=">
+    <pickle>
+      <tuple>
+        <global name="TALESMethod" module="Products.Formulator.TALESField"/>
+        <tuple/>
+      </tuple>
+    </pickle>
+    <pickle>
+      <dictionary>
+        <item>
+            <key> <string>_text</string> </key>
+            <value> <string>python:  map(lambda x: [x,x], here.getPortalNodeTypeList() + here.getPortalProjectTypeList() +  here.getPortalTicketTypeList())</string> </value>
+        </item>
+      </dictionary>
+    </pickle>
+  </record>
 </ZopeData>