how many related actions and record actions can be added in record, is there any limit?
Discussion posts and replies are publicly visible
I have not seen any limits here posted, and we have one Record that just crossed to 101 Related Actions and all is operating fine.
My use case is unique, back in the day when we converted from the OLD Portal environment to Tempo (our system has been running since 2007), Sites were not as robust yet so we transitioned by creating an Applications record with a listing of each app available in our system. All Related Actions for these applications themselves are added under the parent Applications Record and only visible when viewing that application.
Hi Chris,How many users use this application? how was application performing?
Rajesh Kilaru said:Hi Chris,How many users use this application? how was application performing?
Some updates as the original note was a few years ago:
~25,000 users had/have access to this record and a subset of it's related actions, which was operating fine with 101 related actions.
We upgraded to Appian 23.3 in late 2023, afterwards the record still worked fine for end users, system administrators began receiving "Memory Circuit Breaker" errors when attempting to edit the record type.
We opened a case (624375), and after some re-factoring and were able to reduce the 101 related actions to ~30. This record type now runs 32 related actions on Appian 24.1 with no issues.
Chris said:and after some re-factoring and were able to reduce the 101 related actions to ~30
ugh. we're still stuck with >70. It makes things.... slow. The refactoring you did was, i assume, "combine X separate related actions into a parent related action with in-process branching", or similar? We need to do some of this but our manpower is very limited and it's such a big lift. Any secret tricks you may have, in the meantime, might be appreciated.
Mike Schmitt said:ugh. we're still stuck with >70. It makes things.... slow. The refactoring you did was, i assume, "combine X separate related actions into a parent related action with in-process branching", or similar? We need to do some of this but our manpower is very limited and it's such a big lift. Any secret tricks you may have, in the meantime, might be appreciated.
Our updates were easy, luckily - had a number of functions essentially duplicated (Start Process links available on the Summary page, and in Related Actions), and some legacy actions that were due for cleanup (retired processes/functions, etc).
Depending how your app is setup and used, if you could get away with moving some of the related actions to the Summary page or other views as a!startProcessLink(), that would be one way to reduce RA's...