Announcement

Collapse
No announcement yet.

Using Automation Agent - Before Persist for UI checks

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Using Automation Agent - Before Persist for UI checks

    I understand that the "Before Persist" option in automation agents is primarily used for Integration transactions. Can this also be used for UI checks in place of Action checks? The reason I am asking is to consolidate all the business rules in one place rather than duplicating in both Action checks and Automation agents. As an e.g. I would like to detect a duplicate order release based on a reference field/qualifier and not persist the transaction if there is already an order release present. This logic needs to be in place for both integration transactions and manual entry.

    Thank You,
    Vijay

  • #2
    Re: Using Automation Agent - Before Persist for UI checks

    Automation Agent can be used for Integration or manual entry or both, depends on the setup.

    Another option is to use "User Exit".
    You may refer to some other posts in the forum.
    Exit Stage Right or Left? - Oracle OTM / G-Log GC3 Community Support
    http://www.otmfaq.com/forums/f20/ref...2572/#post8063
    --
    Joseph Liang
    MavenWire APAC
    http://www.mavenwire.com/

    Comment


    • #3
      Re: Using Automation Agent - Before Persist for UI checks

      Joseph, Thank you very much for the tip on User Exit, it works like a charm. Since this is PL/SQL, I am assuming we can do java stored procedures from PL/SQL to do more complex validations like calling external web services. Is the User Exit a reliable option? Anything I need to watch out for before starting to use it extensively?

      Comment

      Working...
      X