DocuSign CLM Subworkflows

1. SUBWORKFLOWS
And why they don’t suck!
DOCUSIGN CLM

2. REASONS WHY THEY DON’T SUCK
Process
Separation
Future
Maintenance
Quick
Testing
Help future
users maintain
the system
without breaking
it
Keep each
process
separated into
their own
sections
Test your
configurations
faster and on the
stop
Workload
Distribution
Delegate work
between team
members easily

3. By separating every process (Legal Review, External
Review, Exhibit Generation, etc.) into their each
subworkflow, you can more easily build, test, and
maintain a system!
When each process is separated you can focus on each
process individually for each section of the project
timeline rather than worrying about the entire process
altogether.
PROCESS SEPARATION!

4. Clients can easily get overwhelmed and
confused when you try to squeeze all of
their processes into a single workflow.
By using subworkflows you make it easier
for clients to identify where each process is
in their system. And ultimately helps them
to maintain the system on their own!
FUTURE
MAINTENANCE

5. TESTING
This speeds up the testing process tremendously,
especially when you’re working with a very large
workflow! You can use Params to kickstart the
subworkflow individually.
QUICK

6. WORKLOAD DISTRIBUTION
Subworkflow #1
Subworkflow #2
Subworkflow #3
You can designate separate processes to
different developers without the need for each
one to to wait on another to finish in a workflow
before they begin their configurations.
This also prevents the potential for overriding
eachothers work when there may be
miscommunications about who is in/out of
workflows since CLM does not currently have
the ability to check workflows in or out.