Thu, 12 Jan 2017 17:07:55 +0100Fixed issue 34900: Email definition of the template was not correctly selected
Naroa Iriarte <naroa.iriarte@openbravo.com> [Thu, 12 Jan 2017 17:07:55 +0100] rev 31479
Fixed issue 34900: Email definition of the template was not correctly selected

If there was more than one email definition, one of them set as default, sometimes, when clicking the email button, the application was not choosing the correct email definition, which is the one with the "default" checkbox checked. It can happen also to have an email definition with the default checked but the language is different from the bussines partner's language, in this case if there exists another template which is not checked as default, but its language is the language of the business partner, this will have priority.

The problem here was that there was a piece of code which was using a Map, and it was overwritting the email definitions with the same language. This happened because the key used to store the email definitions in that map was the language it self. So, in the case of having, for example three email definitions with the same language and one of them set as default was failing because in the map was only stored the last one.

To fix this a new condition has been added. Now, if the email definition is marked as default, it is stored in the map. It does not matter to overwrite the other email definitions because only one can be the default and will be the one stored here. If the email definition is not marked as default instead, a comparation will be done to check if there already exists an email definition with the same language. If not, then, this email configuration will be added to the map. This is to prevent deleting the default configurations of a language.

Fri, 13 Jan 2017 11:47:44 +0100fixed bug 34797: 3.0 selector as process param don't apply filter expression
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 13 Jan 2017 11:47:44 +0100] rev 31478
fixed bug 34797: 3.0 selector as process param don't apply filter expression

When a 3.0 selector is used as parameter within a process (ad_process), filter
expressions it might define were not applied in popup filters.

There were 2 problems in the code:
- Incorrect default assignment using bitwise or operator instead of boolean OR.
- Incorrect retrieval of selector definition id

Fri, 13 Jan 2017 10:03:39 +0100fixed bug 34939: 3.0 selectors cannot be used in classic mode
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 13 Jan 2017 10:03:39 +0100] rev 31477
fixed bug 34939: 3.0 selectors cannot be used in classic mode

When a 3.0 selector was included within classic mode, the JS failed to load.

The problem was cancelAndReplace.js was included within classic mode JS but it
depends on resources not available in this mode.

Because cancel and replace is not designed to work in classic mode, its JS is
now not included in this mode.

Thu, 22 Dec 2016 13:22:46 -0500Related to issue 34676: Code review improvements
Mark <markmm82@gmail.com> [Thu, 22 Dec 2016 13:22:46 -0500] rev 31476
Related to issue 34676: Code review improvements

Reordered conditions in where clause.

Thu, 22 Dec 2016 22:54:41 +0530Fixes Issue 34676:It is possible to see prices for list prices for
Atul Gaware <atul.gaware@openbravo.com> [Thu, 22 Dec 2016 22:54:41 +0530] rev 31475
Fixes Issue 34676:It is possible to see prices for list prices for
organizations that you don't have access to.

Problem is Organization property of Product Price in the Product Price By
Warehouse view is not checked whether it appears in Natural Tree of the
Current Logged in Organization.

Wed, 11 Jan 2017 17:26:45 +0100Fixed issue 34502: Multi record selection for processes is now available
Naroa Iriarte <naroa.iriarte@openbravo.com> [Wed, 11 Jan 2017 17:26:45 +0100] rev 31474
Fixed issue 34502: Multi record selection for processes is now available

It is now possible to create a process and check the flag "Multi record" which means that it is possible to select more than one record and execute the current process.

Mon, 28 Nov 2016 15:07:38 +0100[pi-process-multi-record] A null check has been added.
Naroa Iriarte <naroa.iriarte@openbravo.com> [Mon, 28 Nov 2016 15:07:38 +0100] rev 31473
[pi-process-multi-record] A null check has been added.

It is possible to have a process (for example add payment) called from a different kind of button. This caused a null pointer exception in the code of ob-parameter-window-view.doProcess. This is now avoided by a check.

Mon, 28 Nov 2016 09:02:01 +0100[pi-process-multi-record] Merge with latest pi
Naroa Iriarte <naroa.iriarte@openbravo.com> [Mon, 28 Nov 2016 09:02:01 +0100] rev 31472
[pi-process-multi-record] Merge with latest pi

Tue, 22 Nov 2016 16:09:12 +0100[pi-process-multi-record] processes executed for more than one record
Naroa Iriarte <naroa.iriarte@openbravo.com> [Tue, 22 Nov 2016 16:09:12 +0100] rev 31471
[pi-process-multi-record] processes executed for more than one record

Now, it is possible to select more than one record and execute a process. Before this fix, even it was possible to select more than one record, the process was only affecting the first selected record. The javascript logic which handles this has been added.
Also, a refresh of the view, in the cases of having multi record processes, has been added.

Tue, 22 Nov 2016 13:14:49 +0100[pi-process-multi-record] Merge with latest pi
Naroa Iriarte <naroa.iriarte@openbravo.com> [Tue, 22 Nov 2016 13:14:49 +0100] rev 31470
[pi-process-multi-record] Merge with latest pi