There are additional considerations when using the reject script statement if you install your application with other third-party applications in the same Microsoft Dynamics GP system. Depending on when the trigger runs relative to the button’s change script (before or after, using the attach_type parameter), reject script has different results. The following table shows multiple applications using triggers:
![[spacer]](1p.gif){kind=small}
|
Completion order |
Process |
|---|---|
|
1 |
App. 1 trigger - runs before the Save button change script |
|
2 |
App. 2 trigger - runs before the Save button change script |
|
3 |
App. 3 trigger - runs before the Save button change script |
|
4 |
original Save button change script |
|
5 |
App. 4 trigger - runs after the Save button change script |
|
6 |
App. 5 trigger - runs after the Save button change script |
Prior to the original Microsoft Dynamics GP change script, any application that issues a reject script statement will cancel all processing for the current focus event. For instance, if application 2 uses the reject script statement in a processing procedure, it cancels all remaining focus triggers as well as the original save button change script. This ensures that no further processing continues until all applications meet the appropriate conditions.
Once the Microsoft Dynamics GP change script runs successfully, all following triggers run successfully. For instance, if application 4 uses reject script, a focus trigger for application 5 still runs.