Hi,

We are currently confronted with an early session timeout after two hours of inactivity when users log in using SSO (Microsoft Azure AD).
Org-wide session timeout and profile-level session timeout are set at 8 hours.
However these values seem to not be used at all.

I found this helpful article: https://help.salesforce.com/articleView?id=000317746&type=1&mode=1

I am afraid point 3 at the end:
"If users are running custom Visualforce pages and using lighting with SSO single sign on, a new configuration may be required in many cases - please file a support case for developer support if this is needed for SSO reconfiguration. Premier Support required."
is applicable

I was wondering if it means the SSO setup should be done all over again? Or is something else meant by reconfiguration?
We would not need premier support if the sso should be redone, but I am not sure if that will help because the SSO was just set up on a new sandbox. So maybe something else has to be reconfigured?

Kind regards,
Olivier Van den Nest

i m writing trigger, created custom field  on product object  Total Quantity and Available Quantity .
i have to fill Available Quantity field when opportunityLineItem is Created
code is successfully deployed but not update  Available Quantity field

trigger AvailableQuantityonProductTrigger on OpportunityLineitem (after insert) {
    integer remainingQuantity=0;
    set<id> oliIds=new set<id>();
for(OpportunityLineitem o:Trigger.new){
    if(o.Quantity!=null){
    oliIds.add(o.id);
    }
 }
 list<OpportunityLineitem> oliList=[SELECT id,Quantity,Product2.Name,Product2.Total_Quantity__c,
 Product2.Available_Quantity__c FROM OpportunityLineitem WHERE id IN:oliIds];
 for(OpportunityLineitem oli:oliList){
    if(oli.Quantity!=null){
         remainingQuantity=integer.valueOf(oli.Product2.Total_Quantity__c) - integer.valueOf(oli.Quantity);
     }
     else{
         remainingQuantity=0;  
     }
     if(remainingQuantity!=null){
     oli.Product2.Available_Quantity__c=integer.valueOf(remainingQuantity);
     }
}
update oliList;
}
Thank you

Hi,

We are currently confronted with an early session timeout after two hours of inactivity when users log in using SSO (Microsoft Azure AD).
Org-wide session timeout and profile-level session timeout are set at 8 hours.
However these values seem to not be used at all.

I found this helpful article: https://help.salesforce.com/articleView?id=000317746&type=1&mode=1

I am afraid point 3 at the end:
"If users are running custom Visualforce pages and using lighting with SSO single sign on, a new configuration may be required in many cases - please file a support case for developer support if this is needed for SSO reconfiguration. Premier Support required."
is applicable

I was wondering if it means the SSO setup should be done all over again? Or is something else meant by reconfiguration?
We would not need premier support if the sso should be redone, but I am not sure if that will help because the SSO was just set up on a new sandbox. So maybe something else has to be reconfigured?

Kind regards,
Olivier Van den Nest