#idempiere IRC log for Thursday, 2017-09-07

*** jdpaniagua has quit IRC01:41
*** jdpaniagua has joined #idempiere02:24
Not-cd20[IDEMPIERE] ralexsander created IDEMPIERE-3471 Fix amount in words for Brazilian Portuguese02:39
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347102:39
Not-cd20[IDEMPIERE] ralexsander created IDEMPIERE-3472 Env.parseVariable not keeping unparseable variable03:08
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347203:08
Not-cd20[IDEMPIERE] ralexsander updated IDEMPIERE-3472 Attachment set to "IDEMPIERE-3472.patch"03:08
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347203:08
*** brent has quit IRC04:26
*** brent has joined #idempiere04:35
*** Junior has quit IRC05:09
*** Junior has joined #idempiere05:23
*** nmicoud has joined #idempiere06:06
*** CarlosRuiz has joined #idempiere09:00
Not-cd20[IDEMPIERE] hieplq updated IDEMPIERE-3471 labels set to "+Patch"10:07
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347110:07
Not-cd20[IDEMPIERE] hieplq updated IDEMPIERE-3472 labels set to "+Patch"10:08
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347210:08
Not-cd20[IDEMPIERE] hieplq created IDEMPIERE-3473 2Pack: two patch modify same record just one win10:19
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347310:19
Not-cd20[IDEMPIERE] hieplq created IDEMPIERE-3474 recent list shouldn't update record change by import csv10:23
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347410:23
Not-cd20[IDEMPIERE] norbert.bede created IDEMPIERE-3475 Window Customisation Row Sequence doesn't applied10:37
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347510:37
Not-cd20[IDEMPIERE] norbert.bede updated IDEMPIERE-3475 description set to "*awaited behaviour:* when admin creates a window customisation for Multi Row Only and define specific columns sequence - this will override application dictionary grid sequence - until custom user specific order doesn't exists. *assume next business logic*: # when user wants setup over window customisation - which is default for role - own then10:37
Not-cd20system must render in window - user customisation icon - default window customisation sequence first fields/columns defined in applied window customisation then outstanding fields from grid/system level. *example - grid seq in app dict* * field1 * field2 * field3 * field4 * field5 *window customisation seq. definition* * field4 * field5 *user customisation window sequence - will render* * field4 * field5 * field1 *10:37
Not-cd20field2 * field3 *steps to reproduce* 1. create new window customisation for sales order any role 2. add new tab definition for order header - set Multi Row Only = Yes 3. specify columns e.g documentno as seq 1 and date ordered as seq 2. 4. logout then cache reset 5. open sales order in Multi Row mode BUG: column order is not updated - doesn't follow defined sequence. *BUG* This Bug cause - admins - can't define10:37
Not-cd20default column order/sequence. *business case*: eg. 20 sales people must have identical default sequence column order otherwise hard to keep ad1. quick new user kick out ad2. return to back to general column order - defined by sales manager. "10:37
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347510:37
Not-cd20[IDEMPIERE] norbert.bede updated IDEMPIERE-3475 description set to "*awaited behaviour:* when admin creates a window customisation for Multi Row Only and define specific columns sequence - this will override application dictionary grid sequence - until custom user specific order doesn't exists - so window customisation sequence will be default role column order. *assume next business logic*: # when user wants setup10:38
Not-cd20over window customisation - which is default for role - own then system must render in window - user customisation icon - default window customisation sequence first fields/columns defined in applied window customisation then outstanding fields from grid/system level. *example - grid seq in app dict* * field1 * field2 * field3 * field4 * field5 *window customisation seq. definition* * field4 * field5 *user10:38
Not-cd20customisation window sequence - will render* * field4 * field5 * field1 * field2 * field3 *steps to reproduce* 1. create new window customisation for sales order any role 2. add new tab definition for order header - set Multi Row Only = Yes 3. specify columns e.g documentno as seq 1 and date ordered as seq 2. 4. logout then cache reset 5. open sales order in Multi Row mode BUG: column order is not updated - doesn't10:38
Not-cd20follow defined sequence. *BUG* This Bug cause - admins - can't define default column order/sequence. *business case*: eg. 20 sales people must have identical default sequence column order otherwise hard to keep ad1. quick new user kick out ad2. return to back to general column order - defined by sales manager. "10:38
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347510:38
Not-cd20[IDEMPIERE] norbert.bede updated IDEMPIERE-3475 description set to "*awaited behaviour:* when admin creates a window customisation for Multi Row Only and define specific columns sequence - this will override application dictionary grid sequence - until custom user specific order doesn't exists - so window customisation sequence will be default role column order. *assume next business logic*: when user wants setup10:38
Not-cd20over window customisation - which is default for role - own then system must render in window - user customisation icon - default window customisation sequence first fields/columns defined in applied window customisation then outstanding fields from grid/system level. *example - grid seq in app dict* * field1 * field2 * field3 * field4 * field5 *window customisation seq. definition* * field4 * field5 *user10:38
Not-cd20customisation window sequence - will render* * field4 * field5 * field1 * field2 * field3 *steps to reproduce* 1. create new window customisation for sales order any role 2. add new tab definition for order header - set Multi Row Only = Yes 3. specify columns e.g documentno as seq 1 and date ordered as seq 2. 4. logout then cache reset 5. open sales order in Multi Row mode BUG: column order is not updated - doesn't10:38
Not-cd20follow defined sequence. *BUG* This Bug cause - admins - can't define default column order/sequence. *business case*: eg. 20 sales people must have identical default sequence column order otherwise hard to keep ad1. quick new user kick out ad2. return to back to general column order - defined by sales manager. "10:38
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347510:38
Not-cd20[IDEMPIERE] norbert.bede updated IDEMPIERE-3475 description set to "*awaited behaviour:* when admin creates a window customisation for Multi Row Only and define specific columns sequence - this will override application dictionary grid sequence - until custom user specific order doesn't exists - so window customisation sequence will be default role column order. *assume next business logic*: when user wants setup10:39
Not-cd20over window customisation - which is default for role - own then system must render in window - user customisation icon - default window customisation sequence first fields/columns defined in applied window customisation then outstanding fields from grid/system level. *example - grid seq in app dict* * field1 * field2 * field3 * field4 * field5 *window customisation seq. definition* * field4 * field5 *user10:39
Not-cd20customisation window sequence - will render* * field4 * field5 * field1 * field2 * field3 *steps to reproduce* 1. create new window customisation for sales order any role eg sales people 2. add new tab definition for order header - set Multi Row Only = Yes 3. specify columns e.g documentno as seq 1 and date ordered as seq 2. 4. logout then cache reset 5. open sales order in Multi Row mode BUG: column order is not10:39
Not-cd20updated - doesn't follow defined sequence. *BUG* This Bug cause - admins - can't define default column order/sequence. *business case*: eg. 20 sales people must have identical default sequence column order otherwise hard to keep ad1. quick new user kick out ad2. return to back to general column order - defined by sales manager. "10:39
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347510:39
Not-cd20[IDEMPIERE] norbert.bede updated IDEMPIERE-3475 summary set to "Window Customisation Multi Row Only Sequence doesn't applied"10:40
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347510:40
*** CarlosRuiz has quit IRC11:07
Not-cd20[IDEMPIERE] hieplq created IDEMPIERE-3476 2Pack: attribute set install is not reference by UUID12:25
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347612:25
*** jdpaniag_ has joined #idempiere12:31
*** jdpaniagua has quit IRC12:34
*** mbozem has joined #idempiere12:40
Not-cd20[IDEMPIERE] hieplq updated IDEMPIERE-3476 Attachment set to "IDEMPIERE-3476.patch"12:47
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347612:47
Not-cd20[IDEMPIERE] hieplq updated IDEMPIERE-3476 labels set to "+Patch"12:47
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347612:47
Not-cd20[IDEMPIERE] hieplq updated IDEMPIERE-3476 status set to "Peer Review Queue"12:47
Not-cd20[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-347612:47
*** aguerra has quit IRC13:23
*** mbozem has quit IRC14:11
*** nmicoud has quit IRC15:38
Not-cd20[iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-4.1 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/17:32
Not-cd20[iDempiere] globalqss a219573 - IDEMPIERE-3449 - fix login failing when the role in preferences doesn't have any org accessible for the user going into the system17:32
Not-cd20[iDempiere4.1] jenkins built #180 completed (success) http://ci.idempiere.org/job/iDempiere4.1/180/17:42

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!