Overview:
This feature will provide an integration between NavInfo and IEC projects. Once completed, key fields the CNWA approvals section of IEC projects will be autopopulated with auto-populate based on related projects from NavInfo.
UX Design:
...
IEC user will activate a trigger that would pull all identified fields into IEC.
See attached document with fields
NPP File Reference and File Reference Number
This would be a one-time update from NavInfo (for MVP); if fields are subsequently update in NavInfo, IEC users update their project manually. After MVP, we expect users to be able to have fields auto-updated if they are updated in NavInfo
Integration should capture the fields identified in the attached document (we can go over them again)
Users should be able to edit the information that comes into IEC
jackie, remind me why?
Users should NOT be able to edit CNWA approvals sections (this will be in a separate PBI #148799)
If the NavInfo database adds or removes a field, how will we handle this?
Indicate when field has been updated in the Nav
)
Full feature: Users would be able to pull more than once.
Users would have the option to pull as often as necessary until they are ready to begin editing
Once they begin editing, there will be no more option to pull (this prevents data from accidentally being over written)
CNWA approvals section should NOT be locked, this should be pushed whenever changes are made in navinfo (PBI #148799)
This feature should go to ACC first so users will be able to test it out before it goes to Prod.
...