Method Community

Hi.

First off, I would like to directly ask the purpose of a few shared results.

If you look at the edit view of  Screen: 'Oppportunity', you will find a dropdown- Field: 'Customer'.

The edit wizard for the 'Customer' field has 3 shared result actions created or set in its "Button_Click" event.

If possible, i would like to know ultimately how these are important to this, and other screens, seeming as they are shared results. Why are they being set? How / why are they used? Will losing these actions by customizing the screen or changing what popups are shown cause other screens not to display properly because of such actions or screens are being changed ?

--------

Lastly, i am curious if thorough documentation of screens is being created. Not just in how to use the screens or why these screens were created, but from the unseen level as well; what actions the screens & objects take in the background and how this may aid or hinder the use of method depending on how the screen is customized.

Thanks,

~Joe

 Hi Joe,

We're looking into this, I'll update you as soon as we have some answers.

Hey Joe,

The main  purpose of this button, is to add a new customer for a campaign. The action results have to do with setting up the new customer and linking the new customer to the campaign

The action results you’re looking at on the opportunities screen do 3 things.

resultNewCustomerCampaign - This grabs the campaign that the client was brought in from and adds it to the clients details screen on the customer table.

resultOpportunityLastPopupCalled - This grabs the new customers name and populates it into the customer drop menu field.

resultLastEntityFullName - this AR is being cleared as a cleanup action before moving forward.

Anytime you change a screen that is using a shared action result, you take the chance of breaking another action. Always investigate what the action result is doing before you make changes or delete the action result.
You last question about documentation for the current behind the scenes actions. We currently have no timeline for this type of documentation but will consider it for the future.