Hello,
When I log in to Creatio, then close the browser, reopen it, and try to access Creatio again, it turns out that I need to log in again. From what I understand, this is due to the fact that cookies are set to expire at the end of the session, so they are removed when the browser is closed. As a result, the system setting "UserSessionTimeout" is not being respected here. Is there any option to change this behavior?

Like 2

Like

1 comments

Hello,

 

When you close the browser, in this case, the value of UserSessionTimeout is generally not used. The browser, by default, should not delete cookies; this only happens if the user sets it up that way.

I also logged into the environment on a new browser with default settings, closed it, reopened it, and I was still logged into the environment, which is expected because the cookies still exist.

I would recommend checking the browser settings and how it handles cookies.

It seems that it's now easy to block third-party cookies, but our system stores third-party cookies, and, for example, in Chrome, this is called 'site data on the device,' where you can choose to clear everything when you close all windows.

Show all comments
Question

How to increase the timout as everytime, I install a package in local instance (Creatio 7.18.4 Customer Center), the session ends and the installation fails.

Appreciate your input.

 

Thanks!

Like 0

Like

1 comments

Hello,

 

Thank you for your question!

 

This can be done by editing the value in UserSessionTimeout system setting.

 

By default, the system has the next time range for the "User session timeout" parameter: the minimal value is 10 minutes and the maximum value is 720 minutes (12 hours). So you can set the needed value in system settings for all users ("User session timeout") according to this range:

 



Also, you can open a user profile and set the personal timeout period for the specific user (need to go to the  "Access Rules" tab):

 



Kind regards,

Anastasiia

Show all comments

Hello,



We are having recurring random issues with the OData API which no longer responds to our requests:

 

https://.creatio.com/0/odata/Order?$count=false&$skip=0&$top=10000 (OK)

https://.creatio.com/0/odata/Order?$count=false&$skip=10000&$top=10000 (OK)



(...) OK



https://.creatio.com/0/odata/Order?$count=false&$skip=50000&$top=10000 (not OK)

Generally "Unexpected end of file from server"

or no json response format

or no response at all from server ...

Sometimes we have this issue at fisrt request (skip=0) ... 



The problem seems to focus on the "Order" and "OrderProduct" objects and strongly penalizes us for carrying out our internal statistical analyzes.

 

Could you guide us on how to solve this problem?

 

Regards,

Like 0

Like

1 comments

Hello,



In order to solve that issue we would like to ask you to mail us on support@creatio.com, so we can get more detailed information and will be able to help you.



Best Regards,

Tetiana Bakai

Show all comments