Blueprints forcibly appearing in 22.2 is against our policies.
Does anyone else think Blueprints does NOT reflect their working style? We will NEVER use blueprints because it doesn't reflect our business at all, nada, nil, null, etc.
Our official policy is to use an admin created, vetted, official template, no ecxeptions.
Why is Workfront taking away our ability to govern what users see? With all the talk of governance, Workfront is eroding our ability to govern.
We chose Workfront for our ability to customize what users see based on OUR policies and SOP, not Workfront's uneducated recommendations. Forcing an unusable feature on us seems like a pretty arrogant blunder.
