EASYProcess and AI | K-Rise Systems
EASYProcess™ + AI

AI for JD Edwards.The EASYProcess™ Way.

Six ways to put AI to work, for the people who use apps and the people who build them. Your users get AI in the tools they already know, and JD Edwards stays isolated from AI.

6Ways to do AI with EASYProcess
Any AIChatGPT, Claude and more
0Direct AI access to JD Edwards
Day 1Developers build with AI, no training needed
01 · For business users

Your EASYProcess Apps, Ready for Any AI

In EASYProcess, business logic lives in Functions. The EASYProcess MCP server turns the Functions you choose into tools that ChatGPT, Claude and other AI assistants can use. Users work with EASYProcess apps from the AI console they already know, with no need to log in to EASYProcess apps.

Your userWorks in their AI console
AI of their choiceChatGPT, Claude and more
EASYProcess MCP serverOne per tenant. Turns Functions into AI tools
Functions / APIsYour business logic, in every app
JD EdwardsYour data, isolated from AI

1 · Methods become Functions

Each Function is defined once, with inputs, outputs and a description. Each one is a REST API with a clear contract.

POST../Function/POInquiry

2 · Pages use them too

One API for pages, chat and agents. The Open PO Inquiry page and AI both call POInquiry: change it once, and both get the change.

PagesChatAgentsMCP

3 · The MCP server makes them AI tools

Each exposed Function is a tool, and its description guides the AI. Users stay in their AI console.

POST../Function/NotifySupplier
Security and Governance Built In

You Stay in Control.

Opening business apps to AI raises fair questions from IT. EASYProcess™ answers them by design.

You choose what AI sees

Expose only the Functions you select. Everything else stays invisible to AI.

Describe it in your own words

The description you write for each Function is what AI reads to decide when and how to use it.

Connect once, securely

Sign in once with your existing login: Microsoft 365, Okta or your EASYProcess account. EASYProcess is then there in every AI conversation.

AI runs as the user

Every request carries the user's identity. AI sees only what that user is allowed to see.

Your enterprise systems stay isolated

AI talks only to EASYProcess, never directly to JD Edwards or your databases. EASYProcess stands between AI and your enterprise data.

Example: Customer Service

Order Status Without Leaving the Call.

A customer is on the line. The agent asks their AI assistant for the order's status and tracking number, and the answer comes from EASYProcess in the same conversation.

  • Agent stays with the customer. No hunting through screens.
  • No logging in to EASYProcess apps. The AI calls the right EASYProcess Function behind the scenes on the agent's behalf.
  • Live, trusted answers. Same EASYProcess data, same business rules, same user permissions.

Illustrative example

Illustrative example

02 · For business users

AI Chat Inside Every EASYProcess App

One click on the AI Chat button in the app header opens a chat panel on the left side of the screen. The chat calls the same Functions as the app.

  • Any AI provider. ChatGPT, Claude, Copilot and more. Customers plug in the provider of their choice.
  • Same controls as #1. Exposed Functions, descriptions and permissions carry over.
  • Two directions, one platform. #1 brings EASYProcess to your AI. #2 brings AI into EASYProcess.
03 · For business users

AI Agents That Work for You

An AI agent works toward a goal. It decides the steps, uses EASYProcess Functions as tools and checks the results until the job is done.

A goal

You describe the outcome in plain language, not the steps.

Tools

It acts through EASYProcess Functions, the same ones your apps use.

Its own decisions

It chooses the next step, such as which vendors count as late.

A loop

Act, check the result, decide again, until the goal is met.

Inside EASYProcess apps

Agents use the app’s Functions as tools. Saved agents run on the EASYProcess scheduler; on-demand agents start when a user asks.

Your own agent platform

Copilot Studio, n8n or a custom agent connects through the EASYProcess MCP server.

An agent is only as good as its tools.

Build from 400+ services

EASYProcess’s built-in service collection.

  • Query tables, call JDE BSFNs and much more
  • Combine services into Functions with clear inputs and outputs
  • Their descriptions tell agents when to use them

Or let AI build them

