#199 "lock" object editing is counter intuitive

[lennelei]

Hi,

when trying to edit a lock, every manipulation doesn't always give the expected result.

I made a lock and set it up to accept 2 maximum non exclusive tasks.

I then tied to return to an unlimited access : but I cannot simply check the "unilimited access" box again (JOC won't let me deploy the object in that case).
I first have to delete (or change) the number2 in the maximum non exclusive tasks field. I then can check the box and deploy the object.

Moreover, I think that checking the box should also force the suppression of the max_non_exclusive attribute.

Presently, if I check the box without deleting the content of the maximum non exclusive tasks field, it will leave the max_non_exclusive attribute in the XML : I'll have to uncheck the box, delete the content and check it again (or edit the XML).

Regards.

Alexis

[AdityaJ]

Hello Lennelei,

Thank you for your request,

I am able to reproduce this issue in my environment. This issue is reported as a bug in our Change Management System.

Please find the JIRA issue link for your reference:

• JOC-1165: "Lock" object editing is not able to deploy the changes once value is given to Max. non-exclusive Tasks. (change.sos-berlin.com)

Please follow the JIRA Issue JOC-1165  for release date and updates.

Thanks and best regards
Aditya Jain