Two mockups of a request experience for casual business users — people who know what they need (“add a new client”) but not where it lives in the hierarchy or which properties matter. The full Metadata Request screen stays as-is for power users; this is a lightweight front door that feeds the same workflow engine, with placement and properties resolved by smart defaults, search, AI suggestion, or the approving data steward.
CONCEPT 01
Guided Wizard — “New Request”
Three plain-language steps. No Request ID, no workflow selector, no request-lines grid, no property panel. The user answers questions; EPMware builds the request line behind the scenes.
demo.epmwarecloud.com/requests/new
E
＋
⌂
🗂
?
New Request
Maria Chen · Omnicom Media Group
✓ What you need
2 Details
3 Review & submit
1
What do you need?
Add something newA client, account, entity…
Change somethingRename, move, update info
Retire somethingNo longer in use
What kind of item is it?
Based on your role, you can request Clients and Products.
What is it called?
Describe it in a sentence (helps us place it correctly)
2
Where does it belong? (start typing — or skip it)
Cardiovascular DiseasesBayer Group › Bayer Pharmaceuticals
Consumer Health Above BrandBayer Group › Bayer Consumer Health
Bayer CorporateBayer Group
I’m not sure — let the data team place it for me
✦
Suggested placement
Based on the name and description, this looks like it belongs under Bayer Pharmaceuticals › Cardiovascular Diseases — the same parent as 3 similar CTEPH items.
Use this placementSee why
Everything else — IDs, workflow, approvals — is handled automatically.
BackContinue
1Intent first, jargon never“Add / Change / Retire” replaces Action codes, Dimension pickers, and the request-lines grid. One request = one thing; power users keep the multi-line grid in the classic form.
2Three ways to resolve placementFuzzy search over the live hierarchy with full breadcrumb paths; an explicit “let the data team place it” escape hatch; and an AI suggestion inferred from name + description — a natural showcase for the AI roadmap.
CONCEPT 01 — STEP 3
Review, Submit & Track
The confirmation reads like a receipt, not a workflow console. Auto-resolved values are labeled so the user understands what the system filled in for them.
demo.epmwarecloud.com/requests/3918
E
＋
⌂
🗂
?
Request #3918 — submitted
Maria Chen · Omnicom Media Group
Your request
Request
Add a new Client
Name
Bayer CTEPH AI Software
Placement
Bayer Group › Bayer Pharmaceuticals › Cardiovascular Diseases AI suggested
Member ID
1374708 auto-assigned
Required details
Client codes & descriptions defaulted from parent
Approver
Omnicom Master Data team routed by workflow
3
Where it stands
✓
Submitted
Today, 4:11 PM
2
In review
Master Data team
3
Approved
You’ll get an email
4
Live in systems
Deployed everywhere
Need to add anything? Reply to the confirmation email or leave a comment.
View my requests
3Status in human terms“Pending Submission / Workflow Stage” becomes a four-stop tracker. The underlying workflow engine is unchanged — this is a read-only translation of workflow status for requesters.
CONCEPT 02
One-Card Quick Form
For prospects who want even less: a single card, four questions, embeddable anywhere (portal, intranet, Teams/Slack). Best when the use case is overwhelmingly “request a new member” and stewards do all placement.
portal.omnicom.com/apps/new-client-request · powered by EPMware
4
Request a new client
Takes about a minute. The Master Data team handles the rest.
Client name
Which agency / group is it for?
Just pick the closest fit — the data team will fine-tune placement.
What’s it for? (one sentence)
When do you need it?
No rush
This week
Urgent
Send request
4Priority, not workflow“When do you need it?” maps to the Priority field in plain words. The form creates a standard EPMware metadata request with the Deploy Only (or any) workflow attached — stewards see the full classic screen.
APPENDIX
How the simple form maps to the full Request Form
Useful talking points for prospects: nothing is removed from the platform — complexity is relocated, not lost.
Full form element
In the simplified experience
Request ID, Request Date, Requested By
Auto-generated; shown on the receipt only.
Workflow & Workflow Status
Pre-assigned per form/template by the admin; status translated to the 4-stop tracker.
Action / Dimension / Member codes
Derived from “Add / Change / Retire” + item type; one request line built automatically.
Parent selection (hierarchy tree)
Type-ahead search with breadcrumbs, AI-suggested placement, or “let the data team place it.”