#93 [1.0.0] Deactivate account fails to change status

[Ignatius Reilly]

Deactivating an Account from the CRM interface fails to change field party.status_id from PARTY_ENABLED to PARTY_DISABLED

The only effect of deactivation is to close all relationships to account managers, which in effect hides the account from access by an account manager.

But formally changing the status is essential.

[Scott Gray]

Logged In: YES
user_id=1324421
Originator: NO

Si,

Because the crmsfa.deactivateAccount service takes an optional parameter "expireDate", I can either:
1. Just set the statusId if expireDate is empty and leave a TODO in the code, nothing is passing expireDate at this stage anyway
2. Do the whole thing and create a service to update the statusId and then schedule it run on expireDate.

What do you think?

[Si Chen]

Logged In: YES
user_id=908761
Originator: NO

Scott,

I don't think that we actively use the expireDate in any of our calls to deactivateAccount, do we? This field might be a "we'll support it later" kind of thing. Let's just go with your option #1 for now.

Si

[Scott Gray]

Logged In: YES
user_id=1324421
Originator: NO

Thanks for the feedback, committed in crmsfa rev. 1767