how can I add the multicurrency data to my Opportunity page, like it worked properly in the Classic UI?
For example, I would like to add the Opportunity value in USD, than the system calculate the EUR value, or if I add the value in EUR, the system will calculate the USD value.opps
Our R&D team has a task to implement a multicurrency field in Freedom UI in the 8.2 application version.
Unfortunately, there are no examples in the documentation or application of implementing it in the current application versions. So please wait until 8.2 when this column will be available out-of-the-box and could be used on the pages.
The problem is that the responsible field takes information from the contacts lookup. Contacts include not only system users of the company and employees, but also other contacts created on your website. That is, this field will contain all the contacts you have created, as well as system users. You can change the lookup from which the information for the responsible field will be taken and thus have only the contacts you have selected when filling out this field.
I've been working on applications in the application hub and I've had some trouble with the run app button defaulting to a different section than I'd prefer, is there a way to change which page the button opens? I haven't been able to find instructions on how.
I have a section called 'Requests' that has 3 multiple edit pages based on a section FIELD value. Now, the parent edit page has been disabled (it is in a 'not in use' state). How can I enable it? I need a common page that is not based on a Field value.
I recommend you to keep the main base page unused.
The other three pages you can make inherit from this first one getting a base page for common problems, for example, you need to add a business rule or a field and you need it in three sections, you go to the base page, create what you need there and voila, all the pages get this new field or business rule....
Hello, I have an issue regarding email accounts. We use a shared mailbox for sending automated emails. In Créatio, I had to add my email with my Office 365 account and then add the shared mailbox. The problem is that all automatically sent emails from Créatio using the shared mailbox end up in the "Drafts" folder of my personal mailbox instead of the sent items of the shared mailbox. Do you have any information on this issue?
We have the same issue, Seems to only happen when there is an attachment or an image in the Email. Went though support many times, and their response is it is how the Exchange Web Services does it and was told to reach out to MS.
We have examined the problem and determined that the issue is specifically associated with emails that contain attachments. Mind it, if there's a signature with a photo in the template, it will also be considered an attachment. We would like to explain the email sending process from our system to help you understand the steps involved and how they relate to the problem you are experiencing.
1) Sending Emails Without Attachments:
When you send an email without any attachments, our microservice Email Listener, responsible for sending and synchronizing emails, sends a request to the mail server with the parameter MessageDisposition="SendAndSaveCopy". This request includes information about where (the folder ID) and in which mailbox the mail server should save the email.
It is important to note that the mail server confirms the success of this request without any errors.
2) Sending Emails With Attachments:
The process for sending emails with attachments is more complex and involves multiple steps:
- The system requests to save the email as a draft with the parameter MessageDisposition="SaveOnly".
- Next, the system requests to add attachments to this draft email using the <m:CreateAttachment> operation.
- Finally, the system sends a request to save and send the email, indicating where (the folder ID) and in which mailbox the mail server should save the sent email.
Like the previous case, the mail server confirms the success of all the requests related to this process without errors.
In such cases, we recommend reaching out to the mail server provider or the responsible party for assistance and guidance on troubleshooting the issue further.
Unfortunately, in this case, we do not have specific recommendations on what should be checked because the issue appears to be related to the mail server or mailbox itself. Our role was to send the request to save and send the email, specifying the folder ID and the target mailbox where the mail server should save the sent email. The mail server confirms the success of all the requests related to this process without errors.
Please note that we already have had experience with the same behaviour in other clients with this type of mailbox, and they were resolved on the level of mailbox configuration. Our recommendation, in this case, is to check the mailbox configuration. You can involve Microsoft's team for better analysis and understanding, as, unfortunately, as this is a third-party solution, we cannot provide you with complete information about Outlook's mailbox configuration.
Is there a way to only allow certain users the ability to import data by section/object? It seems to me that it is a 'all or nothing', but I want to grant permissions just for one section/object but keep restrictions in for all the others.
We are facing one issue specifically related to displaying images in the word document. We have a use case where we want to print rows of data which includes images as well to the word document, which is working fine.
But we do have some exceptions where for a particular row image is not there, but rest of the column data is present. In this specific case, the data is printed correctly but in the image column we are getting a blank canvas. Instead of blank canvas we want to display a default image is no image data is present in the DB for the rows.
Upon reviewing your request, we have identified that the current underlying logic of our program is configured to operate in the way you described. That is, if there is no image, a macro is displayed (a gray square) instead of an empty field. However, we understand that this is not ideal for your specific needs.
We want to assure you that we have submitted a request to our development team to implement this feature in upcoming versions of our program. We understand the importance of providing the best service to our customers and will diligently work towards implementing the changes you have suggested.
Thank you again for bringing this to our attention.
Such problem can appear when you've opened the app in a few tabs and logged out+ loged in on one of the tabs. For example: the tab with the configuration page is open and you're writing code there. Then you press the save button, click on the nearest tab to check the result, and relogging to the second tab. After this, your changes in the first settings tab will not be saved. Or it can happen if you have two settings tabs for one object.
I would recommend you to close all tabs and try to add the CSS again, save it and check the result by reloading the page button.
Such problem can appear when you've opened the app in a few tabs and logged out+ loged in on one of the tabs. For example: the tab with the configuration page is open and you're writing code there. Then you press the save button, click on the nearest tab to check the result, and relogging to the second tab. After this, your changes in the first settings tab will not be saved. Or it can happen if you have two settings tabs for one object.
I would recommend you to close all tabs and try to add the CSS again, save it and check the result by reloading the page button.
We're trying to set it up so that one of our mini pages used for record creation (wherever the record creation is started from, as there are several screens with a button to create the record) always has a default value set. We can't set the default on the entity, as records coming in from the integrations shouldn't have these fields set to any default, only set to whatever comes in through the interface. Is there any configuration that can be done to set default values for pages themselves?
We know about setting defaults when calling the crt.CreateRecordRequest request which is done from the calling page, but would ideally like to be able to set it one time for the creation mini page itself to avoid code duplication. We are on 8.1.0
Thanks for the suggestion Franck, and interesting/concerning that the entity-level business rules only apply when creating records through the UI and not for all data!
Unfortunately the business rule value setting is much too limited in Creatio for what we need, only being able to set to a constant/static value which is defined when setting up the business rule. We need to be setting the value based on some logic through code, but would ideally be doing so with declarative code rather than imperative code which modifies the fields manually.
But if you want to avoid transferring the values in every place you open the mini-page, consider the following implementation in the mini-page view model:
Set the attribute value in the "crt.HandleViewModelInitRequest":
request.$context.AttributeName= “AttributeValue”;
Provide it not to be overridden to default null value in "crt.HandleViewModelAttributeChangeRequest":
Thanks for the reply, those will definitely be useful - for example I didn't know you could set default values when calling the crt.OpenPageRequest, I thought it was only possible to do so using the crt.CreateRecordRequest, so thanks for that!
I believe the workaround for putting the logic in the mini-page would mostly work, but with the following caveats:
1. You would not be able to clear the value of the field manually, which is unfortunate
2. This would make a change to the page that would cause the confirmation dialog to appear if closing the mini-page without the user making any modifications to data - not the end of the world, but it would be nice to avoid that
A quick question - what is the difference between simply assigning a request.$context.AttributeName using
request.$context.AttributeName="value"
Vs using the _setAttributeValue method in your reply? Is there any functional difference between the two, or is it just preference?
Sure, setting the mini page default values via HandleViewModel InitRequest and HandleViewModelAttributeChangeRequest has some disadvantages. That’s why we recommend using ModelInitConfigs in OpenPageRequest.
However, it may still be used if the user doesn’t need to set the field value to null. Especially considering the facts that:
- removing the string field means setting a value to an empty string (not null);
- the numeric field value might be set to 0 instead of removing it.
Regarding your question about setting the attribute value – I clarified it with our R&D department. There is no functional difference between the two approaches, but only the direct assigning is recommended to use as the most stable method:
request.$context.AttributeName="value"
Thank you for such an important question. I have already changed my examples accordingly.
