Fully automated workflow

Agree with Rob. At a high-level, it sounds possible. However, will people ever interact with any data from this? What do you hope to gain by performing this in Appian and instead not in a RPA tool or DB? Is there intelligence that the iBPMS can provide insight into, are there some steps somewhere in the middle a person might do, or is there exception flows that a person might do? 

Hello Christine, Thanks for your comment. We have exception queues which will be handled by Appian Users but mostly straight through process only. I have explained my requirement in by previous reply to Rob. Please suggest which one will be the good option for this requirement.

Hello Christine, Thanks for your comment. We have exception queues which will be handled by Appian Users but mostly straight through process only. I have explained my requirement in by previous reply to Rob. Please suggest which one will be the good option for this requirement.

Nothing you have written raises any red flags with respect to accomplishing this in Appian. 

Christine does ask an important question though.  What I'm hearing is that you wish to reconcile data throughout a series of systems when an event occurs.  This pattern is well-worn territory, and there are fit-for-purpose tools to do it.  Unless there are mitigating reasons that Appian has to be the tool,  it doesn't seem like a perfect fit.

It would be like using the back of a shovel to hammer nails into a board,  it would work, but a hammer would be a better tool.

Having said that, it seems like you may wish to expose an Appian process as a webservice:

• It will call a series of webservices to identified systems.
• Based on a the return values either use a looping function or MNI (multiple node instance) to retrieve further data
• Perhaps you will update some of those data items based on the original trigger
• Update the external systems via a WebService call (again, possible a looping function or MNI)
  
  

Some cautions.  MNI may be resource intensive.  The volume of data inside the process sounds like it might vary in size, be careful with your memory footprint (use sub-processes with short life cycles).  Seek opportunities to make a series of lightweight process models instead of monolithic ones.

Hello Richloan,

Thanks for your comment. 

I have developed my application in such way you mentioned in your comment. I raised this question to get the best solution for my requirement. Comments which you have posted are valuable to design my application.