OK I have a big cluster...I am trying to get a new feature to our base product to work...here is the logic I have come up with...its pusedo

if preview is on OR approval engine is off
if savedetails throws an error
do stuff
else
set some variables
run save details
elseif approval engine is on AND preview is off
don't save details
set those same variables as above (redundant I know)


but I have nothing for else is that ok?
basically normal base behaviors is to save details if there is no error

but this client wants an approval first...so when we send it, we don't want to save it until it is approved. The problem is the title to display once you send it for approval or send it w/ base behavior depends on the variables set, so i need those in any case...unless there is an error in savedetails...

savedetails is run according to our coding standards like this:


that new id is needed when preview is checked regardless is the approval engine is on or not

I am OK with this code...the redundant variable setting has been OKed its just...there is no else...is that ok??