1
0
-1
1 answer
- 321
Hi Stéphane
Unfortunately that is not possible.
Either you can remove the entire add-on with Exalate and Connect on the entity page, or you have to keep it on but then end-users can use it too.
Thank you.
Kind regards,
Mathieu Lepoutre- Stéphane Thillay
Hi Mathieu,
That's the conclusion I ended with and give up on the idea.
Now that we're giving our project another trying, we shifted our expectation to tolerate both buttons, to be seen by few users. But we still have concerns : Distinguish an "Exalate" versus a "Connect" - community.
Regards,
Stéphane
Add your comment...
We are in a Salesforce-to-Jira connection, Salesforce Cases must sometimes be escalated to upper support level teams on Jira.
Before escalation, Agent on Salesforce must specify which Project/Type/Squad is targeted on Jira. Then an Exalate trigger starts the synchronisation that will create an issue and sync back some details to Salesforce (like the Jira key, status, sprint, ...).
We want to extend our process to allow connecting a Case to an existing Jira Issue. Here, Salesforce doesn't have to provide Project/Type/Squad values as the issue already exist.
On Salesforce Case page, we include the Exalate component that embeds an "Exalate" and "Connect" button. The "Exalate" button is unwanted as it doesn't go through the process of asking for the Project/Type/Squad fields. Only the "Connect" button is used.
How to be sure the "Exalate" button does nothing?
We already try putting some conditions on top of the Salesforce outgoing script so it return ASAP if the mandatory field are not populated. However, that also impacts the "Connect" button, that does nothing too.
Is there a way to distinguish, at script level, if it is either an "Exalate" or a "Connect" operation ongoing? So we can let the connection continue, even if the mandatory fields are missing. Remeber: the fields are mandatory for Issue creation only, no for connecting a Case to an existing Issue.
Regards,
Stéphane