Enterprise object catalog
This reference lists every object type you can hold in a repository, what it represents, and where it lives. What your license lets you view or edit per type is summarized in the License capability matrix; how to create and organize items is covered in Manage items.
The Lives in column names the only place an item of that type can be created or moved to. It takes three forms:
- A root folder name — the item belongs to that object family and lives in that root folder or a subfolder of it.
- Repository root or folder — the item lives directly under the repository or in a folder you create there. It cannot go inside an object family's root folder or anything beneath it.
- On the object it applies to — the item attaches to another item, so it appears throughout the tree.
| Object | Represents | Lives in |
|---|---|---|
| Activity | A step of a process | Processes |
| Business Service | A service offered to internal or external parties | Business Services |
| Capability | Knowledge or ability needed to execute the business | Capabilities |
| Chart | A graphic view of performance indicators — see Create a chart | on the object it applies to |
| Class | A data or implementation class used by IT | Classes |
| Control | A control around your activities — see Risks and controls | Controls |
| Control Instance | A control applied to a specific object | on the object it applies to |
| Dashboard | A gadget page that visualizes repository content | DashboardsDashboard A configurable view in Process360 Live that aggregates KPIs, charts, and filters across one or more processes for stakeholders to monitor performance. |
| Diagram | A web-authored diagram | repository root or folder, or a Simulation Project |
| External Agent | A party outside your enterprise, such as a customer or vendor | External Agents |
| External Data | An uploaded spreadsheet that feeds simulation | repository root or folder |
| External File | A non-iGrafx document, such as a Word or PDF file | repository root or folder |
| Folder | An organizational container | repository root or folder |
| Glossary / Term | Your organization's vocabulary | Glossaries |
| IGX Diagram / IGX Document / Component | Content authored in the iGrafx desktop client | repository root or folder |
| Interface / Service / Operation | What a system offers: its interfaces, services, and operations | Interfaces |
| Journey / Moment / Touchpoint | A stakeholder journey and its moments and touchpoints | Journeys |
| Opportunity | The potential positive effect of taking on a risk | Opportunity Catalog |
| Opportunity Instance | An opportunity recognized on a specific object | on the object it applies to |
| Performance Indicator | A measurement on a business object — see Performance Management | on the object it applies to |
| Process | A process that produces your products or services | Processes |
| Product | A physical or non-physical product sold or processed | Products |
| Report | A saved report definition or narrative template | Reports |
| Requirement | A requirement on other repository objects | Requirements |
| Resource | People, roles, organizations, systems, equipment, and locations | Resources |
| Risk | A risk inherent in your business — see Risks and controls | Risk Catalog |
| Risk Instance | A risk recognized on a specific object | on the object it applies to |
| Shape Library | Custom shapes for web diagrams | Shape Libraries |
| Shortcut | A link to another repository item | wherever its target could go |
| Simulation Project | A process simulationProcess Simulation Running a designed process model against scenarios (volumes, resources, durations) to predict performance before making real-world changes. setup | repository root or folder |
| Strategy / Goal | A long-term plan and the goals it pursues | Strategies |
| Table | A tabular view of performance indicators — see Create a table | on the object it applies to |
| Web Address | A URL to a page outside the platform | repository root or folder |
| Work Product | Material or information that flows between processes and parties | Work Products |
Business Service
Represents a service available to external and internal parties, including indications of service levels. Business Services can nest, so a service can decompose into sub-services.
Capability
Represents the knowledge required to execute business or process activities — and whether you need to acquire, keep, or reduce effort to maintain it. Capabilities nest, and each has a Capability Type from the repository's configured type list. Capability relationships (Enables, Delivers, Required For) connect them to processes, journeys, products, and services — see Object relationships.
Class
Represents a data or programming class used by your IT staff to implement systems. Classes nest.
Dashboard
A page of gadgets — list reports, charts, tables, and performance indicators — that visualizes repository content in the DashboardDashboard A configurable view in Process360 Live that aggregates KPIs, charts, and filters across one or more processes for stakeholders to monitor performance. area. A new dashboardDashboard A configurable view in Process360 Live that aggregates KPIs, charts, and filters across one or more processes for stakeholders to monitor performance. can copy its layout from an existing one.
Diagram (web-authored)
A diagram created and edited in the web — the main modeling document. Each diagram has a Diagram Type chosen at creation. Authoring, viewing, and importing diagrams is covered in Diagramming; a diagram's shapes describe enterprise objects, which is how diagrams connect to the rest of the model.
External Agent
Represents a factor outside your enterprise, such as a customer or vendor. External Agents take part in RACI relationships and work product flows, but do not nest.
External Data
An uploaded spreadsheet (XLS/XLSX, CSV, TSV, or TXT, up to 32 MB) whose rows drive the simulation external data generator. See External Data object.
External File
A non-iGrafx file — for example a Word, Excel, or PDF document — stored and versioned in the repository. See Work with external files.
Folder and Shortcut
A Folder is a generic container for organizing items; each object family also has typed folders (for example a Process Folder) offered inside its branch. A Shortcut is a link to another item, so the same item can appear in more than one place in the tree without being copied; its page shows "This item is a shortcut to" the target. A shortcut can be disbanded — replaced with an independent copy of the original (when the original has children, you choose whether those become shortcuts or copies too). Disbanding makes a shortcut a quick way to branch an As-Is process into a To-Be design: shortcut the As-Is process where the To-Be belongs, disband it to get an editable copy, then change the copy while the As-Is stays intact. To create or disband one, see Manage items.
Glossary and Term
A Glossary collects Terms — the vocabulary of your organization, including how abbreviations should be read. A Term's Term References list shows where the term is used.
Client-authored Diagram, Document, and Component
IGX Diagram, IGX Document, and Component objects hold content created with the iGrafx desktop client (FlowCharter, Process, Process for Six Sigma) and added to the repository. They are edited through check-out into the client and check-in back to the repository.
Interface, Service, and Operation
Represent what a resource — often a computer system — offers: an Interface contains Services, and a Service contains Operations. Services can decompose into sub-services; interfaces cannot contain other interfaces; operations are the leaves.
Journey, Moment, and Touchpoint
Represent the journey of an external or internal stakeholder: a Journey contains Moments, which contain Touchpoints. Journeys nest and carry a Journey Type from the repository's configured type list.
Opportunity and Opportunity Instance
An Opportunity represents the potential positive effect of taking on a risk; an Opportunity Instance is its occurrence on a specific object — an instance can relate to only one object. Both carry types from the repository's configured type lists, and the Provides Benefit To relationship connects them to the rest of the model.
Process and Activity
A Process represents a process involved in producing your products or services; an ActivityActivity A named step in a process (e.g. "Approve Invoice"). Each event in an event log records one activity occurrence for one case. is a step beneath it. Processes contain Activities and nest into sub-processes; Activities also nest. Diagram shapes typically describe Processes and Activities, and processes carry RACI assignments and work product flows.
Product
Represents a physical or non-physical product that is sold or processed. Products nest into product hierarchies.
Report
A saved report definition or narrative template, run from the Reports area. A Report is edited through check-out and check-in and builds a version history, the way a diagram or external file does. See Reporting.
Requirement
Describes a requirement on other repository objects. Each Requirement has a Requirement Type — Business, Financial, Functional, Governance/Compliance, Performance, Personal, Product, Risk, or Technical.
Resource
Represents what's required to perform processes: organizational structure, functional roles, people, computer systems, equipment, locations, and IT architecture. Each Resource has a Resource Type from the repository's type hierarchy, and a Labor resource can be linked to the platform user it represents. Resources are the targets of RACI relationships and carry simulation scheduling fields.
Shape Library
A custom collection of graphics used as shapes or artifacts in web-authored diagrams. See Diagramming.
Simulation Project
Holds a process simulationProcess Simulation Running a designed process model against scenarios (volumes, resources, durations) to predict performance before making real-world changes. setup — the scenario built on a diagram, run from the Simulation area. Simulation itself is documented in the Process Simulation guide.
Strategy and Goal
A Strategy describes a long-term plan of action; Goals are the outcomes it pursues. Together they group related strategies, goals, and performance indicators — the backbone of scorecard-style performance management.
Web Address
A URL object that opens a browser page outside the platform — useful for linking policies, wikis, or systems into the model.
Work Product
Represents physical objects or information that flow between External Agents, Processes, Resources, and Interfaces — an order, a report, a part. Each Work Product carries at least one Work Product Layer (Business, Information, or Data), and its Work Product Flows record what sends and receives it.