• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 10 subscribers
  • Views 6188 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Best Practices

Activity Chaining Issue : Which is better - to use a Submit Button or a!startProcess from a normal Button

ejass
A Score Level 1

Hi All,

We are currently developing an application which is having a Huge number of Objects/Nodes in Process Model and with Activity Chaining, persisting a lot of Data, performing a lot of other operations as well Using a Submit Button and coming back to the same page.

I have a functionality in a sub process which is a parallel process on calling multiple Integrations from external Sources, using this on the main process Model with activity chaining on the Submit Action. 

I have faced an issue where the activity chaining breaks and the applications shows the home page.

We need a solution where we have decided to make the above specified functionality independent.

So my question is : which is better .. Pros and Cons : 

1. Use the same Submit Button which calls the Parent Process Model, which in turns call the Sub Process only (based on Condition), so making it independent.

2. Use a!startProcess function : call the sub-Process on Button click(No Submit Button) from interface independently and display the updated details in back to the Interface.

 

Please let me know which is the best approach and what can i implement to optimize the whole

  Discussion posts and replies are publicly visible

Parents
  • 0
    Hi,

    If you have huge number of nodes/ objects in process model between two UI tasks then the process can break since Appian limits to have 50 nodes between the two UI nodes, this includes script tasks, gates, sub-process calls etc.

    I suggest you perform small operations like saving small amount of data to DB or change status by using a!startProcess function since if you include large operations then it will delay the page load time and even lead to performance issues.

    In cases where you have to navigate the process flow and include new assignee's or perform heavy transactions, you can proceed with modeling them via nodes, but make sure you do not include more then 50 nodes, a way to avoid this is to logically group multiple nodes to a single script node or use save to multiple datastore entities if the data is independent.

    Thanks.
Reply
  • 0
    Hi,

    If you have huge number of nodes/ objects in process model between two UI tasks then the process can break since Appian limits to have 50 nodes between the two UI nodes, this includes script tasks, gates, sub-process calls etc.

    I suggest you perform small operations like saving small amount of data to DB or change status by using a!startProcess function since if you include large operations then it will delay the page load time and even lead to performance issues.

    In cases where you have to navigate the process flow and include new assignee's or perform heavy transactions, you can proceed with modeling them via nodes, but make sure you do not include more then 50 nodes, a way to avoid this is to logically group multiple nodes to a single script node or use save to multiple datastore entities if the data is independent.

    Thanks.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.