Fabric Project Tree
A Fabric project has a tree-like structure. Known as the Project Tree, it displays components in a hierarchical order. Each entity in the tree initiates a different action.
The Project Tree is displayed on the left side of the Fabric Studio window.
To initiate an action, right click on a component and select the action. For instance, right clicking on Broadway creates a new flow.
A current active project in the Studio has its name displayed at the top of the Project Tree, i.e., in the below example, the current active project is Demo_6_5.
Click for more information about Creating a New Project.
Project Tree Components
Each project has the following main components:
Shared Objects used by all Logical Units and project references and may include the following sub-branches:
Resources, files that can be saved as part of a project.
Environments
Templates
Logical Units - a collection of all Logical Units defined in the project.
References - reference information that can be used throughout the LU instances. References may include the following sub-branches:
Broadway
Java, Functions, Globals, Resources
Translation
IID Finder
Web Services - a collection of functions that can be exposed through Fabric’s Web Service layer. Web Services may include the following sub-components:
- Broadway
- Java
- Resource files and Graphit objects.
Initiating an action may be done by any of the following three methods:
right-click on the context menu in the Project Tree
using the Fabric item (top menu bar)
via View > command Palette… (top menu bar)
Project Tree Components
Each project has the following main components (under Project > Implementation):
Logical Units / Data Products - a collection of all Logical Units / Data Products defined in the project. Of this collection, two system logical units - that exist by default in any project - are References and Web Services:
- References - reference information that can be used throughout the logical units, such as reference common tables.
- Web Services - a collection of functions that can be exposed through Fabric’s Web Service layer. Web Services may include [Java WS](), [Graphit WS]() and supportive Broadway flows.
Shared Objects - are used by all Logical Units and project references and may include the following sub-branches:
- Broadway
- Interfaces
- Custom Interface Types
- Java Functions, Globals
- Resources, files that can be saved as part of a project.
lib - Java library files, required by a project, such as utility JARs or JDBC drivers, that are not provided as part of the product.
Note: The project-resources folder resides at the project tree is not part of the Fabric project but it is a useful folder you can use at your workspace.
Click for more information about UI Components and Menus.
Project Components Prefix Conventions
Using a common prefix for each project component improves maintenance throughout a shared implementation.
The following table lists the recommended project component prefixes conventions:
|
Component |
Recommended Prefix |
|
Function |
fn% |
|
Input Parameter |
i_% |
|
Output Parameters |
o_% |
|
Web Services |
ws% |
|
Table Population |
pop% |
|
Instance Group |
Ig% |
Note that when using the above prefix conventions, it is also recommended to use meaningful names for the project’s components.
Fabric Project Tree
A Fabric project has a tree-like structure. Known as the Project Tree, it displays components in a hierarchical order. Each entity in the tree initiates a different action.
The Project Tree is displayed on the left side of the Fabric Studio window.
To initiate an action, right click on a component and select the action. For instance, right clicking on Broadway creates a new flow.
A current active project in the Studio has its name displayed at the top of the Project Tree, i.e., in the below example, the current active project is Demo_6_5.
Click for more information about Creating a New Project.
Project Tree Components
Each project has the following main components:
Shared Objects used by all Logical Units and project references and may include the following sub-branches:
Resources, files that can be saved as part of a project.
Environments
Templates
Logical Units - a collection of all Logical Units defined in the project.
References - reference information that can be used throughout the LU instances. References may include the following sub-branches:
Broadway
Java, Functions, Globals, Resources
Translation
IID Finder
Web Services - a collection of functions that can be exposed through Fabric’s Web Service layer. Web Services may include the following sub-components:
- Broadway
- Java
- Resource files and Graphit objects.
Initiating an action may be done by any of the following three methods:
right-click on the context menu in the Project Tree
using the Fabric item (top menu bar)
via View > command Palette… (top menu bar)
Project Tree Components
Each project has the following main components (under Project > Implementation):
Logical Units / Data Products - a collection of all Logical Units / Data Products defined in the project. Of this collection, two system logical units - that exist by default in any project - are References and Web Services:
- References - reference information that can be used throughout the logical units, such as reference common tables.
- Web Services - a collection of functions that can be exposed through Fabric’s Web Service layer. Web Services may include [Java WS](), [Graphit WS]() and supportive Broadway flows.
Shared Objects - are used by all Logical Units and project references and may include the following sub-branches:
- Broadway
- Interfaces
- Custom Interface Types
- Java Functions, Globals
- Resources, files that can be saved as part of a project.
lib - Java library files, required by a project, such as utility JARs or JDBC drivers, that are not provided as part of the product.
Note: The project-resources folder resides at the project tree is not part of the Fabric project but it is a useful folder you can use at your workspace.
Click for more information about UI Components and Menus.
Project Components Prefix Conventions
Using a common prefix for each project component improves maintenance throughout a shared implementation.
The following table lists the recommended project component prefixes conventions:
|
Component |
Recommended Prefix |
|
Function |
fn% |
|
Input Parameter |
i_% |
|
Output Parameters |
o_% |
|
Web Services |
ws% |
|
Table Population |
pop% |
|
Instance Group |
Ig% |
Note that when using the above prefix conventions, it is also recommended to use meaningful names for the project’s components.
