we using allready 4th day info window processing option. i want to share: data generation is quite problematic, because no value preferences for process parameters. If user select wrong parameters produce very ugly data's !!
so i'm suggest to improve parameter fields process parameters with standard value preference option.
Workflow: Admin could predefine client/org wide then user override his predefined values for process parameters. User select rows to process, click to processing, and popup parameter window will load predefined parameter values.
standard sequential of idempiere is: default logic/Preference/DataType defaults
i think we can improve it with a new ticket.
this sequential should configurable.
i found one bug. First, i give you example for better understanding. If you have two process with same parameter, lets say Document Type, it is not possible to save value preference for each document type. Problem is in UNIQUE INDEX ad_preference_attribute (ad_client_id , ad_org_id , ad_window_id , ad_user_id , attribute). I suggest change column AD_Process_ID to NOT NULL DEFAULT 0 and add it to ad_preference_attribute INDEX.
These sql commands solved the problem, it should be added to your migration scripts:
DROP INDEX ad_preference_attribute;
CREATE UNIQUE INDEX ad_preference_attribute ON ad_preference USING btree (ad_client_id , ad_org_id , ad_window_id , ad_user_id , ad_process_id, attribute COLLATE pg_catalog."default" );
, i think great would be if the value preference is related to Process and Also Window (Info Window in this case). I noticed that you are setting only AD_Process_ID of value preference, not AD_Window_ID. Example: I have two windows which share one process, but user wants to set different value preferences for each Info Window Process. So Value preference should depends on process and info window. I think this should be very helpful.
Thanks for value feedback.
I remember changed constrain index. maybe it's lost when make patch.
about preference per process and window, it's in my mind.
can review step 4 in comment at "06/Jun/14 1:44 PM"
in your test it can't save per window + process, cause maybe by issue relate unique constrain.
i will fix bug and retest it.
again, many thanks in support me.
I find it .
unique constrain is define in AD (Table>Table Index). but I miss step run "index validate" to generate script
i update patch to fix your comment, please help me check it.