The campaigns module lets you track the execution of workflows on a set of objects declared in DataGalaxy. A campaign is based on the selection of a workflow previously configured in DataGalaxy (see How is a workflow defined?) and the selection of a set of objects on which to apply the workflow.
Once started, a campaign lets you track the progress of the objects concerned, and simplifies interactions by notifying the actors involved in each phase.
Why run a campaign?
A data governance initiative requires respecting operating rules and involving key players, to ensure that objects are correctly defined and contextualized. The goal is to obtain elements that users can understand and exploit as quickly as possible. DataGalaxy can make these rules explicit directly within the application, to help you achieve your goals.
You can track and manage your campaigns from the campaigns module, accessible from the application's sidebar.
What does a certification campaign look like?
In this example, a campaign is based on a critical data certification workflow, and the process is as follows:
- The Chief Data Office (CDO) team determines the perimeter of items to be certified and starts the campaign.
- Data stewards complete the information for each object.
- The CDO team validates the modifications made.
- A final check is carried out by the company's Data Governance Committee.
- Once the entire process has been completed, the objects participating in the campaign can be considered "certified".
The scope of application of campaigns is vast: they may concern certification, quality, legal constraints, sensitive data, and more. The concepts of campaigns and workflows have been designed to adapt to your needs.
How is a workflow defined?
A workflow is declared at the workspace level. It describes the operating rules of a process, and is defined by:
- An object attribute: an attribute that can be controlled to activate transitions. In many cases, this attribute is a status that lets you monitor the progress of the campaign at the object level.
- Campaign phases: phases that let you monitor overall progress.
- Transitions: the sequence of phases supported and the conditions required to activate them.
- Assignees: groups, roles or users responsible for carrying out tasks during a phase.
Workflows must be created using private API routes, which are introduced to you when you activate the feature on your environment.