Can a workflow create a task from a catalog item that has mandatory fields?

[jubael]

Let us say we have two catalog items. One is a Purchase Request Process, and has mandatory fields. The other is PC Request Process, and it only has two fields, one of which is a multi-line text field for a description of work.

In my Developer environment, I have only:

Where the step 2 is calling the Catalog Item that has mandatory fields, and I'm using all the fields.

This simply created a task with the Trigger Task Variables:

I've been able to create catalog tasks, whereby I populate the system fields, but the variable sets, for the questions related to the called catalog item, I can't understand how to populate manually or bring over, nor was I able to present the form.

 

I want the requestor to fill out a simple form, and then I want staff to be presented with the purchase request form at the step after the requestor has completed the two-question catalog form. Is this possible?

[jubael]

After that I expect staff to review the task created in step 2, and fill out the question sets/form that the Catalog Item manages.

[jubael]

I spoke to my Platform Administration, from the mindset of a systems programmer, and after our conference we determined that the user is asking us to do something like "reuse a workflow from another catalog item" but is formally asking if we can "leverage the input form for the catalog item when the fulfiller receives a basic request."

We believe that this is beyond the scope of the platform, because the requestor input needs to align with the leveraged catalog request to make proper use of the workflow. His suggestion was to make a new workflow similar to the procurement workflow.

I'm still wondering if we can generate the step 2 catalog task, with the expectation the fulfiller is manually populating it to process it, automatically, or if the fulfiller would be expected to go to the catalog and kick off the procurement catalog item, manually filling in the form.

1. Requestor[required] requests a new endpoint device [dropdown list]

2. Workflow makes a new catalog task for fulfiller with fields 1 and 2 populated by the new endpoint request.

3. Fulfiller opens task, and sees fields [variable set inputs] necessary to route by the procurement workflow.

4. Procurement workflow operates successfully.

5. Service Desk receives ticket to deploy newly acquired device.

The above is the business process.

Is it possible for the workflow to present fields to populate, as described above, or will the fulfiller need to expect to trigger their own purchase request, changing the requestor?

Thank you all for taking the time to help a new-to-SN developer facilitate adoption at scale. 👊

[jubael]

This is the solution. We will set the UI to allow the fields to be edited. Here I use an example of making one field editable. I believe that this will be the same solution for the problem related above, but I've not tested it on my example yet. I have simply found the way to make the entry form input editable.