This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Locked tasks

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
When a human task is imported from IBM® WebSphere® Business Modeler some of the items in the editor will be locked. This locking is designed to ensure interoperability between IBM WebSphere Business Modeler and IBM Integration Designer. If you unlock and modify any of the locked items then your human task might no longer be synchronizable with IBM WebSphere Business Modeler exports. It is, therefore, recommended that you do not unlock items.

In creating BPEL processes a typical workflow involves iterative development between IBM WebSphere Business Modeler and IBM Integration Designer. When you import a process from IBM WebSphere Business Modeler that contains human tasks some of the properties of those tasks will be locked. Locked properties are displayed with a padlock icon.

You can modify unlocked properties and still maintain interoperability with IBM WebSphere Business Modeler.

When you select a locked property, in the Properties view you will see the message The property_type property is currently locked because the human task was created in IBM WebSphere Business Modeler, where property_type is the locked property that you have selected. You cannot modify a locked property.

It is strongly recommended that you do not unlock properties. Once a property is unlocked, and the task is saved, the property cannot be locked again.

Provided that you do not modify locked properties, when you Synchronize with Modeler Export (to update the task with new changes made in IBM WebSphere Business Modeler), you will find that there are no conflicting changes. See the related topic Synchronizing human tasks in iterative development for more details on synchronizing.