Good practice to verify the dependencies of the custom attribute with scripts/API's/Plugins and Operational Behavior before removing from the RTC editor presentations
Arun K Sriramaiah 2700076GE8 Visits (1378)
Have you run into issues saving a workitem after removing custom mandatory attributes from an RTC editor presentation?
Note: A good practice is to verify the dependencies of the custom attribute with scri
Scenario: Below is one scenario that explains why even after removing the mandatory attribute the workitem save operation was still not successful.
The case below talks about Operational Behavior causing the issue while saving the workitem.
When you have a workitem mandatory attribute you want to remove from the editor presentation but still want it in another workitem type, check the attribute dependency with the Preconditions for a workitem before removing from the editor presentation.
In the case below, the customer is not able to save the workitem even after the attribute is removed from the editor presentation.
Check the below details:
Open RTC project Area>> Click on the >> process configuration tab >>navigate to Operation Behavior under Team Configuration >> Operations Window.
Navigate to Work Items>> Save Work Items (Server) >> Click on the role which should be affected by this configuration >>
The Preconditions for a work item will be displayed.
Click on "Required Attributes For Type and State"
In this use case that the 'Custom attribute ' still set mandatory in preconditions.
Note: Uncheck the 'Custom attribute' and save the project configuration.
*Required Attributes For Condition
Whichever custom attribute removed from the editor presentation should be unselected. Once finished, click OK and save the project area.