Community Tip - You can change your system assigned username to something more personal in your community settings. X
(preface: we use Change Management for Initial Release and Revisions for WTParts & WTDocuments, Promotion is used only for WTParts tomove from one"frozen/Released equivalent" State toanother)
So I'm trying to do a Workflow that will allow for a release at an advancedmaturity (State) for a limited kind (not Type or SoftType) of WTParts. I've pretty much got everythingexcepta logical test for "is the QueryResult element a WTPart" so I don't end up trying to set EPMDocuments &WTDocuments to States that are not in their Lifecycle. The idea here is toset the State onWTParts in the Resulting Objectsin preparation for the Change Transition when triggered. As an example, making something Obsolete is more closely related to aChange than a Promotion Notice so in this casewe'd set State to"Pending Obsolescence" which would have a change transition to "Obsolete".
Any guidance on how to test a mixed list of WTPart, WTDocument and EPMDocuments to diffentiate the WTParts?