Hi, I am trying to add a column to a custom report that collects Task data. The new column will show the highlighted number (in this example: "00041") in the task name/description.
The debug says this field is ColumnID: "displayIdentifier" coming from Row Object: wt.change2.WTChangerRequest2.
Is this number only available in the ChangeRequest2 table?
If so, how can it be linked to Work Item?
TIA!
Hi @mariaSutton
So you can use condition if the primaryBusObj instance of WTPart or EPMDoc, or Change Tassk, or Change Order and get the value from that object..
You always needs to retype the primaryBusinessObject to correct type if you want to work with them..
PS> there is not general table for primaryBusinessObject - this object can be any object in the system and each object type usually has own table and APIs.
There are several type groups as Persistable that can be used on most of the object types.
PetrH
Hi @mariaSutton
Workflow task is just one type. The task is connected to the PrimaryBusinessObject that can be almost "any" object in the system.
In the workflow PrimaryBusinessObject is also variable where you can find many sub class types as Change Order, Change Request, etc. but usually one workflow is used for one specific object type.
Here is example for more change object type workflows
//change activity
wt.change2.WTChangeActivity2 thisActivity = (wt.change2.WTChangeActivity2) primaryBusinessObject;
String number = thisActivity.getNumber();
//change order
wt.change2.WTChangeOrder2 changeOrder = wt.change2.WTChangeOrder2)primaryBusinessObject;
String number = changeOrder.getNumber();
//change ChangeRequest
wt.change2.WTChangeRequest2 changeRequest2 = (wt.change2.WTChangeRequest2)primaryBusinessObject;
String number = changeRequest2.getNumber();
PetrH
@HelesicPetr is correct. There is no parent object that can be used. The 'Primary Business Object' is not a type, per se, that can be used to build a query and return information about all potential objects that can be routed through a workflow. Depending on what data you need, maybe this approach can work for you. I've used this for first pass yield reporting. Rather than try and get all the actual types that represent the PBOs - just focus on the voting and work items. If you're interested in the result of votes (i.e. Workflow task has been completed) you can introduce the table like in the image below.
Then to get the Number of the object you can just pull the calculated attribute of the PBO's Identity through from the Work Item directly, as shown below.
This works if A) you don't need to know about tasks that are potential or accepted (i.e. not completed) and B) if you don't need to input criteria into your report based on the PBO Identity.
If either of those things are needed then you would have to pull in all of various PBO tables into the report design and using a concatention function you can represent a single column for 'number' and show the number from the applicable PBO type in that row. This is more advanced.
---
---
Yes, the Primary Business Object can be used with ChangeIssues to see all Variances and PR's in your workflows.
---
A different case: link CR's to Work Items. Remove the ChangeIssue above, and link to ChangeRequest instead
---
This shows every CR that is involved with a workflow. Likewise you could link with ChangeActivity
I think maybe you're after something like below which is from https://www.ptc.com/en/support/article/CS294349 (I added the User table so I could quick filter to a test data sample). You can see that the 'change number' appears in a single column regardless of object type, i.e. it shows CR, CN, CA, etc. Within that function if you want to build out additional information in the string such as "[Number], [Description]" you can use Concatenate within the Null function arguments to include the additional information beyond the number. This solution also allows you to integrate the Promotion Requests because it is not specific to "Change Issues" or object types related to "change" only. I have done this and tested and it works. You can continue to layer in as many 'Null value' functions as you need.
