Cprime Apps has been rebranded as Anova Apps. Please note the only effect is the company name - all of our products’ names, logos, functionalities, support, etc. is exactly the same. The new location to our documentation space is https://anovaapps.atlassian.net.
User-defined routines (UDR) are functions that perform specific actions that you can define in your SIL™ programs for a later use. These can considerably improve the readability and maintainability of your code.
The name of the UDR cannot contain spaces.
Definition of UDRs must be done before the code, even though it is not used anywhere up to that point. Therefore, the following code is invalid.
However, you are allowed to declare global variables and constants before function definitions:
Running the above code in the Power Scripts for JIRA (formerly known as JJUPIN) Runner gadget:
The list of parameters in the definition of a UDR can be of any length (including 0) and their respective types can be any valid SIL™ type.
UDRs use a "pass-by-value" policy. This means that even though you modify the value of a parameter in your function, on exit the value will be lost.
Parameters of user-defined routines can be made read-only in the scope of the routine by adding the keyword "const" before the parameter definition in the signature of the routine.
There are three categories of variables that can be used in a UDR:
These are the variables you define in the body of the UDR. These can be used throughout the body of the UDR. On exit, the values of these variables are lost.
These are the values passed to the UDR in the list of parameters. Because SIL™ uses a "pass-by-value" policy, even though you modify the value of these variables in the body of the function, on exit, their original values will be restored.
These are the variables that are already defined and can be used right away (issue fields, customfields and any variables defined before the routine). You can use issue fields and custom fields anywhere in your code (including in the UDR body) without having to declare them.
Notice that the key variable is a standard issue field that you could otherwise use anywhere in your SIL™ program without having to declare it.
Return values can be used to communicate with the context that called the UDR or to halt its execution.
Notice that there is no need to declare the type of the return value; this will be evaluated at runtime. Therefore, even though the check on the following program will be ok, at runtime the value of d will NOT be modified because of the incompatibility between date (on the right-hand-side) and number (on the left-hand-side).
There can be only one return value (at most). If you would like to return more values of the same type, consider using an array or a struct.
You can return simply from a routine without specifying a value. However, you should always remember that by design routines return a value, even if it is undefined. The following code is therefore valid:
Of course, the above code will print the text 'S IS NULL' in the log.