Comments
We need the unload event to make sure that the ProgressIndicator gets closed when the user navigates away. We want to register a postSave handler that opens a ProgressIndicator, do some asynchronuous task, and then close the progress indicator. The above works only when the user selects "Save"the form is autosaved, It does NOT work correctly when the user selects Save & CloseSave & Newthe "The postSave handler doesn't support waiting on a Promise. Hence, the code of the postSave handler will be broken off halfway the async logic. The ProgressIndicator is never closed.If we would have an Unload event handler we could mitigate the above.
In order for planning to check workload, you must add the Machine Center or Work Center to the Capacity Constrained Resources. Then planning will take load into account. Be aware that this might result in stopping and starting a single step several times with backward scheduling. This happens when there are pockets of availability that are smaller than the required capacity.
We do use this work around, but it is often confusing for the end user. We find we get a lot of help desk calls to remind them how to handle this. I understand it is a circular reference given the current logic, but a BOM marked as "Rework" could also be developed to bypass the level calculations.Further, some organizations do not want the production order components to be edited from a BOM to support their QA requirements.