Define which relationship types are valid between which classes.
Suggested Relationships are the rules that tell Freelucy which relationship types are valid between which classes. They drive two things:
The dropdown of target tables that appears when a user opens Freelucy on a CI.
The list of permitted relationship types when the user drags one element onto another.
If a class pair has no suggested relationship defined, Freelucy will not let users connect them. This is intentional — it's how Freelucy enforces your CSDM and metamodel governance.
Open the Suggested Relationships table
From the application navigator, go to Relationships → Suggested Relationships.
You'll see every rule currently in effect. Each row is a triple: a base class, a relationship type, and a dependent class.
Create a new suggested relationship
Click New on the Suggested Relationships table.
The new-record form opens.
Fill in:
Base class — the class on the upstream side.
Relationship — the relationship type from cmdb_rel_type.
Dependent class — the class on the downstream side.
Save.
The rule is now active. Users opening Freelucy on a record of the base class will see the dependent class in the picker, and the chosen relationship type will be available when they connect them.
Direction matters. Suggested Relationships are directional. If you want users to be able to map both ways between two classes, define two rules — one for each direction.
