Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview:

...

  • IEC user will activate a trigger that would pull all identified fields into IEC. What will the unique identifier be that links projects?

    • 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

...