Hi Chaturika, We got your point and we will consider this improvement for a next release with a proper graphical representation.
BTW, we are encouraging users to write self contained custom functions as much as possible to reduce the complexity. So that its better to define constants within the custom function scope. Without having a proper graphical representation of the connectivity between a custom function and a global constant, facilitating such a feature might lead to a confusion. We had to introduce global variables concept, since there was no other option to achieve some use cases. Thanks, Viraj. On Fri, Jul 22, 2016 at 5:03 PM, Chathurika De Silva <[email protected]> wrote: > Hi ESB Team > > Currently the constant operator provides just a setting of value and > mapping to an output. In the present mapping configuration the constant is > not defined as a constant, rather the defined value is assigned directly to > the relevant output. > > If there is a mechanism to define a global constant, this can be reused > (e.g. in custom functions) and hence will upgrade the usage of the data > mapper as well. I have created [1] for this and hope this will be > considered as this will add a greater value. > > [1] https://wso2.org/jira/browse/DEVTOOLESB-640 > > Thank You > Erandi > > -- > *Chathurika Erandi* > Senior Software Engineer, > WSO2 Inc. > > *E-mail:* [email protected] > *Mobile: *+94714 328 612 > *Blog*: chathurikaerandi.blogspot.com > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
