7.7 Custom entrypoint randomly redirects to index instead of actual entrypoint

You may try adding &to_pdf=true to the url of the window you are trying to open.

If you installed the entrypoint to the Accounts module, you might also want to try adding module=Accounts to the url.

Thanks Chad and Shad.  I tried both of those things, as well as combining those things together.  Neither of them worked but were great ideas!  

After banging my head against a wall for a few days now, I actually found out this is a known bug that has yet to be resolved.  A PHPSESSID is not created until you access a BWC module, and if you have not yet accessed a BWC module, you will be redirected.  I could circumvent this by adding /#BWC/index.php?blahblahblah but that means my custom entrypoint would have the Sugar module bar at the top.  

https://web.sugarcrm.com/support/issues/e64a7da1-1130-ac0c-9824-556c10e9a5d9

Ah too bad, good find though.

I'm not sure if it is related, but the issue seems to be an authentication-related issue. Try putting this at the top of your entry point code:

global $current_user;
$current_user = BeanFactory::getBean('Users');
$current_user->getSystemUser();

This basically allows the session of the entry point to act as an admin user, so use this with caution. This might be a temporary workaround.

If the content being displayed needs to adhere to the ACL rights for their sugar user, this wouldn't work because they'll be able to see all records instead of those granted by their user/team/roles.

BAH!  I was so hopeful.  That sounded like a great idea but a no-go either.  

Hi Shad Mickelberry 

entryPoints will be deprecated very soon, so I encourage you to implement a view instead.

Kind regards

Got this resolved finally.  All I had to do was add "SUGAR.App.bwc.login();" to the initialize function of the record.js override.  

extendsFrom: 'RecordView',

initialize: function(options) {
this._super('initialize', [options]);

this.context.on('button:order_history:click', this.order_history_popup, this);
SUGAR.App.bwc.login();
},

Hi Andre, that's really good to know. Entry points are super common in integrations.

Do you know when this is going to be deprecated?

If we use endpoints instead, how can we make a completely public endpoint to act like entry points currently do?

Thanks!

Hi André Lopes, just checking in on this. 

Do you know when entry points will be deprecated?

If we use endpoints instead, how can we make a completely public endpoint to act like entry points currently do?

Thanks!

Hi Chad Hutchins 

By a "completely public endpoint" do you mean an endpoint which doesn't require authentication?

As far I understand it is not possible.

Additionally SugarCRM still didn't publish the estimate date to deprecate entryPoints.

Kind regards