Hello!

 

The specified field is intended to set a section as the default value for the user.

The home pages are the main places where people enter the workspace.

Perhaps you will find the mentioned article useful for implementation:

https://community.creatio.com/questions/default-page-login

Alona Dolya,

Thank you for your answer. I know the article you linked to and unfortunately it does not answer my question.

In Freedom UI, the home page does not load by default for users after logging into the system. In Freedom UI, after logging in the desktop set in Setup apperance loads by default. However, I need the start pages to load by default in Freedom UI as it was in the standard UI and I don't know how to set it.

Has anyone managed to solve such a problem?

Nope, still awaiting for Creatio to provide us the ability to choose the default page in new shell like we used to in classic shell, being forced on desktop view also...

A couple similar request for the same issue has been made already (https://community.creatio.com/questions/all-apps-workplace-0)  & ( https://community.creatio.com/questions/default-logon-page-homepage-vs-…), still awaiting for some more control in future version of Creatio 8.1.x

Dear Maciej,

From the 8.1.1 release, there is a possibility to define that by using system operation with code "CanViewAllAppsWorkplace".

Also, please consider that  "All Apps" workplace is displayed to a user only when they have 1+ workplace available. And it namely contains the list of all available apps inside his available workplaces, but not a list of all existing apps in the system.

Have a great day!

Hello Solem,

To make changes to the addon, you can modify the Modifications package node of the addon structure.

There is an article in Creatio Academy with an example of how you can customize the Timeline component: https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

Hello,

You can use this documentation:



Work with attachments | Creatio Academy



Regards,

Orkhan

Hi Orkhan,



Thank you but these are Classic UI instructions, I am looking for the equivalent in Freedom UI as new fresh installations do not have classic UI alternative in some sections.







Do you have such documentation & functionality for Freedom UI ?



Thanks,



Damien







 

Hello,



Please be informed that it is not possible to edit templates that are used in running campaigns. You can edit email templates in Content Designer. I am sending you an instruction that describes how to do it in detail: https://academy.creatio.com/docs/8.x/creatio-apps/products/marketing-to…

Hi Harvey,

 

We can create an attribute to store a value that you want to set in HandleViewModelInitRequest. Then, in HandleViewModelAttributeChangeRequest, we can check if the current field value matches the one you previously set. If it does not match, we can assign the stored value to it. This way, we ensure that the desired value is assigned to the field.



In the given example, we have created an attribute named "UsrInitialValue".

viewModelConfig: /**SCHEMA_VIEW_MODEL_CONFIG*/{
			"attributes": {
				"StringAttribute_ljc6yh6": {
					"modelConfig": {
						"path": "PDS.UsrTestString"
					}
				},
				"UsrInitialValue": {}
			}
		}/**SCHEMA_VIEW_MODEL_CONFIG*/,

This attribute is used to store a specific value that we set during the initialization process. In the crt.HandleViewModelInitRequest handler, we set a value for the request.$context.UsrInitialValue. And in crt.HandleViewModelAttributeChangeRequest, we check if the current field value matches the value we set previously in the request.$context.UsrInitialValue. If they don't match, we update the field with the new value.

 

handlers: /**SCHEMA_HANDLERS*/[
			{
				request: "crt.HandleViewModelInitRequest",
				handler: async (request, next) => {
					request.$context.UsrInitialValue = "testInit";
					request.$context.StringAttribute_ljc6yh6 = await request.$context.UsrInitialValue;
					return next?.handle(request);
				}
			},
 
			{
				request: "crt.HandleViewModelAttributeChangeRequest",
				handler: async (request, next) => {
					var srtValue = await request.$context.StringAttribute_ljc6yh6;
					var initVal = await request.$context.UsrInitialValue;
					if (request.attributeName === 'StringAttribute_ljc6yh6' && srtValue != initVal) {
						request.$context.StringAttribute_ljc6yh6 = initVal;
					}
					return next?.handle(request);
				}
			}
		]/**SCHEMA_HANDLERS*/,

Artem Smyrnov,

I think this would prevent any modification to the data, including intended changing by the user or system. Obviously it could be changed to add some more conditions, but really the main thing we want/frequently need is for the crt.HandleViewModelInitRequest request to be able to initialise a value and not be overwritten by the standard page loading stuff (loading default values for the entity, clearing out the field where there are no default values etc). I'm pretty sure this was possible in Classic UI, it just doesn't seem to be currently in Freedom UI without some pretty nasty hacks.

Harvey Adcock,

There is no logic that could be used to revert changes to the column value that were done by the handler.

As a solution, you need to create a column that will not use any other handler and set the value using your custom handler. This will prevent the value from being overwritten by other handlers or custom logic.

We have a workaround in place, but this capability has been required a few times - it would be good if Creatio supported setting values on the page in the init handler (or some other handler, maybe a new initvalues handler or something) since per-page default values is often required.

Hello Harvey,

The style HTML tag (inside the head tag) usually contains CSS rules, which are crucial for the init page rendering, or the most general CSS rules. These rules could be overridden in a common way:

1. Create a new module, choose LESS in the left panel, and add the CSS rules.
2. Add the name of this module to the dependencies in the Page client module, starting with the prefix “css!”

Here is an additional example - https://community.creatio.com/questions/how-can-i-hide-task-properties-pre-config-page .

Best regards,

Natalia

Hi Natalia,

Unfortunately this doesn't seem to be working for me for 2 reasons:

1. The style in the CSS is not taking precedent over the OOTB style that is included in the style element in the DOM. Does Creatio have any way of overriding the OOTB elements' styles without resorting to using !important everywhere?
2. The client module seems to be "compiling" my code and modifying it from what I wrote (first line after this) into what appears in the browser sources (second line after this point) and these are completely different - Creatio cannot take 40 pixels off 100% height and conclude that it's always going to be 60% height:
   1. height: calc(100% - 40px)
   2. height: calc(60%)

Do you know of any resolution to these issues?

Hi Harvey

 

You can use this addon to apply CSS styles globally: https://marketplace.creatio.com/app/experceo-global-jscss-editor-creatio

If you can identify the selector, you can easily override the CSS properties values using !important keyword.

I hope this helps!

Mohamed Ouederni,

Thanks Mohamed, generally we're trying to keep add-ons to a minimum unless strictly necessary to avoid too many dependencies and potential points of failure, but worth knowing.

Using Natalia's recommendation, I was able to apply the CSS - for any others having this issue, the resolution to my first issue was just to set the style as being important, though another resolution might be to make the selector more specific (CSS specificity) than the ones acting upon it. And the resolution to my second issue was that it's a LESS CSS issue rather than Creatio's issue, but it can be worked around using the following escaping of the calculation:

height: calc(~"100% - 40px")

Which I found from this Stack Overflow question: https://stackoverflow.com/questions/11972084/how-to-prevent-less-from-t…

Hello, 

None of this is tested (and I've not used the Tableau embed script to know if it would work this way), but you can try using require for it by adding the following: 

requirejs.config({
	paths: {
		Tableau: 'https://public.tableau.com/javascripts/api/tableau.embedding.3.latest.min.js'
	}
});

Note, you can add this before the page code define and then include as a reference for it: 

define("UsrMyCustomObject1Page", ["Tableau"], function (Tableau) {

Then use as something like: 

const viz = new Tableau.TableauViz();
viz.src = 'https://my-server/views/my-workbook/my-view';
viz.toolbar = 'hidden';
document.getElementById('tableauVizElement').appendChild(viz);

Ryan

Hi Adharsh



You can use this addon to add JS scripts globally: https://marketplace.creatio.com/app/experceo-global-jscss-editor-creatio

 

Go to System Settings -> ExpGlobalJSValue to update the global JavaScript script.

 

require(["https://public.tableau.com/javascripts/api/tableau.embedding.3.latest.min.js], function(lib) { 

       window.Tableau = lib;

});



Then you can use window.Tableau  in your js code.



Hope this helps!

You can try using the password input which will mask the entire text as ****. This control doesn't appear in the toolbox, so to add it, you could add an input, then in the code change "type": "crt.Input" to "type": "crt.PasswordInput". You can see an example of this control in the page SysUserProfilePage (user profile page)

Ryan