Understand components used in process mapping in Ardoq ShiftX
Updated on: 6 April 2026
Learn what components are and how they are used to keep processes consistent and reusable in Ardoq ShiftX.
What is a component?
A component is a reusable part of a process, such as a role, team, system, School or Unit. Components are used across many processes. They keep names consistent, show who is involved and which tools are used, and make processes easier to update when things change.
Types of components
Applications
Applications are systems or software used in a process step. They show where work depends on technology and help people understand which systems are involved.
HR Organisation Unit
The HR Organisation Unit represents Schools and Units. They show where work sits in the University structure. They help make ownership and hand鈥憃ffs clear without naming individual people.
Information object
Information objects are things like forms, policies or documents used in a process. They show what information is needed at each step and where it is passed on.
People
People represent individuals who take part in a process. Avoid using named people where possible, as staff can move roles or leave. Use roles instead to keep processes accurate and easier to maintain over time. Use people only when a specific individual must be shown.
Roles
Roles describe a job or function, not a named person. Using roles keeps processes accurate when people change jobs or leave.
University groups
Groups are committees, boards or working groups. They are used when decisions or oversight sit outside normal teams or Units.
How to add a component to a process step in Ardoq ShiftX
Follows these steps:
- when in the process, click into the step narrative
- type @
- choose the correct School, Unit, role, group, system or information item
Use roles instead of named people to keep processes stable.
Create or update components
Create components only when needed. Sometimes there may not be a component that fits what you need and you'll need to create a new one. Always check if the component already exists to avoid duplicates. Be careful when updating components, as changes can affect many processes. Use clear, consistent names so components are easy to understand and reuse.
Create or update roles and information:
If you need a component type that is not available, email the AI and Automation team at ai-automation@st-andrews.ac.uk.