Had been away for a while. <br><br><div><span class="gmail_quote">On 24/05/07, <b class="gmail_sendername">Romain Courteaud</b> <<a href="mailto:romain@nexedi.com">romain@nexedi.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Shresth K [2007-05-21 20:23:14 +0530]:<br><br>> Do you mean that it was *included* by mistake as it is present in the<br>> current implementation and I hope it is, because I can see a use case where<br>> it is needed.
<br>><br>> The expected beheviour was to return the container object, and it was<br>> >not possible for the user to choose where to create the object.<br>> ><a href="http://svn.erp5.org/?view=rev&revision=5582">
http://svn.erp5.org/?view=rev&revision=5582</a><br><br>The parameter is still present in the configuration, but not used<br>anymore in the current implementation (because it was removed by<br>mistake).<br><br>So, it currently does not work.
<br><br>This feature has to be readded in the system. For preventing futur errors, a<br>Selenium test also needs to be written (in<br><a href="http://svn.erp5.org/erp5/trunk/bt5/erp5_ui_test/PathTemplateItem/portal_tests/relation_field_zuite/">
http://svn.erp5.org/erp5/trunk/bt5/erp5_ui_test/PathTemplateItem/portal_tests/relation_field_zuite/</a>),<br>but I don't have time for fixing it currently.<br><br>Feel free to submit a patch for the fix and the test if you already
<br>wrote them ;)</blockquote><div><br>I haven't yet written any tests or patch as I was in the process of understanding the use case better. As of now this definitely is needed and as confirmed by you that it was there, I shall put it as a future todo. As I am still learning the system, I don't have an insight to the extent that I can make such modifications. Hence I was searching for the revision in which any related implementation was reverted back but got none. May be I need to look harder to find something related or if anyone can help, you are most welcome.
<br><br>Herein is the use case that I have analysed and would request you to give your opinion on it:<br>A sales manager may be responsible for 2 regions - A & B<br>All modules exist for all regions such as Person Module A, Person Module B, Organisation Module A, Organisation Module B to ensure access and visibility based on region.
<br>There are 2 sales modules - Sales-Asia, Sales-Europe<br>Now while creating a Sales Order, if he/she needs to create a new Person/Organisation through the RelationStringField(while setting the source/destination), the existing implementation has no way to know in which module to create the new object. For
e.g: Should it be Organisation Module A or Organisation Module B<br>In this scenario, I find the Container Getter Method invaluable. If the object is being created in the context of Sales Module A then the method can decide that the object must be in {Person, Organisation} A .
<br><br> <br> Thanks,<br>Shresth<br></div></div><br>