Implications

Updated on 08 Mar 2024
1 Minute to read

Article summary

Did you find this summary helpful?

Thank you for your feedback

Other Implications❔ Identify how synergies flowacross features to amplify results!🔎

In today's dynamic business landscape, organizations rely heavily on their software systems to streamline operations and improve efficiency. One integral component of these systems is Business Rule Designer, which allows organizations to define and automate their business logic. However, the impact of Business Rule Designer extends beyond its primary domain and has significant implications on other modules within the software ecosystem. In this article, we will explore how Business Rule Designer Influences Form Designer, Notification Designer.

Form Designer

One of the significant implications of Business Rule Designer on Form Designer is the introduction of Form Relations.

Through Form Relations, Business Rule Designer enables organizations to establish relationships between Source Records and Target Records. This is invaluable when dealing with complex data structures and dependencies.

Notification Designer

Effective communication is a key component of any business operation, and Notification Designer facilitates this by allowing organizations to create and manage various notification templates. These templates are used to send alerts, updates, and reminders to users and stakeholders. The integration of Business Rule Designer with Notification Designer provides a seamless workflow for automation.

The following GIF illustrates the Implications of Business Rule Designer on other modules.

Figure: Business Rule Designer Implications on other modules

Let's explore the following use-case.

Use-Case
User Persona: Application Designer

Solution

ACME Solutions' IT Department has a requirement to have a Service Request created automatically from an Incident whenever an Incident is assigned to a certain workgroup.

In order to achieve this the Create Record feature of Business Rule Designer can be used to create a service request automatically.

Step 1: Create a Business Rule named Incident to Service Request.

Step 2: Select a condition such that whenever an Incident is created for a particular workgroup, then the Business Rule should execute.

Step 3: Select the Create Record feature of Business Rule Designer and use a pre-existing Form Template that has been created under Form Designer to create a Service Request from an Incident.

Was this article helpful?

What's Next

Overview