Dear Lisa,

You just need to click on the gear icon on the folder http://prntscr.com/q0wsnm and select Copy option. As you see, I've created the same folder with identical filter. As for dashboards, you can either create the copy of the whole dashboard tab http://prntscr.com/q0wt23 or copy 1 element of it through the dashboard designer http://prntscr.com/q0wtc7

Best regards,

Dean

Thanks Dean,

I know about the copy features.  Sometimes I'd like to copy folder or dashboard criteria from one section to another.  It's not possible to do that.  Also, I'd like to copy the criteria from one series in a graph dashboard to another series, or even just a subset of that data.  It's not possible to do that either.  I end up having to recreate the entire query in each series.

It would be nice if we could just save a particular query or apply the criteria from one or multiple folders to a dashboard without selecting the folders. Especially if deploying to other users. 

Dear Lisa,

We will register this idea in our R&D team backlog to consider the implementation of such logic in the future application releases.

Best regards,

Dean

Hello Dean, has there been any forward movement on this idea? Also, when looking at this logic it would be great if these dashboard and folders could be available between environments since dashboard aren't able to be created through packages. 

Nathan,

Thank you for your question!

I have double-checked this information and currently, there are no updates on the ETA of implementing this feature in Creatio.

We will make sure to provide this information as soon as we acquire it.

Thank you for your understanding!

Regards,

Danyil

Hello Sanae,

Unfortunately this is base application logic that stores opportunity amount in USD currency. You can build a process that will be triggered upon record modification in opportunity amount field for example, that will read this value from opportunity amount field, than this process will calculate correct opportunity amount value based on currency exchange rate and modify opportunity amount field. I will also let our R&D team know that currently opportunity field values are stored using USD currency ignoring "Base currency" system setting. Thank you for reporting this issue!

Best regards,

Oscar

Thank you Oscar, 

I did it another way. I changed the amount field type in opportunity section to currency instead of Decimal. It's working well. 

Hello Ahmad,

This is an expected application logic that displays two series chart in the way displayed on the screenshot in case chart type is different for each serie. There is no way to build a chart with two series with different type for each serie which won't overlaps. You need to create two separate charts for each serie or use same chart type on one dashboard. I will also let our R&D team know that this issue occurs and probably they will modify this logic in one of future releases.

Best regards,

Oscar

Oscar Dylan,

Okay, thank you

Well i did it in js:

            onEntityInitialized: function() {

               

                this.callParent(arguments);

                

                if (this.get("Stage").value === "991d70f4-7a10-42b8-bb9c-fd8096d05d9b") {

                    this.showInformationDialog("Set the new Date to call");

                    this.set("DateToCall", null);

                }

            }

If someone knows how to set a Date to Null in a process, i m interested with

LÉZORAY Nicolas,

You can create date parameter and leave it empty. Then specify this parameter as a value that must be inserted to date field. It will leave this field empty or make it empty if it was filled in.

Best regards,

Angela

Thank you it works !

Hello!

Can you please contact our support team directly with the question you described above? We might need to have an access to the system where you face this behavior.

I will add details here after we finish with the investigation.

Thank you!

Hello Nicolas,

Thank you for reporting this issue to us! It helped to solve the problem in an out-of-the-box logic of 7.15.2 version of the application. The reason of this error was in fact that in base logic of 7.15.1 version "OpportunityInStage" and "OpportunityStage" objects have the same title in french localization https://prnt.sc/q0jozy and it provokes an error when choosing an object in formula or via lookup value in process elements. To resolve this issue we've renamed OpportunityInStage object title to "Etape dans l'opportunité" and it solved the error.

Best regards,

Oscar

It works !

Thank you !

Dear Julius,

There is indeed issue with the CKeditor and the system setting in the current application version. However the problem has been already resolved and the functionality will be working correctly starting from nearest version 7.15.3

Best regards,

Dean

Dear Pedro,

