IDempiere/FullMeeting20140416

⇐ Table of Contents | Full Meeting Minutes | Full Meeting 2014-04-16

CarlosRuiz: Good morning
nmicoud: Bonjour
JanThielemann: hi
Deepak: Good morning/Afternoon
Deepak: I have one question, I think we discuss to auto create ASI based on document type configuration on Attribute Set Window
Deepak: Did anybody worked on it?
CarlosRuiz: Deepak, I don't remember that discussion
Deepak: Carlos, this was when we discussing dateMaterialPolicy
Deepak: I am trying to find out thread
Deepak: Carlos, I found it http://www.globalqss.com/wiki/index.php/IDempiere/FullMeeting20130102
CarlosRuiz: reading...
CarlosRuiz: I see
CarlosRuiz: do you mean defining which document type has ASI as mandatory
CarlosRuiz: in some way that can be done with actual functionality
CarlosRuiz: configuring always mandatory and then defining the exclusions in the next tab
Deepak: yes
Deepak: Carlos, I think discussion was followed to auto create ASI when it is mandatory for a document, and sequence number is allocated and user has not provided asi
Deepak: This may be true in case if we want to create serials on MR, shipment or production
CarlosRuiz: yep - in general a way to capture or generate serials massively is needed
Deepak: Do anybody has started on that task?
CarlosRuiz: not that I'm aware
Deepak: Should we create ticket for that as new feature?
Deepak: So someone can pickup?
CarlosRuiz: I remember a contribution from Peru that implemented a form to capture serials - but I think it's not worked for idempiere
Deepak: ohk
Deepak: Please note that I have finished Idempiere-1770 for shipment, MR and Customer returns
Deepak: I will commit my first patch today
Deepak: Then will start work on Inventory related document'
CarlosRuiz: good - that requires some design discussion - maybe you can upload a design document to check and discuss with hengsin previously
Deepak: Carlos, do you mean design document needed for Idempiere-1770 or related to Auto ASI features with document level mandatory rule?
CarlosRuiz: the new ticket
Deepak: ohk, I need to research, I think there may be design document
Deepak: Or I need to document your proposal in 2nd Jan 2013 meeting
CarlosRuiz: that's not a design
Deepak: I think we discussed that topic very well. So may be I know how can we do that
CarlosRuiz: don't worry - if is not too hard - sometimes is easier to do it and show a patch
CarlosRuiz: hieplq, did IDEMPIERE-1461 work with nmicoud suggestion?
hieplq: hi CarlosRuiz, no work
CarlosRuiz: ok - let me take a look
CarlosRuiz: :-) forgot that feature is not on r2
hieplq: :)
nmicoud: wow, i've never look how to add feedback to processes - that's so good :) thanks
CarlosRuiz: yep - better than a "Processing" message :-)
nmicoud: definetely :D
CarlosRuiz: hmm - seems like a bug of dev? I used change role - and the favourites didn't refresh to reflect new role
nmicoud: probably ; it's ok on my version (sources of january)
CarlosRuiz: my fault - I think I messed up the roles
CarlosRuiz: yep - role access update fixed it
nmicoud: ok ; If you have time today, could you have a look at https://idempiere.atlassian.net/browse/IDEMPIERE-1899 ? about what we talker friday (default mail text per user)
CarlosRuiz: sure
CarlosRuiz: hieplq, I don't understand what you're trying to achieve with IDEMPIERE-1461
nmicoud: thanks Carlos
CarlosRuiz: M_InOut has two zoom conditions configured
hieplq: when receitp line is empty, when zoom, i want goto material receipt
hieplq: current it goto shipment window
CarlosRuiz: from which window?
hieplq: I add condition logic to achieve it
hieplq: from Invoice (Vendor) window, tab landed costs
hieplq: I see case empty file in other window
CarlosRuiz: I see - that must not be needed
Deepak: Carlos, for ticket IDEMPIERE-1905 it is good to identify which process to be updated
Deepak: I think we had list of all iDempiere process, sometime back I shared
CarlosRuiz: yep Deepak - good idea
Deepak: Carlos, You may have access to that list on google drive
Deepak: We created one when working on linking to next document from process
hieplq: why it is not need? It's zoom to wrong window?
CarlosRuiz: I mean - must not be needed - seems like a bug elsewhere
CarlosRuiz: if none zoom condition apply - then the table zoom windows are applied
CarlosRuiz: and for M_InOut is defined shipment for sales and receipt for purchases
hieplq: when field is empty, defaut method chech isSO always true, it's root reason of zoom wrong windown
hieplq: it's can resolve by condition logic. but it's must add logic, irgore check sql where when case empty
hieplq: because when empty, check sql where return false => irgore result check of condition logic
CarlosRuiz: hieplq, traced to MLookup line 577
hieplq: yes. it always return true in case empty
CarlosRuiz: is not checking context - just doing a select
hieplq: context is check when code next run
CarlosRuiz: no, I mean - not in zoom condition
CarlosRuiz: but the default zoom
hieplq: current: condition is evaluate, when result is false (return 0), default zoom is evaluate, but it wrong because DB.isSOTrx always true
hieplq: it will working perfect when i add new condition line for empty case, just add logic condition, no add sql where.
hieplq: but it's more good when add logic. ignore evaluate "sql where" when record is empty
CarlosRuiz: attached a patch to check the context of window for default zoom (not zoom condition)
CarlosRuiz: that must work with most of windows - except windows like payment that combines so/po trx in same window
hieplq: ok. will test it. thanks very much. see it more good than my idea :)
hieplq: I'm tested it's working perfect.
CarlosRuiz: hieplq, JanThielemann, not my intention :-) but seems the patch also solves IDEMPIERE-1862
hieplq: will test it now
hieplq: CarlosRuiz. yes. it's also resolve.