Is there a way to prevent the Contract credit card info from copying to the renewal quote?

Hi Katherine,

Running the renewal s as a quote normally should make a duplicate of current information in the original quote such as customer, billing method, OOS, etc. this includes the credit card information.

i understand the rationale you present however this would require a code change. Further, some customers may want include this in the quote thus to include/not include probably would require a parameter which is basically what you are asking.

I am not aware of such and as Alliance’s lifecycle is at the point that additional functionality is not planned for development for the standard product, the only solution for this is an RFE BRD developed as a local customization.

An alternative solution may be to develop a process flow to remove the value when a new quote is created  I have not specifically looked into this but it sounds like a possibility 

Looking at the Process Flow options, it does appear you should be able to craft a process flow which executes periodically:

However, a process flow which executes on quote creation during renewal does not seem to work when I tried that route instead with a valid API action to remove the credit card information.

Thank you for the feedback Phil. I think a periodic process flow could work for us in this case. I will give that a try.

Hi Katherine,

You may still want to give an event driven process flow a shot on your side. It did not work on mine but this may be due to perhaps the services were not running which I am inquiring with the group maintaining the server.

Hi Phil,

Thanks for the suggestion, I will try both. We currently have one event driven process flow which runs during the contract renewal to update something on the contract. It periodically fails to update and we haven’t figured out why so we may end up sticking with a periodic process flow for this.

HI Katherine,

I had a discussion with the developers about triggering event driven process flows generating a quotation from a contract renewal.  The situation is the event creation triggers will NOT work from of quotation creation event executed by the renewal process.

Essentially, when a quotation is generated from the contract renewal, it is basically copying the existing contract and does an update event. The process flow event for upon creation is never called as the action performed is update, not create.

If you set the event to trigger upon update, then any changes to the quotation will trigger the process flow.  It would also mean that you cannot update the CC information while the document is still a quotation (think trying to add more OOS or even the CC information itself after the quotation was created, it would just remove it again).  Then the only time you could update the CC information is after it was converted to a customer contract from what I understand.

So, looks like the periodic schedule method is the only one which will work.