Agile PLM concurrency problem
Hi,
We have a URL based Process Extension that basically sets three
multi list attributes through out the BOM structure of an item based on
the values selected by the user in UI. When two users trigger the PX on
the same item at the same time or on different items with common BOMs,
we are encountering the below problem:
1. PX picks up the first user’s thread, gets the already present selection on the multi list , adds the values user selected to the existing selection and sets all the values on the multi list attribute.
2. Meanwhile, PX picks up the second user’s thread, who is also trying to set values on the same multi list value. Here we are refreshing the object and getting the already present selection for the multi list on the object. At this point, instead of giving the value which was set by the first user, it gives the old value which was present initially when the PX got triggered (not giving the latest value from the existing selection of the multi list). Is there any way we can lock a particular object from editing by any other thread
1. PX picks up the first user’s thread, gets the already present selection on the multi list , adds the values user selected to the existing selection and sets all the values on the multi list attribute.
2. Meanwhile, PX picks up the second user’s thread, who is also trying to set values on the same multi list value. Here we are refreshing the object and getting the already present selection for the multi list on the object. At this point, instead of giving the value which was set by the first user, it gives the old value which was present initially when the PX got triggered (not giving the latest value from the existing selection of the multi list). Is there any way we can lock a particular object from editing by any other thread
0