Hello,

To achieve your goal, you will need to apply the development.

You can find basic examples for launching the process from the page from our partners CustomerFX:

1) Starting a Process from Client-Side Code on a Creatio Freedom UI Page

2) Programmatically Starting a Process from Client Code in Creatio

Thank you.

Hello,



Currently, auto-numbering of fields in an object is a new functionality that the mobile app does not yet support. Support for this functionality will be available at the beginning of the new year.  



If you need auto-numbering on an object and want it to work everywhere, both on the web and in the mobile app, you need to implement the auto-numbering logic not through default values, but by implementing it in code on the object.

Hello Alexander, 

when implementing autonumbering on the back-end, you can choose any action you want in the replacing object. 

In your case, instead of the default "Before record added", you can set the process to be triggered by the "After record saved" event.

Best regards,

Max.

Hi Max,



thank you very much for your reply. We tried it, but it wasn't possible. Could it be that the "Invoice" module in the original "Invoice" object blocks the creation of individual event BPs?

Alexander Lovenjak,

The original object should not block the creation of the event BP's.

Have you tried using the "Before record updated" event?

When an object is saved it basically sends an Update query to the database so this event should work properly.

Best regards,

Max.

Hi Max, thank you for your help. It seems, that there is a bug within the invoice object. Creatio consulting tries to find it. The event handling changes doesn't help.

Best regards

Alex

Hi, Julius!



As you have your own field in Opportunity (e.g. "UsrCode"), so you can use:



    onEntityInitialized: function() {

                 // onEntityInitialized method parent realization is called.

                this.callParent(arguments);

                // The code is generated only in case we create a new element or a copy of the existing element.

                if (this.isAddMode() || this.isCopyMode()) {

                    //  Call of the Terrasoft.BasePageV2.getIncrementCode base method, that generates the number 

                    // according to the previously set mask. 

                    this.getIncrementCode(function(response) {

                    // The generated number is stored in [Code] column.

                        this.set("UsrCode", response);

                    });

                }

            }

Dear Julius,

Since opportunity section does not have an existing Code column, you can create one using means of section wizard.

No special methods needed for new column, since we are calling parent realization in the onEntityinitialized method, which has the logic of working with auto incrementing. Just be sure to indicate your custom column in the this.set method by its name, but not title.

As for the back end realization of the auto incrementing, follow the instructions just the same, but indicate name of the custom column.

Regards,

Anastasia

Anastasia Botezat, Vladimir Sokolov,

I tried this again. But it's not working. No value gets set.

I have created the System Settings, the Property on Opportunity, And I have adjusted the JavaScript to have the correct string value, "UsrCode".

It's not working this time either. Is the on-client method unavaliable on the Opportunity object?

Maybe the Opportunity object does not know the Systems Settings i Created. The system settings code names are : OpportunityLastNumber and OpportunityCodeMask

UPDATE : It is working while using Copy. But no Code is set when adding an Opportunity with the Mini-Page. I am now working on this. Any advice appreciated.

UPDATE 2 : Creating and Copying works as long as I do not have a Mini-Page. I tried to add the same JavaScript in the MiniPage methods{}. But that's not working. Any tricks to use MiniPages?

Julius,

The auto increment logic is not a part of basic mini page logic. The 

getIncrementCode method is written on the BasePageV2. However, mini pages are inherited from BaseMiniPage, which does not have such method.

You can add the getIncrementCode method realization to the mini page, so that it will execute the logic. 

As for the back-end part, the changes are displayed on the client side only after record is saved. Therefore, it is impossible to view the code value on the opportunity page immediately. 

Regards,

Anastasia

Anastasia Botezat,

 I did not get this to work with Mini-Page. I have anyway decided to work without the mini-pages. When Creating a Opportunity I just get the regular edit page where the incremented numbers work fine. Thank you.

Anastasia Botezat,

Hi,

This dint worked  even to me. 

https://community.bpmonline.com/questions/auto-increment-issue

I have posted the issue in detail in the above link. Please help!!!!

regards,

Sriraksha