Best practice for VBCS Mashup
SummaryHow to make VBCS Save more user friendly?
Trying to get some inputs from VBCS related forums on this topic.
We build a custom page in VBCS to display contact details and some additional data. On this VBCS page we have a Save button to post the data from VBCS to Contact object. This VBCS page is embedded/iFramed to Contact detail page through Mashup, and because it has partyNumber as its page input parameter, we can display contact data properly on VBCS page when it's opened from CX Sales.
My question is on the VBCS Save button and CX Page-Level Save buttons (i.e. Save, Save and Close). What's the best approach to address Save?