Hello Markus,

We investigated this behaviour and currently, the system behaves correctly since you can add a macro in the signature so it could fit the template or depend on some value.



We have already registered the idea for our R&D team to implement this functionality in further releases. I will assign your case to this project in order to increase its priority. 



Best regards,

Bogdan

Hello Federica,



Could you please send the screenshot once again?



Best regards,

Bogdan

Hello Bogdan,

Here's the image, sorry for the mishap

Federica,

Basically, there is a table in the database called EntityConnection. You can delete all the records from this table that refer to the objects which you do not need (for example, contact, requests etc).

You can do the following:

delete from EntityConnection where SysEntitySchemaUid in (select Uid from SysSchema where Name = '')

where '' is the name of the object, for example, Contact.

But the thing is if you delete the records from the EntityConnection table - the next fields on the activity page will be deleted automatically as well:

Best regards,

Bogdan

Thank you Bogdan! That's exactly what I did (according to your suggestion) ! :) Do you happen to know how to change the icon too? 

I made a few tests and to access the icons I need to implement EmailItemSchema client module

Now: 

Hi Federica,

The "BETArchiveFirstGeneration" and "BETArchiveSecondGeneration" tables have been added in the 7.17.1 version of Creatio. They are used as a way to archive old records from the BulkEmailTarget table. Records older than 1 year go into those tables.

To get information about the OLD licenses usage you would need to use the VwBulkEmailTarget view as it looks into both the BulkEmailTarget and BETArchive tables. 

Best regards,

Max.

Thank you very much Max for clarifying! :)

Hello Vincent,

Please be informed that at the moment, in the existing interface of mobile application approvals, it is not possible to implement such logic as you described.

A request for the implementation of this functionality has already been registered and I will also attach your request there to increase its priority.

Thank you for choosing Creatio!

Kind regards,

Mira

Hello Petrika,



It's possible to add DCM panel for the portal user by following the instruction on our Community:



https://community.creatio.com/articles/enable-dcm-portal-users



Best regards,

Bogdan

Bogdan i believe the article is outdated. For example the object "Case status changed actions" didnt exist at all in nowdays versions of Creatio

Petrika,

Unfortunately, we don't have new examples of such implementation.

So, you can refer to the post by the link in the previous comment. 



Please note, that we have already registered the idea for our R&D team to implement this functionality in further releases. I will assign your case to this project in order to increase its priority.  





Best regards,

Bogdan

Bogdan,

I tried the operations described in the article and they didnt work.

I think there is some modifications that needs to be done in Operation Permissions and Object Permissions Bogdan. 

Because when i deploy the same portal page in another instance (which has an empty database) the cases appear !

Hello.

You can use the functionality "Binding data to the package".

To do this, you need to create a "Data" element in the "Configuration" section and bind the necessary data to the "FileImportTemplate" object.

Please find more information on your request in these Creatio articles:

https://academy.creatio.com/docs/developer/development_tools/packages/packages_basics/overview#title-2105-9

https://academy.creatio.com/docs/developer/development_tools/packages/bind_data

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 :)