Announcement

Collapse
No announcement yet.

App action not available for Releasing OB Line action

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

  • App action not available for Releasing OB Line action

    Hi Gurus,

    Instance: 5.5 CU6

    We have a requirement like this.

    The user selects more than one OB Line and then do enter Tag1 and Tag2 fields in the mass update screen.

    After updating the OB Lines, he selects the Action ''create_and_release_ob_line' and then releases the OB Lines.

    Now the requirement is that if the user by mistake has selected another OB Line(where Tag1 and Tag2 fields have not yet been entered), then OTM should stop releasing the first 2 OB Lines and give a screen saying that to enter Tag attributes for the third OB Line.

    In other words, I need an action check on ''create_and_release_ob_line'' Action. After investigation,I have found out that there is no App_Action_gid available for it in PUBLIC domain.

    Any idea how shall this requirement can be met and the solution should not affect other domains .Should we need to create a new App action Gid and then use it only for my domain?Any indepth details or links on it will be highly appreciated.

    Let me know..

    Thanks.
    Nikesh.

  • #2
    Re: App action not available for Releasing OB Line action

    You can refer to my another post at http://www.otmfaq.com/forums/f18/age...119/#post10017

    Note: Although my original post is for "Action Reasons", but it applies "Action Check" as well.
    --
    Joseph Liang
    MavenWire APAC
    http://www.mavenwire.com/

    Comment


    • #3
      Re: App action not available for Releasing OB Line action

      Originally posted by josephliang View Post
      You can refer to my another post at http://www.otmfaq.com/forums/f18/age...119/#post10017

      Note: Although my original post is for "Action Reasons", but it applies "Action Check" as well.
      Hi All,

      The requirement is now satisfied with the simple logic in xsl itself.
      I have customised the code to handle validation at the screen itself.

      Thanks a lot anyways for the replies.

      Cheers,
      Nikesh.

      Comment

      Working...
      X