Certain service parameters populate some recommended values under static values.
For methods, if the ability to map the input parameters to an existing or possibly even custom list of static values was added, it would be helpful for configuring that method call later and even help the original developer convey the type of inputs that are expected for a particular input parameter.
Currently, that would need to be documented externally or the developer would have to go into the method canvas itself and determine how that input is expected.
Configurable Static Values
-
- Posts: 178
- Joined: August 31st, 2021, 11:37 am
- Contact:
-
- Posts: 472
- Joined: November 16th, 2021, 11:15 am
- Contact:
Re: Configurable Static Values
I talked with Jeff on this and got clarification.
If you make a method, you might have a parameters like:
Action: Add/Update/Delete
SkipPriceCalculation: True/False
And it would accept only the values specified. But the developer using the prebuilt method will not know this and could give "Edit" as the action or "true"/"yes" as the SkipPriceCalculation value.
This feature request is to have some static text that gives future developers guidelines on what type of data the method parameters accept.
If you make a method, you might have a parameters like:
Action: Add/Update/Delete
SkipPriceCalculation: True/False
And it would accept only the values specified. But the developer using the prebuilt method will not know this and could give "Edit" as the action or "true"/"yes" as the SkipPriceCalculation value.
This feature request is to have some static text that gives future developers guidelines on what type of data the method parameters accept.
word count: 83
-
- Posts: 472
- Joined: November 16th, 2021, 11:15 am
- Contact:
Re: Configurable Static Values
This is being tracked in task #10009 and is related to forum post viewtopic.php?t=44
word count: 17