🤖 OasisPro · IFS Cloud AI Assistant · Early Access
Your next IFS Cloud improvement can start with a sentence.
The IFS Cloud AI assistant from OasisPro, called the OasisPro Development Assistant, lets you describe the change you need in plain language, review what it proposes, and apply it. No ticket queue for a new field. No waiting a sprint for a notification. Just a sentence, a review, and a result.
Most small IFS Cloud changes are not hard. They are slow. A user asks for a field, someone writes it up, someone else builds it, and a simple improvement takes far longer than the work itself.
This post covers what the assistant does today, what it does not do yet, and how to see it on your own system.
Describe it. Review it. Apply it.
Three steps, and the middle one is the one that matters. You always see the proposed change before it is applied, so speed never costs you control. The assistant is powered by OAI and built for IFS Cloud teams who want to ship improvements without the usual queue.
Watch the demo
Watch the IFS Cloud AI assistant turn a sentence into a change
See the describe, review and apply flow from start to finish, on a real IFS Cloud change.
Want to see it on your own backlog? Book an early-access demo.
What the IFS Cloud AI assistant can do today
- 1. Create custom fields. Describe the field you need and review the proposed definition before it is applied.
- 2. Create enumerations. Add the value lists your processes rely on without hand-building each one.
- 3. Configure custom events. Set up the trigger logic that reacts when something happens in IFS Cloud.
- 4. Configure notifications. Make sure the right people hear about the right event, set up from a plain description.
- 5. Make supported Page Designer changes. Adjust pages through supported workflows, with the proposal in front of you first.
- 6. Keep your work in your own workspace. Your projects, prompts and saved work stay with you and can be reused.
Describe it
Say what you need the way you would say it to a colleague. No spec document, no ticket template, no translating a business need into technical jargon first.
Review it
The assistant proposes the change and you check it. This is the control point: nothing is applied until you have seen what it will do.
Apply it
Once you are happy, apply it through a supported workflow. The result is a real change in IFS Cloud, not a mock-up or a suggestion in a document.
A straight word on scope
The assistant works through supported workflows. That means the field, enumeration, event, notification and Page Designer changes listed above. If a request falls outside them, treat it as a conversation with us, not a promise. We would rather tell you what it does not do yet than oversell it.
Why a sentence beats a ticket queue
The expensive part of a small IFS Cloud change is rarely the build. It is everything around it: capturing the request, explaining it, waiting for someone with the right skills, and checking the result matches what was meant.
Starting from plain language removes the translation step. The person who knows what the business needs describes it directly, and the proposal that comes back gives them something concrete to react to, rather than a document to approve.
Keeping projects, prompts and saved work in your own workspace matters too. A good request is worth reusing, and your team should be able to find it again.
The best IFS Cloud improvement is the one nobody has to wait for. Describe it. Review it. Apply it.
Where this is heading
Today the assistant handles configuration changes. The next step is bringing Lobbies, Quick Reports and summaries together through OAI agents, so the same plain-language approach reaches how people see and report on their data.
To be clear, that is the vision, not what ships today. We are labelling it that way on purpose. You should know exactly what you are getting in an early-access demo, and which parts are still ahead of us.
If you have strong views on what should come first, a demo is the best place to say so. Early users shape the roadmap.
New fields and pages still need the right access.
Every change you make raises the same follow-up question: who should be able to see and use it? PermissionWorks helps you answer that, and testing permissions properly is where most teams slip.
Read the IFS Cloud permission testing guideSee the assistant work on a change you actually need.
Book an early-access demo. Bring a real field, notification or page tweak from your own backlog and we will show you the describe, review and apply flow on it.
What is the OasisPro Development Assistant?
It is an IFS Cloud AI assistant, powered by OAI, built by OasisPro. You describe the change you need in plain language, review the proposed change, and then apply it using supported workflows.
What can the IFS Cloud AI assistant do today?
Today it supports creating custom fields and enumerations, configuring custom events and notifications, and making supported Page Designer changes. Your projects, prompts and saved work are kept in your own workspace.
Does it change my IFS Cloud environment without my approval?
No. The workflow is Describe it, Review it, Apply it. You see the proposed change first, and you decide whether to apply it.
Are Lobbies, Quick Reports and summaries available yet?
Not yet. Bringing Lobbies, Quick Reports and summaries together through OAI agents is the direction we are building toward. It is a vision, not a shipped feature, and we will say so plainly when each piece is ready.
Is this an official IFS product?
No. The OasisPro Development Assistant is an OasisPro solution for IFS Cloud customers. It should not be presented as an official IFS product.
How do I get access?
Early-access demos are open now. Book one through the OasisPro contact form, or email info@oasispro.co.uk, and we will walk you through it on a real use case.
Start with one sentence
You already know the improvements your IFS Cloud users keep asking for. The only question is how long they wait.
Describe it. Review it. Apply it. Then see how much of your backlog was never really hard, just slow.