# Process types Available in... * Data Fabric * MDM Platform When creating a new Process from Talend Studio, you can select one of the proposed Process types: Before Saving/Deleting, Entity/Welcome Action, Smart View, or Other. The table below describes the different Process types: | Process type | Description | Associated plugin | | --- | --- | --- | | Other | Any type other than the listed ones. This process is usually executed after
an event occurs on master data in the MDM Hub. | Any in the list of available plugins. | | Before Saving | A Process that validates master data according to certain conditions before
saving it in the MDM Hub. This Process can be linked with a Job designed in
the Integration
perspective to perform the validation operation automatically.

This Process can alter the MDM record before it is committed in the database.
For instance, a Job may be run that completes the record with calculations
and/or enrichments.

Information noteNote:

The naming of this Process follows a specific pattern:
beforeSaving\_<entity>.

Note also that, for improved readability, in the MDM Repository view,
Processes are stored in subfolders by type and only the second part of
the name is displayed. | Any in the list of available plugins. If this Process is
linked with a Talend
Job, it uses the callJob plugin. This
plugin executes a call to the Job created in the Integration perspective to
evaluate the data to be saved and returns an error or warning message if
validation of this data is necessary.

For further information, see [Setting schema for a Before Saving/Deleting Job](https://help.qlik.com/talend/en-US/studio-user-guide/7.3/setting-schema-for-before-saving-deleting-job). | | Before Deleting | A Process that evaluates master data according to certain conditions before
deleting it from the MDM Hub. This Process can be linked with a Job designed
in the Integration
perspective to perform the operation automatically.

Information noteNote:

The naming of this Process follows a specific pattern:
beforedeleting\_<object name>.

Note also that, for improved readability, in the MDM Repository view,
Processes are stored in subfolders by type and only the second part of
the name is displayed. | Any in the list of available plugins. If this Process is
linked with a Talend
Job, it uses the callJob plugin. This
plugin executes a call to the Job created in the Integration perspective to
evaluate data before deleting it and forbid the change by an error
message.

For further information, see [Setting schema for a Before Saving/Deleting Job](https://help.qlik.com/talend/en-US/studio-user-guide/7.3/setting-schema-for-before-saving-deleting-job). | | Smart View | An XSLT-based Process that is automatically detected by Talend MDM Web UI.

It sets up a more customized graphical presentation for a given data object
(hiding some fields, displaying icons, etc.). The business user may choose
to display or print the object with this read-only personalized view or to
switch to the usual generated view where edits are possible.

Information noteNote:

The naming of this Process follows a specific pattern:
Smart\_view\_<entity>\_[<ISO2>][<#name>],
where the 2 character language ISO code and the name suffix are
optional. <ISO2> allows you to define multilingual smart views,
and the <#name> suffix allows you to have several
alternates smart views of the same entity.

This Process name will automatically fallback to
Smart\_view\_<entity> if the language is not
found, and the language you use to define the Smart View HTML parameters
in the Smart View editor will be picked as the default language.

Note that, for improved readability, in the MDM Repository view,
Processes are stored in subfolders by type and only the second part of
the name is displayed.

For further information, see [Creating a Smart View Process](https://help.qlik.com/talend/en-US/studio-user-guide/7.3/creating-smart-view-process). | Usually XSLT which transforms an XML document using XSLT.

But you can choose any number of steps using any plugin, as
long as the result at the end is HTML. | | Entity Action | A Process that is created in the Studio and automatically
listed in the Data Browser page in
Talend MDM Web UI. A business
user can then select any of these Processes listed in the Web User Interface
and click the Launch Process button
to start the selected Process.

This Process is always linked to a specific entity. You can design this
Process to do any tasks you want, for example sending the entity by email or launching a workflow to do
certain modifications on master data pertaining to the entity to which
the process is attached.

Information noteNote:

The naming of this Process follows a specific pattern:
Runnable\_<entity>. However, if you want to
customize the Process name, you must specify an Optional
Name in the Create Process wizard.
This adds a hash sign before the word you want to add to the Process
name. For example, giving the Optional Name Send
to an Entity Action Process on the Agency entity
would give the Process name Runnable\_Agency#Send.

Note also that, for improved readability, in the MDM Repository view
Processes are stored in subfolders by type and only the second part of
the name is displayed.


For further information, see
[Creating an Entity Action Process](https://help.qlik.com/talend/en-US/studio-user-guide/7.3/creating-entity-action-process). | Any in the list of available plugins. However, typical associated
plugins are callJob and
workflowcontexttrigger if the
Process is linked with a Talend Job or a workflow. | | Welcome Action | Similar to the Runnable Process but is not linked to a specific entity.

This Process is created in the Studio and automatically listed in the
Welcome page in Talend MDM Web UI.

You can design this Process to do any task you want, for example adding a new
record/entity or launching a
workflow to do certain modifications or synchronization on master
data.

Information noteNote:

The naming of this Process follows a specific pattern:
Runnable#<name>; for example
Runnable#AddNewRecord.

Note also that, for improved readability, in the MDM Repository view,
Processes are stored in subfolders by type and only the second part of
the name is displayed.

For further information, see [Creating a Welcome Action Process](https://help.qlik.com/talend/en-US/studio-user-guide/7.3/creating-welcome-action-process) | Any in the list of available plugins. However, typical associated
plugins are callJob and
workflowcontexttrigger if
the Process is linked with a Talend Job or a workflow. |