What the tools do, on screen
Worked examples
Real questions, answered from the system itself.
Four everyday configuration questions, put to the tools on a demo TRIRIGA with made-up data. The tools read the instance's own metadata.
Worked example
A different SLA at each location
One customer, one service, two locations, and a different SLA at each. The answer: one service agreement, one service line per location with its own respond and due terms, and the SAM records that come out of it when the contract is activated.
Worked example
Email the requester when a service request is submitted
Before building anything, it checked the instance and found that TRIRIGA already ships this behaviour: the Submit action triggers an out-of-the-box workflow that notifies the Requested For person. The job is to verify it and switch it on, then customise it if you need to.
Worked example
Map a work task's org stamp from the responsible org
Map a work task's organisation stamp from the responsible organisation with two new workflows and one edit.
What was asked
Show me what it would take to adjust this to map the org stamping from the responsible organisation on that work task.
The change that would be required: two new workflows, one edit. On the associate organisation, set customer org from responsible org.
It's called Cloud Login
Add an IdP in TRIRIGA without turning on SSO
TRIRIGA Platform 5.0.7 supports adding an identity provider while keeping SSO=N, under Tools, System Setup, Integration, OAuth Settings. For teams moving to IBM MREF, that means several identity providers can sit in one system.
The answers come from a TRIRIGA instance through the agreed tooling; your own estate's configuration determines what applies.
The safeguards
- Work starts in non-production. Production stays read-only unless you agree otherwise in writing.
- A person confirms every deployment (Object Migration).
- The tools sign in to TRIRIGA with an account you provide and control.
- Credentials kept apart. The service user's password is held in a per-customer secret store.
- The tools are agreed with you. Write tools stay off until the policy for that environment turns them on.
- Every call is logged with environment, action and outcome, and kept for 90 days.
- A clear way out. Remove the bridge and the service user, and the tools can no longer reach your instance.
What we hold


AJAEX LTD is an IBM Silver Business Partner and holds Cyber Essentials. Ask us for the security pack.