Locked fields for templates.PNG (190.2 KB)No lock icon for workflow field.PNG (127.44 KB)We have created a lot of specs using a template with an assigned workflow. Recently we resolved some of those specs to select a different workflow for business reasons. When we issued up these resolved specs, we want to keep the workflow that we resolved to but the workflow reverts back to the template workflow.
Based on Oracle documentation, it says if the workflow field on the template is locked, it will remain locked even when specs are issued up. The logic makes sense. However, there is no lock icon on our template to indicate the workflow field is locked. Our system behaves like there is a lock on the workflow field. Is this an intended behavior? Or is this a bug? Is there anyway that we can remove this lock from the template and break the inheritance without removing the workflow from the template? And also, is there anyway that we can remove this lock/inheritance for existing specs created from this template?