Sunday, April 30, 2017
Workflow & Collaboration

Master Data and Workflows

Data governance defines the process through which master data should be managed. It is the role of technology to implement that process and enforce its adherence. Maestro Workflow provides this technology, enabling a much more sophisticated workflow capability than can be accomplished with MDS’ business rules. Maestro Workflow also provides better visibility back to governance with respect to the performance of the organization, allowing governance to amend processes as needed, based on how well the current ones are executed.

Key Workflow Capabilities

Maestro Workflow delivers capabilities in four key areas:

  • Workflow Tasks: Assign tasks to users, typically including the contribution and/or approval of master data. Tasks can be prioritized and assigned to a single user or a group of users. Users are notified via email when a task requires completion, and are presented with a simple form for completing that task.
  • Workflow Administration: Configure workflow tasks, including who is assigned to complete tasks, the design of the form for each task, the priority and duration, etc. Administrators also have visibility into the current state of workflows.
  • Workflow Design: Design workflows using drag-and-drop workflow authoring in Visual Studio. Workflow patterns are provided to support a variety of process requirements, including state-based and flowchart-based flows. Workflows can conditionally split, merge, and branch based on run-time values.
  • Web Based Tasks: Provide users with a Web-based task list for managing their work.

Architecture

Workflows are powered by the Maestro SDK service, which centralizes their management. The workflows themselves, as well as data stewards, all interact through this service. As a platform, Maestro Workflow leverages native .NET components, and workflow development occurs in Microsoft Visual Studio, using Maestro Workflow project templates and libraries. No additional Microsoft or third-party software must be licensed.

Example Workflow Scenarios

Product and Customer are the two most common MDM domains. Workflow is a critical need in both of these domains.

Product: Creation of a new product, from initial inception to final approval, can involve many different actors across the organization. Workflows allow management to create tasks and assign them to different actors. As each task in a workflow is completed, the process immediately moves forward to the next task or tasks. Formal approval can be included in the process, providing centralized control over which final products are made available to the rest of the organization.

Customer: A workflow is often needed as part of a customer data onboarding process. As a new customer is created, its address/name/phone/email will need to be verified. Based on the outcome of verification, some stewardship may be required to address any identified issues. The customer will then need to be matched, and based on the results, reviewed. Additionally, new source and/or master customer records may need to be further attributed with categorization or hierarchy information.

In both cases, Maestro Workflow provides the tools to model complex process requirements and drive a collaborative process within your organization.

Request more information about Maestro Workflow & Collaboration

12345678910

Welcome to MaestroCentral!

Profisee customers and partners are invited to login with their provided credentials to access secure content, including software downloads, installation guides, release notes, and supporting utilities and materials. For additional MaestroCentral accounts, Maestro Administrators should request via the Profisee Support Portal.

Member Login

Username:
Password: