Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to update Current feature to Proposed feature #229

Open
MarksNgahi opened this issue Mar 14, 2019 · 2 comments
Open

Unable to update Current feature to Proposed feature #229

MarksNgahi opened this issue Mar 14, 2019 · 2 comments
Assignees
Labels

Comments

@MarksNgahi
Copy link

Issue 1 - Unable to update a Current address to a Proposed address.
Steps to reproduce the error message is as follows:

  1. Search for an existing current address.
  2. Click on the Update AIMS Feature button.
  3. Change the Life Cycle from current to proposed.

image

The default Life Cycle type is Current and if a user forgets to change it we have to decline the request and re-add it.

Issue 2 - Unable to update the road centre line of an existing Proposed address.
Steps to reproduce the error message is as follows:

  1. Search for an existing proposed address.
  2. Click on the Update AIMS Feature button.
  3. Click on the button used to select a new road centre line.
  4. Select a different road centre line and submit.

image

This causes issues because if a road centre line needs to be changed, the address has be retired and then re-entered. The user has to attach the address to the correct centre line and make it proposed again.

@SPlanzer
Copy link

SPlanzer commented Mar 17, 2019

Hi @MarksNgahi

This was discussed during development. As per the comment in issue 213; addresses can not be changed from current to proposed.

I have also looked at the validation rule table and AIMS is set to reject such an action.

validationruleid description ruleid severity validate visible
47 "LifeCycle for an Update cant be changed from Current to Proposed" "AIMS: V0023" "Reject" TRUE TRUE

I do not understand myself why we can not change the lifecycle from current to proposed but as per #213 espatial at the time have said it is to protect data integrity.

As this is at the database level, I will leave this with the addressing team to decide if this should be raised with spatial to be resolved.

@SPlanzer
Copy link

I have opened an new issue to manage the updating of the road (#230)

@SPlanzer SPlanzer removed their assignment Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants