I'm not as familiar with FileDOC as FileResult, because we use FileResult even for transcription that we get from the hospital, but based on my knowledge of the routing list function it seems like you would want to use the routing list and a team. Here is that syntax if you are not familiar with the routing list:
U is for provider and T is for team
The 3 digits after the colon is entry code for the provider or team
The entry before the first pipe will get a verify task and any subsequent providers or teams after the first pipe will get a review task
I believe it works similarly for both FileDOC and FileResult, but the tasks are different.
I was also looking into the cclist parameter a little more and it looks like the syntax is something like this:
This can also be a pipe delimited list and includes several more parameters than what is indicated in the string above
This is the list I took out of the SP that actually executes the cclist:
@UserID int =0,
@DestinationName varchar(255) = '',
@PaperTray varchar(255) = '',
@IncludeEnvelope BOOL = 'N',
@EnvServerName varchar(255) = '',
@EnvPrinterName varchar(255) = '',
@EnvPaperTray varchar(255) = '',
@EnvTemplateName varchar(255) = '',
@Address1 varchar(255) = '',
@Address2 varchar(255) = '',
@City varchar(255) = '',
@State varchar(2) = '',
@Zip varchar(12) = '',
@PriRecipFLAG char(1) = 'N'
It looks like it can only be provider or referring provider for the recipient type.
Distro type looks like it can be print, fax, or review task.
There is a line in the SP documentation that leads me to think there is a better document regarding this, but I've not found it yet. The documentation says this about the cclist.
"valid formats are listed in the document creation specification"
I am not what the document creation specification is.
Maybe Justin knows what this is.
Hope this is helpful in some way.