Hello,

Unfortunately, it's not possible to adjust the size of the folder panel at this time. However, we've registered this idea in our R&D team backlog for consideration and implementation in future application releases. 
 

Thank you for helping us to improve our product.
 

The folders scroll to the right when they get too long. You should be able to scroll right to get to the buttons if the folder name is too long.

Ah yes!  So they do ... 

Creatio's virtually invisible scroll bars strike again!  (I think that at some point all of our 250+ users have asked if the scroll bars can be made bigger ... difficult to use on a smaller laptop)

Thanks for pointing that out!

Rob Rudloff,

Yes - I only know this because of the same complaint from my users as well. It's so easy to miss.

Ryan

Yes, some UX improvement with these scroll bars is definitely needed :)

An easy way to accomplish what you're after is to: 

1. Create a collection parameter in the process
2. Populate the contacts from the ESQ into the collection parameter (see link below)
3. Then use normal subprocess for each contact in the collection

See here for how to add the results of the ESQ from the folder to a collection param: https://customerfx.com/article/working-with-collection-parameters-in-a-process-in-creatio/

Ryan

Ryan Farley,

Thanks Ryan. I'll give this a go now.

Ryan Farley,

I'm still struggling to get the result I'm after with the following code:

Parameters: 
- ContactFolderId (Guid)
- ContactsList (Collection)
    - ContactsList.ContactId
    - ContactsList.Name

var sectionName = "Contact";
var folderId = Get<Guid>("CommunityFolderId"); //"2d3c0306-1e43-4ba7-943b-a3d261b66897";

	var folderSchema = UserConnection.EntitySchemaManager.GetInstanceByName(sectionName + "Folder");
	var esq = new EntitySchemaQuery(folderSchema);
	var dataCol = esq.AddColumn("SearchData").Name;

	var folderEntity = esq.GetEntity(UserConnection, folderId);
	var folderData = folderEntity.GetBytesValue(dataCol);

	var serializedFilters = System.Text.Encoding.UTF8.GetString(folderData, 0, folderData.Length);
	var dataSourceFilters = Terrasoft.Common.Json.Json.Deserialize<Terrasoft.Nui.ServiceModel.DataContract.Filters>(serializedFilters);

	var folderFilters = dataSourceFilters.BuildEsqFilter(
		UserConnection.EntitySchemaManager.GetInstanceByName(sectionName).UId,
		UserConnection
	);

	var contactEsq = new EntitySchemaQuery(UserConnection.EntitySchemaManager, "Contact");
	contactEsq.AddColumn("Id");
	contactEsq.AddColumn("Name");
	contactEsq.Filters.Add(folderFilters);

	var contacts = contactEsq.GetEntityCollection(UserConnection);

	var list = Get<CompositeObjectList<CompositeObject>>("ContactsList");

	foreach (var contact in contacts)
	{
		var item = new CompositeObject();
		item["ContactId"] = contact.GetTypedColumnValue<string>("Id");
		item["Name"] = contact.GetTypedColumnValue<string>("Name");
		list.Add(item);
	}
return true;

