• Note that the UI presents these details

    imageSo - the question is - how to access this data from the workflow

     

     

  • Here is the answer

     

    select

      ta.APPLICATION_NAME Trusted_APP_NAME, ta.APPLICATION_DESCRIPTION, ta.CLIENT_ID TRUSTED_APP_CLIENT_ID,

      r.name, r.description

    from 

     T_AV_CHANGE_REQUESTS r

     join T_AV_TRUSTED_APPLICATION ta on ta.id = r.source_object

    where 1=1

      --and r.id = 123456 -- Set request Id from workflow variables

      and source_type = 'TA' -- Trusted Application

    order by r.id desc

    ;

     

    Expand Post
    • another approach:

       

      In the createChangeRequest API, you can add the following to the payload:

      • <Parameters>
      • <Parameter [scope=public|job|private]>
          • <Name>value</Name>
        • <Value>value</Value>
        • </Parameter>
      • </Parameters>

       

      This will create a variable which will be accessible in the workflow.

      Expand Post
      • Yes

        but it is much better not to rely on the goodwill of the other party

        Especially when trying to detect malicious attack

         

        It would have been nice to get this information without accessing internal tables

        (And without relying on data the client is sending)