Scribd
Upload
55 views2 pages

Appian Advanced Process Modeling

The document discusses how to design processes in Appian by breaking long processes into start processes and subprocesses. Some advantages of shorter processes are that they take less memory, are easier to maintain, allow parallel work, and components can be updated independently. Processes should be split when they require multiple users, contain timers or rules, or reuse standard operations. Subprocesses can run synchronously or asynchronously, with tradeoffs between memory usage and activity chaining.

Uploaded by

Krithika Karthik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
55 views2 pages

Appian Advanced Process Modeling

The document discusses how to design processes in Appian by breaking long processes into start processes and subprocesses. Some advantages of shorter processes are that they take less memory, are easier to maintain, allow parallel work, and components can be updated independently. Processes should be split when they require multiple users, contain timers or rules, or reuse standard operations. Subprocesses can run synchronously or asynchronously, with tradeoffs between memory usage and activity chaining.

Uploaded by

Krithika Karthik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Appian Advanced Process Modeling:

In Appian, Data is centralised & structured using Record Data types.


Break long process in to start process & sub process
Use of start process: quick archival & deletion , also runs in different
engine

1. How to design process in Appian?


To create shorter related action process
Use start process & sub process to break long process

2. Advantage of shorter process:


Any active process in appian takes memory , so shorter process takes
less memory
Instead, build short-lived processes that start or end with a database
record. easier to maintain, and your server’s system resources will be
utilized more efficiently.
Active processes cannot be updated to a new version
Easy for testing
If you break it up into multiple processes, you can have multiple people
working in parallel.

3. When Should I Split Processes?


Break up a process into several shorter processes if your process
requires multiple touches or approvals from different users.
f a longer process model remains active because it contains a timer or
rule event
If you have to handle a large set of data from an integration,
If your application has to reuse the same standard operations, isolate
these repetitive steps using a different, possibly shorter process.

Workflows that contain reusable steps, stay idle because of a timer, or


use an integration are likely to require a sub-process.
Subprocess - can run synchrously / Asynchronously

Synchronous: Parent flow will wait for child process to complete before
continuing to the next node. Ex: Approval from depts
Process variables can be transferred back & forth between child &
parent process
Allows activity chaining
Memory usage is large when compared to Ayschronous
Aysnchronous: Parent flow continue to the next node as soon as as
subprocess starts.Ex: Send an Email & integration
Process variable can be transferred to the subprocess that cannot be
returned back to parent process.
Not allows activity chaining
Memory Usage is less since it not wait for parent but it finish

You might also like