With the design-time MCP server (see #5).

  • Describe the tool you need, and AI builds the Function
  • Same guardrails: DV only, inside your project
  • Reviewed in Git before it reaches Production

Build once, use everywhere. Every Function you build is a tool for agents, in-app chat and any AI, and an API for your pages.

Example: the morning PO follow-up agent

“Every weekday at 7:30 AM, find vendors with PO lines unacknowledged for 7 or more days, notify each one, and send me a summary.”

STEP 1

Wake up

The EASYProcess scheduler starts the agent at 7:30 AM.

STEP 2

Find vendors

Calls the Vendors Function and pages through the results.

STEP 3

Check the age

Keeps vendors with a PO line open 7 days or more.

STEP 4

Notify

Calls NotifySupplier for each vendor, with approval if required.

STEP 5

Report

Sends a summary: who was notified, and any failures.

Easy to change: switch 7 days to 5 by editing one sentence instead of code. Illustrative example.

People stay in charge.

AI asksThe agent requests a tool, such as NotifySupplier for vendor 4343.
EASYProcess checksThe tool needs approval, so EASYProcess does not run it yet.
Run pausesThe run is saved and the approver notified. No AI cost while waiting.
Person decidesApprove, reject or edit. The agent then continues.

The model cannot skip it: the approval check lives in EASYProcess, between “AI asked” and “EASYProcess runs it.”

  • Runs as the user. No shared service account. The agent sees only what that user is allowed to see.
  • Changes need approval. Reading is low risk. Changes wait for a person; unanswered requests time out and are logged.
  • Limits and run history. Round, time and cost limits. Every run and tool call is recorded for audit.
04 · For business users

AI Built into Everyday Business Apps

Developers use the built-in EASYProcess tools to add AI prompts directly into business processes. Users get the benefits of AI without worrying about how to use AI.

Developer

Uses the built-in EASYProcess tools to add AI prompts to an app.

AI-powered app

AI runs inside the everyday business process.

End user

Gets the results without having to learn AI.

Example: AP invoice processing

  • AI reads and processes incoming invoices.
  • End users add their own prompts for vendor-specific invoice variations.
05 · For developers

Build EASYProcess Apps with AI.

Through the design-time MCP server, you build and change the Functions and pages in the project you choose, with Claude or another AI at your side. Your users get a normal, fast EASYProcess app.

STEP 1

Set up the project

Open a project in the EASYProcess IDE and add the pages and Functions AI will work on: existing ones to change, or empty new ones to build.

STEP 2

Build Functions

With AI’s help, you build and change the Functions in the project, using design-time tools like ModifyFunction.

STEP 3

Build pages

With AI’s help, you build and change the pages in the project with ModifyPage. Each page calls its Functions as REST APIs.

While building

Any AI connects through MCP and works only on what is in the project.

Once live

A normal EASYProcess page calling EASYProcess REST APIs. No AI at run time.

No training required

Any developer can start building with EASYProcess on day one.

You decide what gets built. AI builds it.

You set the scope

Developers create the project in the EASYProcess IDE and choose which pages and Functions go into it.

You add, AI builds

For something new, add an empty page or Function to the project. AI builds it out from there.

AI stays inside the lines

AI can’t create projects, add objects to a project, or touch anything outside it.

Every AI change is tracked and reviewed.

AI makes a changeOnly to pages and Functions added to the project.
Saved in GitEvery AI change goes into Git source control.
You review itSee AI’s source changes in the EASYProcess IDE, line by line.
You promote itOnly reviewed changes move to QA and Production.

Safe by design: AI works in Development only.

DVDevelopmentAI via MCP server
QAQuality assuranceNo AI access
PDProductionNo AI access
  • DV only. The design-time MCP server connects only to the Development environment.
  • Normal promotion. Changes reach QA and Production only through EASYProcess IDE promotion, after you review them.
  • Isolated by design. EASYProcess is fully database-driven, so DV access gives no access to other environments.
06 · For developers

AI Assistant Built into the EASYProcess IDE.

A chatbot inside the IDE, opened from the canvas right where developers build. It works in every environment.

  • No training required. Developers hit the ground running from day one.
  • Answers from EASYProcess docs. The assistant draws on the RAG documentation server for EASYProcess-specific answers.
  • Answers in context. Ask the IDE. AI help is one click away.

Illustrative example

Get Started

One Platform. AI Everywhere.

Secure by design: you control what AI sees, AI runs as the user, JD Edwards stays isolated, production stays protected, and people approve changes. Book a 30-minute demo and see it with your own JDE use case.