Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
4 subscribers
Views
2191 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Based on Appian best practices in the documentation over the forum for Data Stor
a.sheikh
over 12 years ago
Based on Appian best practices in the documentation over the forum for Data Stores
forum.appian.com/.../Data_Stores
, We read that the best way to retrive data from external RDBMS into Data Store is to put into a sub process and call this sup process using process-to-process messaging, We want to understand in which cases do we have to do this best practices as we are evaluating the real need to use the one extra integration point like JMS. We just want a description about why is the best practices to do so, and is it only for retrieval data? or we can us it for both? ...
OriginalPostID-26716
OriginalPostID-26716
Discussion posts and replies are publicly visible
0
rajeshwers
over 12 years ago
We have all of our database calls SELECT, UPDATE, and INSERT as a call to a sub-process. Here are some advantages:
1. Helps with reusability. You will probably end up calling these processes multiple times across many processes.
2. If there are any changes at the database level, you have to just change the sub-process and republish it instead of having to republish the parent process. This is particularly useful when you are creating a new database/table. If you end up changing the design multiple times, you can just republish the sub-process.
3. It is lot easier for all of our developers to find where the database calls are. This is helpful for development and debugging.
4. You can have different developers work on the parent and sub-process resulting in faster application development.
5. We named our database related sub-processes with the table name as well. With hundreds of queries, this will increase the productivity of your developers as well.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
a.sheikh
over 12 years ago
Thank you Raj, I just want to calirfy the best to call these sub processes, is it using the sub-process node or call it using process-to-process message??
Appian wrote in the documentation the best way is to call it using process-to-process message, why is this?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mohammad Abusinnah
Appian Employee
over 12 years ago
Process to Process messaging allows to trigger events within a process, a process can contain many operations that are triggered by different events from type receive message (e.g. Update Student Table, Retrieve Student Record..Etc.).
Triggering a sub process smart service executes the from the start event of the sub process.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
meghan.mahar
Appian Employee
over 12 years ago
This is some great information. I've added parts of it the Data Stores page in documentation (
forum.appian.com/.../Data_Stores
Thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel