Hello,
 

Could you please provide more technical details regarding your implementation? Are you using OpenID for authentication in Creatio? What specific issues have you encountered with your current setup when using ?autoOpenIdLogin=true in the link?

Have you considered an integration option through SSO with an automatic redirect setup? This would ensure that if the user is already authenticated on the IdP side, they will be automatically redirected back and logged into Creatio. 

With this setup, the user will be redirected to the IdP, logged in automatically if in current session he is logged in on Identity provider side, and then redirected back to the record page without login page.
 

(Steps for achieving this are outlined in the following article: SSO setup guide.

Please note that Step 5 – “Set SSO as the default option” is essential. The rest of the SSO setup instructions should be followed according to the latest version in the Creatio interface.)
 

If you’re using a cloud environment, please inform the support team of the need to enable auto-redirect.
 

We recommend testing this approach, and we hope it will be helpful!

Hello!

The root cause of the issue is that in addition to new records in the queue, users also see their own records that are in the works on the Agent desktop.

I would be happy to provide you with some information on the basic logic of work in the Agent desktop.

1) The selected contacts/roles in the [ Team ] tab can process the content of the queue from the agent desktop.
2) There are some changes when a user starts working with one of the records from the queue:
-  The record status changes to "In progress".
- The "Operator" column fills as a current contact.
- This record automatically disappears from all other users from the Agent desktop. This is done so that different users do not process the same record at the same time.
But the user who has this record in progress will continue to see this record until the conditions for processing this record are met and its status changes to "Processed".
-Then the record will disappear from the Agent desktop for all users, including the one who processed it.

So, we identified two reasons for this behavior:

1) The case status was changed in the case itself instead of the queue.
2) The case status was changed by another user.

To process the queue element correctly, you need to do all changes in the queue item itself.

Dear Iuliia,

You can manage the number of digits after the decimal point in the "How to display" section in the "Format":



Additionally, please make sure that the column itself in the object has the correct value type:



Have a great day!

Alina Yakovlieva,

thank you, it's very helpfull! 

Home pages don't typically have a record source, so there's no record context to use there. Unless you've connected some object type to the page, it doesn't have any context of a record to bind to. 

Can you describe more what you're trying to accomplish?

I don't have a data source connected, but I was hoping to use dates inputted as page parameters to filter a list.  The quick filters for dates are limited to columns on the object, but I was hoping to be able to filter the list by a date from a related object. 

I have the same need, but as I understand, it is not available yet

https://community.creatio.com/questions/how-have-date-range-filter-home…

Hello,

Please describe in detail how exactly this was implemented and provide screenshots of this button's settings.

Mira Dmitruk,

I used the 'Refresh data' action to trigger the 'crt.LoadDataRequest' and control the visibility of elements to switch between views (Calender and List).

#Code Logic in Handler

handlers: /**SCHEMA_HANDLERS*/[{
    request: "crt.LoadDataRequest",
    handler: async (request, next) => {

// Check if the data source name is "ListOrCalenderView"
if (request.dataSourceName === "ListOrCalenderView") {

   // Retrieve the current view mode (Calendar or List)
   const IsCalenderView = await request.$context.IsCalenderView;

   // If the current view is not Calendar (i.e., it's List View)
   if (IsCalenderView === false) {
       // Set the Button caption to "List View"
       request.$context.ListOrCalenderView_caption = "List View";
       request.$context.IsCalenderView = true;
 // Set the ListView flag to false since we are now in Calendar view
       request.$context.IsListView = false;

   } else {
  // If the current view is Calendar, switch to List View
  request.$context.ListOrCalenderView_caption = "Calender View";   request.$context.IsCalenderView = false;
  request.$context.IsListView = true;

 }

}

Regards,

Ajay K
 

Mira Dmitruk,

Do you have any alternative solutions besides switching between List and Calendar views?

Is this a classic page or Freedom UI?

Freedom

Anas Masa'deh,

I don't believe the ootb business rules allow for using an OR condition when the filter is based on page values. You'll likely need to filter via code. See https://customerfx.com/article/dynamically-filtering-a-lookup-on-a-creatio-freedom-ui-page/

Ryan

Have you tried adding a crt.LoadDataRequest handler to dump request.dataSourceName out to the console to see if you can determine the name of the dataSourceName attriubute the list uses - and that it does fire that request? I assume it triggers this request when it get's it's data - similar to how lookups do, see https://customerfx.com/article/dynamically-filtering-a-lookup-on-a-creatio-freedom-ui-page/

Assuming it does and once you know the name of the dataSourceName it uses for the request you could add the conditions.

Alternatively, I believe you can add the filter conditions directly in the datasource in the viewModelConfigDiff, but you'd need to know the attribute name used in that scenario as well. Something like https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/front-end-development/freedom-ui/data-sources/data-processing#title-2438-3

Ryan

Dear Anas, 
 
To achieve this functionality you can add a new boolean field (for example: IsActive) for users. This field will be updated by a business process that will start every hour.  

The business process can set the value of the IsActive field according to the filtration or you can create an object where you will specify the shifts that users have. 
 
I hope this helps. Have a great day! 

Alina Yakovlieva,

Thank you for responding!, 

could you please elaborate more about the steps that you provided? 

Greetings!
 

The issue is that if you remove the requirement for the "ReactionTimeUnit" and "SolutionTimeUnit" fields and leave them empty, you won’t be able to save the record. 
 

An error will occur:  
"Specified argument was out of the range of valid values. Parameter name: Index value is out of range"

These fields are mandatory because the entire out-of-the-box product logic of the Service relies on them being filled in.  

As a workaround, you can set default values for these fields, and everything will work fine.

Alternatively, you can build your application completely independent of the out-of-the-box functionality.

Regards,

Orkhan

Orkhan,

Much appreciated!