Hi all, we are in middle of planning for complete moving data from apps to

To expand on the record security, we faced the same issues when migrating from portal to tempo. With the goal of removing processes from memory as much as possible, we bypassed (mostly) process-backed records. With many process instances and complex security, we bypassed entity backed records - as best practice of creating one group per process instance is not feasible for us.

What we do is store user information in the CDT/database (employee ID) for all who act in the process. We then utilize service-backed records to retrieve the data from the DB via a!queryEntity(), filtering for records that employee (loggedinuser()) should have access too. If they are in an admin group, filtering is bypassed and all records are shown, etc. As service-backed records are very customizable, this works out great - with a little extra coding of course (than entity or process-backed).

To expand on the record security, we faced the same issues when migrating from portal to tempo. With the goal of removing processes from memory as much as possible, we bypassed (mostly) process-backed records. With many process instances and complex security, we bypassed entity backed records - as best practice of creating one group per process instance is not feasible for us.

What we do is store user information in the CDT/database (employee ID) for all who act in the process. We then utilize service-backed records to retrieve the data from the DB via a!queryEntity(), filtering for records that employee (loggedinuser()) should have access too. If they are in an admin group, filtering is bypassed and all records are shown, etc. As service-backed records are very customizable, this works out great - with a little extra coding of course (than entity or process-backed).