Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you restrict Object Types when using the Create Package step from a Request ?

Highlighted
bzdafro
Collector

How do you restrict Object Types when using the Create Package step from a Request ?

Hi,

 

We are moving from a deployment model (where users create their packages)  to a demand model (where users fill in details on one master request form and select what they want to do, and the request spawns the package etc ).    The issue we are trying to figure out is how to set / or restrict the object type being used by the  "Create Package" step?    We have one workfow with the deployment steps ( pre-migration > Deploy to IT > Deploy to QV  )    but  will have many object types using this workflow.   Each object type is for a different technology - Oracle moves, SQL moves, Unix moves etc.    The user selects what type of Code Deployment they are performing on the Request.    We can't figure out how to use the Create Package step to not only spawn the package, but auto select the object type, based upon what type of deployment the user is doing.     Is something like this possible?

 

There is a field on the Package Create step (shown below ) to set the default workflow, but nothing referencing object type.     Or does everyone create separate workflows for deployment types  ( this is what we are trying to get away from doing ).  

 

 

6 REPLIES
randull
HPE Expert

Re: How do you restrict Object Types when using the Create Package step from a Request ?

Hi,

 

You can make this using tokens from the request type validations where the user choose only the object types you listed.

 

You can use the following guide as your reference,

 

http://support.openview.hp.com/selfsolve/document/KM994606

 

Also, the data model can help you out.

 

http://support.openview.hp.com/selfsolve/document/KM00208454

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
bzdafro
Collector

Re: How do you restrict Object Types when using the Create Package step from a Request ?

Hi,

Thanks for the links. We have looked over this documentation and cant find what we are trying to do documented anywhere. We could easily add a field on the request and build a select query for the user to choose the exact object type. Say they choose 'SQL Code Move'. How could the Create Package workflow flow create a package and only allow the user to select 'SQL Code Move' as the Object type? ( When the workflow has 50 other object types availble to choose)

randull
HPE Expert

Re: How do you restrict Object Types when using the Create Package step from a Request ?

Hi,

 

 

You can use the "Create package" execution step to create the package from the request.

 

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
bzdafro
Collector

Re: How do you restrict Object Types when using the Create Package step from a Request ?

Yes we are using the Create Package step on our workflow.  It does spawn a new pkg # and associates it with the parent request.   However, when the user jumps to the workbench to open the pkg, they still have to choose  an object type and app code ( required fields).    The user is being presented with all the object types available on the workflow ( which will be a lot ).    We would like only the object types associated with the action on the parent request to be shown.     If they choose SQL deployment, only SQL object types are available.    We have a wide range of deployment types that we manage - .NET, Oracle, WebSphere etc.... 

 

 

 

 

 

Utkarsh_Mishra
Honored Contributor

Re: How do you restrict Object Types when using the Create Package step from a Request ?

If you are using general workflow for all the obejct types, then I don't think that  applying sepecific OT filter will be feasible. But you can try the alternative.

 

Create the Pakage workflow according to "OBJECT TYPE". i.e. for SQL, create the workflow that will have only SQL Object type assocatiated with it... similarly can create for other object types like Oracle Apps , EBS etc..

 

 

And for the scenation where for a change requst multipe object types migration is invloved, then try using the RELEASE, where you can select multiple packages (of different object types).

 

 

 

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
skbd
Regular Collector

Re: How do you restrict Object Types when using the Create Package step from a Request ?

OK - perhaps I am not understanding everything here, but what I would do is create one Request workflow and multiple different Package workflows.

Then you can define the allowed object types for each given package workflow via the Deployment Management Settings tab in the workflow as I show in the pic.

If you are wanting to do this in a single package workflow, then you are in for a struggle.

Edit - realizing this is over a year old, so you may have already figured it all out and I would be very interested in the approach you took.

 

Steve

 

//Add this to "OnDomLoad" event