Hello Andreia,



Unfortunately, it can't be configured automatically. 

So, after creating a new record from the lookup you have to configure the relationship manually, 



As a workaround, you can create a new business process to achieve your business task,



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

Thanks, Bogdan.

Hello Julian, 

The error message indicates that more than 24 hours passed after the last incoming message and prevents you from initiating the chat once again from your side, such limitation is done in order to prevent Spam messages (so your messages sent after 24 hours from last incoming message won't be delivered to a client).

However, you will be able to continue the same chat with no error message once there is a new incoming message from a client.

Best regards, 

Anastasiia

Anastasiia Zhuravel,

WhatsApp allows sending of pre-approved HSM messages after 24 hrs. We have seen that if we (manually) reopen the chat and send a correctly pre-approved HSM message, this is successfully sent even after 24 hrs. Is this the correct/supported method of sending approved HSM messages in Creatio, or should we send some method?

julian hatteea,

Hello, 

We have double-checked this information and so far, this functionality is not implemented in our system. We have already registered the corresponding query for our R&D team and will be waiting for implementation of pre-approved HSM messages functionality in the upcoming versions. 

Thank you for helping us to make our Application better. 

Best regards, 

Anastasiia

Hello Adharsh, 



Please change SchemaName back to UsrSchema******Detail and change the Parent schema back to FileDetailV2. Then compile the system. 

IF the issue persists, please contact us at support@creatio.com

Best regards,

Yurii

Hello Yurii Sokil,

 

I have made the changes and compiled my instance. Post that I could see the detail as an attachment. But still, I could face the error in the console on the opening of the pre-configured page and deletion of records too.







Regards,

Adharsh S

Adharsh,

Please contact us at support@creatio.com 

This situation need deeper analysis than we can provide on community. 

Yurii Sokil,

I'm also facing the same error in console while implementing using the above method.

Hi Adharsh, 

In this case you can set up access rights, so only needed persons(e.g. Supervisor) will be able to see the items.

Please check the next post, it contains a very detailed instruction regarding how this functionality can be implemented:

https://community.creatio.com/articles/how-show-action-set-access-right…

Best Regards, 

Bogdan L.

Bogdan Lesyk,

I am able to hide the "Setup Access Rights" based on roles by referring the document. 







Similar to that when I tried to hide the "Follow the feed" based on roles. In the base I could find only the "Enable" property for the button. So I have overridden that method as below and it got disabled based on roles,

            getChangeUserSubscriptionIsEnabled: function() {

                return this.get("CanManageAccessRight");

            }

But the requirement is to hide the button based on Roles. I also tried to override this method "getEsnTabVisible" but I am still able too see the Follow the feed button in UI. 



Is there any other way to achieve this use case?



Regards,

Adharsh S

Hello Adharsh,

You can find the answer to your question in this Community post.

Best regards,

Bogdan S.

Hello Adharsh,

Something else must be going wrong. I just tested this and my filters do get applied to the virtual lookup for me. My code looks like this: 

"ContactLookup": {
	dataValueType: Terrasoft.DataValueType.LOOKUP,
	type: Terrasoft.ViewModelColumnType.VIRTUAL_COLUMN,
	caption: "Test",
	referenceSchemaName: "Contact",
	isSimpleLookup: true,
	lookupListConfig: {
		filters: [function() {
			var filters = Ext.create("Terrasoft.FilterGroup");
			filters.add("TestFilter", Terrasoft.createColumnFilterWithParameter(Terrasoft.ComparisonType.EQUAL, "Name", "Ryan Farley"));
			return filters;
		}]
	}
}

and the result is: 

Ryan

Hello Adrash,

We've also tested Ryan's code and it works. Please use the same approach on your side to complete the business task.

Best regards,

Oscar

Ryan Farley, Oscar Dylan,

 

I have even tried with your code also, But I still find the same result. There is no error in console too. I am not sure what is been missed.





 

The only difference I could see is that I have implemented this virtual lookup in the Detail schema page and you have done this is Edit Page of a section.

Will this make any difference it Filtering the records?  Ideally it shouldn't do such way.



Regards,

Adharsh S

Adharsh,

You need to debug the logic and see if the filter is returned upon:

var filters = Ext.create("Terrasoft.FilterGroup");
			filters.add("TestFilter", Terrasoft.createColumnFilterWithParameter(Terrasoft.ComparisonType.EQUAL, "Name", "Ryan Farley"));
			return filters;

execution. Also check if there is no other logic is connected to the same column which may affect the filter.

Best regards,

Oscar

This is an old thread, but I wanted to renew the conversation.  I'm having the same issue.  I've filtered lookups many times this way with no issue. 

I have a modal page that inherits from BaseEntityPage.  There is a virtual lookup on the page.  With isSimpleLookup = true, the lookup won't reference lookupListConfig at all.  It just ignores it.  If I change isSimpleLookup = false, it will reference lookupListConfig and fire the code for filter.  My problem is that since my module is already in a modal window, the lookup cant render as a modal also.  I must use a simple lookup.  I can filter simple lookups on other modules, but not this one.  There must be something different about how the module is being rendered.

Any thoughts on how to get the simple lookup to filter here, or be able to use a modal lookup on another modal page?

More on this.  So it looks like this is an issue inheriting from BaseEntityPage.  I changed my modal module to inherit from BasePageV2 and now it works.  Not sure if this is expected and I'm not sure what other issues I'll face using BasePageV2, as this is "base card schema".

Hello!

The error indicates that the WebSockets are not properly set up in your local environment. 

Please take a closer look at the Setup WebSockets Academy article that describes the process of setting up Creatio configuration files for the correct operation of websockets.

Please let us know in case any additional information is required. 

Best regards, 

Olga. 

Olga Avis,

Thanks, the issue is fixed.



Regards,

Adharsh S

Hi Adharsh, 



We  checked your problem and came up with the following solutions: 



1. You may turn off 'Values of the type Lookup' that you don't want to use in your drop-down menu. In this way you'll get just one button to choose. But please be careful because all you previous activities will be shown due to the page that is opened upon clicking on the chosen button. (In your case - Schedule).

 







2. The second way you can implement it using code (in case option 1 was applied all the changes from option 1 should be reverted before applying the next code): 



Bellow you may find the example: 

 define("ActivitySectionV2", [], function() {

  return {

    entitySchemaName: "Activity",

    details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,

    diff: /**SCHEMA_DIFF*/[

      {

                    "operation": "merge",

                    "name": "SeparateModeAddRecordButton",

                    "parentName": "SeparateModeActionButtonsLeftContainer",

                    "propertyName": "items",

                    "values": {

                        "controlConfig": {

                            "menu": {

                                "items": {

                                    "bindTo": "EnabledEditPages",

                                    "bindConfig": {

                                        "converter": function(editPages) {

                                            if (editPages.getCount() > 1) {

        // Add some condition here

        // Add filter to display only specific pages

        var result = editPages.filter(function(page) {

            return page.get("SchemaName") === "UsrActivity1Page"; // Display only activities

        });

        return result;

    } else {

        return null;

    }

                            

                                        }

                                    }

                                }

                            }

                        }

                    }    

                },

    ]/**SCHEMA_DIFF*/,

    methods: {}

  };

});

P.S. 

In this case you still have a little drop down menu (with one option): UsrActivity1Page - the object page that will be displayed. In this case all your activities remain the same. 



Hopefully it will help you! 



Best Regards, 



Bogdan L

Bogdan Lesyk,

The above code is really helpful.

As you mentioned a little drop-down menu with one option is shown.



But the use case is to show only one button("NEW TASK") similar to what we have in OOTB which is mapped to the Activity Type - "TASK".



Even though we are adding a new edit page, I don't want to have a separate button for it.



I just need to show the OOTB button "NEW TASK" and ignore all others, similar to what you see in the below image.







It will be really helpful, as how to implement this.



Regards and Thanks,

Adharsh S

Adharsh,

Then you need to use the first option Bogdan proposed and also override the initAddRecordButtonParameters method on the ActivitySectionV2:

initAddRecordButtonParameters: function() {
				var caption = this.get("Resources.Strings.AddRecordButtonCaption");
              	this.set("AddRecordButtonCaption", caption);
            }

And specify "New task" as a value of the "AddRecordButtonCaption" localizable string in the ActivitySectionV2.

Best regards,

Oscar

Oscar Dylan,

We are using two EditPages one is OOTB - "Activity Type - TASK" which is used to create tasks through UI. That's where we need the OOTB button with activity type as "TASK".

Apart from this, we are creating a new custom edit page for Another Activity Type. We don't need to show the button in UI.



If we follow the first option proposed by Bogdon, the business case will get failed.



I need to use both edit pages in the Activity section. But it's enough to show only the OOTB button ("NEW TASK").



Is there a way to implement this.



Regards and Thanks,

Adharsh S

Hello,

This logic is defined in GridSettingsPage of Nui package, in 

isCaptionHidden: (primaryDisplayColumnName === args.leftExpressionColumnPath),

It is necessary to replace the schema and change this logic.

Regards,

Dean

dean parrett,

Thanks!