Yep, stepelementrenderer was the right answer! You will notice that there are a lot of similar Methods that render all kind of stuff you see in MPP. As all the various elements have their unique look&feel, my version for the Operations may not work for the other elements the same way. I also would add the cycle_time to the caption, just like you did.
I also prefer option 2 for doing the rollup, as we normally need these kind of data in the db for various purposes.
We can use a similiar concept that is used for the Files flag in ItemType Manufacturer Part and Document. Take a look at the ItemType Document File. There you can find a Server Method that is called at 4 different events. We can use a modified version of this Method for 4 server events in the mpp_Step ItemType, that makes a SUM of the cycle_time property.
There are two options:
1. Trigger a SQL procedure (just like the files flag Method) that makes a SUM of the step cycle_times and writes the value in the operation cycle_time
SELECT SUM(CYCLE_TIME) AS SUM
FROM innovator.[ <-- add source itemtype --> ]
WHERE (SOURCE_ID = ' --- add source_id--- ')
2. Use AML instead of SQL procdure.You normally just use SQL procedures, when you really have no other options. When we work inside a ProcessPlan, we already have full permission access to Operations and Steps. So it should be possible update the cycle_time with AML.
