Difference between revisions of "NF11 Min Max Validation Process Parameters"

From iDempiere en
m
(Document)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Goal:''' Functional
+
'''Goal:''' Technical
  
'''Developer:''' [[User:Hieplq|Hieplq]]
+
'''Developer:''' Zuhri Utama, [[User:Hieplq|Hieplq]]
  
 
'''Feature''' '''Ticket:''' [https://idempiere.atlassian.net/browse/IDEMPIERE-5062 IDEMPIERE-5062]
 
'''Feature''' '''Ticket:''' [https://idempiere.atlassian.net/browse/IDEMPIERE-5062 IDEMPIERE-5062]
Line 8: Line 8:
  
 
===Description===
 
===Description===
It seems the min/max validation for process parameters is not implemented at all.
 
  
Maybe we can consider hiding those fields until implemented.
+
Now you can define minimum and maximum for process parameters with type Integer, Amount, Date, Number, Quantity, Cost+Price or. String.
  
The minimum implementation must cover the same as AD_Column (DisplayLogic and numbers)
+
Configuration is as usual:
  
Also it would be interesting to add support for dates (see [https://idempiere.atlassian.net/browse/IDEMPIERE-5052 IDEMPIERE-5052])
+
[[Image:01_MinMaxProcessPara.png]]
  
 
+
[[Category:New Features|T]]
[[Category:New Features|D]]
+
[[Category:New Features w11|T]]
[[Category:New Features v9|D]]
 
[[Category:To Be Documented]]
 

Latest revision as of 16:59, 5 January 2024

Goal: Technical

Developer: Zuhri Utama, Hieplq

Feature Ticket: IDEMPIERE-5062

Description

Now you can define minimum and maximum for process parameters with type Integer, Amount, Date, Number, Quantity, Cost+Price or. String.

Configuration is as usual:

01 MinMaxProcessPara.png

Cookies help us deliver our services. By using our services, you agree to our use of cookies.