Design around the job
Choose the views, inputs, and actions the team needs to complete its work.
Build internal tools on your business data.
Work Surfaces. Give your team an application designed around its workflow, with the records and actions it needs.
Product walkthrough. Press Space or Enter to pause or play.
Work Surfaces. An application shaped around the job.
Connect business records
Use shared objects and existing tools rather than copying context into another application.
Review and release
Inspect the application, test the workflow, and make the reviewed version available to its users.
From a working copy to a working application.
Follow Factory Control through its implementation and release, then see the separate operating review that remains open.
Factory Control uses native components and project-local bindings to connect work items, requirements, and reviews.
Open the interface and follow a lithium work item before applying the source. The preview lets the team review how the work fits together.
The reviewed Factory Control application is active. The team can open it to track the three queue items and their linked requirements.
The linked Logistics Exception Desk preview still shows pending Compliance. An application release does not approve a change to shipment policy.
In practice
Meridian needs a work queue that connects requirements, implementation, and reviews. Factory Control gives the team that application on Pascal’s existing objects and workflows. The active application can be used while the lithium policy change follows its own approval path.
Explore the solutionDiscuss an internal tool.
Show us the workflow that needs a better tool. We’ll discuss its users, data, actions, and a first application scope.