Hello!

Could you compare the language ID in the TST environment with the dev environment?

The language should have the same ID.

You can add data binding with the culture record to the package to achieve this.

Thanks Alona,
I am a little bit confused because in translation xml there is only language code not Id but I try

Regars Tomek

Hello,

Could you please describe what exactly your business idea is in more detail, provide a screenshot with example where and how you want to set this up?

Mira Dmitruk,

Hi;
I create such page

the claim request field is link to entity page

byt i can change it I would like it to be readonly

Regards Tomek

Tomasz Branicki,

I believe the only way to accomplish this is to use a preconfigured page instead of autogenerated. 

Ryan

Hello!

Unfortunately, the file is not available.
Please re-send it once again.

Alona Dolya,

Hi.
 that is ScriptTask we use

private bool UsrSetClaimRequestCrSignalScriptTaskExecute(ProcessExecutingContext context) {
    var uc = Get<UserConnection>("UserConnection");
    
    var claimSignalDAO = new ClaimSignalDAO(uc);
    
    var signalId = Guid.Parse(context.Process.FindFlowElementByName("UsrClaimRequestStartSignals").GetPropertyValueByPath("RecordId").ToString());
    var signalTypeId = claimSignalDAO.GetSignalType(signalId);
    var crId = claimSignalDAO.GetParameterGuid(signalId);
    
    Set("UsrClaimSignalType", signalTypeId);
    Set("UsrClaimRequest", crId);
    
    return true;
}

Hi;
Does anyone have idea why script element do not see the start element by name.

Regards
Tomek

Hello Dmitrii,

It's not so apparent from the description where the problem exactly is. Could you please share two parts of the code:

1) the custom module;

2) how did you add the button on the page

Добрый день.

Вы можете настроить Debug режим для логера Ldap в файле nlog.settings в папке Terrasoft.WebApp.

Расширенное логирование позволит вам узнать какие этапы синхронизации прошел ваш пользователь.

Hello,

We have registered the idea and forwarded it for consideration to the responsible team for further review and release in one of the upcoming versions.

 

Currently, only workarounds at the client's business logic level are possible: either using a regular text field with maximum length and performing encryption of the value before saving and decryption after retrieval at the business logic level, or using two "Secure Text" fields and splitting your string into two substrings, storing them in the two fields, and concatenating them upon retrieval.

Hello!



I'd suggest to approach the support team via support@creatio.com to have a closer look at the error.

It is hard to determine the root cause without having the access to the Word plugin itself. 

Thank you,

Kate

Hello Vladimir,



It's expected behavior.  



As for now, your business task could be achieved by business process. 

Hello,

Please make sure to contact our support team directly at support@creatio.com and describe this issue in more detail, so we could help resolve it.

thx Mira.

it correctet itself.

its looks the engin cant localize any paremeters or page.

But its start working



regards

Tomek

Hello Sasori,

unfortunately, it is quite difficult to analyze the issue like as there might be too many different reasons for such an error.

I kindly recommend you creating a separate support case and our team will help resolving the problem you are facing.

Kind regards,

Gleb.

Thank you Gleb :)

I was having similar issues.  What I found out is it depends where the detail is at.  For example I was creating a detail around work history.. One of the default fields was contact.  If I entered any contact other than the employee I was looking at it wont show on that contact record.  There is a logical dependency there...  I took the contact component out and works fine....  @Sasori... that is My guess as to what you are running into.

Jason Miller,

Thank you very much Jason !