Object Types for Initiate Workflow are limited - How to specify Part Request?

[avillanueva]

I am creating a test workflow for a Part Request but want to use the initiate workflow option in the workflow administrator.  The problem is that Part Request is not one of the selectable types to link to the primary business object.

I've tried copy/paste, leaving type blank and searching by number. Is there a way to add additional types to the list?  As a backup, I considered if this is a dead end, just asking for the number and putting a lookup method in the workflow which will retrieve the part request and set it to the PBO. This is a generic problem since the list of objects above is short. There are more objects that you can run workflows against in the system. 

[joe_morton · Accepted solution]

I've used copy/paste during testing to quickly initiate a workflow on a Baseline object. That worked for me, but it's not something we want our users to have to do.

We've implemented several workflows where the subtype created has a custom lifecycle template where the first state initiates the workflow. The first task goes to whoever created the object and basically asks them to complete the task when they're ready to submit whatever it is to the next step.

[avillanueva]

I may have done something wrong. Copy/Paste did end up working. Thanks.