Standard Change Proposal changes state to closed on submit or save

[keithcox]

I am wondering if anyone has run into this issue before. On the Standard Change Proposal we have run into an issue with the state changes to closed on submit or save. We have made a few modifications to the workflow and added the save button to the form instead of the menu. Save button is the ootb button with no changes to it. Instead of having users created the new template request through the template management catalog item we have them going to my proposal and clicking the new button to create. Once all fields and change request values are populate if you click save or submit the state is changing to closed and its creating the template, it starting the workflow but with the state changes to closed its bypassing the approvals. I have looked through the ootb business rules, and client scripts and do not see where this would change the state to closed. 

Has anyone seen a behavior similar to this before? If not does anyone know what would change the state on save? We are on Istanbul patch 10.

Thanks 

Keith

[keithcox]

I have identified the issue I'm facing but can't seem to figure out why it's happening. We are using a workflow(oob) that contains approvals for the Standard Change Proposal. On save or submit an approval is taking place before the workflow can begin which is then causing some oob business rules to kick in to validate the template then create the template since the approval has taken pace. I have verified that the approval engine is turned off to allow the workflow to proceed. I have looked at change, standard change proposal, and catalog business rules and do not see any that would automatically set these to approved. Has anyone experienced this before or can you point me in the right direction to identify what is approving these proposals? I have looked through the logs but do not see where this is getting set to approved.

Thanks,

Keith