Right now we have an existing application (non-appian), it has two tables: an ap

guozhangy over 10 years ago

Right now we have an existing application (non-appian), it has two tables: an approved table and a pending table. When a record is in pending stage, it was stored in pending table and it will move to the approved table after the approval.

My question is what is the best pratice to handle the Pending records when we move to Appian? Should we keep the Pending records in the table or should we move the Pending records into the Appian Process instance? We can have three options:

1. Keep the pending records in pending table only, all the related actions (EDIT/DELETE/APPROVE) will be in a new Process Modal.
2. Keep the pending records in Appian process instances, all the related actions (EDIT/DELETE/APPROVE) will be in quick tasks.
3. Keep the pending records in both Pending tables and Appian process instances, all the related actions (EDIT/DELETE/APPROVE) will be in quick tasks.

From my experience, I feel more comfortable to use option 1, it's much e...

Discussion posts and replies are publicly visible

Parents

0 guozhangy over 10 years ago

Thanks for all the replies. It seems the only advantage of using Process Instance is the race condition, which I have heard of but I never implemented purposefully in my Process Modal/Quick Tasks.

I also checked the Memory Efficient best pratices, my process modal is very complicated and clumsy because of all those ad hoc Quick Tasks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 guozhangy over 10 years ago

Thanks for all the replies. It seems the only advantage of using Process Instance is the race condition, which I have heard of but I never implemented purposefully in my Process Modal/Quick Tasks.

I also checked the Memory Efficient best pratices, my process modal is very complicated and clumsy because of all those ad hoc Quick Tasks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data