Advanced Workflow (AWF) Deployment Size Recommendations

The Advanced Workflow (AWF) feature manages the lifecycle of records in specific types of applications or questionnaires by visually modeling your business process and connecting steps in that process to actions in Archer. Performance information and deployment size recommendations vary based on the number and complexity of AWF scenarios in your deployment.

On this page

Workflow Complexity

The following table provides guidelines to evaluate the complexity of your AWF scenarios in your deployment.
Complexity Standard Nodes Send Notification Nodes

Simple

5-10

0

Semi-Complex

10-30

1-2

Complex

30+

2+

Deployment Size

The following table provides deployment size recommendations based on the number and complexity of AWF scenarios in your deployment.

Size

Number of Scenarios

 Complexity

Small Deployment

1-4

Simple

Medium Deployment

5-9

Semi-Complex

Large Deployment

10-20

Complex

Important: If your deployment exceeds the criteria of a large deployment for any of the categories, contact your Archer sales representative for additional hardware sizing assistance.

Small Deployment

Hardware Configuration

The following table describes the hardware configuration for a small deployment.
Server Type Quantity CPUs Memory

Web Server

1

4

16GB

Database Server

1

4

16GB

Performance Analysis Notes

  • Data imports of up to 1,000 new records to applications with simple workflow typically do not over-utilize hardware resources or cause errors.
  • Data imports of up to 10,000 new records to applications with semi-complex workflow typically utilize moderate Web Server CPU resources, and sometimes cause errors.
  • Data imports of any size for applications with complex workflow typically utilize near-maximum Web Server CPU resources, and frequently cause errors.
  • This environment supports the creation of up to 17 new records per minute for applications with simple workflow. Further increasing the rate of record creation typically results in longer content save times.

Medium Deployment

Hardware Configuration

The following table describes the hardware configuration for a medium deployment.
Server Type Quantity CPUs Memory

Web Server (runs IIS and AWF services)

2 (load balanced)

4

16GB

Services Server

1

4

16GB

Database Server

1

8

48GB

Performance Analysis Notes

  • Data imports of up to 1000 new records to an application with simple or semi-complex workflow typically do not over-utilize hardware resources, and rarely cause errors.
  • Data imports of up to 10,000 new records for an application with semi-complex workflow typically utilize moderate hardware resources, and rarely cause errors.
  • This environment supports the creation of up to 133 new records per minute for applications with simple workflow. Further increasing the rate of record creation typically results in longer content save times.

Large Deployment

Hardware Configuration

The following table describes the hardware configuration for a large deployment.
Server Type Quantity CPUs Memory

Web Server (runs IIS and AWF services)

4 (load balanced)

8

24GB

Services Server

2

8

24GB

Database Server

1

16

96GB

Performance Analysis Notes

  • Data imports of any size to applications with workflow of any complexity typically do not over-utilize hardware resources or cause errors.
  • This environment supports the creation of up to 300 new records per minute for applications with simple workflow. Further increasing the rate of record creation typically results in longer content save times.