What are the benefits of Custom Functions and how do they differ from External Action Blocks?
Custom Functions
- Available in all subsets without scoping.
- Bound to a domain only (i.e. Text) so you can pass any view with same domain.
- Return values can be used as arguments to other functions and statements.
- QAT Custom Function Manager automates the consumption and management of internal and third party function libraries.
External Action Blocks (EABs)
- Must be explicitly scoped.
- Bound to a Gen view (i.e. import entity or workset view) so you must pass the same view.
- Return values cannot be used as arguments to other functions or statements.
- No automation for third party library consumption.
Custom Functions are implemented with runtime libraries, and behave just like any other native Gen function. Once registered, they must be deployed one time and are always available for use. Select the function from the list, provide its parameters, and go!