Please note that autonumbering became available starting from Creatio version 8.0.5, you can find more info in this Creatio article and this:
It is now possible to number new records in Freedom UI automatically quicker and easier using the [ Autonumber ] field. You can set the number prefix and change the quantity of digits in the number. Creatio populates the field both when you add a record manually and when a business process or integration add it.
Also, as far as having the button trigger both - there are two routes you can take.
Route 1 - If you'd always go to this other page after saving, you could just do that when the save request is triggered. This article shows how to listen for when the page is saved, then you could navigate to the other page from there: https://customerfx.com/article/adding-code-to-the-save-event-of-a-creat…
Route 2 - If you're only wanting to save, then go to this other page, when your own button is clicked, and not for all saves, then you can wire up your own handler for your button. This article shows how to to that: https://customerfx.com/article/adding-a-button-to-execute-custom-code-o… In the handler, you'd save the page, then navigate to the other page. If you go this route (creating a custom request for your button). It would look like this:
{
request:"cfx.clickMeButtonClicked",
handler: async (request, next)=>{// make sure you've added the "@creatio-devkit/common" as mentioned in the articles const handlerChain = sdk.HandlerChainService.instance;// first save the record
await handlerChain.process({
type:"crt.SaveRecordRequest",
$context: request.$context
});// now navigate to the other page, this navigates to the orders section
await handlerChain.process({
type:"crt.OpenPageRequest",
schemaName:"OrderSectionV2",
$context: request.$context
});return await next?.handle(request);}}
Please note that it's best to pass context to each handlerChain.process call. So, in your example, the second call should be:
// now navigate to the other page, this navigates to the orders section
await handlerChain.process({
type:"crt.OpenPageRequest",
schemaName:"OrderSectionV2",
$context: request.$context
});
We are trying to implement the MiContact Center connector for Creatio but are having some issues.
We can make outgoing calls (using the phone icon) but the system is not recognising incoming calls.
Can someone advise as to what we should see in the UI when making and receiving calls, and also what I need to do within the app to make this function fully?
You can change that by adding a handler like this - note this will change the value from "New record" when adding a new record for the page:
handlers:/**SCHEMA_HANDLERS*/[{
request:"crt.HandleViewModelInitRequest",
handler: async (request, next)=>{const result = await next?.handle(request);const cardState = await request.$context.CardState;if(cardState =="add"|| cardState =="copy"){
request.$context.HeaderCaption="Add a new something";}return result;}}]/**SCHEMA_HANDLERS*/,
As far as binding it to some page value, you could use the same but first get a value from the page. Something like this:
handlers:/**SCHEMA_HANDLERS*/[{
request:"crt.HandleViewModelInitRequest",
handler: async (request, next)=>{const result = await next?.handle(request);const cardState = await request.$context.CardState;if(cardState =="add"|| cardState =="copy"){
request.$context.HeaderCaption="Add a new something";}else{// get a value from the pageconst someValue = request.$context.someAttributeOnThePage;
request.$context.HeaderCaption= someValue;}return result;}}]/**SCHEMA_HANDLERS*/,
Tried to set up your application on our system. But unfortunately, there were errors. Nothing happens when you save the settings for a recurring activity. Activities are not duplicated (although there is no error).
This package in the marketplace is for MSSQL systems only. If this is a could system it's most likely a Postgresql system, not MSSQL. The package will install on a Postgresql system, but won't work (and I believe doesn't show any errors). Do you know if the system it's installed on is MSSQL database or not?
We are trying to set a dashboard to find out the user logged in to the system. We have set the below filter :
Question : When we try to login as a user then we need to see only that user usage and not the other user’s data also when the user manager logs in, then the manager needs to see his usage as well as the users associated to him in the org structure. How do we achieve this scenario?