Can't modify the Foreign ID on the Requisitions UI when adding a new node
Description
On 17.0.0, when you add a new node, the default timestamp is added automatically as the foreign ID on a node.
The field is editable, and you can change it to use whatever you want.
Unfortunately, during the process of upgrading angular/angular-ui-bootstrap something happened and now, even if you edit that field and add something there, the content is ignored, and the numeric timestamp will be used instead.
The problem is associated with an angular directive used to validate the foreignId (to enforce that all the nodes are going to have a unique foreign ID within the requisition). This directive used to work fine on Angular 1.2.28, but with 1.4.9 it has to be updated.
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Alejandro Galue February 19, 2016 at 7:52 AM
All the custom directives have been checked at runtime to be sure that all of them are working as expected.
Alejandro Galue February 19, 2016 at 7:25 AM
Fixed on revision bdeafcbaea448b554900a04bfd9c81b893683e4b on foundation-2016
Alejandro Galue February 19, 2016 at 7:23 AM
Fortunately, the fix for this problem was easy. Check the attached file and apply it if you need the fix right now.
After applying the fix, clear your browser's cache and reload the WebUI on your browser.
On 17.0.0, when you add a new node, the default timestamp is added automatically as the foreign ID on a node.
The field is editable, and you can change it to use whatever you want.
Unfortunately, during the process of upgrading angular/angular-ui-bootstrap something happened and now, even if you edit that field and add something there, the content is ignored, and the numeric timestamp will be used instead.
The problem is associated with an angular directive used to validate the foreignId (to enforce that all the nodes are going to have a unique foreign ID within the requisition). This directive used to work fine on Angular 1.2.28, but with 1.4.9 it has to be updated.