10. Common keyword principle

 

The intelligent link between the field and the ERP

The common keyword is particularly powerful trigger logic in SOOKSOOK.

It's not just a field or a tag.
👉 It is a central mechanism that allows several elements of the system to be intelligently connected in order to decide whether an ERP flow should be triggered.

In a traditional architecture, integration rules are often rigid, complex and difficult to maintain.
With the common keyword, SOOKSOOK simplifies this logic by introducing a correspondence principle.

👉 It is not an isolated rule that triggers the flow,
👉 but the overall consistency between several elements.

---

General principle

Each piece of data in SOOKSOOK (publication, message, form, etc.) is placed in a context.

This context is defined by:

• who creates the data

• on what equipment

• in what environment

• for what use

The common keyword acts as ainvisible conductive threadwhich connects all these elements.

👉 It allows you to say:
“This data belongs to this ERP scenario”

---

10.1 Role

🔹 Principle

The common keyword makes it possible to link the different components of the system together in order to structure the flow.

It is used to connect:

• publishing,

• the profile,

• the machine,

• the routing rule,

• XML programming.

---

🔹 Explanation

Without this mechanism, specific rules would have to be created for each possible combination:

• user machine data type destination

👉 This would be complex and difficult to maintain.

With the common keyword:

✔ a simple match is enough
✔ the system becomes more readable
✔ flows are easier to manage

---

🔹 Concrete example

👉 Post with keyword:ACIERIE

• user profile:ACIERIE

• machine :ACIERIE

• routing:ACIERIE

• XML:ACIERIE

➡ Result:

✔ full consistency → triggered flow

---

👉 If an inconsistency appears:

❌ blocked flow

---

🔹 Global vision

The keyword acts as alogic connectorbetween all the bricks of the system.

👉 It aligns the field, the data and the ERP system.

---

10.2 Where it can be defined

🔹 Principle

The common keyword can be defined at several levels of the system.

This characteristic is essential because it allows the operation to be adapted to various organizations.

---

🔹 Possible locations

The keyword can be defined:

• in the flow configuration,

• in the user profile,

• in the technician profile,

• in the machine or equipment profile,

• in the routing rule.

---

🔹 Explanation

Each element of the system can carry contextual information.

The keyword allows you to match this information with each other.

👉 Example:

• a site → keyword

• a machine → keyword

• a flow → keyword

👉 Everyone speaks the same “language”

---

🔹 Flexibility

This logic allows:

• manage multiple sites

• manage multiple clients

• to manage several types of flows

• to evolve the system without breaking it

👉 We change a keyword → we change the behavior

---

10.3 Effect

🔹 Principle

The system analyzes the consistency of the keyword across all elements.

---

🔹 Operation

When the correspondences are consistent between:

• the data

• the profile

• the machine

• routing

👉 the stream becomes eligible for sending

---

👉 Otherwise:

❌ the stream is automatically blocked

---

🔹 Explanation

The keyword acts as aglobal validation key.

It ensures that:

• the data is sent to the right place

• the correct scenario is used

• the correct XML format is applied

---

🔹 Benefits

This mechanism allows:

• simple activation,

• great flexibility,

• multi-site or multi-client management,

• a clear separation of the different integration scenarios.

---

🔹 Advanced example

👉 Keyword:SECURITE

➡ HSE flow
➡ XML security
➡ specific routing

---

👉 Keyword:MAINTENANCE

➡ maintenance flow
➡ other XML
➡ other destination

---

👉 Without changing the system
👉 just by changing the keyword

---

Strategic role in SOOKSOOK

The common keyword is not a simple parameter.

👉 This is the heart of integration logic.

It allows you to:

• simplify configuration

• avoid mistakes

• make the system adaptable

• structure flows

---

Conclusion of the chapter

The common keyword completely transforms the way ERP flows are managed.

Instead of multiplying complex rules:

👉 we use simple, coherent and intelligent logic

---

👉 SOOKSOOK does not trigger a flow because data exists
👉 he triggers it becausethe whole system is aligned

---

👉 Result:

✔ simpler
✔ more powerful
✔ more flexible
✔ more reliable