Similar to Window Customization, this ticket implements a Process Customization feature:
I reviewed our code and created a patch that you can find attached.
I integrated this to trunk with a new peer review commit with minor modifications.
However I think the ticket gets short, if possible can you please add also the following columns in AD_UserDef_Proc_Parameter:
AD_Reference_ID (as advanced field)
AD_Reference_Value_ID (as advanced field)
AD_Val_Rule_ID (as advanced field)
DefaultValue2 (as advanced field)
I'm working on that and I will soon submit the patch for review
As you suggested I added some new columns as follows:
When you have some time, please review the new patch
Thanks , integrated your new patch.
Just wondering if the IsRange is OK as a flag, or maybe would be better to be a _Yes_No list and allow to customize a range parameter into a normal and viceversa.
The IsRange field is readonly, filled by a callout with the same value from the original parameter just to be used on display logic for DefaultValue2 and Placeholder2 fields.
Maybe should I only used the context insted of creating this field.
Anyway i think that a parameter should not be customized as range by users, as it may need code changes.