When I run the process (passing 2d3c0306-1e43-4ba7-943b-a3d261b66897 into the ContactFolderId parameter, I'm getting an error saying:

Terrasoft.Common.ItemNotFoundException: Value "Id" was not found.
  at Terrasoft.Core.Entities.EntityColumnValueCollection.GetByName(String name)
  at Terrasoft.Core.Entities.Entity.InternalGetColumnValue(String valueName)
  at Terrasoft.Core.Entities.Entity.GetTypedColumnValue[TResult](String valueName)

I tried changing it to the following alternatives but I got the same error:

var item = new CompositeObject();
	item["ContactId"] = contact.GetTypedColumnValue<Guid>("Id");

and

var item = new CompositeObject();
	item["ContactId"] = contact.Get<Guid>("Id");

I feel like I'm missing something obvious somewhere.

You can set them up as dependent lookups by adding a Provinsi column to the Kota lookup and then just one simple business rule to filter. See https://customerfx.com/article/how-to-make-dependent-lookups-in-creatio-formerly-bpmonline/

Ryan

Ryan Farley,

ok the tutorial stated for an older version of creatio(formerly bpm'online) but how do you do it on the newer version where do i find the subcategory and category folders? is it in lookup folder?

Michael Fernando Handoyo,

Hi Michael, 

I updated the screenshots in the article to reflect the current version of Creatio. https://customerfx.com/article/how-to-make-dependent-lookups-in-creatio-formerly-bpmonline/

Ryan

Ryan Farley,

thank you, now it is easier to understand

Hello!

To set up something like this u will need:

At first create process which which will deactivate user depends on contact Id. I named it Deactivate sub.

1. 1. Add parameter "Contact" type "Id"

2. Setup read data element, to find the user connected to this contact.

3. Modify this user.

Then create a parent process that will run "Deactive sub" i named it Deactive.

1. 1. Add parameter collection and add inside it parameter type Id.

2. Add a subprocess parameter which is "Deactivate sub" and set process parameters.

Add a button to the page, and set it to run the process as it shown on the screenshot.

Use this to create a similar process for activating users. However, I recommend adding checking if a user exists for this contact.

Hello sprity,

If i understood you correctly, you want to control visibility state or togle mode of the folders tree. The handler you provided, well, is responsible for this logic.  

Here is an example of how you can do it:

Toggle mode (open if closed, close if open):
{ 
    request: 'crt.FolderTreeVisibleRequest', 
    params: { 
        folderTreeName: "FolderTree_blabla", 
        togglePanel: true 
    } 
}

Explicit visibility mode (always open or always close, regardless of current state):

{ 
    request: 'crt.FolderTreeVisibleRequest', 
    params: { 
        folderTreeName: "FolderTree_blabla", 
        visible: true  // or false to close 
    } 
}

As mentioned, this handler also saves the state to the user profile, meaning that when the page is reopened, the folder tree will be in the same state (open or closed) as it was before. If you'd prefer not to save the state in the profile, you can manually update the visibility attribute, like so:

{folder tree name}_visible => FolderTree_blabla_visible

Hope this helps! Let me know if i understood you correctly and if you have any questions let.

Yevhenii Grytsiuk,

Thank you for this Yevhenii. One of the more difficult parts of working with Freedom UI is the inability to dig into the out of the box code to see how to change the behavior. This was easy with classic, but for Freedom we have to dig through all the minified code to see if we get lucky finding what we are after. 
Until there's better documentation outlining what all the various requests are to handle, it would be great to have some sort of switch (like the IsDebug setting to enable debug mode) that just dumps all the fired requests to the console (and maybe include what object/component fired the request?) Not sure how reasonable that would be since it's likely quite a bit of stuff would show there, but might make it easier to see the requests that fire when some action is taken.

Ryan

Ryan Farley,

Sounds great to me. I will register your idea so that our r&d team hopefully would implement it.

Hello!

We checked your problem and unfortunately, there is no possibility to add a “Show folders” button item.

When you created a new section, you should have seen this popup:

Best regards,

Kate

Hello ,

You can Create Dynamic Folder based on their name . Please see the Attachment.

smit suthar,

Thanks Smith, I know to do this, but I have dozens of Lookups, for this reason I want to do a Dynamic Folder of LOOKUPS using the Starting as Using the Name (with my own prefix) or specifiing the package... But don't know how to get this filter (repeat for lookups)

Thanks again

Hello Julio.Falcon_Nodos,



You can create a dynamic folder and add "starts with" filtering for your prefix.

Anton, I have no access to object Code, I mean the internal code name of the lookup. What you get there is the name, localizable, not unique of the lookup, what I need to access is what you see in the image, below, and select "Code starts with Ndos" or "Package = Nodos.BirthdayGreeting"  to get all lookups created in the package in the folder.

Anton Starikov,

Anton, when I saw Name I refer to the internal code name, not to the localizable Name of the lookup, see my comment above. Thanks

Hello,

1. Please be informed that static folders functionality is not available in the custom section. We have created a corresponding query for our R&D team.

2. In the basic system version only the following section can have static folders:

employees

process library

process journal

lookups

system settings

As for the Contacts section, static folders are available with the "Marketing" product only.

Is this going to be added at some point? It seems dumb not to have it everywhere. 

Hello!

Unfortunately, this functionality is still not available. Our team is working on it, but we can not provide an ETA for it. 

Hi Julien,

Yes, the filter from folders will get appended to the filters you set for the section. You just need to add your filters in a filter group so they are properly applied as a whole, in addition to the folder filters - rather than just add the filters individually to the filters returned from callParent. For example:

getFilters: function() {
    var filters = this.callParent(arguments);

    // now create a filter group for your filters
    var customFilters = Ext.create("Terrasoft.FilterGroup");
    customFilters.logicalOperation = Terrasoft.LogicalOperatorType.AND;
    customFilters.add("ActiveFilter", 
        Terrasoft.createColumnFilterWithParameter(
            Terrasoft.ComparisonType.EQUAL, "Active", true
        )
    );
    customFilters.add("NoWidgetFilter", 
        Terrasoft.createColumnFilterWithParameter(
            Terrasoft.ComparisonType.NOT_EQUAL, "Type.Name", "Widget"
        )
    );

    // now add your filter group to the filters that get returned
    filters.add(customFilters);
    return filters;
}

It does work without a filter group if you're just adding a single condition, however, in your code you're "OR"ing all your new conditions together with the folder conditions. Using a separate group keeps it all grouped with the same conditions and will work as expected.

Ryan

Thank you Ryan !