Hello,

In Creatio, a new user’s initial landing page is determined by the first desktop in the desktop list (if no custom homepage is configured). To make sure new users see the Sales desktop on their first login, place the Sales desktop first in the list.

What to do
1) Open System Designer -> Workplace setup
2) Open Workplace setup and locate the list/order of desktops.
3) Move the Sales desktop to the top (first position).

Hello.

The GetCanEdit 400 error is most commonly related to how the page's data source is configured, particularly when it comes to the relation criteria used to resolve a specific record.

When the relation criteria on a page are set up incorrectly, or point to a relationship that cannot be properly resolved at runtime, Creatio is unable to determine a valid related record for the given context. As a result, the value primaryColumnValue is passed as null when the request is sent to RightsService/GetCanEdit. Since this service expects a valid GUID value in order to perform the permission check, receiving a null value instead leads to a GUID deserialization error, which in turn causes the request to fail with a 400 status code.

To resolve this, we recommend reviewing the relation criteria configured on the page. Please verify whether these criteria correctly reference the intended relationship, and whether the referenced relationship is expected to always resolve to a valid record in your specific business scenario. If the relation criteria are not required for the page to function correctly, or if they are pointing to an incorrect or unnecessary relationship, we would recommend removing them.

If reviewing the relation criteria does not resolve the issue, this behavior may alternatively be caused by a duplication of the data source on the page. In such cases, having more than one data source referencing the same entity schema on a single page can also lead to similar permission-check errors, and this would need to be reviewed separately as a possible root cause.

Best regards,
Antonii

Hello Payal Motwani,

Deactivating business processes via a script task is not recommended.

If you really need to do it, send a POST request to the endpoint: [CreatioURL]/0/ServiceModel/ProcessEngineService.svc/DisableProcess?sysSchemaId=00000000-0000-0000-0000-000000000000

The sysSchemaId parameter is the process's SysSchemaId, found in the corresponding table:

SELECT "Id" FROM "SysSchema" WHERE "Name" = 'UsrNameOfYourProcess'

Before disabling the process, decide how to handle any currently running instances - you may want to cancel them.

To check the count of running processes, send a POST request to [CreatioURL]/0/ServiceModel/ProcessEngineService.svc/GetRunningProcessesCount with the payload:

{
    "countSpecifiedVersion": false,
    "managerName": "ProcessSchemaManager",
    "schemaId": "00000000-0000-0000-0000-000000000000"
}

To cancel all running instances of the process, send a POST request to [CreatioURL]/0/ServiceModel/ProcessEngineService.svc/CancelExecutionBySchemaId?schemaId=00000000-0000-0000-0000-000000000000

Eduard Dovydovskyi,

Thank you so much. I will try this :)