← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 708467] Re: Act_window : Incomplete behavior

 

Hello Guys,

Everyone of you are trying your best way out to represent your desired
way to work. You all are right.

My aim of posting this was to mention that the feature we presented has something missing in its original approach.
My view says that, we clicked on shortcuts(which lead us to SPECIFIC set of records),so we should see absolutely specific records.


1. Default for new records:
-- I disagree with Olivier (This is really rare,inconvenient to write this) that this is negligible. We actually have to care I believe.
I am not sure that all the records (generated by the click on act_windows) would be readonly always. Lets think as an administrator who doesn't really like to bother to do more clicks.
-- 'default_*' is the best preferable solution here as very well initiated by Ujjvala. Thanks Ujjvala.
-- I guess, we all agree to this point.

2. Filtered records on click of act_windows:
-- @Steffi, 'HARD DOMAIN' was a workaround for 5.0 series and 6.0 comes with a great turn with search panel which lets you clear all the conditions and make a new filter as per your need. In 5.0, what happens is the resulting windows do not let you create a new search and thus puts you in a restricted area of choosing something very limited.
-- I am not in favour of domain like [('field','=',active_id)] which will again put some restrictions and user would feel being in jail.
-- Let us just don't talk about specific example.
-- Steffi talks in functional aspect and Olivier talks very accurately in order to put framework and Changes on safer stand.
-- However,I can suggest a solution where we can think of these alternate solutions:
A. Introduce a key on context like {'context_domain':[(''field","=",active_id)]},so that while the act_window gets loaded first time,this domain is applied ORed with normal condition(as what happens currently) on search panel.(name_get one).
B. When act_window click is triggered, Clients should interpret as [('field','=',active_id)] only for the first time. As soon as the clear is clicked, domain and context should be set to [] and {} (as it happens currently).

Note : Setting name_get() on search panel seems a little uncomfortable
as it will disturb the result. If this is true, name_search() should
always be treated in parallel to generate the accurate results on
search. Look at the bug 708593, which I think,should be fixed on addons
taking this discussion into consideration.

Thanks.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/708467

Title:
  Act_window : Incomplete behavior

Status in OpenERP Server:
  Confirmed

Bug description:
  There has been a problem observed on act_windows(links or shortcuts).

  The problem is, act_windows do not respect domain and they work
  according to context set on search panel,but this context can lead to
  a completely wrong result.

  Example:
  Install stock module(With demo data).
  Go to Sales/Products , edit the code of CPU1 to be CPU.
  Click on Stock Moves(act_windows), you will see that the the purpose of link is not served at all. (result includes records for cpu2,cpu3) as well.

  
  Second problem, clicking NEW should set default product_id on new Stock.move,which doesn't happen anymore.

  Overall,
  1. If domain is not supposed to beset, there should be a special key which loads FILTERED records on links.
  2. 'default_FIELD':active_id or kind of relevant entry should appear in context.

  Thanks.





References