In the latest build or two, I have noticed a new Feature/bug that hasn't happened before.

Scenario: Designer builds an internal change order the price of the ICO is $0.00 when they are complete. Later, we go to approve that change order and DT asks if we want mark the items in this ICO as non-billable, which should be yes for an ICO since it should be a no cost impact to the project.

However, what we are experiencing is after clicking yes on mark items as non-billable during the approval process, it is then applying credits/debits to that ICO and suddenly there is money associated with that ICO as an approved change order.

This is bad for three reasons:

1.) There should not be any money associated with an internal change order without the option add a placeholder.

2.) There is no way to audit the BOM from this window to determine if clicking yes will have any affect on the outcome of the approval. How does the approver know if clicking yest will have an impact on price, one should be able to assume that the dollar amount would not change as part of the approval.

3.) There is no undo! This morning the $0.00 ICO I approved suddenly had $25K in credits.

What should happen is that when you are ready to approve your CO, your CO is already how it should be and everything should be approved AS IS. DT asking if we then want mark items as non-billable which results in sudden price difference is bad operation.