tracker issue : CF-3194049

1) Currently, cfschedule's result attribute is undocumented. Suggested wording:

-----------
Req/Opt: Required for the list action. (once Bug #3194048 is fixed)
Description: Name for the query in which cfschedule returns the result variables.
-----------

2) Currently, cfschedule's result struct is undocumented. Suggested wording (using cfquery's result struct doc as a reference):

-----------
The cfschedule tag also returns the following result variables in a query. You can access these variables with a prefix of the name you specified in the result attribute. For example, if you assign the name myResult to the result attribute, you would retrieve the status of the second retrieved task by accessing #myResult.status[2]#. The result attribute provides a way for functions or CFCs that are called from multiple pages, possibly at the same time, to avoid overwriting results of one call with another.

Variable name    |    Description
---------------------------------------------------------------------
result_name.chained_task | {description here}
result_name.clustered | {description here}
result_name.crontime | {description here}
result_name.enddate | {description here}
result_name.endtime | {description here}
result_name.eventhandler | {description here}
result_name.exclude | {description here}
result_name.file | {description here}
result_name.group | {description here}
result_name.interval | {description here}
result_name.last_fire | {description here}
result_name.mode | {description here}
result_name.oncomplete | {description here}
result_name.onexception | {description here}
result_name.onmisfire | {description here}
result_name.overwrite | {description here}
result_name.path | {description here}
result_name.priority | {description here}
result_name.proxy_port | {description here}
result_name.proxy_server | {description here}
result_name.proxy_user | {description here}
result_name.publish | {description here}
result_name.remaining_count | {description here}
result_name.repeat | {description here}
result_name.resolve_url | {description here}
result_name.retry_count | {description here}
result_name.startdate | {description here}
result_name.starttime | {description here}
result_name.status | {description here}
result_name.task | {description here}
result_name.timeout | {description here}
result_name.url | {description here}
result_name.username | {description here}

Of course, hopefully the underscores are removed first (per Bug #3194042).

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3194049

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments: