• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 9 subscribers
  • Views 2966 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

Web API requirement.

sharathp0002
Certified Senior Developer

Hi Folks, 

 

I'm trying to achieve the following.

Use case:

In our application, Appian is implementing as a headless application. Business wants to complete tasks from the external web application, but the process flow should be built in Appian. As a poc we are planning to built two screens from the external web application. When the user fills out input parameters  and clicks on submit web API will initiate process flow and send back response.
Now user from the external web application will be on the second screen and fill the input parameters and submit the form this time Appian should able to another 2nd web API and continue the process flow.
 
Is it possible to stop process flow till the second API call and then resume process flow whenever we get request from the external system.
 
Any inputs would be great, as I'm just beginning, I can implement more efficient code.  
Thanks

  Discussion posts and replies are publicly visible

Parents
  • 0

    Why don''t you create two WebAPI endpoints? I think it would be easier and will it it more reusable assuming that you divide the operations properly?

    For example:

    Create a Process Model with these Elements

    1. User Input Task->
      1. Form 1 (Enter User Information)
      2. User enters information
      3. User submits
      4. Send data to Web API #1
      5. User gets response.
    2. User gets response -> If continue = YES (XOR Gateway)
      1. YES:
        1. User Input Task
        2. Pass data from Form 1 to Form 2 (Enter other details) in Process Variables
        3. User enters information
        4. User submits
        5. Send data to Web API #2
        6. User gets response
      2. NO, display reason not to continue
    3. User Input Task -> Form 3 -> Display Confirmation
Reply
  • 0

    Why don''t you create two WebAPI endpoints? I think it would be easier and will it it more reusable assuming that you divide the operations properly?

    For example:

    Create a Process Model with these Elements

    1. User Input Task->
      1. Form 1 (Enter User Information)
      2. User enters information
      3. User submits
      4. Send data to Web API #1
      5. User gets response.
    2. User gets response -> If continue = YES (XOR Gateway)
      1. YES:
        1. User Input Task
        2. Pass data from Form 1 to Form 2 (Enter other details) in Process Variables
        3. User enters information
        4. User submits
        5. Send data to Web API #2
        6. User gets response
      2. NO, display reason not to continue
    3. User Input Task -> Form 3 -> Display Confirmation
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.