Tutorial | Blueprint Designer#
Get started#
Start using the Blueprint Designer by building and applying a new blueprint version.
Objectives#
In this tutorial, you will:
Fork and edit a Govern model version template.
Make changes to fields and views.
Customize a workflow and add a sign-off.
Apply your new blueprint version to an item.
Update your new blueprint with more complex views.
Prerequisites#
To complete this tutorial, you will need:
Dataiku 13.3 or later.
An Advanced Dataiku Govern license.
A Full Designer or Governance Manager user profile.
Familiarity with some technical specifications, available in our reference documentation on Blueprint Designer.
Customize a blueprint version#
If you want to do something like change the fields of a Govern item, you can create a custom blueprint version. In this section, you will copy and modify the blueprint version of a Govern model version.
Fork a blueprint version#
In most cases, you should fork (copy) an existing blueprint version and customize the copy.
Open your Govern node.
From the waffle menu, select Blueprint Designer.
In the left sidebar, select the Govern model version blueprint.
Click Create New Version.
Keep the default selection: Fork the system default. This will create a copy of the system default blueprint version.
Name the blueprint version
<YOUR_INITIALS> Tutorial Govern model version
.Click Fork. This will create the new blueprint version and open the editor.
Add a field#
Next, we’ll make some changes to the blueprint version.
Navigate to the Fields panel on the left.
To add a new field, click the plus button next to the search bar above the list of existing fields.
Define the new field as a Reference.
In the Field Name, type
Owner
. This will automatically generate a field ID, but you can define your own.Click Create.
Let’s finish configuring the new field.
Check the isList checkbox.
Set the cardinality Min field to
0
.Under the section Type: REFERENCE, leave the default selection Store.
From the Allowed blueprints dropdown, select User.
Click Save Draft.
Configure views#
Now, we will configure some views that will organize our fields.
Navigate to the Views panel.
Click on Model Version info.
On the Description view component, select the More Options menu.
Select Insert view component > After selection.
Next, finish adding the new view component.
In the list of available fields, choose Owner by clicking the plus button. This will add it to the list of selected fields on the right.
Click Create.
Click Save Draft to finish adding the Owner field you previously created to the model version info view.
Customize the workflow#
Another thing you can do in the Blueprint Designer is change the workflow of an item.
Return to the General panel.
In the Workflow section, click Add Step.
In the newly-added step at the bottom of the workflow, type
Validate
in the Step name field.From the View dropdown, choose Review info.
Drag this Validate step under the Review step.
Click Save Draft.
Add a sign-off process#
Next, let’s add a sign-off process to the new step in the workflow.
In our Validate step, click Create Sign-off.
For the Sign-off name field, type
Validation Sign-off
.For the Description field, type
Validation review process
.Under Validation Rule, keep the Make approval mandatory checkbox selected.
Continue to configure the sign-off:
In the Feedback section, select + Create Group.
In the Title field, type
Business reviewer
.Enable the Roles checkbox.
From the Select Roles dropdown menu, select Business reviewer.
In the Final approver section, enable the Roles checkbox.
From the Select Roles dropdown menu, select Final approver.
Click Create at the top of the page.
Activate and apply your template#
Now, take a look at your changes. You can archive you blueprint version once you are done testing it.
Caution
Make sure that you want to activate your blueprint version globally on your instance before completing this section.
Click the back arrow to return to your blueprint version.
Click Save and Activate > Activate.
Find a model version to govern on your instance or import this project into your Dataiku Design instance as a test project.
Govern the model version, making sure to select your blueprint version as the template.
Open your Govern model version.
Notice that the workflow steps include your new validate step.
You will also see your new owner field.
Tip
If you’re unfamiliar with how to govern a model version, see Tutorial | Dataiku Govern framework.
Advanced views in the Blueprint Designer#
If you want, you can try taking your views a few steps further in complexity. In this section, you will define and try out more granular settings in the Blueprint Designer.
Limit item selection#
Reference fields let users select existing items or create new items. With the Blueprint Designer, you can limit this action to only selecting or creating items.
In the Blueprint Designer, re-open your custom blueprint version.
Navigate to the Fields panel.
To add a new field, click the plus button.
Select Reference.
For the Field Name, type
Qualification Project
.Click Create.
In the Allowed blueprints dropdown, select Govern project.
Next, we’ll add this field to the same view that we worked with earlier in the tutorial.
Navigate to the Views panel.
From the available views, open Model version info.
On the Owner view component, select More Options > Insert view component > After selection.
In the list of available fields, choose Qualification Project by clicking the plus button.
Click Create.
In the Details panel of the Action Item component, find the Choose how the user can select items dropdown.
Choose Only select existing items.
Add a view condition#
Let’s also add a condition to the Action Item view component such that it only appears when the Description field is populated.
In the Conditional view section of the Details panel, open the Visibility condition dropdown and select Description.
From the Condition type dropdown, select Is not empty.
Click Save.
You will see a warning that tells you this change will affect an associated artifact. Take a moment to understand why, and then click Save.
Review changes#
Once you have made your changes, you’ll want to view their effects on the Govern model version.
Open the Govern model version that uses your custom blueprint version.
Notice that there is no Qualification Project field on the Overview page. The Qualification Project field does not appear yet because we added a view condition.
Click Edit and add some text to the Description field. The Qualification Project field should then appear in the page.
Click Select existing next to your Qualification Project field and choose a project.
What’s next?#
You just learned how to make a custom blueprint version in the Blueprint Designer. You can experiment with adding fields to different views to see where they appear in the applied template.
See also
If interested, take a look at importing templates in Tutorial | Use imported templates in the Blueprint Designer.