Cost - Change request approval workflows additional condition option

[ashley.weirUMD5E]

Currently we would like to setup Change request workflows so they go to the appropriate team members for each review type. 

Our CRs are split into cost banding which is easy to do but then they are further split down into the CR type, which is a current metadata field we have added e.g. Design, Operations, Customer change etc... 

At the moment there is no field we can select to further split these out. If custom metadata fields could be added this would really enhance the CR customisation and make it easier to direct the CRs to the appropriate technical reviewers

[ian_turner]

Hello, can you please clarify your request with additional detail?

We already support custom attributes in workflow conditions as per 

And/Or you can customise our system types and use in workflow conditions 

So is unclear specifically what is being requested beyond the current capability?

[ashley.weirUMD5E]

Hi Ian, 

Thats the change Order in terms of it being a PCO OCO etc.. 

In our Change Requests when they are a PCO they have a set of subcategories e.g.

Design Change, Client Change, Risk, Operations etc... 

It would be preferable if this could be a filter in the CRs to select one of these sub options rather than having 20 different "main" change order types like there is in your screenshot. This makes it more difficult to manage the changes. Currently the CRs are a bit too rigid

[ian_turner]

Sorry i still don't follow. Let me try again and I'll split in to 2 responses so hopefully you can help me understand what I'm missing

OPTION 1. Use customised standard "Type" attribute which is a sub category of PCO, COR, OCO etc. It can be used for organising, numbering, grouping PCOs etc and for workflow conditions

I added the 3 examples from your original request Customer change, Operations, Design

[ian_turner]

OPTION 2. Use a custom attribute which is a sub category of PCO, COR, OCO etc. It can be used for organising, numbering, grouping PCOs etc and for workflow conditions

I added the 3 examples from your original request Customer change, Operations, Design to a new custom attribute called CR Type

[ian_turner]

I tagged the PCOs using both methods, and both methods can be used to achieve a similar outcome.

Apologies If I'm misunderstanding but am a little confused what is missing?