Notifications
Clear all
Topic starter
Hello Chuggers!!
I am in the process of creating a custom text function that I would like to have available through the system (within a VFE form and callable from a quick text).
I have written the function and saved it as a text component. When I manually add the text component within an encounter, I can them activate this function from a quick text successfully.
I would like to not have to manually add this text component in the encounter (nor do I really want to add this text component to my encounter definition - Document Templates).
Is there a good/best place to add this text function so that it is available inherently through the system/encounters?
I was thinking about adding my function to either: mellib.txt, usrlib.txt or usrlibccc.txt files. Looking for other suggestions on how others have fulfilled the need to include a custom text function within the system. Did you create your own custom text file that would be loaded as part of CPS startup through a "load ... " call from usrlib or usrlibccc files?
Any comments or feedback would be appreciated.
Thank you in advance for picking your brains.
Posted : November 26, 2018 8:06 am
I'm thinking that usrlib.txt is the way to go if you want to get to it everywhere. I have stayed with using custom function libraries and calling them when needed. I just find this to be the cleanest way to go for me, but your experience could be different. Lee did a great break down of the pro/cons of how to access the functions you write:
https://forum.centricityusers.com/forum/using-libraries-for-mel-functions/#answer-190349
Posted : November 27, 2018 1:35 am
