Dear Puneet

You may have some considerations to treat contact names in Creatio:

1. 1.- Adjust the System Setting called: ContactFieldConverter (Order of first/last names) to Creatio complete Full Name based on the specified selection
2. 2.- You must select one of the provided choices to Creatio convert the Full name of the contact, see the image
3.  

3.- Have in consideration Contact field names are as follows (Code/Title):

• - Full name: Name
• - First Name: GivenName
• - Middle Name: MiddleName
• - Last Name: Surname
• 4.- Also, if you need to display some of the contact name fields, you need to add them in the Contacts_FormPage

Regards

Julio Falcón

Hello !

We're also adding API contacts
I don't fill in the GivenName or Surname when I create the contact, just the Name.
If I check the database, the GivenName and Surname have been filled in.

Julio Falcón (NoCode-Services),

Thanks Julio! My query is little different. I am sending GivenName and Surname using API. Creatio system is creating Full Name automatically using GivenName and Surname. In the contact section list I see Full Name populated; but GivenName and Surname are blank. How can I get GivenName and Surname to display on the section list? Screenshot:

Dear Puneet,

You must have in consideration to insert records in Creatio via OData or importing from excel, YOU MUST include all required fields, in this case Full Name is a required field, sou you need provide it in the API JSON.

Also if you provide this data in the JSON they must be inserted in Creatio. Can you share the JSON and Method you are using to insert on Creatio?

Try to use a tool like SQL Query to made a select to all records to see where are the data you 're inserting

Julio

I tried with this JSON and works

{
    "GivenName": "John",
    "MiddleName": "Fitzgerald",
    "Surname": "Kennedy",
    "BirthDate": "1990-01-01T15:24:00Z",
    "TypeId": "60733efc-f36b-1410-a883-16d83cab0980" 
}

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.

You can see an example of this in 8.2 on the new Web Analytics page. At the bottom there are two lists, a selected record on one filters the second one. This is all done with no code, however, I am not sure if that is only available in 8.2 or also in prior versions.

Yes, as Ryan says, it is possible to configure this in Freedom UI without code. You can see an example of this in the screenshot above - you select the Invoice items list, in your example, and apply a filter by page data, specifying the Invoice list data source.

This is definitely available in 8.1.3, and I believe it's been around since at least 8.1.0 but possibly longer.

Thank you very much Harvey and Ryan - it helped me a lot! 

Hello,

In order to fix this issue, turn on (or add) feature  "LoadAllColumnValuesInDuplicateSearch" and clear browser cache, then import should load all columns and work as expected.

Hello!

To get the data of a specific lookup you need to use the following request:

https://sitename.creatio.com/0/odata/Lookup(lookup_id)

If you want to get the content of such lookup, then you should make a request directly to the object which the lookup is connected to. For example:
https://110032169-demo.creatio.com/0/odata/Account(record_id)

Have a nice day!

Hello!

Unfortunately, this option is not available. We will register the idea with our development team so they can implement the option to import services.

Thank you for helping make Creatio better!

Best regards, 
Orkhan

Hello,

Basically, you can use advanced filter, where you can search for records using multiple keywords. As for the search component or global search, unfortunately the multiple search logic has not been implemented in there.

However, a task has already been registered in our R&D team to consider and implement such a feature in future releases.


Best regards,
Malika

Hello,

Currently, there is no possibility to work with chats in the mobile application. However, we have already registered a task for our R&D team to explore the possibility of implementing this functionality in future.

Thank you for your question!

Hello,

Any updates on the issue I'm currently facing?

Thanks

Hello!
 

This is basic system functionality—if a DCM has previously been used in requests (or other areas) and work has already been done in it, the system does not update it, as it may not be necessary for the user. Therefore, on the left side, you’ll see an icon that first prompts for confirmation to apply changes for the current request.

Regards,
Orkhan

Hello,

You can create a business process, using no-code tools that, when creating a contract, will check if a contract exists for that account and, if so, will notify the user. To do this, you may need elements such as:
Signal start, Read data, Modify data, Delete data and Pre-configured page
 

You can also configure a duplicate search process using the Find and merge duplicates element and a pre-configured deduplication rule.  Before setting up the element, ensure bulk duplicate search and global search features are configured, and the relevant section has active duplicate search rules.

Best regards,
Antonii.