Hi All,

Can anyone answer on this?

Thanks,

Sourav

Dear Sourav, 



I would suggest you to carefully check the web.config file located in the root folder of Creatio. 

In this file you can find the list of login providers (the place where you enabling JIT by the guide):



        <provider name="SsoAuthProvider" type="Terrasoft.WebApp.Loader.Authentication.SSO.SsoAuthProvider, Terrasoft.WebApp.Loader">

          <parameters>

            <add name="UserType" value="General" />

            <add name="UseJit" value="false" />

          </parameters>

        </provider>

        <provider name="SSPSsoAuthProvider" type="Terrasoft.WebApp.Loader.Authentication.SSO.SsoAuthProvider, Terrasoft.WebApp.Loader">

          <parameters>

            <add name="UserType" value="SSP" />

          </parameters>



If you want to enable JIT for portal user you need to make sure that key <add name="UseJit" value="false" /> is added to the block related to the "SSPSsoAuthProvider"

so it looks like:

    <provider name="SSPSsoAuthProvider" type="Terrasoft.WebApp.Loader.Authentication.SSO.SsoAuthProvider, Terrasoft.WebApp.Loader">

          <parameters>

            <add name="UserType" value="SSP" />

            <add name="UseJit" value="true" />

          </parameters>



After that please make sure that SspLogin.aspx is specified in all keys instead of NuiLogin.aspx to make sure that user will get a proper portal cookie in case if you want to use a Service Provider initiated SSO flow to create portal users. 

Also please note that in this case ordinary company employees will have to login via direct link only or use the link to NuiLogin.aspx module if they want to use SSO as well. 



Kind regards,

Roman

Roman Brown,

Does this mean we can only use Jit either for Portal User or for Company Employee user?

Regards,

Sourav

The 2nd error is resolved I figured out the reason is that the field name(code) is same as the section name(code).



But I didn't find out the reason of 1st error. 

Hi,

As for the first error message, find this Id from the error message in the UI sources in the developer console F12 -> Sources tab -> Search and see which object is returned in ViewModule.aspx when searching for the Id from the error message (like here https://community.creatio.com/questions/how-overcome-item-unique-identi…). Then you need to remove the SysModule record from the system that is related to the object found in the UI sources.

Best regards,

Oscar

Hello Balaka,

Sorry for the delay with the response. Unfortunately, it is not possible to add cases to the detail page because the DCM module is not compatible with the detail page. 

We will create a request for the R&D team to implement functionality to create a DCM in the detail pages as well. 

Best regards,

Bogdan

Hi Marry,

Unfortunately, are no such basic tools for imported records/

 

The only way to achieve your business task is to create a new business process with a start signal with an event that should trigger the signal (Record added / Record modified).



Please note you should enable this business process before the import and disable afer.

Best regards,

Bogdan

The issue was in the foreign key constraint left in the database after the column was deleted from your object and this constraint prevented the database structure from being updated. We've removed that foreign key and the issue was fixed.

Best regards,

Oscar

Hi Oscar,

Thanks for the help

Hello,

Yes, it is possible to set up SSO through OKTA. Unfortunately, we do not have specific instructions for this product, but you can use the Single Sign-On via ADFS Academy article for your reference. 

Best regards,

Bogdan

Bogdan,

We are also trying to configure from OKTA's side as well. But there are certain ask that we are unsure about. Could you please suggest on the following questions from Creatio perspective?

• Single Sign On URL - https://site.creatio.com/ServiceModel/AuthService.svc/SsoLogin
• SP Entity Id -
• Default Relay state -

Thanks,

Sourav

Bogdan,

Is there any information on this?

Thanks

Sourav, 



This application is in "Upcoming" state meaning that it will be available in Future. 

As for your first question, you need to insert following values:

 

• Single Sign On URL - https://site.creatio.com/ServiceModel/AuthService.svc/SsoLogin
• SP Entity Id - https://site.creatio.com/
• Default Relay state - you can leave it blank. 

Kind regards,

Roman

 

Roman Brown,

What is the LocalCertificateFile and where to get this for onsite applications?

Thanks,

Sourav

Add a boolean attribute to the page:

attributes: {
    "IsButtonEnabled": {
		dataValueType: Terrasoft.DataValueType.BOOLEAN,
		type: Terrasoft.ViewModelColumnType.VIRTUAL_COLUMN,
		value: true
	}
}

Then bind the enabled property of the button to the attribute:

{
	"operation": "insert",
	"parentName": "Header",
	"propertyName": "items",
	"name": "MyButton",
	"values": {
		"itemType": Terrasoft.ViewItemType.BUTTON,
		"caption": "My button",
		"click": {"bindTo": "onMyButtonClick"},
		"enabled": {"bindTo": "IsButtonEnabled"}
	}
}

Now when it is clicked, set the attribute to false:

onMyButtonClick: function() {
    this.set("IsButtonEnabled", false);
}

Ryan

Ryan Farley,

Hi Ryan, thank u for ur asnwer, is it for Classic or Freedom UI?

Hello,

Thank you for your question. 

Please, note that it's not recommended to bind users, organizational structure, roles, licenses, and other administrative things to a package. It will be very hard to handle that if you decide to install that package after the moment when the client adjusts that administrative things according to his or her needs directly on the production.

Unfortunately, there is no script we could provide you with but in case you decide to bind this data and transfer it to another environment we suggest checking all changes on the copies before delivering it to the production websites. The organizational structure is in the "SysAdminUnit" and "SysAdminUnitInRole" tables and you are right, it's possible to bind it to the package via SQL scripts only.

Best regards,

Anastasiia

We usualy do the following:



Create separate package for Roles

1. Add Data for SysAdminUnit 

2. Add Data for SysUserInRole



Before you install the package

Switch off trigger TRSysAdminUnitRoot in table SysAdminUnit (otherwise it will block adding new roles)



Install the package

Switch on trigger TRSysAdminUnitRoot in table SysAdminUnit



And always remember, that deleting of data cannot be transfered without SQL script

Hello Cesar,

Unfortunately, there is no option to change the default value anymore.

As a workaround, you are able to change the duration after creating the task.

Thank you,

Artem. 

Hello Artem,

In version 8.0.10, is it possible to change the default value assigned to the duration of activities?



Thank you,

Andreia

Hello Andreia,

 

Unfortunately, this option is still not available at the moment. However, a task has already been registered in our R&D team to consider and implement such a feature in future releases.