Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Option to Include Pack Out data in Pack Out Results

Description

It would be very convenient to have an option to include the actual pack out data in the pack out results. This feature would prevent me from re-creating future versions of pack outs. Instead, I could just modify the pack out that got created during the pack-in process.

Here is an explanation:
Step 1:
I work in an environment where Developer A creates a plugin. Developer A creates a 2Pack.zip to accompany the plugin export that will be tested in Dev and QA environments.

Step 2:
Developer B installs the plugin (with 2Pack.zip) in a different environment for testing. Issues are found. Changes are made. Developer B must now recreate the pack out. Often times the packout can include 10+ lines. This process of re-creating the packout is cumbersome and error prone.

Step 3:
Repeat until plugin reaches production.

This concept (request) would be very beneficial for me as well. I create and destroy environments all the time. I find myself keeping entire servers around because I do not want to re-create the pack out.

Thank you for your consideration. Please let me know if you have questions.

Environment

None

Activity

Show:

Carlos Ruiz August 24, 2020 at 8:50 AM

Closing as potential idea after >6 years of inactivity.

MarcoL August 23, 2020 at 12:09 PM

triaging Marco Longo

only manual way still in 7.x

Marco

Hiep Lq June 15, 2014 at 10:40 AM


in meeting 20140528 we talk about this issue. i plan to start it.
please confirm with below flow:

1. at pack-out site always export MPackageExp data
2. at pack-in site. if is pack-in by install plug-in, ignore data of MPackageExp, don't import it.
3. at pack-in window, add check-box include "Package Exp". when dev check this checkbox, import MPackageExp other no import.
default of "Package Exp" should is true
4. with a MPackageExp is version up.
when pack-in will check it.
case current version in db < new version override data of MPackageExp
case current version in db >= new version show message to confirm override or non.

Hiep Lq May 27, 2014 at 5:45 PM

i see this improve is very good.
have two way to make it please advice:

auto: always make self pack-out for every pack-out info
in afterSave of pack-out, make two line pack-out detail, after that user can edit it.

manual: make new process and a toolbar button in pack-out window.
when run process make two line pack-out detail

Chuck Boecking March 20, 2014 at 6:47 PM

Hi Carlos and Hieplq,

I had not thought of using the Pack Out Type = Data option for this task. It took me a while to figure out the Data SQL syntax, however, I got it to work, and it works like a champ.

I documented the process here for future reference.
http://www.chuckboecking.com/blog/bid/379711/How-to-Pack-Out-your-Pack-Out-Details-Team-Development-in-iDempiere

Thank you for taking the time to read this and offer the suggestion. I gave you credit for helping find and document the correct answer. Is the way I gave credit acceptable?

Regards,
Chuck

Incomplete

Details

Assignee

Reporter

Labels

Components

Priority

Created March 19, 2014 at 2:32 AM
Updated October 2, 2020 at 4:14 PM
Resolved August 24, 2020 at 8:50 AM