Visibility Configuration
This configuration controls the visibility of an object, such as a connection or node, within and between packages.
Setting visibilty
To set the visibility of an object:
- Right-click the object.
- From the context menu, select
Configure visibility. The settings window opens. - Choose one of the following visibility levels:
| Name | Icon | Visibility area |
|---|---|---|
| Private | Available only in the current module | |
| Protected |  |
Available only in the current module and its supernodes |
| Internal |  |
Available only in the current package |
| Public |  |
Available in all packages. To use the object in another package, you must reference the object's package. |
| Published |  |
Available in all packages and as a web service. Choose it when you publish the node as a web service. |
Specifics
When you publish a node, the name you set for it becomes the web service method's endpoint. This name can also be used as the /Node parameter in batch processing.
If a node is inside a supernode hierarchy, all parent supernodes must also be visible to make the node available according to its visibility configuration.
By default, all modules of a package have "public" visibility (i.e., are available in all packages).
Using objects from other packages
To use objects from other packages, such as workflow nodes, connections, or derived components, you must set their visibility to Public and create a reference to the package they are in.
The process of creating a package reference is described in Referencing Packages.
Briefly:
- In the Navigation pane, right-click
References. - Select
Add. The Add reference to package window opens. - In the Package file path field, enter the file path for the package you want to access.
- Click Add.
After you create the reference, you can access the objects from the external package through Reference node or Node execution nodes. This also allows you to use the package's derived components.
Read on: Workflow Progress Control