Hi everyone,

I work daily with Creatio Freedom UI, both on web and mobile, and I noticed a few gaps between the two versions. I would like to suggest some improvements for the mobile app.

1. HTTP client for mobile (like sdk.HttpClientService on web)
On web, we can use sdk.HttpClientService to make HTTP requests inside Freedom UI. On mobile, this is not available. It would be great to have something similar for mobile too, at least when the app is online. This way, we could call external services directly from mobile scripts, using the current authenticated user session. Right now, we don't have a clean way to do this.

2. Basic context info for remote modules
It would help a lot if remote modules on mobile could easily access basic information, such as:
- current user
- current instance (URL/environment)
- user's time zone
- list of user's roles

This information is often needed for simple logic (for example, showing or hiding something based on role), but right now it is hard or impossible to get on mobile.

3. Real-time updates (WebSocket support) on mobile
Web Freedom UI can use WebSocket for real-time updates, but mobile does not support this yet. Adding WebSocket support to the mobile app would allow live updates (for example, notifications or data changes) without the need for constant manual refresh or polling.

All three points are about making the mobile app closer to the web version in terms of what developers can actually do. Right now, mobile feels more limited, and these gaps make some solutions harder to build or impossible without workarounds.

Has anyone else run into these limitations? I would be curious to hear if others need the same things, or if there are any workarounds I am missing.

Thanks!

I already raised this issue here: https://community.creatio.com/questions/creatio-mobile-discard-unsaved-…

On web, I can handle crt.CanDiscardUnsavedDataRequest to control when the "discard unsaved changes" popup appears. On mobile, this option doesn't exist, even though the same business logic often needs to work on both platforms. I understand the popup protects users from losing data by accident, and I'm not asking to remove that protection by default. I just want the option to override it when I decide it's needed, the same way I already can on web.

I know this wouldn't cover system-level gestures or hardware back buttons, since those happen outside the JS layer. That's also true on web (closing the tab isn't covered either), but the handler is still useful for everything that goes through crt.ClosePageRequest and similar in-app navigation. Adding this would bring mobile closer to feature parity with web, giving developers the same control they already have, without changing default behavior for users who don't need it.

Hello,
I would like to suggest adding a simple local key-value storage API to the Mobile Freedom UI SDK, similar to the standard web localStorage.
Currently, if a developer wants to store some technical data only on the device, scoped to the current user, there is no direct way to do it. The only supported option is to create a dedicated object with a relation to the user, add a filter on read, and configure access rights. This works, but it is more complex than needed, and the data is also written to the server database during synchronization, even if it is not really needed there.

A simple API like this would solve the problem:

localStorage.setItem('someSetting', { ... });
const value = localStorage.getItem('someSetting');

This would allow developers to store temporary or technical data directly on the device, without creating extra objects and without sending this data to the server.

Thank you for considering this idea!

I completely love the "Live Data Update" option for objects, one of my fav features to be added in Creatio. However, there are many cases where I want to be able to override that behavior and not have the live data update message sent to the UI. For example, if I am doing hundreds of adds/updates in a process, I likely don't want all those updates to go to the UI since that sort of thing can cause a lot of "flickering" and lag for the user that triggered the process as each message is received and the UI loads the data. Another case is where I am loading in a large amount of data from an external source via OData, the user context that the OData connection is using will receive the messages for all the adds/updates. The same for Excel imports, these should have Live Data Update off by default. There are many cases where the Live Data Update feature could cause a negative impact on the system and is unnecessary since it's not something that is for the user.

Please provide a way that the Live Data Update feature can be bypassed/disabled for single (or batch of) transactions for scenarios such as:

1. OData connections
2. Entity object adds/updates
3. Processes - Ideally, as an option for a single Add Data or Modify Data element, or at least as an option for the entire process
4. Excel imports (should be bypassed/disabled by default for these)

Thank you.

Ryan

It would be very useful in having good, consistent reporting to extend the current date macros available for doing so. Currently, if I want to filter to only include the rolling year's values, I have to put in a filter like Date >= Previous days <365> (and another for Date <= Today, if dates can be in the future) but this is quite clunky and not always the most clear (from memory, Previous Days does not include today's date, hence the greater than or equal to).

Even worse is that there is no real way (without doing something like creating a custom date object & maintaining the lookups to it for all objects with a date) to put a filter on to say "show me the last x complete months", with the partial workaround being similar to the above one, but this does not fulfil the "complete months" aspect of the filter.

I would propose the following would be very useful additions to the filtering setup used in folder config, BP read data steps, chart/metric config, list filtering config & other areas that filtering can be set up throughout Creatio:

High priority:

• Previous x for each of the dropdown's sections, so week, month, quarter, except for "Every year"
• Following x for each of the dropdown's sections as above

Nice to have:

• A checkbox/similar on Previous/Following macros to select whether the current day/week/month etc should be included, to both remove the slight ambiguity and give users more control without needing 2 date filters