Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Categories Workflow
Created by Guest
Created on Aug 15, 2026

One-Click Export/Import of Complete Workflow Process (Canvas, Nodes, and Logic) Between Environments

Idea / Problem Statement:

Moving a workflow process from one Maximo/MAS environment to another (e.g., Dev → Test → Prod) is far harder than it should be. Today it requires manually configuring Object Structures, External Systems, and MIF Interfaces (MXWFInterface) just to export/import a single workflow — and even then, the canvas layout, nodes, and connecting logic frequently do not transfer correctly unless every child object (WFNODE, WFCONDITION, WFSUBPROCESS, etc.) is painstakingly included by hand. Admins often end up with an XML file that only contains header data, forcing them to rebuild the workflow visually from scratch in the target environment.

There is no simple, native, purpose-built way to export a complete workflow process (including its visual canvas layout) from Workflow Designer and import it cleanly into another environment.

Suggested Solution:

Add a native "Export Workflow Package" / "Import Workflow Package" action directly inside the Workflow Designer application (similar to Application Designer's "Export System XML"). This should:

  • Automatically bundle the parent process and all dependent child objects (nodes, conditions, subprocesses, assignments, canvas coordinates) into a single package with no manual Object Structure setup required.
  • Validate dependencies (e.g., missing subprocesses, actions, or roles) before import and clearly flag conflicts.
  • Preserve the visual canvas layout exactly, so imported workflows don't need to be manually redrawn.
  • Work independently of Migration Manager/MIF configuration, so any admin can use it out of the box.

Business Impact / Justification:

  • Reduces workflow deployment time from hours (manual Object Structure setup, MIF configuration, XML troubleshooting) to minutes.
  • Removes the integration/MIF expertise barrier — currently only advanced admins can reliably do this.
  • Prevents costly errors from incomplete exports (missing nodes/arrows) that silently break business processes when promoted to Production.
  • Aligns Workflow Designer with the ease-of-use already offered by Application Designer's Export/Import System XML feature.
  • Directly benefits any customer using multiple environments (Dev/Test/Prod).
Idea priority Urgent
Needed By Quarter