Managed enterprise workflow platform
Workflow for everywhere
Enterprise workflow that spans the systems a process actually touches. Configured by business analysts, connected to PeopleSoft, Oracle Cloud and third-party systems, and hosted and maintained by Gideon Taylor.
One platform across your systems
PeopleSoft, Oracle Cloud, Workday, Salesforce, ServiceNow or an in-house system, under one workflow and one audit trail
One accountable team
Your analysts build, GT builds for you, or both — while Gideon Taylor hosts the platform and maintains the integrations
Already in your license
GT eForms customers hold the license already. Hosting is the only added cost.
What GT eFlow is
GT eFlow is a managed enterprise workflow platform from Gideon Taylor. Business analysts build the forms, the logic, the approvals and the system connections through configuration. It runs outside your ERP and treats PeopleSoft as one connected system among several, so a process touching four systems is still one workflow and one audit trail — and Gideon Taylor operates the platform underneath it, so there is no infrastructure on your side.
How it works
Connect, build, route
Three steps, none of them a development project.
Connect
A connection describes an external system once. From there one form can prompt from one system, prepopulate from a second and write its result to a third.
Build
An analyst drags pages, segments and fields into place and configures each in a settings panel. Size, range and validation rules belong to the field definition, so they carry into every form that reuses it.
Route
Approvals run as durable workflows that survive restarts and outages. Whether a step routes, and to whom, is resolved from form data or from a connected system.
Capabilities
What you build with it
The parts a business analyst works with directly. Forms, logic, searches, workflows, notifications, roles and system connections are all configuration.
Changing the form doesn't wait for a release
Drop a field on the page and set its labels, defaults and validation in the live settings panel.
Every rule, written the same way
Whether a field shows, what it defaults to, which step an approval takes, who receives the notification — the same editor and the same three parts: value, logic, settings.
The brain of the form
One configured source of system data, used anywhere the form needs it — prepopulation, prompt lookups, search pages, logic conditions, security and user lists.
Endpoints that register themselves
Give the platform a service’s OpenAPI specification and its endpoints appear — PeopleSoft, Oracle Cloud or third-party — scoped per instance, so several environments of the same system coexist.
Four systems, one row of data
The columns of a result row don’t have to come from one place — each can be drawn from a different system and assembled into a single row.
Public, or behind your SSO — you pick, form by form
An open link takes submissions from people with no account at all; your single sign-on and its security cover everyone else. Either way, it’s the same form landing in the same workflow.
A rule that reads as a sentence
Pick the workflow event to listen for, add a condition if it should only fire sometimes, and choose the action.
Architecture
Outside the ERP, connected to all of it
GT eForms works deeper inside PeopleSoft. GT eFlow works across the systems around it. Running outside the ERP is what makes that reach possible — and what lets Gideon Taylor carry the operational load.
Managed means managed
Hosting, security patching, compliance infrastructure, integration maintenance and platform updates are Gideon Taylor’s. Upgrades are run by GT and scheduled with you, with room to test before go-live.
Isolated by deployment
One tenancy per client, each with its own application, database and cache. Nothing is shared between customers.
Authorization on every request
Permissions are checked on every request rather than inferred from how a user reached a page. Tokens are rejected the moment they are revoked.
REST at the boundary
Integration is REST only. No direct database access into the systems around it, and no message-bus coupling at the boundary.
Upgrades preserve your work
Client configuration layers over the delivered product rather than modifying it, so an upgrade does not overwrite it and there is no re-application project afterwards.
Engagement
Your forms. Your workflows. Our platform and our people.
How much of it you build is your decision, and it can change over time. Pick a model to see where the line sits.
Gideon Taylor’s team designs, builds and manages your forms and workflows. You describe the business problem and we deliver working automation, hosted and maintained.
Gideon Taylor owns
- The platform, hosting and security
- Every system connection and its upkeep
- Form design and business logic
- Workflow configuration and approval chains
Your team owns
- The business problem and the process requirements
- Sign-off on the result
Suits organizations that need the outcome without staffing three skill sets, and processes that need deep ERP integration.
Your team and ours work together. Gideon Taylor handles the integration, the hosting and the hard parts. Your team handles form design and business logic, with our guidance behind it.
Gideon Taylor owns
- The platform, hosting and security
- Every system connection and its upkeep
- Guidance and review as you build
Your team owns
- Form design and business logic
- Approval chain configuration
- User management and data classification
Suits teams building their own capability who want expert cover while they do it.
Your team builds on GT eFlow independently. Gideon Taylor manages the platform, the hosting, the security and the integration maintenance. You own the business logic and the form design.
Gideon Taylor owns
- The platform, hosting and security
- Integration maintenance and platform updates
Your team owns
- Form design and business logic
- Approval chain configuration
- User management and data classification
- Process requirements and rollout
Suits teams who already have the analysts and want the operational burden to sit somewhere else.
Gideon Taylor builds the platform, implements the solutions, hosts the infrastructure and maintains the integrations. There is no gap between the software vendor and the consulting partner, because they are the same team — and it is the team that has spent over 20 years on the other side of the integration.
GT eFlow for everywhere.
Nothing is retired. Nothing is replaced.
The two products divide by reach, not by age. One question tells you which you need.
Does your process stay inside PeopleSoft?
GT eForms
GT eForms is the better tool, and it is not changing. Approvals route on PeopleSoft’s own Approval Workflow Engine, submitted data writes back to real records, and it holds Oracle Validated Integration — the only form builder certified by Oracle for PeopleSoft. If your process belongs inside PeopleSoft, we will tell you to stay on it.
GT eFlow
That is what GT eFlow is for. One workflow across PeopleSoft, Oracle Cloud and the systems around them, hosted and maintained by us, with PeopleSoft as one connected system rather than the container. It also covers the case where the objection is the interface rather than the transaction underneath it, and migrating the system of record is not on the table.
Both, on one license
Then so do we. Keep everything you built in GT eForms and extend it where eForms cannot go. For an existing customer this is not a second license — it is a part of the one you already hold, with hosting as the only added cost. GT eFlow is designed so the forms, approval chains and business logic you have already built move onto it, so you are extending what you built rather than starting over.
Operations
Running it
What your administrators and builders work with once a workflow is live, and what an auditor asks for afterwards. Everything underneath it is ours.
Roles and filtered navigation
The menu is generated from what a user is permitted to reach, rather than hidden by convention.
Security grant requests
Access is requested and granted in the product as per-user, per-task bundles, each with its own status and trail.
Append-only audit trail
Every workflow action is logged, and a workflow keeps its place across restarts and outages.
Comments and activity log
A rich-text comment feed alongside the activity log, with logging granularity set per form type.
Bulk data export
A background job produces form data, form lists and form logs as CSV with download links.
Row-level security
Security on the subject of a form is applied inside eFlow, and row security enforced by a source system is honored.
Learn how GT eFlow fits your environment
We will review your current environment, identify where GT eFlow fits, and work out an approach for your organization — whether that is your team building on the platform, our team building for you, or extending existing GT eForms workflows into a multi-system environment.
- Built by business analysts through configuration, with TypeScript extensions for the rest
- Connects PeopleSoft, Oracle Cloud and third-party systems, and those systems to each other
- One accountable team for the platform, the implementation, the hosting and the integrations
- Already covered by the license existing GT eForms customers hold
Questions
Frequently asked questions
What is GT eFlow?
GT eFlow is a managed enterprise workflow platform from Gideon Taylor. Business analysts configure the forms, the logic, the approval workflows and the connections to external systems, without writing code. It runs outside your ERP and connects to it, so a single workflow can span PeopleSoft, Oracle Cloud and the other systems a process touches, under one audit trail. Gideon Taylor hosts and maintains the platform, so there is no infrastructure on your side.
How is GT eFlow different from GT eForms?
The two products divide by reach. GT eForms runs inside PeopleSoft, routes approvals on PeopleSoft’s own Approval Workflow Engine and writes back to PeopleSoft records, which makes it the better tool for a process that stays inside PeopleSoft. GT eFlow runs outside the ERP and treats PeopleSoft as one connected system among several, which is what lets a workflow span PeopleSoft, Oracle Cloud, Workday, Salesforce, ServiceNow or an in-house system at once, reach people without an ERP account, and run on infrastructure Gideon Taylor operates. The qualifying question is a single one: does the process stay inside PeopleSoft? If it does, eForms. If it does not, eFlow. If your processes do both, so do we.
How does GT eFlow work with our existing GT eForms investment?
GT eForms for PeopleSoft continues to be the best-in-class solution for PeopleSoft-native workflow automation, and it is not being changed or retired. GT eFlow becomes relevant when your workflows need to reach beyond PeopleSoft — connecting to Oracle Cloud or other systems, serving external users, or offloading infrastructure management. GT eFlow is designed so that your existing forms, approval chains and business logic move onto the new platform, so you are expanding what you have already built rather than starting over. For an existing GT eForms customer this is not a second license; it is a part of the license already held, with hosting as the only added cost.
Can Gideon Taylor just build the solutions for us?
Yes. Many organizations engage Gideon Taylor’s team to design and build forms and workflows on GT eFlow, especially where deep ERP integration knowledge is needed. You describe the business process and we deliver working, managed automation. This is how GT eForms grew: the consulting team uses the platform to deliver results, and customers adopt it as their own over time. There are three ways to engage — we build it, we build it with you, or you build it on a platform we run.
What does Gideon Taylor manage, and what do we manage?
Gideon Taylor manages hosting, scaling, security patching, compliance infrastructure, integration maintenance, workflow execution and platform updates. Your team manages business logic, form design, user management, data classification decisions, process requirements and approval chain configuration. Where that line sits can move — under a build-for-you engagement, Gideon Taylor takes the form design and business logic as well.
Which systems can GT eFlow connect to?
PeopleSoft, Oracle Cloud and third-party systems — anything that exposes a REST interface. A connection records a base URL, an authentication type and an adapter, and each endpoint records its method, path and request and response shapes. Pointing the platform at a service’s OpenAPI specification registers its endpoints automatically. Connections are scoped per instance, so several environments of the same system — one HCM and three Campus Solutions, for example — coexist as distinct connections under one platform.
Do I need developers to use GT eFlow?
Forms, logic, searches, workflows, notifications, roles, navigation and system connections are all configuration, so the great majority of what an organization needs is built by a business analyst without writing code. Where a requirement genuinely needs more, a developer extends it in TypeScript: around forty hook points exist across form build and save, field change, page and segment navigation, five levels of validation and workflow step activation, each available before, after or instead of the standard behavior.
Can people outside our organization take part in a workflow?
Yes. Applicants, vendors, citizens and partners can submit into an enterprise workflow directly, rather than through a standalone web form whose data is re-keyed afterwards. GT eFlow is cloud-hosted and sits outside the ERP perimeter, which is what makes this possible — a PeopleSoft-native product cannot offer it. Each customer has an isolated tenancy, so a public surface for one client is never adjacent to another client’s data, and every request is authorized independently, so a public entry point cannot become a route into an internal task. Public access, external identity handling and abuse prevention are shaped to what a given process needs, so this is a conversation worth starting early.
Where does our data live, and how is it isolated?
Each client runs their own cloud tenancy with a separate application, database and cache. Nothing is shared between customers. Authorization is checked against the user’s permissions on every request rather than inferred from how they navigated there, tokens are rejected as soon as they are revoked, and service-to-service traffic is signed and allowlisted with production secrets held in a managed vault. Row security enforced by the system your data comes from is honored rather than bypassed.
How does GT eFlow handle single sign-on?
The product is delivered with username and password authentication, and Gideon Taylor sets up single sign-on against your identity provider as part of the implementation. If single sign-on is a procurement requirement on your side, raise it early so it can be sequenced into the project.
What happens to our configuration when the platform is upgraded?
It is preserved. Client configuration layers over the delivered product rather than modifying it, so an upgrade does not overwrite it and there is no re-application project afterwards. Upgrades are run by Gideon Taylor and scheduled with you, so there is time to test and prepare before they land.
What is GT eFlow not designed for?
GT eFlow is purpose-built for enterprise workflow — forms, approvals and integrations across PeopleSoft, Oracle Cloud and other enterprise systems. It is not a general-purpose application builder, and it is not trying to replace your application development platform. It is not a replacement for your ERP; it integrates with and extends it. It is not a reporting tool, so keep using your existing BI tools. And the managed model is core to how it works: this is not a self-service platform you run on your own infrastructure.