Understand how hooks can be used to perform custom actions
- Last UpdatedOct 23, 2024
- 1 minute read
There are many scenarios where the extensibility hooks can be used to check for specific conditions, process custom actions to control the flow of middleware event, and so on. The examples listed in the table below explain how the hooks can be used to perform custom actions.
|
Hook Intercept |
Condition/Process |
Hook Type |
Example Scenarios |
|---|---|---|---|
|
sp_U_Process_CheckIn |
Process Status changed from or to Certified. Changing the status of a process from or to Certified requires a user to have special permission/privilege. |
Pre-Hook |
A pre-hook can intercept the incoming middleware call (e.g., Process.CheckIn) to validate whether the user has a special permission to change the process status from/to certified, and act based on the outcome from the custom validation. |
|
sp_I_Cert_User_Link |
A visual inspection of user’s certification is required before the certification is attached to the user. |
Pre-Hook |
A pre-hook can intercept the incoming middleware call (e.g., Cert_User_Link.Add) to send an email (using workflow) to the factory supervisor for authorization before the certification can be attached to the user. |
|
sp_U_Job_Exec_ |
Creating a new work order that is not instantiated from a process requires authorization from the supervisor. |
Pre-Hook |
A pre-hook can intercept the incoming middleware call (e.g., Job_Exec.StartDataEntryJob) to initiate a workflow for the supervisor to authorize the transaction before the data entry job is created in the MES database. |
|
sp_U_Storage_Exec_AddInv |
Push the inventory quantities to the ERP. |
Post-Hook |
A post-hook can do the post processing on the Storage_Exec.AddInv call to push the inventory quantities to an external application/database. |