Introduction to the Semarchy Workbench | ||
---|---|---|
Previous | Next | |
Introduction to Semarchy Convergence for MDM | Logical Modeling |
To access Semarchy Workbench, you need a URL, a user name and password that have been provided by your Semarchy Convergence for MDM administrator.
To log in to the Semarchy Workbench:
http://<host>:<port>/semarchy/
where
<host>
and
<port>
represent the name and port of host running the Semarchy application. The Login Form is displayed.
To log out of the Semarchy Workbench:
A model edition is a version of a model. This edition can be in a closed or open status. Only open editions can be edited.
Opening a model edition connects the workbench to this edition.
Note: Before opening a model edition, you have to create this model and its first edition. To create a new model and manage model editions, refer to the Models Management chapter.
To open a model edition:
The Semarchy Workbench is the graphical interface used by all Semarchy Convergence for MDM users. This user interface exposes information in panels called
Views and
Editors .
A given layout of views and editors is called a
Perspective .
There are several perspectives in Semarchy Workbench:
When a perspective opens, a tree view showing the objects you can work with in this view appears.
This view appears on the left hand-side of the screen.
In this tree view you can:
Certain perspectives includes an
Outline view. This view shows in tree view form the object – and all its child objects – in the editor currently opened.
This view appears on the left hand-side of the screen.
You can use the same expand, double-click, right-click actions in the outline as in the tree view.
An object currently being viewed or edited appears in an editor in the central part of the screen.
You can have multiple editors opened at the same time, each editor appearing with a different tab.
Editors are organized as follows:
When the object in an editor is modified, the editor tab is displayed with a star in the tab name. For example,
Contact* indicates that the content of the Contact editor has been modified and need to be saved.
To save an editor, either:
You can also use the File > Save All menu option or Save All toolbar button to save all modified editors.
To close an editor, either:
You can also use the File > Close All menu option or the Close All option the editor’s context menu (right-click on the editor’s tab) to close all the editors .
In the editors and dialogs in Semarchy Workbench, the
Auto Fill checkbox accelerates object creation and edition.
When this option is checked and the object name is entered using the CamelCase, the object Label as well as the Physical Name is automatically generated.
For example, when creating an entity, if you type
ProductPart in the name, the label is automatically filled in with
Product Part and the physical name is set to
PRODUCT_PART.
Diagrams are used to design models and workflows.
The Model Diagram Editor shows a graphical representation of a portion of the model or the entire model.
Using this diagram, you can create entities and references in a graphical manner, and organize them as graphical shapes.
The diagram is organized in the following way:
Info: After choosing a tool in the palette, the cursor changes. Click the Diagram to use the tool. Note that after using an Add... tool, the tool selection reverts to Select.
For more information about the model diagrams, see the Diagrams section in the Logical Modeling chapter.
The human workflow diagram shows a graphical representation of the human workflows.
Using this diagram, you can design tasks and transitions for a workflow.
The diagram is organized in the following way:
In this diagram, you can drag the transition arrows to change the source and target tasks of a transition.
For more information about the human workflow diagrams, see the Creating Human Workflows in the Working with Applications chapter.
Other views (for example: Progress, Validation Report) appear in certain perspectives. These views are perspective-dependent.
User preferences are available to configure the workbench behavior. These preferences are stored in the repository and are specific to each user connecting to the workbench. The preferences are applied regardless of the client computer or browser used by the user to access the workbench.
Use the Window > Preferences dialog pages to set how you want the workbench to operate.
You can browse the Preferences dialog pages by looking through all the titles in the left pane or search a smaller set of titles by using the filter field at the top of the left pane. The results returned by the filter will match both Preference page titles and keywords such as “general” and “stewardship”.
The arrow controls in the upper-right of the right pane enable you to navigate through previously viewed pages. To return to a page after viewing several pages, click the drop-down arrow to display a list of your recently viewed preference pages.
The following preferences are available in the Preferences dialog:
Under the Data Stewardship preferences node, preference pages are listed for the data locations accessed by the user and for the entities under these data locations. These preference pages display no preferences and are used to reset the Filters, Sort and Columns selected by the user for the given entities, as well as the layout of the editors for these entities (the collapsed sections, for example). To reset the preferences on a preferences page, click the Restore Defaults button in this page.
Sharing preferences between users is performed using preferences import/export.
To export user preferences:
To import user preferences:
Tip: This section provides a quick introduction to the SemQL language. For a detailed description of this language with examples, refer to the "Semarchy Convergence for MDM SemQL Reference Guide".
SemQL is a language to express declarative rules in Semarchy Workbench. It is used in Enrichers, Matchers, Validations, Filters and Consolidators.
The SemQL Language has the following characteristics:
A
Qualified Attribute Name is the path to an attribute from the current entity being processed.
This path not only allows accessing the attributes of the entity, but also allows access to the attributes of the entities related to the current entity.
Examples:
FirstName
: Simple attribute of the current
Employee entity.
InputAddress.PostalCode
: Definition Attribute (
PostalCode ) of the
InputAddress Complex Attribute used in the current
Customer entity.
CostCenter.CostCenterName
: Current
Employee entity references the
CostCenter entity and this expression returns an employee’s cost center name
CostCenter.ParentCostCenter.CostCenter
: Same as above, but the name is the name of the cost center above in the hierarchy. Note that
ParentCostCenter is the referenced role name in the reference definition.
Record1.CustomerName
:
CustomerName of the first record being matched in a matcher process.
Record1
and
Record2
are predefined qualifiers in the case of a matcher to represent the two records being matched.
The SemQL Syntax is close to the Oracle Database SQL language for creating expressions , conditions and order by clauses.
In expressions, conditions and order by clauses, it is possible to use the SemQL functions. The list of SemQL functions is provided in the SemQL Editor
Info: SemQL is not a query language: SELECT, UPDATE or INSERT queries are not supported, as well as joins, sub-queries, aggregates, in-line views, set operators.
Enricher Expressions
InitCap(FirstName)
InitCap(FirstName) || Upper(FirstName)
Replace(Upper(InputAddress.City),'CEDEX','')
In these examples,
InitCap
,
Upper
and
Replace
are SemQL functions. The concatenate operator
||
is also a SemQL operator.
Validation Conditions
InputAddress.Address is not null and
( InputAddress.PostalCode is not null or InputAddress.City is not null)
In this example, the
IS NOT NULL
,
AND
and
OR
SemQL operators are used to build the condition.
Matcher
InputAddress.Country || InputAddress.PostalCode
SEM_EDIT_DISTANCE_SIMILARITY( Record1.CustomerName, Record2.CustomerName ) > 65
and SEM_EDIT_DISTANCE_SIMILARITY( Record1.InputAddress.Address, Record2.InputAddress.Address ) > 65
and SEM_EDIT_DISTANCE_SIMILARITY( Record1.InputAddress.City, Record2.InputAddress.City ) > 65
In this last example,
SEM_EDIT_DISTANCE_SIMILARITY
is a SemQL function.
Record1 and
Record2 are predefined names for qualifying the two record to match.
The SemQL editor can be called from the workbench when a SemQL expression, condition or clause needs to be built.
This editor is organized as follows:
Plug-ins allow extending the capabilities of the Semarchy Convergence for MDM using Java code and external APIs.
Plug-ins are used to implement enrichers or validations not feasible in SemQL.
The plug-ins have the following characteristics:
Examples of plug-ins:
More information:
Previous | Top | Next |
Introduction to Semarchy Convergence for MDM | Logical Modeling |