ER Generic Server Openings

Overview

ER Generic Server openings are a special type of openings used to customize server operations. Its resource set includes precommit, init, compute, and UX-specific openings.

 

ER Generic Server Openings
│
▼
┌─────────────────────────────────────────────┐
│ Types of Openings (Business Rules)                                                           │
└─────────────────────────────────────────────┘
│
├── Precommit → Validate before saving
├── Init → Set values during creation
├── Compute → Perform calculations
└── UX → Control user interface

 

What are Precommit Triggers

Introduction

Precommit Triggers (also known as ER Generic Server Openings) are server-side business rules that execute before a transaction is committed to the database.

They allow you to implement custom logic using EKL (Engineering Knowledge Language) to control and validate system behavior.


Key Concept

  • Precommit triggers run before data is saved
  • The action (for example, promote or modify) is already performed
  • But the change is not yet committed to the database

     Example:
    During a promote operation, the object’s maturity is already updated when the trigger runs, but it is not yet saved permanently.

 

Types of Server Business Rules

  • Check (PLMPreCheck) – Used for validation
  • Override (PLMPostCheck) – Used to modify behavior
  • Action (PLMAction) – Used to perform additional operations

     

Where Precommit Triggers Are Used

Precommit triggers are executed during various operations such as:

  • Create
  • Modify attributes
  • Delete
  • Connect / Disconnect
  • Promote / Demote
  • Revision ....and more

for more info you can check this page:

Explore more about: Precommit trigger

 

Order of Operations

When a transaction is executed, the system follows this sequence:

  1. The system registers the transaction
  2. The system executes the action (for example, promote)
  3. The system triggers the Precommit Business Rule
  4. If no error occurs, the transaction is committed
  5. If an error occurs, the transaction is aborted

     

Supported Environments

Precommit Triggers are available in:

  • On-Premise
  • Private Cloud
  • Dedicated Cloud
  • Public Cloud
Precommit triggers run on the <strong>server side using EKL</strong>
They are part of <strong>ER Generic Server Openings</strong> in Data Setup
They replace older server-side validation mechanisms (deprecated)

 

****Additional Info****

Init Openings

An opening ID is an entry point used to customize business logic. Initialization at Creation (init_create) allows to define attributes on new objects.

Initialization at Creation init_create allows to define attributes on new objects. This opening ID is executed on the proxy object that represents the future entity, either a business object or a relationship. This future entity only exists as a Java object in memory until a create method is invoked. Refer to the documentation of any app to determine if it supports this opening ID.

For more information, refer to the following DS documentation page:

Explore more about: Init Openings

 

Compute Openings

Compute openings enable apps to customize server operations by creating and triggering business rules that compute values and provide results. However, compute openings cannot modify any objects, including the current object.

 

UX-Specific Openings

The “UX-Specific ER generic server openings” are dedicated to customizing the New... dialog boxes and the Properties tab of the Information panel in web apps. UX openings allow you to guide users through the user interface by limiting their options and providing direct feedback prior to saving their changes.

For more information, refer to the following DS documentation page:

Explore more about: UX-Specific Openings

 

Other References

User Assistance: About EKL Server Functions > EKL Profile Cards

How to use Precommit Trigger

 

Authors: @AB @PJ

Comments 0