The purpose of this article is to explain and illustrate configuration steps for conditional validation. In the context of the article, conditional validation refers to an operation whereby validation for a secondary attribute is triggered/enabled when a condition on a primary attribute is met. The article extends concepts covered in our official Application Design Guide, and utilizes the best practice of combining a form validation (which shows useful information but is non-blocking) with a step validation (blocking), used when the user should be forced to fix an issue before proceeding.

In many cases, a Semarchy user may want to... (More)

When you create a new Business View for an entity, this Business View allows you to display data to business users in the front-end application.

In Business Views, you can add Transitions. A Transition allows you to add child entities and other objects so that you can provide more information to the business user.

What's a Transition?

For example, if your Business View is for Customers, you could add a transition to the child entity Addresses. This transition will allow the business user to browse Customers and then see all the Addresses linked to that particular customer record.

Other examples... (More)

This article gives an example of an advanced validation rule that navigates to parent and child records from a central entity (Customer). If you are struggling to write SemQL for a complex business requirement, this example might give you ideas on how to structure your own validation rule.

Business Background

This is a Customer B2B use case. Here are some relationships between entities in this B2B data model.

• Customers (child) belong to a MasterCustomer (parent)
• MasterCustomers (parent) can have many SubGroups (child). SubGroups are a way to categorize different Customers within 1 MasterCustomer.
• Customers can belong to many SubGroups... (More)

This article shows how to manage Complex Attributes with Complex Type in a Semarchy xDM model. Complex Attributes are useful to manage multi-attributes information like Addresses or Legal Information, that you need to use for multiple entities in your model.
It allows you to save design time and to keep a clear view of your business model by avoiding too many attributes on entities. It's also useful when you use Enrichers to keep both original and enriched values into your model or to store multiples output of Enrichers.

Create Complex Type

Before adding a Complex Attribute to your model,... (More)