Building Blocks > Domain-Specific Building Blocks > Reason Code Building Block > Implementation Model (Reason Code Building Block)
Implementation Model (Reason Code Building Block)
The following diagram shows the relationships between the main Thing Shapes, Thing Templates, and Things in the reason code building block, and their relationships with entities in other building blocks.
Diagram showing the entities in the reason code building block, including which entities implement, extend from, or are dependent upon services in other entities.
In the diagram, arrows with hollow heads and solid lines () indicate that an entity extends from the entity to which the arrow points, arrows with hollow heads and dashed lines () indicate that an entity implements the entity to which the arrow points, and arrows with open heads and dashed lines () indicate that an entity has a dependency upon services on the entity to which the arrow points.
The significant entities in the reason code building block include the following:
In the PTC.ReasonCode project:
PTC.ReasonCode.EntryPoint—Entry point Thing for the reason code building block.
PTC.ReasonCode.EntryPoint_TT—Thing Template for the reason code entry point.
PTC.ReasonCode.Manager_TT—Thing Template for the reason code building block manager. Contains implementation code for services defined in the PTC.ReasonCode.Management_TS Thing Shape. Note: This building block does not have a manager Thing, as it is an abstract building block that is paired with an implementation building block.
PTC.ReasonCode.Management_TS—Management Thing Shape for the reason code building block. Used to define the services for the reason code building block functionality.
PTC.ReasonCode.ModelLogic_TS—Model logic Thing Shape for the reason code building block. Used to give individual models access to model-specific services for this building block.
PTC.ReasonCode.TreeSelectorManagement_TS—Thing Shape that holds the tree selector services.
PTC.ReasonCode.ReasonTree_MU—Mashup containing a tree widget for displaying a nested hierarchy of reasons.
In PTC.ReasonCodeImpl project:
PTC.ReasonCodeImpl.EntryPoint—Entry point Thing for reason code building block.
PTC.ReasonCodeImpl.Manager—Manager Thing for the reason code implementation building block.
PTC.ReasonCodeImpl.EntryPoint_TT—Entry point Thing Template for reason code building block.
PTC.ReasonCodeImpl.Manager_TT—Thing Template for the reason code implementation building block manager. Contains implementation code for the services defined in the PTC.ReasonCode.Management_TS Thing Shape.
Was this helpful?