Hi All, I need your advice on below approaches for handling a scenari

Hi All,

I need your advice on below approaches for handling a scenario.

Scenario:- We have something like a Header/Detail tables. Each header record can contain around 100-200 detail records. User input the Header ID ; we need to get all the detail records and process each one of them and does DB update
Approach 1: Can we go for MNI ,for each detail record ; simultaneously processing all detail records.
Approach 2: In a single sub-process get all detail records ; subject each record through some business logic. Once all detail records are subjected to processing , the CDT which holds all these detail records is used for the Detail DB Update. (Single Update ,but containing all records)
Which among the above two approaches is best for handling this scenario w.r.t to performance and stability of platform. fyi, this is not a batch process ,but an interactive process where the header is keyed in by the user.

OriginalPostID-191410

OriginalPostID-191410

  Discussion posts and replies are publicly visible

Parents
  • Now we might generally get a doubt re how we must ensure that Appian is able to handle the process and all the operations in it comfortably. This should be answered by Appian Health Check at forum.appian.com/.../Appian_Health_Check.html. Here are a few examples:
    Example 1: Let's say you have opted for Approach 2 (without any tweaks) and have written 200 detail records with huge amount of data. This operation might fall under High/Medium risk and the category falls under 'Slow data store operations' at forum.appian.com/.../Appian_Health_Check.html.
    Example 2: Let's say you have opted for Approach 2 (without any tweaks) and have processed 200 detail records(as you have earlier said that each detail record needs some processing prior to update) in a single shot. The operation might be flagged as High/Medium risk and the category falls under 'Slow expressions' at forum.appian.com/.../Appian_Health_Check.html.

    If you aren't aware of the Health Check and its applications, still you can also make a solid design by studying the Health Check concepts and the practices suggested in it.

    Further I am not sure if you have designed the processes (which deals with huge data-sets) under Health Check's constraints. But doing so for some time will give you a wider insight and experience over how to deal with the scenarios which you have asked for.
Reply
  • Now we might generally get a doubt re how we must ensure that Appian is able to handle the process and all the operations in it comfortably. This should be answered by Appian Health Check at forum.appian.com/.../Appian_Health_Check.html. Here are a few examples:
    Example 1: Let's say you have opted for Approach 2 (without any tweaks) and have written 200 detail records with huge amount of data. This operation might fall under High/Medium risk and the category falls under 'Slow data store operations' at forum.appian.com/.../Appian_Health_Check.html.
    Example 2: Let's say you have opted for Approach 2 (without any tweaks) and have processed 200 detail records(as you have earlier said that each detail record needs some processing prior to update) in a single shot. The operation might be flagged as High/Medium risk and the category falls under 'Slow expressions' at forum.appian.com/.../Appian_Health_Check.html.

    If you aren't aware of the Health Check and its applications, still you can also make a solid design by studying the Health Check concepts and the practices suggested in it.

    Further I am not sure if you have designed the processes (which deals with huge data-sets) under Health Check's constraints. But doing so for some time will give you a wider insight and experience over how to deal with the scenarios which you have asked for.
Children
No Data