Controlling the Visibility of an Object Function

When you create an object function named doSomething() on an object named Example, the following is true by default:

• other scripts on the same object can call it,

• any script written on another object that obtains a row of type Example can call it

• external systems working with an Example object via Web Services, cannot call it

• it displays in the Row category of the Functions tab on the Expression Palette.

You can alter some of this default behavior by changing your doSomething() object function's Visibility setting. If you change its Visibility to the value Callable by External Systems, then an external system working with an Example object will be able to invoke your doSomething() via Web Services. Do this when the business logic it contains should be accessible to external systems.

If instead you change the Visibility to the value Hidden in Expression Builder, then doSomething() will not display in the Row category of the Functions tab of the Expression Palette, and it remains inaccessible to external systems. Do this when you want to discourage colleagues from inadvertently invoking the doSomething() function directly because you know that its correct use is limited to being called by some other script on the Example object.