Hello Christian, 

Please write to support@creatio.com, as this issue needs more analysis and will require external access to your instance (from Supervisor and test user).

Thanks, 

Igor

Thanks, will do.

Support helped me out - solution is not perfect. Recreate all relevant dashboard in English and then they are visible in other languages too.

Hello,

If you want to configure the deletion permissions please use Permission to delete messages and comments:



Permission to delete messages and comments gives permission to delete messages and comments left by other users in the [Feed] section, on the [Feed] tab of the Notification Panel, and on the [Feed] tab of the view and edit pages of the system sections.

Please note, that there is no possibility to deny permission to users to delete their own messages and comments even if they do not have access permissions to this system operation.

Hello,

As we mentioned in the submitted case to support, we do not recommend you manually check those boxes, to properly add them please follow the steps below:

1. In the object, permissions section add your restrictions
2. The system will create a "copy" of the object you are working on in the current package as a reference to the original object
3. In that copy, you will see the checkboxes checked for the chosen options from object permissions.

Please make sure to set the "Current Package" system setting to the one you are developing in.

For further questions please refer to your support case.

Thank you.

Hello John, 

Please write an email to support@creatio.com, as your case needs to be analyzed individually. 

Best Regards, 

Igor

Done.  Request #SR-01139268

Hello Petrika, 

Please check whether you portal user has the needed access rights and can access other Contacts records, the issue may occur if the user doesn't have access to the Contacts records.

Best regards,

Anastasiia

That was the issue. Thank you Anastasiia

Hello Petrika, 

Yes, you can access here only Contacts that have existing system users. 

Best regards,

Anastasiia

Hello,

Add the following code in the page schema of main object under methods:

isDetailEnabled: function(detailName) {
        var DCMStage = this.get("UsrDCMLookup").displayValue;   
	if (detailName === "ExampleDetail") {
		if(DCMStage === "Approved"){
                    return false;       //Disable the "+" button
                }
                else{
                    return true;        //Enable the "+" button
                }
	}
	return this.callParent(arguments);
}

Regards,

Sourav

Hi Petrika,

Please make sure that both the "EnableCustomPrefixRouteApi" and the "UsePortalDataService" features are active in the system. To do that,

run this script:

select * from AdminUnitFeatureState where FeatureId = '17ED5BE9-CA87-42A4-A761-3466DBABF925' or FeatureId = '45D7102E-42D5-4E61-ADF8-77F00CD2F3E8'

Please note that the FeatureState column needs to be equal 1 and the SysAdminUnitId has to be equal '720B771C-E7A7-4F31-9CFB-52CD21C3739F'

The "EnableCustomPrefixRouteApi" feature enables web services custom routing and restricts SSP user access services without the /ssp prefix.

And the "UsePortalDataService" one divides services into the portal and non-portal ones.

Best regards,

Max.

Max,

Still doesnt work Max. Select query

Result

Still the 403 response

What should i do ?

Petrika,

In the inner web.config file please check the following line:

<add key="UsePortalDataService" value="true" />

it needs to be set to true.

Also, please check the "List of objects available for portal users" lookup if the "Bpm’online functionality" is included in it.

Best regards,

Max.

Petrika,

also, please check if the "State of feature" is included in the lookup and that both "Feature" and "AdminUnitFeatureState" have operation permissions enabled in the Object permissions section.

Best regards,

Max.

Thank you very much for the professionalism Max.

Feature and AdminUnitFeatureState didnt have permissions. This solved the issue.

Best Regards Petrika

Hi, did you find the answer? 

Gevorgyan Tigran,

Yes,

I had to enable record permissions to an object called Project folder.

I have noticed when you create a detail as a new object in the section wizard, it checks the box on the object for "Record" permissions. The issue is that it doesn't show as record access enabled in the object permissions, only in the object itself. So what you're ending up with is the system thinks there are record permissions for the object but no permissions are set, so the user can't see the record. To fix this, open the object for the detail in the configuration, then uncheck the checkbox for "Record" permissions, then publish the change. 

Ryan

Ryan Farley,

Thanks you! I just found that it wasn't a permissions issue at all. I just had a BP deactivated by mistake. 

Thanks anyway for answering :)