There is no basic option to add timeline tab to the section. It can only be done by the development process. Here is the development guide on how to add the timeline tab which can contain the history of action on the record. 

https://academy.creatio.com/documents/technic-sdk/7-15/creating-timeline-tab-tiles-bound-custom-section

Best regards,

Dean

If you need to actually store the values in the database as uppercase, you could wire up a change event for the fields, and then use toUpperCase and put back the uppercase value into the field. See here if you need help with wiring up the change event: https://customerfx.com/article/triggering-an-event-when-a-field-is-chan…

If you only need to display the value as uppercase (and not necessarily stored this way), then you could add CSS to the page to uppercase the fields. You could use text-transform:uppercase fo the fields in question. See here if you need help with adding the CSS to the page: https://customerfx.com/article/adding-custom-css-style-sheets-in-bpmonl…

Hope this helps

Ryan

Hello Fernando,

There is also another way to achieve this task. Here is a screenshot of a process that will modify the text that you put into a string field http://prntscr.com/ptpvpp using this formula value in "Modify "Recipient's name"" element: [#Read contact.First item of resulting collection.Recipient's name#].ToUpper().

This process will be triggered upon record adding to "Contacts" section and also when updating "Recipient's name" field in existing contact. As a result everything typed there will be updated to upper case. The only one minus of this solution is in fact that you need to refresh the page (F5) or close and open this record once changes are saved. You can use this free marketplace app so to refresh the page without full refreshing (F5) or reopening the record https://marketplace.creatio.com/app/refresh-data-button-creatio.

Method proposed by Ryan is more elegant and accurate in my opinion but in case you don't want additional development to be used you can use the business process from my screenshot.

Best regards,

Oscar

Thanks Ryan & Oscar for your comments!!

Basically we need to force to the user to use the UPPERCASE for text Fields. (Display & Store).

I will take a look on this options and I will send my comments if I find a suitable solution.

Best Regards,

Fernando

Hi Jonas,



You can bind enabled property to a method in diff section like this:



 

define("UsrPage", [],
	function() {
	return {
		entitySchemaName: "UsrObject",
		details: /**SCHEMA_DETAILS*/ {} /**SCHEMA_DETAILS*/ ,
		diff: [
			{
				"operation": "insert",
				"name": "DATEb70c5501-1824-4750-9dc8-2c7ced38a192",
				"values": {
					"layout": {
						"colSpan": 6,
						"rowSpan": 1,
						"column": 18,
						"row": 0,
						"layoutName": "Header"
					},
					"bindTo": "UsrValidityDate",
					"enabled": {"bindTo": "myFunctionCheck"}
				},
				"parentName": "Header",
				"propertyName": "items",
				"index": 2
			},
			{
				"operation": "insert",
				"name": "LOOKUP94e30b0e-aa00-49bb-a050-0103e04cd0fa",
				"values": {
					"layout": {
						"colSpan": 7,
						"rowSpan": 1,
						"column": 0,
						"row": 0,
						"layoutName": "Header"
					},
					"bindTo": "UsrQuoteOwner",
					"enabled": {"bindTo": "myFunctionCheck"},
					"contentType": 5
				},
				"parentName": "Header",
				"propertyName": "items",
				"index": 3
			}
		],
		methods: {
			myFunctionCheck: function() {
				return false;
			}
		}
	};
});

Note, that more than one field can be bound to one property.



Does this work for you?



Regards,

Dmytro

That'll do. Should've thought about that myself! Thanks.

Dear Nicolas,

In OOB system "stage" column is required when opportunity is created. You should check what stage is used when opportunity is created: http://prntscr.com/pqzl32

Dear Angela,

Effectively, i add the stage on the mini-page, and the stage used when opportunity is created is not the DCM first step (it is "En cours").

i have to find where the developper has forced the stage on the mini-page to a specific step.

=> Solution:

The default opportunity's stage was defined on the Opportunity Object.

Thank you Angela !