As mentioned above this 2nd if statement that you added is unnecessary - I took a screenshot and attached here to re-illustrate. The part with a purple square is unnecessary because that is…
Also, I am not sure how this would ever get hit as isn't this basically the same check as line 405?
With both if statements --- if it is null, do we want it enabled or not?
Looks good to me. Ready for QA.
Just to check --- is this wording accurate? ----- i.e. if this is ran on a high level step wouldn't it update all high level steps in that procedure (not sub-steps)?
Also in the designer --- Just to check --- is this wording accurate? ----- i.e. if this is ran on a high level step wouldn't it update all high level steps in that procedure (not sub-steps)?
per below - there is the addition of an extra line.
I know it may seem like overkill ---- but frmVEPROMS & ItemExt have other pending changes like the ones in this pull request:
https://git.v…
Just checking? --- why was this file changed?
Just checking? --- why was this file changed?
It looks like there were 2 files that were changed that shouldn't have been - frmVEPROMS.cs & ItemExt.cs.
This should be cancelled - it is set to merge into the Master branch not Dev.
Refresh Word Attachments uses "vesp_DeletePDFs" - it doesn't take the doc version id as a paramater.
fe7c5893bb
Merge pull request 'B2026-040 - Signoff/Checkoffs not printing unless set to Section Default' (#758) from B2026-040 into Development
This branvh is not up to date & looks like it has unrelated changes in it - I would suggest making a new brach off of Development.