Hello Jasmin, 

We confirmed this information with a responsible R&D team and indeed as of now there is no option to rename these sections or columns, they were designed with "service" titles (section 1,2,3 etc) and renaming option was not implemented for them. 

I have registered a corresponding query for our R&D team to consider implementing this functionality in the upcoming versions of the main application. 

Thank you for the idea and helping us to make our Application better!
Best regards,
Anastasiia

Hello Tyler,

Thank you so much for your idea. We've registered it in our responsible team backlog for consideration and implementation in the future. Thank you for helping us to improve our product. 

Best regards,

Bogdan

Hello Damien, 

Thank you for your idea! 

Let me mention that implementation of the new features could be tracked in the "Release notes" articles directly on our Academy, for each new release version a corresponding article is created . 

If you are interested in a specific query for functionality implementation registered for our R&D team and would like to have an update about it, you can provide us with it's number or case number where this functionality was discussed and we will be able to update you about the progress. The progress of such queries are being tracked directly in our system. 

Best regards,
Anastasiia

Hi Anastasiia,

The Release notes only shows delivered features and not in progress features, as can be seen in the example link,  and there is no published roadmap either to see the road ahead.  (In the example, it also mentions only "in progress" with no time table so that you handle timing on your side, but it gives an idea of what is actively being worked on and what is only at an idea stage).

The problem with the last point here about looking at the number / case number, is that we have no clue if other members of the community at large have already requested the feature, how many people support it, and which features are on track.

Your tracking progress is centralized only internally is very inward focused and not community focused. Each company has its rules obviously 🙂.  However, it's not the most engaging from the community side and not efficient on the community side in terms of requesting ideas, keeping track of other user requests. I would understand in terms of privacy, you want to limit visibility, but this could be limited to only partners / users after log-in ?

Hi Damien,

Thank you so much for your idea. We've registered it in our R&D team backlog for consideration and implementation on the Creatio Community in the future.

Thank you for helping us to improve our product. 

Best regards,

Bogdan

Hello 

We have already registered the idea for our R&D team to implement this functionality in further releases. I will assign your case to this project in order to increase its priority.  

Thank you for helping us to improve our product. 

Best regards,

Bogdan

Hello Bhoobalan,

Thank you so much for your idea. We've registered it in our R&D team backlog for consideration and implementation in future application releases. Thank you for helping us to improve our product. 

Best regards,

Bogdan