Skip to content
Last updated:

Use Projects

Create a project, fill its repository, draw its architecture and write the guide for the next team.

Each card shows a project’s key, name, tags, how many documents and connections it has, its version and state. Search finds a project by name, key or tag; Awaiting my approval shows the ones waiting for you.

Anyone with access to the environment can create one.

  1. Click New project.
  2. Fill Name and Key: up to 16 letters, digits or hyphens, unique in the environment. Add tags if you want.
  3. Under How does V1 start?, choose From documents, From this environment or From scratch.
  4. Fill the Version 1 title and the description, and add members: people who already have access to the environment.
  5. Click Create project and open V1. You become its Admin and Approver.
  • At the top: name, tags, Version & approvals and Mapper AI.
  • The version bar: which version you are looking at and its state. Working version accepts changes; Preserved delivery is read-only.
  • Three tabs: Repository, Architecture and History.
  • On the right: what this delivery holds, the approvals, the people, and the proposals waiting for review.

On an open version, click Add to repository and choose:

  • Upload a file, with a category: code or technical artifact, functional specification (EF), technical specification (ET), guide or other document, or transport;
  • Document URL, for a document that lives elsewhere;
  • Connect environment objects, to reference iFlows, packages, API proxies, queues, systems or schemas.

Accepted files are PDF, Word, Excel and PowerPoint (DOCX, XLSX, PPTX), ZIP, and text or code files such as TXT, CSV, ABAP, CDS, Groovy, JavaScript, JSON, YAML, XML, XSD, WSDL and SQL. Files can have up to 40 MB by default. The limit and the storage of the environment are set by the Integration Mapper team; admins see them in Settings → Projects.

Click an item to download it, upload a new revision, remove it from this version (earlier versions keep it) or, for a reference, open it in the Map, Explorer, Schema, Monitoring or Analytics.

After each upload, the text of the document is read and Integration Mapper proposes:

  • links to the environment objects whose names appear in it;
  • dated milestones;
  • the specification code from its first page.

Nothing proposed counts until someone confirms it. Click Review suggestions and Confirm or reject each one. An interface that is not in the environment can be kept as planned or discarded.

On the Architecture tab, click Edit architecture & connections:

  • Generate from environment draws the systems and interfaces the project references;
  • Add system and Add planned interface add what the environment does not have yet. A planned interface stays planned until a sync brings an iFlow with its name;
  • Open in Document Flow to arrange the drawing, then Save to project;
  • Link existing and Re-check after sync match planned interfaces with what the sync found, by exact name.

Edit guide, at the end of the repository, holds what the next team needs to know, up to 18,000 characters. An Admin approves it as the version’s summary.

Where your environment has Mapper AI for projects, Ask Mapper AI answers questions about the project, and Run Mapper AI reads the documents of the version and proposes facts, interfaces and architecture for review.

Manage, under People, lets an Admin change roles and the Approver mark, and add people who already have access. People without access can be invited only from accepted email domains, set in Settings → Projects.