Projects

A Project is a container that groups related building blocks — integrations, mappings,
data types, crosswalks, comparisons, data processor jobs and app instances — so that
everything belonging to one initiative can be found, reviewed and monitored in one place.

Projects don't change how anything runs. An integration behaves identically whether or not
it belongs to a project. What projects give you is a working view: "show me everything
involved in the Epic ADT feed, and how it ran last night."

When to use a project

Create one per real-world piece of work — a go-live, a customer, a data feed, a migration.
Typical examples:

• Epic ADT Feed — the interface, the integration that processes each message, the
  mappings it calls, and the app instance it writes to
• Nightly Lab Results Load — the scheduled integration, its data processor job, and the
  crosswalks it references
• Castle Rock Migration — everything built for a one-time backload

Creating a project

1. Go to Connect → Projects.
2. Select New Project.
3. Give the project a Name and a Description. Descriptions are worth writing —
   they're what makes a project list readable six months later.
4. Save.

Adding resources

A project can contain any of these resource types:

Resources are added in one of two ways, and the project records which:

• Manual — you added the resource yourself. Manual entries are never removed by a sync.
• Sync — Intely discovered the resource by following references out from something
  already in the project.

Syncing a project

Sync walks the resources already in the project and pulls in everything they depend on.
Add one integration and sync, and the project fills in the mappings that integration
converts with, the crosswalks it looks values up in, the app instances it calls, and so on.

Because sync is reference-driven, each resource in a project also records what references
it — so you can see that a given mapping is used by three integrations before you change it.

Sync only adds; it never removes anything you added manually. If you deliberately
included a resource that nothing else points at, a sync will leave it alone.

Monitoring a project

Opening a project shows its resources plus recent integration executions for the
integrations inside it, with Status, Started At, Ended At and Run Time, and a
link through to the execution log. A run still in progress can be terminated from here. This is
the fastest way to answer "did last night's feed run?" without filtering the global executions
list.

Deleting a project

Deleting a project removes the grouping only. The integrations, mappings and other
resources inside it are not deleted and continue to run.

Deletion is not exposed as an undo in the interface, so treat it as final — but because the
resources themselves survive, recreating the project and re-adding them loses nothing but the
grouping.