| Description |
Users are starting to add multiple locations to entityies. There are some cases where the entity is still active but the location stops doing business or moves. The user would like to make the location inactive
* We should add an inactive flag to the entity location
* User should not be able to make the default location inactive.
* This will have impact on all applications selecting locations so the store provided to modules should exclude inactive locations.
* All entities should have at least one active location (but could have many) so you should not be able to make a location inactive if it is the only locaiton for the entity
* If we change the store will all down stream impact be taken care of?
Question for Mon:
Scenario
* user makes location 1 inactive
* the location 1 is being used on bill 1234
* what happens if :
** the user accesses the bill and the store for the search control no longer sees the record as valid?
** the user posts the bill (probably nothing but what would happen)
!pastedImage_d42559_0.png!
|