My last post talked about setting up a transform map to create HR Cases. This post will talk about triggering that from a Record Producer.
To limit access to the Load Data item in the left navigation menu, a Record Producer can be set up to manage the submission of the template. The visibility of the Record Producer itself can managed through criteria to control who can reach it.
First, for this example I set up a "request" table to manage the bulk requests from the portal form. There is an attachment field and a fake status field just to manage the Flow for it. The record producer was set to write to that "request" table.
The record producer itself was very basic, just one mandatory variable to force the use to attach a spreadsheet.
My flow processed when this request was created. The steps I set up were to do the following:
- Go to my Data Source and remove all the attachment associated to it
- Copy the attachment from the request record over to the data source
- Trigger a scheduled import job to pull in the attachment and run the transform
- Add a step at the end to complete the process
In order to trigger the Transform, I needed to set up a Scheduled Import Job to process the file when I called it from the Flow Action.
When uploaded and submitted, the portal form would look something like this
And just as I had hoped, the outcome was a collection of cases produced by the transform map that I had triggered.
