That is incredibly disappointing, and creating a lot more work (and room for error). With SS2, we can create cross sections and reference them into our deliverables. Then we are free to update and redesign, and the deliverables will always show the correct (only) cross sections. With the SS4 workflow, for every update we make, we must go into our deliverable and change that reference path from the old (bad) cross sections to the new (updated) cross sections. This leaves the door wide open for someone to forget that step, and for the deliverables to continue showing cross sections that could be months (and several iterations) old. I do not like it, no sir, I do not.
PLEASE tell the developers and/or file some kind of change request so that we can have UPDATABLE cross sections. I suppose in the best world, the option to UPDATE or REPLACE would be OK, too. Anything other than what we have now, which is the worst (IMO) possibility.
Thank you for confirming what I suspected.
PLEASE tell the developers and/or file some kind of change request so that we can have UPDATABLE cross sections. I suppose in the best world, the option to UPDATE or REPLACE would be OK, too. Anything other than what we have now, which is the worst (IMO) possibility.
Thank you for confirming what I suspected.