Dear Franck,

To help you with this error we need to investigate the issue and analyze the configuration of the application.

So, please, send a letter to support and we will help you.

Best regards, Alex.

Hi Fulgen,



1. You have to set filter in the Case page:

           

"Owner": {

                "dataValueType": Terrasoft.DataValueType.LOOKUP,

                "lookupListConfig": {"filters": [

                    BaseFiltersGenerateModule.OwnerFilter

                ]}

            }



2. Change define part in the Case page ("UsrBaseFiltersGenerateModule" for BaseFiltersGenerateModule):



define("CasePageV2", ["UsrBaseFiltersGenerateModule"], 

    function(BaseFiltersGenerateModule)



3. Add UsrBaseFiltersGenerateModule schema (you can see commented options for users with or without license as well):

define("UsrBaseFiltersGenerateModule", ["UsrBaseFiltersGenerateModuleResources", "ConfigurationConstants"], 
	function(resources, ConfigurationConstants) {
		function getIsNotNullFilterGroup(refSchema) {
			const userFilter = Terrasoft.createColumnIsNotNullFilter(refSchema + ".Id");
			const filters = Ext.create("Terrasoft.FilterGroup");
			filters.addItem(userFilter);
			return filters;
		}
 
		function employeesFilter() {
			const sysAdminUnitRef = "[SysAdminUnit:Contact]";
			const employeesFilter = Terrasoft.createColumnFilterWithParameter(Terrasoft.ComparisonType.EQUAL,
					sysAdminUnitRef + ".ConnectionType",
					ConfigurationConstants.SysAdminUnit.ConnectionType.AllEmployees);
			// const hasLicFilter = Terrasoft.createExistsFilter("[SysAdminUnit:Contact].[SysLicUser:SysUser].Active");
			const isActiveUserFilter = Terrasoft.createColumnFilterWithParameter(Terrasoft.ComparisonType.EQUAL, "[SysAdminUnit:Contact].Active", true);
			const filters = getIsNotNullFilterGroup(sysAdminUnitRef);
			filters.addItem(employeesFilter);
			// filters.addItem(hasLicFilter);
			filters.addItem(isActiveUserFilter);
			return filters;
		}
 
		function allUsersFilter() {
			return getIsNotNullFilterGroup("[VwSystemUsers:Contact]");
		}
 
		function selfFilter() {
			let primaryColumnName = "Id";
			if (this.entitySchema && this.entitySchema.primaryColumnName) {
				primaryColumnName = this.entitySchema.primaryColumnName;
			}
			const primaryColumnValue = this.get(primaryColumnName);
			return Terrasoft.createColumnFilterWithParameter(
				Terrasoft.ComparisonType.NOT_EQUAL, primaryColumnName, primaryColumnValue);
		}
 
		return {
			OwnerFilter: employeesFilter,
			SelfFilter: selfFilter,
			AllUsersFilter: allUsersFilter
		};
	});

Hello, Fulgen!

Unfortunately, Creatio can not set up additional filtering with OOB functionality for the " Responsible " field. It is possible to solve your business task by creating business rules using development tools. And we have already registered a request for the responsible R&D team to research the possibility of implementation of this solution for the future releases of Creatio application.

Thanks, Vladimir Sokolov

This is exactly what I need, but I am having some issues getting this to work.

I've done all 3 steps, but clearly have an issue with Step 1 as I am getting errors on the Case Page. When I add the Owner filter in the CasePage client module and compile, then CasePage will not load.

So, a newbie question for you, within what section of the CasePage code should the Owner element be added? I assumed businessRules, rather than attributes, modules, details, methods, dataModels, or diff.

I dropped it in as the last businessRules element (adding appropriate , and such). Things compile fine but the Case page does not load. 

"Owner": {

                "dataValueType": Terrasoft.DataValueType.LOOKUP,

                "lookupListConfig": {"filters": [

                    BaseFiltersGenerateModule.OwnerFilter

                ]}

            }

The first time that I tried this I got an error on browser console that BaseFiltersGenerateModule was unknown (sorry, I did not save the exact text of the error, but can reproduce it). So I added BaseFiltersGenerateModule into the define/function statement at the start of CasePage.

Dear Kritika,

Thank you for your question.

Unfortunately, your business task can be achieved neither with basic nor with advanced tools. 

We have already registered the idea for our R&D team to implement this functionality in further releases. 

Best regards,

Anastasiia

Hello Damien,

Thank you for your question. Your task may easily be solved by a Business Process:

- for files, you may use Element "Process File"

- for Feed - you will need two Elements - Reed data and Add data that will process object "Message/comment". You will need to exact the body of the feed on the lead page and create a new feed message on the opportunity page. (It will be also needed to be careful while setting the schema lookup field by choosing Schema -> Opportunity for Add data element)

I hope my recommendation was useful for you.

Best Regards,

Dan

Denis Bidukha,

Thanks a lot, will try that out :)

Hi Vincent!

We reviewed the add-on and reproduced the issue on our end. That was an out-of-the-box compilation-related error. When installing the package, the system did not compile and did not generate static content. We plan to fix this problem in future versions of Creatio. For the time being, I recommend recompiling your system.

Hello!

Unfortunately, there is no way to prevent new records creation in objects during data import and we have a problem registered to our R&D team so to implement such a functionality.

This is due to the logic implemented in the import process.

The system adds missing values to its lookups in order to prevent data loss during the import process.

 

As an alternative solution I can recommend the following:

1. Remove the unwanted column from the file before the import, and add it after the process.

2. Match the naming of the file columns with Creatio's system naming.

3. If the problem is tied to creating a lot of duplicates in the system after imports, you can turn on Creatio's deduplication feature and merge the duplicates together.

I will let our R&D team know about your request so to raise the priority of the problem. Thank you for reporting this issue to us and helping us to make our application better!

Best regards,

Kate

Kate Karpik,

Thank you Kate

Is removing the add permission for a specific lookup a viable work-around?

Stefano,

Unfortunately, the offered solution will not solve this issue.

During the import process, the system checks for the correct access rights for the modification of the object (lookup in this case) of the user that initiated the process.

Hence why the users that lack needed rights will not be able to import the data.

If you were to restrict the access to the lookup, the data will not be added during the import, regardless if needed columns exist in the lookup or not.

Thank you.

Best regards,

Kate

+1 for this

Hello Stefano,

If user self-registration is not required, you can remove the “Register” button from the portal login page:



change the ShowPortalSelfRegistrationLink parameter in the Web.config file to:

 

<add key="UseStaticFileContent" value="false" />



Best regards,

Bogdan

Bogdan,

thank you bogdan

So, if my instance is on  cloud I have to open a case for the support 

Hello,

Please check the object permission for the Contact and Account for "All portal users" in the “Object permissions” section?

alonadolya,

Hi

For Contact and Account, the permission is set for "All portal users". Images attached for reference.

Nisarg Soni,

Hi!

The problem is that the record permissions are turned on and portal users don't have any permissions there. Therefore portal users don't get access to any records. 

Please add permissions of kind (All employees -> All portal users), clear the cache, re-login under a portal user and you should see the records in the list!

Best regards,

Max.

Max,

Hi

Thanks for the solution. It works!

Dear Stefano,

Sometimes you can catch a bug when trying to save a new version of the process with script-task to assembly package.

This bug is actual for 7.18.5 and lower versions, for example. But in 8.0+ versions it's already fixed.

As a workaround, I can suggest you use a simple package, not an assembly one. 

Of course, the best way to fix it is to update your application to 8.0+.

Best regards, Alex.

Aleksei Efimenko,

Thank you Aleksei