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

guozhangy over 9 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 ashish.deshmukh
A Score Level 1
over 9 years ago

I think keeping data in database will be a good option as:
1. Keeping the data in database will help to short live the processes(The processes defined as related actions to edit/delete/modify data).
2. It also depends on the number of records. If number of records are large, the instances which are live will be large, which increases the number of active instances in system which should be avoided.

Also, if possible you can orchestrate the data from two tables and keep only one tables where the Pending and Approved records in table can be differentiated by maintaining status for each record.(That depends upon your database design.)

Hope this is helpful.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 ashish.deshmukh
A Score Level 1
over 9 years ago

I think keeping data in database will be a good option as:
1. Keeping the data in database will help to short live the processes(The processes defined as related actions to edit/delete/modify data).
2. It also depends on the number of records. If number of records are large, the instances which are live will be large, which increases the number of active instances in system which should be avoided.

Also, if possible you can orchestrate the data from two tables and keep only one tables where the Pending and Approved records in table can be differentiated by maintaining status for each record.(That depends upon your database design.)

Hope this is helpful.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data