Marketing Committee Meeting 20230609

From iDempiere en

Date: 2023-06-09
Time: 12:00 UTC
Venue: Mattermost - Channel: Marketing
Called by: Marketing Committee

You can find the detailed meeting here:

Summary of the day
Meeting led by: Diego
Meeting notes and follow-up actions: Diego
Attendance list: Eugene, Chuck, Diego, Carlos

  1. What's new from last two weeks?
    • Bug fixes
      • IDEMPIERE-4836 Adding Access tab on Document Status (Activity) - fix issue with native sequence
      • IDEMPIERE-5216 HTML report Record ID Trl fix
      • IDEMPIERE-5407 Fix Wrong getIdColumnName Validation
      • IDEMPIERE-5507 Sync Print format items with Report view columns fix
      • IDEMPIERE-5643 Error during document's workflows are not displayed on Workflow Activities form.
      • IDEMPIERE-5645 fix NPE on report Script columns
      • IDEMPIERE-5683 Exception: NO Data found for Record_ID
      • IDEMPIERE-5723 NPE when allocate has both AR and AP invoice
      • IDEMPIERE-5740 Dashboard Views Gadget doesn't translate *24.png image name to z-icon name
      • IDEMPIERE-5741 Text editor dialog not using ThemeManager.isUseCSSForWindowSize() correctly
      • IDEMPIERE-5742 Info Product Window: Footer cut off after execution of query
      • IDEMPIERE-5748 currencyrate - date is not truncated
      • IDEMPIERE-5753 Date Picker doesn't set time on first date in Quick Mode
      • IDEMPIERE-5755 Empty value preference logs false parsing error on Dates
      • IDEMPIERE-5756 2PackActivator: should check Adempiere.isStarted instead of getThreadPoolExecutor
      • IDEMPIERE-5759 Fixed potential NPE when sending a null orderclause
      • IDEMPIERE-5766 Recreate Storage Reservation is creating records for non-stocked products
    • Technical Improvements
      • IDEMPIERE-5567 Support of UUID as Key (FHCA-4195) - ChangeLog - FKRules - Recent Items - Toolbar
      • IDEMPIERE-5721 Fill AD_ZoomCondition.SeqNo
      • IDEMPIERE-5730 Context is not parsed in exception message logs thrown from processes
      • IDEMPIERE-5754 Check PInstance_ID before Process Lock DB Update, PInstance 0 on createPricelist
      • IDEMPIERE-5763 Improve reliability of stopping a scheduler
    • Functional Improvements
      • IDEMPIERE-5687 Base Price List
      • IDEMPIERE-5739 Allow Inventory Valuation Report for more than one warehouse
      • IDEMPIERE-5746 Bank Statement and Production cannot use Overwrite Date/Seq on Complete
    • Development Improvements
      • IDEMPIERE-5697 Improve Process Log for more advanced logging options for Processes
      • IDEMPIERE-5735 Useless code in GridTable.dataSave
      • IDEMPIERE-5744 MDashboardPreference.getForSessionQuery: add client filter and remove order by ad_client_id
      • IDEMPIERE-5758 Improve extensibility of ReplenishReportProduction
    • Usability Improvements
      • IDEMPIERE-5743 Info Window: Add Optional Auto Collapsed Parameter Panel option
      • IDEMPIERE-5749 CreatedBy fields should not be forced to be Search if used from processes/info windows
      • IDEMPIERE-5751 Displayed Linked Order field in Purchase and Sales Order
      • IDEMPIERE-5765 Shipment generated service lines cannot be directly edited because the Locator is empty
    • Test Improvements
      • IDEMPIERE-5762 org.idempiere.test-feature should include org.idempiere.test
    • Community news
  2. Sponsorship initiative follow-up - Submission template
    • Some quick finds on the web:
    • This initiatve will initially be limited to top makers. While we learn how to do it, so it is better to start with people the project already has a strong relationship with.
    • Once we do it a couple of times and become more confident in the process, we can re evaluate this constraint
    • Initially we feel that we should have an official iDempiere profile/account.
    • @druiz will See if we're missing something important ->
    • create a form that can be filled with all that we have chosen here ->
    • present it for review in the next meeting
    • (based on the link shared by @chuckboecking and the creation process in the platform.
    • @druiz proposes the workflow to be like
    • Core team should approve the proposals, with their knowledge of the core, they can:
      • a) evaluate viability
      • b) assert that the budget makes sense, is not too low or too high
      • c) analyze potential side effects
      • etc ...
    • Once the project is approved the financial committee should take control over the initiative because of the reasons we just mentioned
    • Actions for next meeting to continue with this topic:
      • a) Review the links provided by @chuckboecking and the requirements to create a campaign
      • b) Open the iDempiere accounts on all platforms
      • c) Create the v1 of the submission form
      • d) Check if different account can be used depending on the campaign or if the account is linked to the profile
Cookies help us deliver our services. By using our services, you agree to our use of cookies.