Understand the screen. Make the change. Share the result.

Turn a screen change into something everyone can inspect.

The Playground brings the XML, a schematic preview, design checks and control documentation into one workspace.

This is an Assetize tool for classic Application Designer presentations. Its preview is a schematic; final rendering, permissions and business behaviour are confirmed in your Maximo test environment.

• Open the Work Order Tracking starter

Make your first change in a few minutes.

Start with the small Work Order Tracking example. You can complete this walkthrough without a Maximo connection or an export.

1. Open the Work Order Tracking starter below. Keep Dictionary on MAS 9.2 and choose the MAS 9.1+ skin.
2. Click a field in the preview. The Inspector shows its control and properties, and the editor reveals its XML.
3. Change an existing label in the XML. The preview redraws after you pause typing. Editing a field value in the preview changes a sample record instead of the XML.
4. Read the Design review below the editor. Select a finding to jump to its source location; open its reference link for the relevant control property.
5. Switch the skin to Pre-Carbon, then MAS 9.0. The XML stays the same while the layout changes.
6. Choose Download to keep the edited XML, or Share link to copy a URL that restores the supported screen state.

Download changes before selecting a different application or using Reset. Those actions replace the XML currently in the editor.

• Start this walkthrough

Start from the product, an example or your own presentation.

The Application picker distinguishes harvested stock screens from the smaller Assetize examples.

Export the application presentation from Application Designer in your Maximo environment. Keep an unchanged copy, then open the XML in the Playground. Custom objects and fields are checked against the bundled dictionary; the Playground does not import your environment’s dictionary or lookups.

Select a presentation XML file, rather than a ZIP archive, a database export or a role-based application package.

Three views of the same presentation.

Move between the XML and the visible control without losing the binding you are inspecting.

Pop out mirrors presentation state, not your edited sample rows. The pop-out window displays “live from the playground” when connected and “snapshot” when it is no longer receiving the editor’s state.

• Browse the controls reference

Find the issue, see its location, choose the fix.

The Design review checks XML and known presentation rules, then resolves data bindings using the selected dictionary and available relationships.

Errors identify problems such as invalid structure or duplicate IDs. Warnings need review against the intended configuration. Notes describe context such as a custom lookup, a partial dictionary or an object supplied by a Java bean that cannot be resolved from the XML alone. Each finding includes its source location and, where available, a control reference.

The “clean” indicator above the editor means zero errors. Read warnings and notes in the Design review as well. A custom field absent from the bundled dictionary needs checking against your own configuration; deleting a valid custom field is not the fix.

A clean static review does not execute Java beans, automation scripts, workflow actions or database validation. Use your Maximo test environment for those behaviours.

• Look up individual checks in Help

Choose the data definition and the visual layout separately.

Dictionary controls binding checks. Skin controls how the same XML is drawn. Changing one does not change the other.

For a binding comparison, keep the presentation fixed and switch Dictionary. For a visual comparison, keep both the XML and dictionary fixed and switch Skin. This makes it clear which setting caused the difference.

The Pre-Carbon skin does not provide a 7.6 dictionary. The picker currently offers 9.1 and 9.2 dictionaries; a skin is a layout model, not a running release of Maximo.

• Read the source-backed UI version changes
• Explore MXH upgrade assessment

Try the layout with records behind the fields.

The main preview uses generated working rows when an object dictionary is available. The Work Order Tracking starter also offers bundled lab sample data.

Type into an editable preview field to change the working record. This lets you demonstrate how a populated screen feels while keeping layout edits in the XML editor.

Preview with real data is enabled for the Work Order Tracking starter that has a sample file. These are bundled 9.2 lab records, not a live connection to your Maximo. Other applications can still use generated rows when their object dictionary is available.

Working record edits live in memory. They are not included in Download, Copy, Share link or the pop-out mirror. Loading a different application, changing the dictionary or changing the data source can reseed the working rows.

The Playground does not save work orders or other business records to Maximo. Download exports the presentation XML only.

Apply a focused change and inspect exactly what moved.

The tricks drawer offers presentation patterns with their source, intended effect and instructions for checking the result.

1. Choose a trick in the editor’s drawer. Read what it changes and which configuration it needs.
2. Apply it to the current presentation. If no control matches, the Playground explains why nothing changed; some recipes describe configuration steps instead of editing XML.
3. Inspect the before/after diff and the added, removed, changed or moved control summary.
4. Use Undo to restore the XML from before that applied trick, or Download change summary to keep its text summary.
5. Follow any additional recipe steps in Application Designer, Conditional Expression Manager or Security Groups, as named by that recipe.

When you edit a loaded stock presentation, “Compared to stock” summarises changes against that loaded original. Opening your own export does not automatically fetch a matching stock baseline.

These are readable, mxdiff-style summaries. The Playground does not produce an IBM .mxs migration transaction or apply a change to Maximo.

• Explore the UI tricks catalogue

Choose the right way to hand over your work.

Keep the XML as the change artefact, and use a share link when a reviewer needs to reopen the screen.

State is reflected in the part of the URL after #. Named, unchanged starters and stock screens can be restored by reference. Edited XML is compressed where supported and embedded in that fragment.

The XML payload limit is 32 KiB after encoding preparation (compressed bytes when compression is available, otherwise raw bytes). If “Too large to share as a link” appears, use Download: the URL omits that XML and cannot restore your custom changes. Compression is an encoding method, not encryption.

Anyone you send a complete share link to can read its embedded presentation. Share it with the same care as the XML file. Working record edits and panel layout are not included in the link.

Give the next person the change and a clear way to verify it.

A useful handover includes the original, the edited presentation and a short record of what the reviewer should confirm.

1. Keep the original presentation export with its application ID, source environment and export date.
2. Download the edited XML. Include the trick summary if used, and note the dictionary and skin used for review.
3. Record the intended behaviour: which field, section, tab or action changed and who should see it.
4. Import the presentation into the appropriate Maximo test environment using your normal Application Designer process.
5. Check actual rendering, lookups, related data, security-group access, conditional properties and actions with representative users and records.
6. Promote the tested artefact through your normal change process, retaining the original for rollback.

Changing a presentation does not create a custom database attribute, a lookup definition or a security grant. Carry those dependencies with the change when your design requires them.

XML processing happens in your browser.

Opening an export reads a local file. Parsing, editing, design checks, preview rendering and change summaries run in the browser.

There is no customer XML database or server-side save operation for this editor. It still loads the application and reference assets from the website, so treat it as a browser tool rather than an installed offline application.

Download an XML copy when you need a durable working file. A browser history entry or a share URL that exceeds the payload limit is not a substitute for that file.

• Read the site privacy policy

Get from a confusing result to the next useful check.

Most surprises come from the selected dictionary, the source of the preview data or the difference between static XML and runtime behaviour.

Go deeper where the change needs it.

Use the focused references for properties, version changes and the configuration around a screen.

Control and dictionary details come from the bundled registry, stock presentations and harvested definitions. The reference pages identify their sources. Layout models also use the documented and practitioner-reported version changes described in the UI version guide.

Start Centers and Operational dashboards have their own tools. The classic presentation Playground does not build a role-based application or an Operational dashboard.

• Maximo UI field guide
• Controls and properties
• UI tricks and recipes
• UI changes by version
• Detailed help and checks
• Start Center templates
• Operational dashboard creator
• MXH assessment documentation