What is the best practice for configuring process instance archival ?

Hi All,

I would like to know what is the best practice for configuring process instance archival recommended by Appian .

Since the default archival setting is 7 days which can be changed by the system administrator, is it solely dependent on the requirements that whether we can keep the process instance for 3 to 7 days or there is a specific best practice of archiving with X days that can be followed during development.

Thanks in Advance!

Akhila

Parents
  • The approach I take is to work with the business to define a 'Process Archiving/Deletion Policy'. There is going to naturally be a tension between the technical need to get completed process instances out of memory as soon as possible, with any true business need to retain them for a specific purpose. Like I try to classify the process models in order to make defining such a Policy as simple and easy to understand as possible:

    • Utility Process Models - e.g. write data to a database - if that's all the process does, it either works or it doesn't. If it does then you can see in the database what the result was.I tend to have these set to 'Delete' immediately (i.e. 0 days)
    • Automated Process Models - it depends!
    • User-Centric Process Models - it depends!

    There needs to be a clear rationale for retaining or archiving completed instances that is linked directly to a business need. If the requirement is, say, auditing, you might implement an audit in a database and say the requirement is fulfilled there. 

    I definitely do NOT let any developer leave the Archiving to the default value as this indicates to me they have not thought about or applied the agreed Policy. If the value happens to be the same as the default I STILL make them configure it explicitly as it tells me they have considered and implemented the Policy. 

Reply
  • The approach I take is to work with the business to define a 'Process Archiving/Deletion Policy'. There is going to naturally be a tension between the technical need to get completed process instances out of memory as soon as possible, with any true business need to retain them for a specific purpose. Like I try to classify the process models in order to make defining such a Policy as simple and easy to understand as possible:

    • Utility Process Models - e.g. write data to a database - if that's all the process does, it either works or it doesn't. If it does then you can see in the database what the result was.I tend to have these set to 'Delete' immediately (i.e. 0 days)
    • Automated Process Models - it depends!
    • User-Centric Process Models - it depends!

    There needs to be a clear rationale for retaining or archiving completed instances that is linked directly to a business need. If the requirement is, say, auditing, you might implement an audit in a database and say the requirement is fulfilled there. 

    I definitely do NOT let any developer leave the Archiving to the default value as this indicates to me they have not thought about or applied the agreed Policy. If the value happens to be the same as the default I STILL make them configure it explicitly as it tells me they have considered and implemented the Policy. 

Children
No Data

 Discussion posts and replies are publicly visible