For the complete documentation index, see llms.txt. This page is also available as Markdown.

How relationships work in Freelucy

Open Freelucy from any CI and start mapping.

YouDesign Freelucy opens on a single CI, your primary element. From there you add other records as upstream or downstream relationships, remap them between sides, and remove them. You do this in whichever view fits the task, and nothing is written to your CMDB until you click Commit.

The primary element with upstream and downstream relationships
Upstream relationships sit on one side of your primary element, downstream on the other.

The mental model

  • Primary element. The record you opened Freelucy from. Every view centers on it.

  • Upstream and downstream. Relationships have a direction. Freelucy keeps the two sides separate so you always know which way a relationship points.

  • Data Hub. The drawer you pull records from to relate to your primary element. See Find records with the Data Hub.

  • Views. Three ways to see and edit the same record: Classic, Flow, and List. Staged edits are shared across all of them. See Choose a view.

  • Stage, then commit. Every edit is staged first. You review the full batch before anything reaches ServiceNow.

You can only map allowed relationships. Freelucy shows tables and relationship types that are defined as suggested relationships or approved by your administrator. If you need a relationship that is not available, ask your administrator to add it. See Manage suggested relationships.

Two ways to add a relationship

Every view supports the same two gestures:

  1. Click to add. Find a record in the Data Hub and use its Add to Upstream or Add to Downstream action. This is the most forgiving path and works the same in every view.

  2. Drag to add. Drag a record from the Data Hub onto a valid drop target. Freelucy lights up only the sides your metamodel allows.

Stage, review, commit

Stage, review, then commit
Staged edits live on the canvas until you commit them as one batch.

Until you commit, every edit is a stage. You can keep adding, remapping, and removing for as long as you like. When you are ready, commit your changes and Freelucy writes the whole batch to ServiceNow at once. Discard instead, and everything staged is dropped.


What's next

Last updated