Hello Eryk,

Yes, we have native support of the offline mode. The offline mode requires an Internet connection only for the first imports and subsequent synchronizations. With this mode, the data is saved on your mobile device. Manually run a synchronization with the Creatio instance server to get the configuration changes and update the data.

You can use the following articles to get more information on how the offline mode works:
https://academy.creatio.com/docs/8.x/mobile/mobile-app-setup/classic-ui/synchronization
https://academy.creatio.com/docs/8.x/mobile/mobile-development/mobile-basics/architecture-mobile/overview-mobile

Have a great day!
 

Hi, thanks for the response.

I may have phrased my question a bit imprecisely - the need I'm describing is fairly specific. I'd like to be able to store some temporary technical information locally on the phone only, scoped to the currently logged-in user. I know I could do this by adding a dedicated object with a relation to the user and fields to hold this kind of data, setting that relation on record save, adding a filter on read, and possibly some security to prevent other users from reading it. But that feels somewhat overengineered, and on top of that, it unnecessarily writes this data to the database. It would be much simpler in this case if the SDK offered something like localStorage, where I could do:

localStorage.setItem('someSetting', { ... })

and later just read it back with:

const settingValue = localStorage.getItem('someSetting');

Hello,

At the moment, the Mobile Creatio Freedom UI SDK does not provide a public localStorage-like API for device-only data. Page attributes exist only within the ViewModel lifecycle, and custom logic runs in an embedded JS runtime rather than a browser, so the standard web localStorage is not available either.
The approach you described (a dedicated object filtered by the current user) is currently the supported way to persist such data. In offline and hybrid mode, records are stored in the local on-device database and transferred to the server only during synchronization, so it works without a connection: https://academy.creatio.com/docs/8.x/mobile/mobile-development/mobile-b…
You are right that the data will eventually reach the server database, and there is no supported way to keep it device-only. A local key-value storage in the mobile SDK is a reasonable suggestion, so please consider posting it in the Ideas section: https://community.creatio.com/?type=idea

Ok, thank you :)

Hello,

You can configure the validator and converter using a remote module, examples:
https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/front-end-development/freedom-ui/remote-module/custom-validator/examples/implement-validator-using-remote-module

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

Hi, I think the links you sent are about the web version, but I clearly mentioned that I need the mobile version.

Just bumping this - any update would be appreciated. Thanks!

Hello,

Yes, it is possible to reference translation labels in the Mobile application. You can retrieve them in the following ways:

1. const label = await ($context as any).getResourceString('MyResourceKey') ?? 'fallback';

This approach allows you to obtain the localized value for a specific resource key directly in code. If the resource is not found, the fallback value will be used.

2. #ResourceString(UsrName)# can be passed as title for dialog, label for button, etc via SDK. It will be resolved automatically.

Hi,

I checked both approaches and they work. Thanks!

Is there, however, any way to access information about the currently logged-in user and their language within the mobile app?

I just realized what my original problem actually was, and why your answer doesn't solve it :)

These solutions work when it's a label defined for the view, but they don't work at all when it's a label that refers to an object field.

[Example 1]

{
    "operation": "insert",
    "name": "TabContainer_gbg1csl",
    "values": {
        "type": "crt.TabContainer",
        "items": [],
        "caption": "#ResourceString(TabContainer_gbg1csl_caption)#",
        "iconPosition": "only-text",
        "visible": true
    },
    "parentName": "TabPanel_poiszvh",
    "propertyName": "items",
    "index": 6
},

Here we have a view label, and as you can see, it's assigned using the ResourceString macro. This works fine.

[Example 2]

{
    "operation": "insert",
    "name": "ComboBox_9ijhdyv",
    "values": {
        "layoutConfig": {
            "column": 1,
            "colSpan": 1,
            "row": 1,
            "rowSpan": 1
        },
        "type": "crt.ComboBox",
        "label": "$Resources.Strings.CaseDS_CreatedBy_lyopz5h",
        "ariaLabel": "",
        "isAddAllowed": true,
        "showValueAsLink": true,
        "labelPosition": "auto",
        "control": "$CaseDS_CreatedBy_lyopz5h"
    },
    "parentName": "GridContainer_945eip2",
    "propertyName": "items",
    "index": 0
},

Here the label is the column name. Unfortunately, in this case, none of the solutions work as expected.

Below is an example of the handler code:

await dbg($context, 'T1: ' + await $context.getResourceString('TabContainer_gbg1csl_caption')); // Correct label
await dbg($context, 'T2: ' + await $context.getResourceString('CaseDS_CreatedBy_lyopz5h')); // Incorrect label: null
await dbg($context, 'T3: #ResourceString(TabContainer_gbg1csl_caption)#'); // Correct label
await dbg($context, 'T4: #ResourceString(CaseDS_CreatedBy_lyopz5h)#'); // Incorrect label: #ResourceString(CaseDS_CreatedBy_lyopz5h)#

Hello,

You can add the Quick Filter component by selecting it in the Freedom UI Mobile Designer and dragging it onto your page layout. After adding the component, ensure that the filter is configured with the appropriate data type and is correctly linked to the corresponding list component.

Please refer to the screenshot below for reference on configuring Quick Filters in the new Freedom UI Mobile Designer.



I hope this helps.

Thank you for choosing Creatio!

Thank you :)

Hi,

For a true one-to-one relationship, I would not recommend maintaining two independent lookup fields unless you really need to store the reverse reference for reporting/integration purposes.

The cleaner approach is to keep a single source of truth:

