Easy move outs and custom callings
Posted: Fri Aug 16, 2013 6:29 am
Just starting as a Ward Assistant Clerk and have some feedback for the tools:
When moving records out it forces a new address or listed as unknown, but there is also the situation where the already recorded address is out of ward boundaries but the record is just now being moved out. This could be detected to provide a third option without needing to copy paste back in the already existing address.
We had an issue where we had a few custom positions that were duplicates of existing official callings (probably due to the previous clerk not finding the official ones). Some ideas related would be:
- Check name of custom position to see if it is similar to official position and warn the user at the time the custom position is created
- Auto remove or ask to remove when a custom position no longer has someone assigned
- Also I noticed it would let me remove the custom position even if someone was assigned still to the position. It seems like there should be a check there to force the user to first remove any assigned individuals from the custom calling before allowing the custom calling itself to be removed rather than silently deleting the other data.
Ben
When moving records out it forces a new address or listed as unknown, but there is also the situation where the already recorded address is out of ward boundaries but the record is just now being moved out. This could be detected to provide a third option without needing to copy paste back in the already existing address.
We had an issue where we had a few custom positions that were duplicates of existing official callings (probably due to the previous clerk not finding the official ones). Some ideas related would be:
- Check name of custom position to see if it is similar to official position and warn the user at the time the custom position is created
- Auto remove or ask to remove when a custom position no longer has someone assigned
- Also I noticed it would let me remove the custom position even if someone was assigned still to the position. It seems like there should be a check there to force the user to first remove any assigned individuals from the custom calling before allowing the custom calling itself to be removed rather than silently deleting the other data.
Ben