@AkhilC16801935

The answer to this depends on how you set up your case structure.

Option 1:

This option is if the process of booking a ticket is a subcase of another case that manages the # of available tickets, for example, a train. First make sure that you have proper data propagation from the parent case to the subcase by including the property that states the # of available tickets. This can be done with a data transform at the time of the subcase instantiation, usually within the "Create a case" shape.

Then, once you resolve one of the subcases, you can update the parent case using the "Update a case" shape to refer to the parent case using  and decrement the property that tracks the total number of tickets available by 1. Then whenever you create a new case, make sure that you are propagating tha

Option 2:

If you just have a singular case for booking a ticket and the reference to the # of available tickets is not held within a case but rather as a property within a data instance, then you can update that data instance once you have resolved the case and then save it. This can be done for example by using a savable data page or Obj-Save within an activity.