License.Request Number -> Application

Then, on the Application page, display the related License through the page configuration rather than trying to populate Application.License Number automatically.

If you are using Freedom UI, the best fit is usually Multiple data sources. Add License as an additional/secondary data source on the Application page and configure the relation criteria using the existing lookup:

License.Request Number = current Application

After that, you can place the needed License fields directly on the Application page. This is the closest match for a real 1:1 UI, because the user sees License data as part of the Application page without duplicating the relationship.

Documentation:
https://academy.creatio.com/docs/8.x/no-code-customization/customization-tools/ui-and-business-logic-customization/multiple-data-sources

A Business Rule is not the right tool for this. Business rules are mainly for UI behavior, visibility, required fields, validation, etc. They do not automatically query a related child record and populate a reverse lookup.

A Business Process can do it, but only if you intentionally want to denormalize the data. In that case, you would need to handle all scenarios: License creation, changing the Application on the License, deleting/unlinking the License, and preventing more than one License per Application. Otherwise the two lookup fields can become inconsistent.

Hi Artem, 

in system settings you can turn on/off the logging for certain types of events - e.g. UseAdminSettingsLog, UseAdminEntitySchemaOperationLog...

I assume what you see is the possible Lookup Values for types of events, however if logging for them is turned off, then no records are created of this type you could see

Best, 
David

David Örnek,

thanks a lot! Does selected Default value checkbox mean that the event is included in the log, and if it isn't selected then vice versa?

Hi Artem,

The Audit log records themselves are stored in the SysOperationAudit table. The list of available audit event types is stored separately in the SysOperationType lookup/table.

This means that the values you see in the advanced filter are the available operation types from SysOperationType, but it does not necessarily mean that records for all of these types are currently being written to the audit log.

Whether a specific type of event is actually logged depends on the corresponding system setting.

Regarding the Default value checkbox in the system setting: if it is enabled, then this logging option is enabled and the corresponding event type should be included in the audit log when such an event occurs.

Hello,

This functionality is currently not available in the mobile application. It can lead to unintended data loss caused by accidental swipes, taps, or navigation actions.

Additionally, overriding crt.ClosePageRequest would not address all navigation scenarios. For example, it would not be triggered when users navigate away from the page using device-level system buttons or gesture-based navigation, which are common on mobile devices.

Hi Krzysztof,
Thanks for the explanation, but I think this doesn't fully explain the limitation. The web app has the same risk (accidental clicks, closed tabs, etc.), but `crt.CanDiscardUnsavedDataRequest` still allows a developer to skip the prompt when needed. The idea isn't to change the default behavior for users, it's to give developers the same option that already exists on web.
The point about system-level gestures and buttons is fair, but it only means the hook wouldn't cover 100% of cases. On web, closing the browser with an OS shortcut isn't covered either, and the hook is still useful for the navigation paths that do go through the app logic.
 

Hello,

Email signatures are configured individually for each mailbox and are not user-dependent by default. This means that if multiple users send emails from the same shared mailbox, the same signature will be applied regardless of which user sends the message.

At the moment, there is unfortunately no out-of-the-box functionality that allows signatures to be dynamically selected based on the user sending the email.

Regarding other ways of configuring emails. They can be sent using the "Send Email" element in a business process and dynamic case management. In such cas,e there are two possible ways regarding signatures:

• When an email is sent manually, the configured mailbox signature will be added automatically.
• When an email is sent automatically, the system sends the email template as configured, and the mailbox signature is not appended. If you would like a signature to appear in automatically sent emails, it should be included directly in the email template.

Hello,

This can be implemented using the MessageChannelService. To proceed, please import the Creatio DevKit SDK, choose the appropriate location in your code to handle subscription and unsubscription, and utilize the sdk.MessageChannelService accordingly.

Please note that this approach is supported starting from version 8.2.0 and later.

Basic subscription example:

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.HandleViewModelResumeRequest",
		handler: async function (request, next) {
			const messageChannelService = new sdk.MessageChannelService();

			request.$context.MySubscription = await messageChannelService.subscribe(
				"TestSender",
				(message) => console.log(message.body)
			);

			return next?.handle(request);
		}
	},
	{
		request: "crt.HandleViewModelPauseRequest",
		handler: async function (request, next) {
			const subscription = await request.$context.MySubscription;
			subscription.unsubscribe();

			return next?.handle(request);
		}
	}
]/**SCHEMA_HANDLERS*/

Basic sending example:

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.HandleViewModelInitRequest",
		handler: async (request, next) => {
			const messageChannelService = new sdk.MessageChannelService();

			const body = {
				// Some data
			};

			await messageChannelService.sendMessage(
				"TestSender",
				body,
				sdk.MessageChannelType.PTP
			);

			return next?.handle(request);
		}
	}
]/**SCHEMA_HANDLERS*/

Hi, thanks for the reply, but I believe your example is for the Web Creatio, while my question was about the mobile app :)

Just bumping this - any update would be appreciated. Thanks!

Hello,

Regarding the TS2304: Cannot find name 'setTimeout' error you’re encountering, there are two possible solutions:

• Install the @types/node package to include Node.js type definitions.
• Alternatively, you can use (globalThis as any).setTimeout() in place of setTimeout().

Either approach should resolve the issue.

Hi, thanks for the reply. I already had the @types/node package installed before, but the (globalThis as any).setTimeout workaround did the trick, thank you! Interestingly, it seems like the setTimeout function was added intentionally, since it doesn't exist in JavaScriptCore natively. However, I don't see clearTimeout there.