Scheduled requests

[Jasper van den Berg]

We want to be able to use Intelligent Capture for Scheduled Requests. Please see details in the attached Word document

 

Regards,

Jasper van den Berg

Feature request - scheduled change requests.docx

[Jim]

Interesting idea, I had this similar issue when running our morning checks process. you could use the update custom fields node at the start of the process based on source to get it working with the current functionality like I had to with ours if you hadn't already considered this  

[Steve Giller]

In the Workflow, test each "Default Value" (e.g. h_description) and if it's empty, populate it with the correct value using an "Update Request" node.

[Jasper van den Berg]

1 hour ago, Steve Giller said:

In the Workflow, test each "Default Value" (e.g. h_description) and if it's empty, populate it with the correct value using an "Update Request" node.

The Workflow works fine, the feature request is to add the input from the intelligent capture when using scheduled request which is currently not supported. See Scheduled Requests (hornbill.com)

[Steve Giller]

I can't speak on behalf of the developers, but the idea of having an Intelligent Capture which by design is for a human to enter details attached to a scheduled request, which by design has no human interaction seems to be a contradiction.

I appreciate that in your example you appear to have a capture with default values, but there is no way of guaranteeing that every capture linked to every scheduled request would have the required default values.

This is why I am recommending that you move the populating of the fields from the Capture to the Workflow.

[Jasper van den Berg]

5 minutes ago, Steve Giller said:

I can't speak on behalf of the developers, but the idea of having an Intelligent Capture which by design is for a human to enter details attached to a scheduled request, which by design has no human interaction seems to be a contradiction.

I appreciate that in your example you appear to have a capture with default values, but there is no way of guaranteeing that every capture linked to every scheduled request would have the required default values.

This is why I am recommending that you move the populating of the fields from the Capture to the Workflow.

But this takes more work to complete and the Workflow is larger than than the intelligent capture, therefore we would like to have the option added. 

The same Workflow can then still be used for all change request and mainly consist of the approval section.

 

Can you please raise this with your development team?

[Jasper van den Berg]

Any updates from the developers?

[Steve Giller]

This is tagged as a feature request so the developers will see it.

That does not guarantee acceptance, or even a response.

The process for feature requests is documented here.