Recommendations for creating user-defined functions

• Try to make user-defined functions as generic as possible to increase the likelihood that the function will be reused. For example, if you must create a very complex function, consider splitting it up into two or three small functions that are more likely to be reused.
• Do not create user-defined functions in a production study or library. Instead, create them in a test study or development library.
• If you create a user-defined function, you must add the assembly as a reference in your function project and add a namespace for the assembly. The namespace is:

  Designer.UserDefinedFunctions

• Use C# attributes to categorize user-defined functions. Attributes are already defined in predefined functions.
• Oracle recommends testing the following parts of a user-defined function:
  • The user-defined function must encapsulate the logic that is required.
  • The correct data points must have been used as parameters.
  • The function must be deployed to the Oracle Health Sciences InForm application and tested with real values.
• Consider creating a repository of user-defined functions that all users can access. A central repository is especially useful if users are working in different locales or if any part of the study is being outsourced.